I've sat through too many demo debriefs where the team asks one big question, "So, what did you think?" It sounds friendly. It also produces the most useless feedback in game marketing. Players say it was cool. They say the art looked nice. They say they'd maybe play more. Then you launch, and the wishlist conversion is still soft because nobody bothered to ask the questions that actually predict whether a demo is doing its job.
A demo is not a graduation ceremony. It's a diagnostic tool. You are not trying to prove that strangers enjoyed 20 minutes with your game. You are trying to learn where curiosity turned into friction, where clarity broke, and whether the build created enough desire that someone wants more right now.
If your feedback form opens with a satisfaction question, you are inviting vague compliments. People are generous in surveys. Store pages are not.
"Did you like it?" is a lazy question
Players often want to be nice, especially if they got demo access from a festival, Discord, or your mailing list. So they round up. They tell you the movement felt good. They say the concept seems interesting. They throw in one bug report so the feedback sounds serious. Then they close the tab and never wishlist.
That gap matters. If someone tells you they liked the demo but will not take the smallest possible next step, the problem is not sentiment. The problem is motivation.
Balatro does not need a survey to ask whether the demo is fun. The signal is obvious. Players understand the run, feel the escalation quickly, and want another hand. A weaker demo can still get polite praise while failing all three of those tests.
Your form should be built around decisions and behavior, not vibes.
The three answers I actually want from demo players
If I only get three useful answers from a player, I want these:
- At what moment did your interest go up or down?
- What felt unclear in the first ten minutes?
- Would you wishlist or follow this game today? Why or why not?
That's the core of it. Not an essay about immersion. Not a five-star rating. Not "any other thoughts?" stretched into a research strategy.
The first question tells you where the demo earns attention or leaks it. The second tells you whether onboarding is doing its job. The third tells you whether the marketing promise is alive after contact with the product.
If someone says, "I was in at the opening shot, got confused by the upgrade screen, and still wouldn't wishlist because I don't know what makes the full game bigger than the demo," that is gold. You can act on that.
Ask about behavior before opinion
I like forms that force the player to reconstruct what actually happened.
Instead of asking whether pacing felt good, ask where they stopped. Instead of asking whether the game looked polished, ask which screen or mechanic made them hesitate. Instead of asking if they would recommend it, ask what they would tell a friend the game is.
Behavioral questions reduce flattery. They also surface contradictions fast. Someone might say they enjoyed the build, then admit they nearly quit during the tutorial room, skipped the crafting system, and could not tell whether the game was meant to be cozy, tactical, or punishing. That player is not ready to carry your marketing for you.
I'd rather get one honest answer about confusion than twenty "looks promising" responses.
The five-question form I keep coming back to
You do not need a giant Typeform. You need a short form that busy players will finish. Here's the version I recommend for most indie demos:
- How far did you get? Give simple choices like 5 minutes, 10 minutes, reached boss, finished demo.
- What moment grabbed you most? Force them to name a scene, mechanic, or surprise.
- Where did you feel friction or confusion? Ask for the exact screen, system, or enemy.
- What do you think the full game is offering beyond this demo? This tests whether your future promise is legible.
- Did you wishlist or follow the game? Yes, no, or not yet, then ask why.
Notice what is missing. No generic enjoyment score. No "how likely are you to recommend this to a friend" corporate survey junk. Most indie teams do not need a net promoter score. They need better judgment.
Segment the answers immediately
Once the responses come in, split players into three groups:
- Wishlisted now. Protect whatever made them convert. Those are your strongest marketing promises.
- Interested, not yet committed. This is the most important group. They usually reveal missing clarity, weak stakes, or a flat mid-demo section.
- Bounced. Painful, but useful. Their feedback often exposes the onboarding problem your core fans stopped noticing months ago.
Most teams obsess over the first group because it feels good. I care most about the middle group. They are telling you the sale almost happened.
If ten players say "I liked the combat but I still don't know what the long-term progression is," that is not random feedback noise. That is a messaging problem. Maybe the demo ends too early. Maybe the store page does not frame the metagame well. Maybe the UI hides the build variety. Different fixes, same root issue.
Use the survey to rewrite your store page too
Good demo feedback does not just fix the demo. It fixes the pitch around the demo.
If players consistently describe your game in the wrong way, your screenshots, trailer, and short description are probably part of the problem. I made this argument in my piece on Steam screenshot order. The store page should make the promise cleanly before the player touches the build. The demo should then confirm it.
When those two things drift apart, conversion drops. You get players expecting one rhythm and finding another. That is how you end up with feedback like "good game, not what I expected," which is one of the worst possible marketing outcomes.
What to ignore
Not all feedback deserves equal weight.
I mostly ignore feature requests from players who did not understand the current loop. I do not overreact to balance complaints from people who barely got past the opening. I definitely do not redesign a demo around the loudest Discord user who wants your game to become a different genre.
Look for repeated friction from the right players. If three different people say the same thing with different words, pay attention. If your best-fit audience keeps stumbling at the same point, fix it fast. If one person asks for online co-op in your single-player deckbuilder, smile and move on.
Fast iteration beats perfect research
You do not need an expensive user research stack to do this well. A form, a spreadsheet, and a few recorded sessions can take you far. What matters is turnaround speed. If the same onboarding issue appears five times this week, fix it this week.
This is where fast-building tools help. If you are prototyping variants in Chatforce, Construct, Godot, or Unity, you can test a rewritten opening, a clearer reward screen, or a stronger end-of-demo tease without turning the process into a month-long engineering project. The tool choice matters less than your willingness to run another clean test.
Too many teams gather feedback like they are collecting fossils. Interesting to look at, never used.
The blunt rule
Your demo feedback form should help you answer one question: why did this player convert, hesitate, or leave?
Everything else is secondary.
If your current survey starts with "Did you like it?" rewrite it today. Ask where the energy rose. Ask where clarity died. Ask whether the player took the next step. If you do that well, your next demo build will not just feel better. It will market better too.