The two models in one sentence each
Fixed price: a defined scope for an agreed amount; changes go through a change request. Time and materials: you pay for the time actually spent, usually within an agreed ceiling, and the scope can change as you learn.
Where the risk sits
| Fixed price | Time and materials | |
|---|---|---|
| Scope | Fixed early; changes are negotiated | Adjusted each increment |
| Budget certainty | High, if the scope does not change | Controlled by a ceiling and regular reviews |
| Risk of wrong assumptions | Priced in by the supplier, or argued about later | Visible early and handled in the backlog |
| Best fit | Small, well-understood work | Work where learning changes the plan |
What public guidance recommends for agile work
The US government's 18F team recommended a time-and-materials contract with a not-to-exceed ceiling for custom software built iteratively. Their reasoning: the buyer pays only for time actually incurred, with detail on each invoice, can stop assigning work without a heavy termination procedure and keeps the software delivered so far (18F De-risking Guide). The same guide suggests judging a supplier by real code they have written rather than by presentations.
This echoes a value from the 2001 Agile Manifesto: customer collaboration over contract negotiation (agilemanifesto.org).
When fixed price still makes sense
A fixed price works well for bounded pieces of work whose scope can be described completely: a discovery with a defined set of outputs, a migration of a known data set, or a design review. Many projects use a fixed-price analysis step followed by time-and-materials delivery.
Safeguards in either model
- Source code in a repository owned by you from the start.
- Working software shown at the end of every increment.
- A written definition of done, based on acceptance criteria.
- A clear way to stop, and ownership of everything delivered so far.
- Explicit terms on data and intellectual property ownership, as also recommended in UK purchasing guidance.
Note
This guide describes common models; it is not legal advice. Have contracts reviewed by a qualified adviser in your jurisdiction.
Sources
- 18F De-risking Guide, Buying custom software development services (archived January 2025)
- Manifesto for Agile Software Development (2001)
- GOV.UK, Define your purchasing strategy (updated 3 September 2026)
Sources checked on 17 November 2026.