Playtest feedback & build tracking
Know exactly what your playtesters felt, build by build
Collect playtest feedback, group it into themes, and turn it into tasks tied to the exact build that players tested.
Takes you to sign-up.
- mira_k v0.14.2 Critical Save system
Lost 40 minutes of progress after quitting from the pause menu.
- dagnyr v0.14.2 High Controls
Dodge roll feels delayed on gamepad. Keyboard is fine.
- pau_vidal v0.14.2 Medium Onboarding
Did not realise I could pick up the lantern.
- nils_b v0.14.1 High Performance
Frame rate drops in the market district on an older GPU.
Old way, this way
Playtest feedback is useful only when you can trace it
Scattered
- Feedback arrives in Discord threads, form exports and screenshots in DMs.
- Nobody is sure which build a comment was about.
- Builds go out through Steam Playtest or itch.io, but what players felt stays elsewhere.
- Task boards track the work, not the reason behind it.
Connected to the build
- Every comment lands in one inbox with a build tag and a severity.
- Similar comments group into themes, so ten reports read as one problem.
- Each build shows its testers, sentiment and top issues side by side.
- A theme becomes a task that still points back to the feedback behind it.
Feedback inbox
Every comment arrives with its build and its weight
Each piece of tester feedback carries the build version, a severity and an automatic theme chip. Filter to the build you shipped last night and read what players actually said.
Lost 40 minutes of progress after quitting from the pause menu. Autosave never fired on level 3.
mira_k · status: new
Builds timeline
See how each build landed with testers
Compare versions by tester count, sentiment and top issues, so you can tell whether the last fix helped or only moved the problem.
Themes board
Turn clusters of feedback into tasks
Similar comments group into one theme. Convert the theme into a task and it keeps a link to every comment and the build it came from.
Onboarding
14 comments
Task: Add parry tutorial before boss 1
Save system
9 comments
Task: Fix autosave on level 3
Controls
7 comments
Task: Buffer dodge input on gamepad
How it works
From a tester's comment to a task, with the build attached
-
Ship
Tag the build
Create a build entry with its version, then point your testers at it from Steam, itch.io or your Discord.
-
Collect
Gather feedback in one inbox
Comments arrive with the build, a severity and an automatic theme, instead of living in chats and spreadsheets.
-
Group
Read themes, not noise
Similar comments cluster together so the loudest voice no longer decides what you fix first.
-
Act
Convert themes into tasks
Each task stays tied to the feedback and the build, so you can check the next release against it.
FAQ
Questions studios ask first
Does Playtestly deliver my game builds?
No. Keep using Steam Playtest, itch.io or your own links to hand out builds. Playtestly is where the feedback about those builds is collected, grouped and tracked.
Who is it for?
Indie developers and small studios who run playtests on Discord, Steam or itch.io and want their feedback in one place instead of forms, chats and screenshots.
How is it different from a task board?
Task boards track the work. Playtestly keeps what players felt, tags it to the build they tested, and lets you turn grouped feedback into tasks.
Can I try it before adding my own data?
Yes. A new workspace opens with demo feedback so you can see the inbox, builds timeline and themes board working before you add your own.
Turn playtester chaos into your next build.
Open a workspace, add your first build and see the feedback inbox with the demo rows already in it.
Takes you to sign-up.