What publishers actually look for in a playtest

What publishers actually look for in a playtest

FirstLook Team

FirstLook Team

· 5 min read

Pitching a publisher used to mean a deck, a vertical slice, and good vibes. Not anymore. Publishers are asking for playtest data earlier in the conversation, and they’re asking sharper questions about what’s in it. A pitch that lands today walks in with hard signals: who played the game, how long they stayed, what they did when they got bored, and whether they wishlisted it on their way out.

We’re making this post for studios pitching (or planning to pitch) to publishers, and it will cover what publishers actually look for when they open your playtest results. Not the surface-level metrics. The data points that close deals, or kill them.

Why publishers care about playtest data more than ever#

The market got harder. Steam ships hundreds of games a week, marketing budgets buy less, and the publishers funding indie deals are pickier about where the money goes. Vibes don’t make the model work anymore. Publishers want predictive data, and the best predictive data comes from real players playing your real game.

If you walk into a pitch with strong playtest data, you’ve already answered the publisher’s hardest question: will anyone actually play this? Three months of clean retention data is more convincing than any deck slide with impressive studio-background. Studios that show up with that data are the ones getting deals.

Retention curves are the single most important metric#

Open any publisher’s playtest evaluation and the first chart they look at is retention. D1, D7, D30. How many of the players who started your game came back the next day. The next week. The next month.

There’s a reason retention is the headline metric:

  • It predicts everything else. Wishlist conversion, monetization, word of mouth, and review scores all correlate with retention curves.
  • It’s hard to fake. You can puff up sign-up numbers or cherry-pick reviews. You can’t fake D7 retention without actually getting people to play the game again.
  • It tells the publisher how to model the deal. A 30% D7 retention game gets a different deal structure than a 12% one. Both can be successful, but they’re different deals.

If your retention numbers aren’t where you want them, the playtest is still useful: it tells you what to fix before you pitch. The studios that ship strongest spend months iterating on the retention curve before they ever take the deck out.

Sample quality matters as much as sample size#

A common mistake: studios run playtests with their Discord superfans, get glowing feedback, and walk into the pitch with shiny numbers. Publishers see through this immediately.

What publishers want to see:

  • Players who match your target audience, not just people who already love your studio
  • A sample size proportional to your claims. 50 superfans saying “this is amazing” isn’t a green light. 500 random qualified players showing 25% D7 retention is.
  • Geographic and platform diversity that reflects where you’d launch
  • A reproducible recruitment method, so the publisher knows it’s not a one-off

If you can’t tell the publisher where your players came from and how you qualified them, the data doesn’t count. The methodology is half of what they’re evaluating.

Sentiment without context is just noise#

“The game was fun.” “I really enjoyed it.” Comments like these aren’t useful to a publisher. They want to know exactly what players felt, when they felt it, and whether the feeling held up across sessions.

Useful qualitative data looks like this:

  • Sentiment tied to specific moments. “The combat clicked at minute 14, after the tutorial.” “Most players quit at the third boss.” “Players who got past hour 2 stayed for hour 5.”
  • Themes across sessions, not one-off quotes. Five players complaining about the same thing is signal. One player loving something is noise.
  • What players talk about unprompted. The features they mention without being asked are the features that landed.
  • Negative signal with patterns. Where players drop off, rage-quit, or get confused. Publishers want to know what would break the launch.

A publisher reads sentiment data as a map of your game’s emotional arc. The studios who present it that way win.

Wishlist intent and audience profile close the deal#

Retention proves players will play. Wishlist intent proves they’ll buy. Together, they close deals.

When you run a playtest, the players who finish should be asked: would you buy this game? Would you wishlist it on Steam? Would you recommend it to a friend? Conversion from “I played” to “I wishlisted” is the single best leading indicator of commercial success a publisher will see before launch.

Publishers also want a profile of who those buyers are. Demographics, platforms, genre preferences, where they spend their time online. The more detailed the audience picture, the easier it is for the publisher to model marketing spend.

This is where most studios under-deliver. They run the playtest, collect retention, gather sentiment, and stop. The wishlist conversion and audience profile get treated as nice-to-have. They’re not. They’re the data points that turn a “looks promising” meeting into a signed term sheet.

What a publisher-ready playtest dossier looks like#

If you’re showing up to publisher meetings with playtest data, this is what should be on the table:

  • Retention curves across D1, D7, D30, with cohorts broken down by acquisition channel
  • Sample methodology explaining who you tested with and why they’re representative
  • Sentiment themes tied to specific gameplay moments, not just star ratings
  • Wishlist conversion rates and how they tracked across the test window
  • Audience profile of the players who converted: demographics, platforms, spend behavior
  • What you changed between tests and how the metrics moved as a result

This is what FirstLook is built for. Studios on the platform run playtests through Discord with qualified player pools, collect feedback and sentiment in context, track wishlist conversion, and pull all of it into one player CRM. When you walk into a publisher meeting, you can hand them one document with all of the above. That’s the differentiated angle, and it’s why the studios pitching seriously in 2026 are running playtests through FirstLook.

If you’re thinking about how your next playtest should be structured for a publisher conversation, talk to us. We help studios build the dossier that closes the deal.