How to Pitch Your Game to a Publisher

Lead with a playable build or a killer gameplay capture — publishers fund what they can feel. Around it: a short deck with the hook in one line, comparable titles with real sales logic, your scope, budget, timeline, and what you specifically need. Pitch genre-fit publishers in batches and expect silence as the median response. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

The build is the pitch

Publisher scouts see dozens of decks weekly; the projects that advance are the ones whose build proved the hook in five minutes. A vertical slice that demonstrates the loop's feel beats any document — polish the first five minutes of it obsessively, because that's all most scouts play.

No build yet? A tight capture of real gameplay is second-best. Concept art and design docs alone signal 'too early' to almost everyone funding at indie scale.

The deck answers their five questions fast

What is it (one line plus one image), why will it sell (genre, audience, three comps with honest reasoning), who are you (shipped work, even jams), what's the ask (amount, what it buys, timeline), and where is it now (build status, wishlists if live). Ten slides, readable in five minutes, numbers you can defend.

Comps deserve care: 'like Hollow Knight' invites a comparison you'll lose. 'Sits between X and Y, whose audiences overlap ours on these tags' shows you understand the market you're asking them to fund.

Run it as outreach, not a moonshot

Build a list of 15-30 publishers active in your genre at your budget scale — their catalogs tell you. Warm channels (events, showcase days, intros from their shipped devs) outperform cold email heavily, but well-aimed cold pitches with builds do land.

Track sends, follow up once after two weeks, and treat every call's questions as free market research. Most funded indies pitched many publishers across months; rejection is workflow, not verdict.

Protect the downside first

Indie game revenue is lumpy and unpredictable, and most advice quietly assumes a hit. Plan for the median outcome instead: a launch that earns modestly and grows slowly. Keep fixed costs low, keep some runway, and make deals you could live with if the game sells a tenth of your hopes.

None of this is pessimism — it's what lets you take real creative risks. A developer who can afford to miss is a developer who can afford to be interesting.

Get unglamorous things in writing

Splits, deadlines, deliverables, who owns what if the project dies — the awkward conversations are dramatically cheaper before money shows up. A one-page agreement between friends feels like overkill right up until it's the only thing that saves the friendship.

You rarely need a lawyer for a first project, but you do need clarity. Write down what was agreed, date it, and make sure everyone has a copy. Future-you will be grateful.

The quiet work that protects all of this

Everything in this post gets undone by an unstable build. A great store page, a clever marketing beat, a perfect jam entry — none of it survives 'crashed twice, refunded'. Stability isn't a feature players praise, but it's the floor everything else stands on.

Give yourself visibility before you need it: crash reports with stack traces, a simple way for players to flag issues from inside the game, and a habit of fixing the top recurring error before adding anything new.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Make the guesses cheap, the agreements written, and the runway longer than the plan.