Baumgart Software Guide Send a brief
  1. Home
  2. Guides
  3. G4

Fixed price or time and materials: choosing a way to work together

How the two common contract models share risk, what public-sector guidance recommends for agile work, and what to ask for in either model.

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 priceTime and materials
ScopeFixed early; changes are negotiatedAdjusted each increment
Budget certaintyHigh, if the scope does not changeControlled by a ceiling and regular reviews
Risk of wrong assumptionsPriced in by the supplier, or argued about laterVisible early and handled in the backlog
Best fitSmall, well-understood workWork 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

  1. 18F De-risking Guide, Buying custom software development services (archived January 2025)
  2. Manifesto for Agile Software Development (2001)
  3. GOV.UK, Define your purchasing strategy (updated 3 September 2026)

Sources checked on 17 November 2026.