Fixed fee or time and materials? Choosing how to price change
Every product project changes. The question is how changes are priced — and which model fits the uncertainty involved.
No product project survives contact with real users unchanged. New requirements emerge, assumptions fail and priorities shift. That isn't a problem in itself. The problem is when changes enter the work informally, with nobody deciding what they cost or what they replace.
Two models, two kinds of risk
A fixed fee buys certainty for a change that can be defined precisely: the user flow, deliverables, dependencies and acceptance criteria are all known. The delivery team carries the estimation risk. Time and materials buys flexibility for a change that can't yet be defined — unknown integrations, research-dependent decisions, technical investigation. The client carries the budget risk, but pays only for actual effort.
A practical rule
- Known, bounded work: fixed fee
- Clear objective, uncertain effort: time and materials with a not-to-exceed cap
- Unclear problem: a short paid discovery before either
- Frequent small refinements: a pre-agreed change budget
- Major accumulated change: re-scope the phase properly
Every change needs a decision
Whatever the model, a new request should become one of four explicit choices: decline it, defer it to a later phase, swap it for something of equal size, or approve it as a priced change. A quiet "yes" is how budgets and timelines drift without anyone noticing.
Make the trade-off visible
A good change proposal states three things plainly: the added cost, the effect on the schedule, and what would move if budget and date must stay fixed. That turns a potentially awkward conversation about extra charges into a straightforward prioritisation decision.
Fixed fee for known work, capped time and materials for unknown work, and discovery first when nobody can responsibly estimate.
