How to Pitch Your Game to a Publisher

Pitching a game to a publisher is a specific skill, and most pitches fail by leading with enthusiasm rather than the things publishers actually evaluate: whether the game is compelling, whether the team can deliver it, and whether there's a market for it. A strong pitch quickly conveys the hook, demonstrates credibility, and shows market understanding, addressing what publishers care about rather than just expressing how much you love your game.

Lead with the hook and prove you can deliver

Publishers see many pitches and decide quickly, which means a strong pitch has to immediately convey what's compelling about your game—the hook, the thing that makes it interesting and distinctive, the reason a player would want it—because if the publisher doesn't quickly grasp why the game is appealing, the pitch is lost regardless of its other merits. Leading with the hook, communicating clearly and compellingly what makes the game special in a way that's immediately graspable, is the foundation, because it answers the publisher's first question: is this game interesting? But conveying that the game is compelling isn't enough, because publishers are also evaluating risk, which means the pitch must demonstrate credibility—that this is a real, achievable project from a team capable of delivering it. A compelling game concept from a team that can't credibly execute it is not investable, so the pitch needs to show evidence of capability: a quality prototype or vertical slice that proves the game is real and the team can build it, a track record or demonstrated competence, a credible plan. Publishers are betting on the team's ability to deliver as much as on the game's appeal, so demonstrating that you can actually make this game—through tangible evidence of progress and capability—is essential to a pitch that lands. The combination of leading with a compelling hook (the game is interesting) and demonstrating credibility (the team can deliver it) addresses the publisher's core evaluation: is this a compelling game that this team can actually make?

Showing market understanding completes a pitch that addresses what publishers actually evaluate. Beyond the game being compelling and the team being capable, publishers are evaluating whether the game can succeed in the market, which means a strong pitch demonstrates market understanding—that you know who the game is for, why they'll want it, and how it fits the market—rather than assuming the game will simply find an audience. A pitch that shows you understand your game's audience, its position in the market, its comparables and how it differs, and the realistic commercial case for it demonstrates the business awareness publishers need to see, because they're making a commercial investment and want evidence that you understand the commercial reality, not just the creative vision. Showing market understanding—who the game is for, why there's an audience, how it fits and stands out in the market—reassures the publisher that you're a credible commercial partner who grasps that making a great game is necessary but not sufficient, that it also has to reach and resonate with a market, and that you understand that market. A pitch that conveys a compelling game, demonstrates the team's capability to deliver it, and shows clear market understanding addresses all three of the publisher's core questions—is the game compelling, can the team deliver it, and can it succeed commercially—which is what a strong pitch must do. The common failures—leading with enthusiasm rather than the hook, failing to demonstrate credibility and capability, and ignoring the market—each leave one of these questions unanswered, undermining the pitch. The strong pitch, by contrast, quickly conveys the compelling hook (the game is interesting), demonstrates credibility through tangible evidence (the team can deliver), and shows market understanding (it can succeed commercially), addressing what publishers actually evaluate rather than just expressing how much you love the game. Mastering this—understanding that publishers evaluate the game's appeal, the team's capability, and the market opportunity, and building a pitch that addresses all three compellingly—is what turns a pitch from an expression of enthusiasm into a persuasive case that gets publishers interested, which is the difference between pitches that land and pitches that get politely declined.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

A strong publisher pitch leads with the compelling hook, demonstrates the team can deliver through tangible evidence, and shows you understand the market. Address what publishers evaluate—appeal, capability, opportunity—not just your enthusiasm.