Publisher Milestones in Game Development

In funded game development, publishers secure their investments by tying financial payouts to specific, pre-negotiated milestones. This article outlines the typical milestone expectations publishers have for developers, from the initial greenlight to the final gold master, explaining what deliverables are required at each stage of the production pipeline.

Why Publishers Use Milestones

Milestones act as a roadmap for the development process and serve as risk management tools for publishers. Instead of providing the entire budget upfront, publishers release funding in installments (milestone payments) only when the developer successfully delivers verified, working builds that meet predefined criteria.

Typical Milestone Stages and Expectations

While every contract is unique, the game industry follows a highly standardized sequence of milestones.

1. Kickoff and Prototype (Pre-Production)

This initial stage establishes the project’s foundation. Publishers expect the developer to prove the core concept is viable. * Key Deliverables: Updated Game Design Document (GDD), production schedule, technical architecture plan, and a greybox prototype testing the core gameplay loop. * Publisher Focus: Verifying that the core gameplay is fun and that the team has a realistic plan to build the full game.

2. Vertical Slice (First Playable)

The Vertical Slice is one of the most critical milestones in a funded project. It is a fully polished, standalone segment of the game that represents final-quality gameplay, art, audio, and user interface. * Key Deliverables: A playable level or 10–15 minute gameplay segment that looks and plays like the final product. * Publisher Focus: Ensuring the art style, performance, and gameplay meet commercial standards before committing the bulk of the production budget.

3. Alpha (Feature Complete)

At the Alpha stage, all core systems, mechanics, and features must be implemented and functional. * Key Deliverables: A build that is playable from start to finish. Placeholder assets (temporary art or audio) may still exist, but no new gameplay features can be added after this point. * Publisher Focus: Assessing the overall flow of the game, pacing, system integration, and core mechanics.

4. Beta (Content Complete)

During Beta, all content—including final 3D models, textures, voice acting, music, and level designs—must be integrated into the game. * Key Deliverables: A complete game with no placeholder assets. The focus shifts entirely to localization, optimization, polish, and QA (quality assurance) testing. * Publisher Focus: Ensuring the game runs stably on target platforms, possesses a balanced difficulty curve, and is relatively bug-free.

5. Submission and Gold Master (Release)

This is the final milestone of the primary development cycle. The game must be completely finished and ready for public distribution. * Key Deliverables: The final master build that has passed platform holder certification (Sony, Microsoft, Nintendo, Steam, etc.) without any critical bugs. * Publisher Focus: Preparing for retail manufacturing, digital storefront deployment, and marketing campaigns.

6. Post-Launch Support

Modern publishing contracts usually include milestones for post-launch deliverables. * Key Deliverables: Day-one patches, scheduled hotfixes, downloadable content (DLC), and ongoing live-ops support. * Publisher Focus: Player retention, community satisfaction, and long-term monetization.

How Milestone Approvals Work

Every milestone delivery undergoes a formal review process: 1. Submission: The developer sends the build, release notes, and documentation by the scheduled deadline. 2. QA Evaluation: The publisher’s internal QA team tests the build against the agreed-upon criteria. 3. Feedback/Approval: The publisher either approves the milestone and triggers the corresponding payment, or rejects it with a list of required fixes (a “cure period”) before re-evaluation.