The Twelve-Slide Publisher Pitch: What Goes on Each Slide and Why

You have twenty minutes in a video call. The publisher's producer has your deck open in another tab and will give it roughly three minutes of real attention before the call, probably while eating lunch. In that window they are answering three questions: what is this game, can this team finish it, and can we sell it? Everything else in your deck — the lore, the mood board, the clever subsystem you are proud of — is read only if those three land first.

Most indie pitch decks fail not because the game is bad but because the deck is organised like a design document: it explains the world before it shows the verb. Here is a build order that answers the three questions in the order they get asked, plus the attachments and follow-ups that decide whether you get a second meeting.

What a pitch is actually for

A first pitch does not win a deal. It wins the next conversation. That changes what goes in: you are not trying to be complete, you are trying to be impossible to misunderstand and easy to forward.

That second part matters more than people expect. The person you pitch to usually cannot sign anything alone. They take your deck into a green-light meeting and repeat your game from memory. If your pitch cannot survive being re-told by a tired stranger in ninety seconds, it will not survive the funnel. Write every slide so it can be quoted.

The twelve slides, in order

Twelve to fifteen slides is enough. One idea per slide, big type, no paragraphs.

#	Slide	Question it answers	Common failure
1	Title + key art + one-liner	What is this?	Logo with no game in sight
2	The hook	Why would anyone care?	A genre label, not a hook
3	Core loop	What do I do with my hands?	Described in nouns, not verbs
4	Gameplay in motion	Does it look good yet?	A static screenshot
5	The twist system	What is yours and not borrowed?	Three systems instead of one
6	Player fantasy / tone	Who is this for?	"Everyone who likes fun games"
7	Comparables	Where does it sit on a shelf?	Only billion-selling outliers
8	Audience + market read	Who buys it?	Genre revenue totals with no source
9	Scope + content plan	How big is it really?	Hours promised, not content listed
10	Team	Can you finish?	Job titles instead of shipped work
11	Status + roadmap	Where are you now?	A plan with no dates
12	The ask	What do you want?	No number, no milestones

Slide 2: the hook has a shape

A hook is a sentence that creates a question in the reader's head. The reliable shape is familiar frame + specific deviation:

• "A farming sim where every crop you plant permanently rewrites the island's weather."
• "A deckbuilder played entirely with one hand on a rotary phone dial."

Notice both are concrete and both are testable — you can imagine the screen. Compare with "an atmospheric roguelite exploring themes of memory and loss," which creates no question and no image.

Write five hooks, read them aloud, delete the ones that need a second sentence to make sense.

Slide 4: motion beats everything

If you have any playable build at all, a looping GIF of five to eight seconds does more than any amount of copy. Pick the single clearest moment of your core loop — not a montage, not a cutscene. One readable action, one readable consequence. If the clip needs a caption explaining what just happened, it is the wrong clip.

Decks get read offline, so put a static frame under every embedded GIF and link a 30-second gameplay video that needs no login to watch.

Slide 9: scope as a list, not a promise

"Twenty hours of gameplay" is unverifiable and everyone knows it. A content list is checkable:

• 4 biomes, 6–8 handcrafted levels each
• 22 enemy types, 5 of them bosses
• 60 items across 4 rarity tiers
• ~9,000 words of dialogue, 0 full voice-over

That list tells a producer more about your budget than a number of hours ever could, and it signals that you have costed the game rather than guessed at it. If your content list and your timeline disagree, they will spot it — so reconcile them before the call.

Slide 12: ask for something specific

Name the money, the duration, and what the money buys. "We are seeking funding to complete the game" is not an ask. "£180k over 14 months to take the vertical slice to a shippable PC version, with three milestones: content-complete alpha at month 7, beta at month 11, gold at month 14" is an ask — and it invites a counter-offer instead of a polite no.

If you genuinely do not know your number, you are not ready to pitch; you are ready to build a budget.

The three attachments

The deck is the trailer. The attachments are the film.

1. A playable build. Ten to fifteen minutes long, no launcher, no build instructions longer than one line, works on a mid-range laptop. Include a skip-to-the-good-part option; nobody at a publisher will grind your tutorial.
2. A one-pager. Single PDF: title, hook, two screenshots, platforms, target date, team, contact. This is the thing that gets forwarded, not the deck.
3. A 60–90 second video. Gameplay first, logo last. Captions burned in, because it will be watched muted.

Keep all three current. A deck that says "prototype" and a build that is clearly a vertical slice makes you look disorganised, not modest.

What they will ask afterwards

Publishers run roughly the same due-diligence list. Having these ready turns a two-week stall into a same-day reply:

• Current budget breakdown by discipline and month
• Team structure: who is full-time, who is contract, who is unpaid
• IP ownership and any existing agreements, including engine and middleware licences
• Platform plans and any existing platform relationships
• Wishlist or community numbers to date, with the honest context
• Risk list and mitigations
• What happens to the project if they say no

That last question is the one people fumble. The right answer is specific — a smaller version, a longer timeline, another funding route — because a team with an alternative can negotiate.

Tailoring, tracking and not pitching into the void

Blanket-sending one deck to forty publishers reads exactly as it is. Before each pitch, spend thirty minutes on that publisher's last two years of releases and check three things: do they ship your genre, at your budget tier, in your territory. If any answer is no, you are wasting both calendars.

Then track the pipeline like production work, because it is: contact, date pitched, deck version sent, response, follow-up due. Five pitches with notes beat forty without. If you keep your design documentation in GameDesignerX, the Pitch Maker module pulls the hook, content list and milestones straight from the documents you already maintain, so the deck stays in sync when scope changes mid-funnel — and the task board is a perfectly good place to park those follow-up dates.

A rehearsal that actually helps

Two days before the call, do this once:

1. Pitch the game in 45 seconds to someone who does not play games. If they can repeat it back, the hook works.
2. Pitch it in 10 minutes to a developer friend, then ask them to list every number you stated. Numbers you cannot defend should leave the deck.
3. Write the three questions you are most afraid of being asked, and script the answers. It will be scope, team capacity, and why the game will be noticed.

The honest closing note

Publishers say no far more often than yes, usually for reasons that have nothing to do with your craft: the slate is full, the genre is cold for them this year, the timing clashes with another title. A rejection with a reason is useful data — log it and move to the next name on the list.

What you control is whether your game is legible in three minutes, whether your numbers survive scrutiny, and whether the person who liked it can sell it to colleagues without you in the room. Build the deck for that person.