Fixed price vs time and materials: which suits a game project

The short answer

Use a fixed price when the scope is clear and unlikely to change, such as a prototype, a port, a reskin or a batch of art. Use time and materials when you are still discovering the game, running live operations or extending your own team. For most full game projects a hybrid works best: a short paid discovery phase, then fixed-price milestones with a small change budget.

How each model works

Fixed price: the real trade-offs

Advantages. You know the cost before you start. Budget approval is simple. The studio has a strong reason to work efficiently.

Costs. Because the studio carries the risk, a sensible fixed quote includes a buffer for the unknown. If the specification is vague, that buffer grows, or the studio protects itself by reading the specification narrowly. Every change becomes a negotiation. And if the price was too low, quality is where the pressure shows.

Fixed price works when both sides can describe done in a way a third person could check.

Time and materials: the real trade-offs

Advantages. You can change direction weekly. You pay for what is done, with no buffer for risk that never appears. Work can start before every detail is known.

Costs. The total is not known in advance. It requires trust, visibility and an involved client: someone must set priorities and review builds, or hours drift. Without that discipline, time and materials is how projects quietly double.

Controls that make it safe: a monthly cap, weekly reports of hours against tasks, a running demo every sprint and the right to stop with short notice.

Why games are awkward for both

Games are found through iteration. A feature that reads well in a document may not be fun in the hand, and nobody can be sure until it is played. A rigid fixed-price contract punishes the changes that make a game good. Pure time and materials offers no ceiling to a client with a fixed budget. This is the reason hybrids exist.

The hybrid most teams end up with

1. Paid discovery or prototype. One to four weeks at a small fixed price. Output: a playable prototype, a design document and an estimate for the rest. See the prototyping guide.
2. Fixed-price milestones. Production split into stages of two to six weeks, each with a playable build and written acceptance criteria. Payment on acceptance.
3. A change budget. Ten to fifteen percent set aside for improvements discovered through play, spent only with your approval.
4. A retainer after launch. Monthly hours for updates and live operations, which are open-ended by nature. See game maintenance cost.

This keeps the total predictable while leaving room to follow the fun.

Which model for which job

What makes a fixed price reliable

• A feature list with clear boundaries, including what is not included.
• Target devices, platforms and performance goals.
• Numbers: levels, characters, screens, languages.
• Acceptance criteria for each milestone.
• Who supplies what, and by when. Late feedback from the client is the most common cause of delay.

Our guide to writing a game development brief shows how to prepare this, and a game design document carries the detail.

Questions to ask a studio

1. What is excluded from this price?
2. How are changes priced and approved?
3. What happens if a milestone is late?
4. How many revision rounds are included for art?
5. When do I receive source code and assets?
6. Who do I speak to each week?

The answers tell you more than the number does. For warning signs, read why outsourcing partnerships fail, and for the legal terms see our contract checklist.

How we work

We quote fixed prices in milestones. Small builds start at $999 and $2,999 on the offer page, larger games begin with a paid prototype, and team extension is billed monthly as described on our co-development page.

Sources: Wikipedia: Fixed-price contract · Wikipedia: Time and materials · Manifesto for Agile Software Development. Checked November 11, 2026.

Related: Outsource game development · Game co-development · Get a quote