Investment Pitches for Games

Summary

An investment pitch for a game asks someone to commit money, support or opportunity to the project. The pitch must sell more than the creative idea. It has to show that the team understands the product, audience, market, production plan, budget and next steps (Della Rocca and McAloon, Four Tips for Pitching Your Game, see source-game-pitching-to-publishers).

For student teams, the useful lesson is not “pretend to be a startup”. The useful lesson is discipline: know what you are making, who it is for, what evidence you have and what help you are asking for.

Key ideas

Pitch readiness

A team is more credible when it can show:

• a playable build
• a clear gameplay loop
• a specific target audience
• comparable games
• evidence of player interest
• production timeline
• budget or resource plan
• team roles and capacity
• clear next step after the meeting

Della Rocca links pitch readiness to traction. That can include the product itself, the team, the community, player metrics or timing in relation to launch (Della Rocca, It’s About Time, see source-game-pitching-to-publishers).

Pitch audience changes the evidence

Pitch audience	What they care about most	Weak pitch sign
Publisher	playable build, schedule, audience, market fit, production risk	”we need money to finish” with no traction
Investor	studio growth, return potential, team credibility, business model	only describing one game with no business case
Grant funder	cultural, regional, innovation or talent-development value	vague public benefit
Kickstarter backer	trust, rewards, delivery plan, community, visible progress	big promises with no delivery evidence
University panel	learning, scope, evidence, feasibility, reflective practice	feature list with no risk plan

Slides are not the pitch

A pitch deck is a tool. The pitch is the argument. Della Rocca warns that teams often jump to deck-making before product strategy, market analysis and evidence are strong enough (Della Rocca and McAloon, Four Tips for Pitching Your Game, see source-game-pitching-to-publishers).

A deck structure for first-time teams

Rami Ismail’s free pitch-deck template, written for developers on their first or second game, orders a publisher pitch as five questions: Who is making it, which opportunity they saw, what they will make, how the funder can benefit, and what the team needs (Ismail, Pitch Template, see source-rami-ismail-pitch-deck-template).

Section	What it has to prove
Who	The team, as it would be if funded, can ship. Shipped games count even if they were not hits.
Saw which opportunity	Why this team is making this game (the “artistic why”) and what market opening it fills (the “business why”).
To make what	The Dream (the final game, shown with key art and mock-ups), the Proof (what already exists, with nothing speculative) and the Work (how the loop, systems or story deliver the promise).
How can you benefit	Comparable games that show a real market and justify the budget.
What do we need	A realistic timeline and budget, then a summary slide with contact details.

Ismail explains the order. The template “assumes your biggest weakness is relevant experience”, so it opens with the team. More experienced teams can move the team section later. He advises keeping the budget at the end so that the funder has seen the whole offer before thinking about money. He also frames the whole deck as selling “the business case – not the game” (Ismail, Pitch Template, see source-rami-ismail-pitch-deck-template).

First-time pitcher red flags

Ismail reports that publishers named three common red flags in pitches: failing to establish credibility, failing to show the game’s strengths, and the lack of a “realistic production mindset” (Ismail, Pitch Template, see source-rami-ismail-pitch-deck-template). His template’s guidance slides point to specific mistakes behind those red flags:

• Asking for too little. “If you end up too high – there’s room to negotiate. If you end up too low, you’ll fail the pitch immediately.” In his view, a low budget suggests the team does not understand what the game costs to make.
• Unrealistic comparables. “Nobody cares that Minecraft & Among Us made a lot of money. They’re not comparables.” He suggests three comparables, scaled to the budget, which the game should clearly beat, compete with, and believably reach.
• Speculative proof. The Proof slides should show only what exists. Thin proof tends to produce “come back later” rather than a deal.
• Selling the current build instead of the final game. Mock-ups of the target game sell the Dream better than screenshots of an early prototype.
• Padding with numbers. “1 billion characters is remarkable. 12 levels is not.”
• Unrealistic timelines. He suggests that 9 months to 2.5 years is generally viable, that most competitive indie games need 1.5–2 years after signing, and that a 30% margin per milestone tends to be safe.
• A deck that needs its presenter. Publishers often read the deck before any meeting, so “Your presentation should work without you.”

These are one consultant’s heuristics from 2023, not industry standards (see the evidence limits in source-rami-ismail-pitch-deck-template). They are still useful as a checklist that students can apply to their own decks.

The short meeting problem

If a meeting is 30 minutes, do not spend 30 minutes talking through slides. A short pitch leaves room for questions, relationship building and next actions. The team should leave knowing what happens next.

