---
title: "Fixed Price vs Time and Materials"
description: "How fixed-price, time-and-materials and capped contracts differ: who carries scope risk, how change is handled, how each fails and which to use for a given project."
url: "https://codesagelabs.com/resources/fixed-price-vs-time-and-materials"
type: "guide"
author: "Anjula Paulus"
published: "2026-10-16"
modified: "2026-10-16"
publisher: "Code Sage Labs"
---

# Fixed Price vs Time and Materials

By Anjula Paulus, Founder and software engineer at Code Sage Labs. Published 2026-10-16, last updated 2026-10-16.

Fixed price and time and materials do not change the work, the team or the amount of engineering required. They change who absorbs the gap between what was imagined and what turns out to be true. Choosing between them is a question about how much of your scope is genuinely known, and answering it honestly is more useful than arguing about which model is safer in general.

## Key takeaways

- The model allocates scope risk; it does not reduce the work or the uncertainty.
- Fixed price buys budget certainty and pays for it in contingency and change requests.
- Time and materials buys flexibility and requires you to manage priorities.
- A cap shares the risk but only works with real burn reporting and stop conditions.
- Mixing models by phase is normal: discovery and build do not need the same contract.

## Terms used in this guide

These words are used inconsistently across proposals. The definitions below are the ones used here.

- Fixed price — an agreed total for an agreed scope, with changes handled by priced amendment.
- Time and materials — payment for effort actually spent, at agreed rates, against a prioritised backlog.
- Capped time and materials — time and materials with an upper limit, above which the supplier absorbs the cost or work stops.
- Scope risk — the chance that delivering the agreed result takes more effort than was assumed.
- Burn — effort consumed so far, usually reported against a forecast.
- Stop condition — a written trigger, such as reaching a percentage of the cap, that forces a decision rather than a surprise.
- Acceptance conditions — the written tests that decide whether a deliverable counts as done.
- Retention — a share of the price held back until acceptance or the end of a warranty period.

## What each model actually does

Under a fixed price the supplier promises a result for a number, so the supplier owns the gap between the estimate and reality. To survive that promise the supplier adds contingency, scopes defensively and must police change, because every unplanned item comes out of their margin. None of this is bad faith; it is the only rational response to carrying the risk.

Under time and materials you own the gap. The supplier has no reason to pad the estimate or to argue about a small change, but nobody except you is holding the total down. The protection is not contractual, it is operational: visible priorities, regular forecasts and a willingness to cut scope when the forecast moves.

## The two models side by side

Each line compares one dimension across both models, with the capped variant noted where it differs.

- Scope risk — fixed price: supplier. Time and materials: buyer. Capped: supplier above the cap.
- Price certainty — fixed price: high, for the agreed scope only. Time and materials: low without active management. Capped: bounded at the top.
- Estimate incentive — fixed price: estimate high to stay safe. Time and materials: estimate realistically, since there is nothing to hide. Capped: estimate near the cap.
- Handling change — fixed price: a priced change request each time. Time and materials: reprioritise the backlog. Capped: reprioritise under the cap.
- Buyer effort required — fixed price: heavy up front, writing scope and acceptance. Time and materials: steady throughout, owning priorities. Capped: both.
- Supplier behaviour under pressure — fixed price: defend scope and reduce quality that is not in the acceptance conditions. Time and materials: keep working unless you intervene.
- Typical failure — fixed price: an adversarial change-request war, or a thin delivery that technically passes. Time and materials: an unbounded total and a project with no edge.
- Cash-flow shape — fixed price: milestone payments against deliverables. Time and materials: monthly against effort.
- Fit for discovery — fixed price: poor, because the scope is what you are trying to discover. Time and materials: good, bounded by a short timebox.
- Fit for ongoing product work — fixed price: poor, because every iteration is an amendment. Time and materials: good.
- Fit for a well-specified replacement or integration — fixed price: good. Time and materials: workable but gives away your certainty.

## Where fixed price goes wrong

Fixed price fails when it is used to buy certainty that the scope cannot support. The contract then makes every discovery a negotiation: the supplier must defend margin, you must argue that an obvious requirement was implied, and both sides spend attention on the contract rather than on the software.

The second failure is quieter. Quality that is not written into the acceptance conditions is where a squeezed fixed price gives way first, and it is usually tests, error handling, documentation, deployment and the non-functional requirements nobody wrote down.

## Where time and materials goes wrong

Time and materials fails when nobody on the buyer's side owns priorities. Without a decision-maker the backlog grows, the team stays busy, and six months later the money is gone and the product has no defined edge. The supplier was working the whole time, which is precisely why the problem is invisible until the invoice total is read as a total.

It also fails when reporting is thin. Hours by person is not reporting. A forecast to completion, revised when it moves, is.

## Making each model safe

Both models work when the known weakness is covered deliberately. Fixed price needs its scope written and its change process agreed before signature. Time and materials needs its visibility and its brakes installed before the first sprint, not after the first surprise.

- Fixed price: written acceptance conditions for every deliverable
- Fixed price: an assumptions and exclusions list attached to the price
- Fixed price: a change-request process with a published rate and a turnaround time
- Fixed price: milestones small enough that a bad one is recoverable
- Time and materials: one named person who owns priorities
- Time and materials: a forecast to completion, revised every cycle
- Time and materials: a budget checkpoint that triggers a scope decision
- Time and materials: working software reviewable at the end of each cycle

## A decision rule

Apply these in order and stop at the first that matches.

- Rule 1: if you cannot write the acceptance conditions today, do not sign a fixed price for the build. Buy a timeboxed discovery instead.
- Rule 2: if scope, data, integrations and acceptance are written and stable, take the fixed price.
- Rule 3: if two or three unknowns remain and the rest is clear, use a capped model and spend the first weeks closing those unknowns.
- Rule 4: if you expect to change direction based on what users do, use time and materials and accept the obligation to manage it.
- Rule 5: if you cannot give the project a decision-maker with real availability, do not use time and materials, because the model depends on one.
- Rule 6: if the project has both a bounded part and an open-ended part, contract them separately rather than forcing one model across both.

## Questions

### Is fixed price safer than time and materials?

Only when the scope is genuinely known and the acceptance conditions are written. Applied to uncertain work it shifts risk onto the supplier, who prices for it and then has to defend the boundary, which is how a project becomes a change-request negotiation.

### How do I stop a time-and-materials project running away?

Appoint one person who owns priorities, require a forecast to completion rather than a list of hours, review working software every cycle, and set a budget checkpoint that forces a scope decision before the money runs out.

### What is a capped time-and-materials contract?

Time and materials with an agreed upper limit. You pay only for effort spent, the supplier absorbs cost above the cap or work stops there, and change is handled by reprioritising under the cap. It suits scope that is mostly clear but not fully resolved.

### Can one project use both models?

Yes, and it is often the best answer. A timeboxed discovery on time and materials, followed by a fixed price for the part that discovery made certain, puts each model where it works.

## Related

- [Explore our software development services](https://codesagelabs.com/services)
- [All guides](https://codesagelabs.com/resources)

*Source: [https://codesagelabs.com/resources/fixed-price-vs-time-and-materials](https://codesagelabs.com/resources/fixed-price-vs-time-and-materials) — Code Sage Labs, Colombo, Sri Lanka. Contact: hello@codesagelabs.com*