The short version: Tie each milestone to a versioned build, named platform, observable tests, source revision, exclusions, and a decision process for change.

Clients ask for fixed-price game development because they want certainty. Studios agree because they want the deal. If the specification says only “multiplayer prototype,” “polished combat,” or “complete vertical slice,” both parties have priced a different imaginary product.

The dispute arrives later wearing the costume of scope creep.

Define evidence before price

Each milestone should identify:

  • target engine and platform;
  • playable path and included content;
  • input devices and supported resolutions;
  • performance test device and conditions;
  • networking assumptions and player count;
  • known exclusions and placeholder content;
  • version-control revision and build identifier;
  • defect severity allowed at acceptance;
  • exact evidence delivered.

“Feels polished” can be a creative goal. It cannot be the only acceptance test.

Demonstrate the risky loop first

A milestone plan should attack uncertainty, not merely produce attractive screenshots. If online synchronization, save migration, procedural generation, console performance, or a novel combat mechanic can break the project, prototype it early.

The client is buying reduced uncertainty. A vertical slice that hides the hardest system is a marketing demo, not risk retirement.

Source control is part of acceptance

Epic’s documentation describes source control as the record of changes used to coordinate a team. Require the milestone to reference a tagged or otherwise identifiable revision. The submitted build and submitted source must match.

Then test a clean checkout and rebuild. Otherwise the accepted artifact may depend on untracked local files.

Change control protects both sides

When a new idea arrives, document:

  1. requested change;
  2. reason and expected player value;
  3. schedule and cost effect;
  4. what is removed or delayed;
  5. who approved it.

Fixed price is viable only for fixed assumptions. Change control is not hostility; it is the mechanism that keeps later decisions honest.

Sources and limits

Contract requirements vary by jurisdiction and project. This article is production education, not legal advice.

Key takeaway

Fixed price is not created by putting one number on a proposal. It is created by defining observable acceptance, exposing uncertainty early, preserving source evidence, and pricing every later change.

fixed pricegame outsourcingacceptance criteriamilestones