Direct answer — What do game publishers look for in a vertical slice before funding a game? A game publisher funds a vertical slice when it proves three things in about ten minutes: the core loop is fun and works end to end, the game has something a buyer can sell, and this team can finish it on the budget and schedule it is asking for. The build has to look and play like the final game, with no placeholders, soft locks or “imagine this part working” moments. Around it, publishers expect a costed budget, a milestone plan with named deliverables, and any evidence that players already want the game.

A vertical slice is a short, final-quality section of a game: one level or one session that shows every system at shipping quality, rather than a wide but rough prototype. It is the single most important asset in a game pitch to a publisher, and the one studios most often send too early. This guide covers the vertical slice game publisher teams expect to see, the budget and milestones behind it, and the mistakes that end the meeting.

I have spent more than 20 years on the commercial side of games. At SFR, I ran the mobile games unit and negotiated with the publishers and developers whose games we distributed; at Gameloft and Blacknut, I worked on partnerships with platforms, telcos and studios. On the receiving side of a pitch, the decision forms fast, and it rarely turns on the deck.

Key Takeaways

  • The build decides the meeting. Finji’s Rebekah Saltsman aims for “a complete playthrough experience in 7 to 13 minutes”; plan for evaluators to judge yours in that window.
  • Show the whole core loop working, not a tour of separate systems. Alex Beck, who pitched more than 500 times to publishers in 2025, says this is where “most pitches break.”
  • A budget is not optional. It is how a publisher checks that you understand what finishing the game costs.
  • Traction is any proof that someone other than the team wants the game: wishlists, playtest results, community, or a previous game’s numbers.

What the first ten minutes of the build must prove

Publishers review many builds, so the first minutes do the work. Alex Beck’s 2026 analysis of his firm’s pitches says the slice is judged “the second the game loads” and gives a simple bar: it “needs to look, feel, and play like the actual final game.” His quality test is useful: the slice should be something you would be comfortable charging money for as one tenth of your full game.

In my experience, a strong slice answers four questions without anyone in the room explaining it:

  1. Is it fun in the hand? David Logan, CEO of publisher Akupara Games, advises studios to “prioritize fun gameplay over graphics.” Start the build in the core loop, not in a cinematic or a menu.
  2. Does the loop close? Beck’s plea is to “show the entire primary loop working. Actually working, end to end.” A combat system next to a crafting screen is not a loop; earning, spending and progressing is.
  3. What makes it special? Competent is not enough. Beck notes that competent slices often do not get funded and that the ones that do usually carry an “X factor.” Make the unique selling point visible within minutes.
  4. Can a stranger play it alone? Beck’s team found that “accompanying tutorial documents just don’t work.” The game has to teach itself, and the basics (a settings menu, stable performance) have to be there.

For a mobile game, the same logic applies with one addition: publishers will ask how the slice monetises and retains. Logan still advises studios to “prioritize your game mechanics over your game’s monetization model” in the pitch itself; the economy belongs in the follow-up, once the fun is established.

Budget and milestones: the slides that decide whether you can ship

The playable build gets interest; the budget and milestone plan turn it into an offer. Logan is direct: having a project budget is “mandatory for a publisher to know the scope of what’s needed in terms of funding.” He recommends itemising monthly costs per team member, plus facilities, hardware, software and marketing.

Publishers read that budget as a test of production credibility. John Young, then VP of business development at Perfect World, described the moment every funder dreads: “we’re $4 million into a $3 million project,” and deciding whether to keep paying. A milestone plan with named deliverables, from slice to alpha, beta, certification and launch, is your answer to that fear. Each milestone becomes a payment trigger in the contract, so a vague roadmap costs you twice: in the meeting and in the deal.

Size the ask to the publisher. Sergei Klimov, writing in Simon Carless’s GameDiscoverCo newsletter about his studio’s own raise, pitched €400k to reach Early Access, another €400k for the Early Access year and €200k for six months of live operations. Three companies then asked whether the team could deliver a “bigger everything” with €2M or €5M. Prepare a version of the plan for a larger budget, because the question will come.

This is the step where I work with studios before any introduction: when we prepare your game for publishers, we tighten the pitch, cost the remaining development and milestones, and agree which rights you will offer.

Free guideThe Publisher Deal Kit.Get the free kit

Traction signals publishers actually weigh

A publisher is buying a forecast, and traction makes the forecast less of a guess. Logan calls Steam wishlists “vital to getting sales on the game’s launch.” Young asked teams to lead with track record: “Our team did X units/DAU/CCU on our previous projects.”

Useful signals, in rough order of how much they reassure a buyer:

  • Numbers from a previous game by the same team, with the platform and period.
  • Store interest: wishlists and their growth, or follower and announcement engagement. Klimov’s team tested its sequel concept with a Steam announcement that drew more than 1,100 likes before pitching.
  • Playtest evidence: completion, session length and what players said, from organised tests rather than friends.
  • Audience data: Klimov notes that publishers looked past the product to the audience, including where it was located.

No traction is not a disqualifier for a strong slice, but invented or inflated figures are. A publisher will check them during due diligence.

The game pitch mistakes that end a meeting

Mistake Why it kills the pitch Source
Placeholder assets and unfinished UI “Placeholder assets scream ‘not ready’” Alex Beck
Systems shown in pieces, loop never closes The publisher cannot judge the game it would fund Alex Beck
Soft locks, crashes, poor performance “Nothing kills momentum faster than a soft lock that forces the evaluator to restart” Alex Beck
Wrong publisher for the platform “Don’t show a mobile-only publisher your console-only game” David Logan
Thirty minutes of lore “That’s boring trash” Rebekah Saltsman
Selling a comparable game better than yours “Don’t sell someone else’s game better than you sell your own” Rebekah Saltsman
Long, convoluted outreach “Convoluted pitches make life more difficult for us” John Young
No budget, or one that collapses under a follow-up question The publisher cannot size the deal or trust the schedule David Logan

Beck’s fix for the build-side mistakes is mechanical: play through the slice at least ten times yourself, then hand it to someone who has never seen it. The deck-side mistakes need one rule: answer the publisher’s questions before they ask them.

Getting the meeting is a separate job. Shortlisting and screening publishers is covered in my guide on how to find a game publisher that fits your indie game, and if you are still deciding whether you need one at all, start with the publisher vs self-publishing decision framework.

What we could not verify

We looked for a public, dated dataset on the share of pitches that turn into funded deals, on the typical cost of producing a vertical slice, and on the wishlist or playtest thresholds publishers use as a cut-off. The only conversion figure we found is one studio’s own experience: Klimov reports 16 approaches leading to 4 discussions. No source publishes the others with a method we could check, so this article gives no benchmark for them.

Before you send the build

Treat the slice as a product, not a demo: ten minutes, one closed loop, no placeholders, tested by strangers. Put a costed budget and a milestone plan behind it, and lead with whatever evidence you have that players want the game. When offers come, read them for more than the advance: the recoup clause and the publisher contract red flags decide what the deal is worth.

Publisher search fees are published on the offer page: EUR 2,000 for preparation, EUR 1,500 per month over an initial 3-month mandate, and a 5% success fee on funding attributable to the mandate and received by the studio, with the retainers credited against it. Game Growth Advisor takes no fees from publishers.

Want a buyer’s read on your slice before publishers see it? Book a free 30-min call and bring your build or gameplay video, your pitch deck, your funding target and your timeline.