In practice

For a 10-slide student pitch deck:

Slide	Job
1	Game title, image, one-sentence hook
2	Player fantasy and target audience
3	Core loop and what the player does minute to minute
4	What is already playable
5	Evidence: playtest notes, wishlists, survey response, festival feedback or tutor feedback
6	Comparables and market position
7	Team roles and relevant skills
8	Production timeline and next milestone
9	Budget, resource need or support request
10	What happens next

If a slide does not help the listener decide, cut it.

This student deck covers the same ground as Ismail’s publisher template but in a different order. It places the team late (slide 7), whereas Ismail leads with the team for inexperienced developers. Both end with the ask. Arguably, a student panel already knows the team, so leading with the game makes sense there. For an external publisher, Ismail’s order puts the team’s biggest perceived risk first and answers it early (Ismail, Pitch Template, see source-rami-ismail-pitch-deck-template).

Once a deck is ready, Ismail’s outreach advice is to set aside your five favourite publishers, email every other publisher on your target platforms, and “let them filter you”. He recommends a short email titled “Game Title – Looking for Publisher” that links to a playable build or trailer and a hosted copy of the deck (Ismail, Pitch Template, see source-rami-ismail-pitch-deck-template).

Evidence

Della Rocca argues that funders expect business thinking alongside enthusiasm. His advice stresses product strategy, market research, playable evidence, player interest, budget, team and next steps (Della Rocca and McAloon, Four Tips for Pitching Your Game, see source-game-pitching-to-publishers).

His timing article says publisher pitching works best when there is enough traction to make success credible and enough time before launch for the publisher to contribute. He treats traction as a mix of product, production, team, community and metrics (Della Rocca, It’s About Time, see source-game-pitching-to-publishers).

Rami Ismail’s pitch template frames a first-time developer pitch as a business case, with attention to team credibility and execution rather than only the idea. He describes refining it with feedback from publishers and developers, and he designs it to “generate interest and further conversation” rather than to close a deal in the room (Ismail, Pitch Template, see source-rami-ismail-pitch-deck-template; also covered by Obedkov, Game World Observer, see source-game-pitching-to-publishers). This is practitioner advice: the numeric rules of thumb are his heuristics, not measured findings.

Kickstarter’s official guidance shows that crowdfunding pitches also need preparation, audience building, preview feedback, budget realism and delivery planning (Kickstarter, Creator Guides, see source-kickstarter-creator-guides).

Practice

Take your current project and write a 60-second pitch using this structure:

1. This is a game for…
2. The player does…
3. The hook is…
4. We have already proved…
5. We need…
6. The next step is…

Success test:

• the listener can repeat the hook
• the ask is specific
• the evidence is visible
• the pitch does not rely on “it will be fun” as proof

Extension:

• write a second version for a grant panel and compare what changes.

Self-test

1. What is the difference between a game idea and a game pitch?
2. Why is a playable build useful in a funding pitch?
3. Give two examples of player-interest evidence.
4. Why should a pitch include a production timeline?
5. Why might a Kickstarter pitch need different evidence from a publisher pitch?

Answers

1. A game idea explains what the game could be. A pitch argues why someone should support it.
2. It lets the funder test the loop and lowers the risk that the team is only describing a fantasy.
3. Wishlists, playtest data, Discord activity, newsletter signups, trailer response, festival feedback or survey responses.
4. It shows whether the team understands scope, milestones and delivery risk.
5. Backers need trust, rewards and delivery clarity. Publishers need commercial fit, production plan and deal potential.

Implications

• Pitching should start with evidence, not slides.
• A strong vertical slice supports the pitch because it proves the loop, tone and production capacity.
• A weak business model canvas will usually become a weak pitch.
• Credibility, the game’s strengths and a realistic production plan are the three things a first-time pitch must make visible. Ismail’s red flags suggest that under-asking and inflated comparables damage credibility more than an ambitious but well-argued budget does.
• The most honest pitch for many student projects is not “this will make money”. It is “this is feasible, well-scoped and valuable as portfolio or research work”.

Open questions

• How much commercial evidence should be required in non-commercial assessment pitches?
• Should students pitch to different audiences in the same assignment to learn how evidence changes?

Related

business-model-canvas-for-games | publishing-and-funding | game-design-documentation | vertical-slice | game-marketing-fundamentals | game-industry-realities | source-rami-ismail-pitch-deck-template | source-game-pitching-to-publishers