How to Pitch a Game to a Publisher: Build, Deck, Budget and Ask
Assemble a publisher pitch around a clear game, a representative build, a credible production plan and a specific commercial request.
Production notes / Page 6
Earlier guides from the Kioto production library. Use the topic rail to narrow the decision or return to the newest entries.
Return to the latest articlesEarlier field notes
66 published articles. Every guide, briefing and analysis states its scope and links to the next useful decision. Editorial images are illustrative, not documentary evidence of staff, premises or client work.
Assemble a publisher pitch around a clear game, a representative build, a credible production plan and a specific commercial request.
Assess code, content, controls, platform services, performance and certification before turning a console release into a fixed commitment.
Choose the right test coverage for each production stage, from focused prototype feedback through regression, compatibility and release readiness.
Plan an external art stream that protects the visual target, engine constraints, review capacity, source files and final integration.
Design a game team around decisions and ownership rather than a generic role list, then scale it without multiplying coordination cost.
A practical budget structure for team burn, external production, tools, contingency, platform work and cash timing, with an editable CSV template.
Build a production timeline from dependencies, review capacity and milestone evidence, then show which assumptions can move the release range.
Estimate a game with transparent scope, team, schedule and risk assumptions instead of a headline price that hides the production model.
Map each stage of game development to a decision, a reviewable build and the evidence needed to commit more people, time and money.
A producer-focused guide to choosing an outsourcing model, defining ownership, planning onboarding, controlling delivery risk and designing a clean hand-off.