Comparison
A price agreed in advance against a defined scope, or payment for the effort spent. The choice decides who carries the risk of the estimate being wrong.
Choose fixed price when the scope is knowable and stable and budget certainty matters more than adaptability. If the requirement can be written down, held still and accepted against clear criteria, fixed price is often cleaner for the buyer. That covers more work than people assume: known integrations, migrations with a defined source and target, audits and well-understood replications.
Choose time and materials when what should be built will be discovered while building it, which describes most product work. Learning something halfway through becomes a decision instead of a negotiation. It is only safe with controls: working software every week, a named person who accepts work, and the ability to stop or change direction at short notice.
Many experienced buyers settle in the middle. A fixed price for discovery bounds the first commitment. After that, either a fixed scope per phase, each small enough to estimate well, or capped time and materials keeps flexibility with a bounded exposure. Both give budget control without pricing an uncertain project in one go.
Fixed price and time and materials are two ways to buy software delivery. Fixed price agrees a number against a defined scope, so the supplier carries the risk that the estimate is wrong and prices a margin for it. Time and materials charges for the effort spent, so the buyer carries that risk and needs visibility and the ability to stop.
Neither model is inherently cheaper. Software estimates are uncertain because part of the work is discovering what the work is, and somebody has to carry that uncertainty. The useful questions are whether the scope is knowable enough to price, how much variance your budget can absorb, and whether someone on your side can direct the work every week.
Open what matters to you.
Fixed price puts the estimate risk on the supplier, who must price a margin for it, because across many projects some overrun and the rest have to cover them. An under-priced fixed price is no bargain: it is delivered under margin pressure, where ambiguous requirements get the cheapest reading and testing is compressed first. A well-run time-and-materials engagement usually costs less for the same work, and it can cost more, because only your governance bounds it.
Fixed price transfers the risk of the estimate being wrong. It does not transfer the risk of the specification being wrong. If the agreed scope is delivered exactly and fails to solve the business problem, the supplier has met the contract and you have bought the wrong thing on time and on budget. The pressure to fix scope early is what causes specifications to be written before anyone understands the problem.
A fixed price rewards delivering the scope with less effort, which encourages efficiency and reuse. When effort runs ahead of the estimate, interests separate. Ambiguity is resolved in the cheapest direction, assumed work becomes a change request, and a better approach found in week six costs the supplier money. Every change becomes a commercial event, and time goes into interpreting a document written before anyone knew much.
Time and materials rewards the supplier for staying useful. That suits uncertain work, with an obvious risk: the supplier is paid for time and controls how long things take. The model relies on reputation, visible output and the buyer’s ability to leave. A supplier who is not delivering value should be replaced quickly, which is only possible when stopping is easy and progress is visible.
A responsible fixed price needs detailed requirements: behaviours, real integration behaviour, real data, non-functional expectations and acceptance criteria. Producing them is real work. A short, fixed-price discovery phase delivers that understanding as something you own, and lets a later price carry a smaller margin. A firm number against a thin brief means the supplier has built this before, has priced in a large margin, or expects to recover the difference through change requests.
Time and materials needs four controls. Bound the first phase with a fixed-price discovery. Cap the exposure with a budget ceiling or a not-to-exceed figure per phase. See working software every week, built in your repositories, in place of a status report. Keep the ability to stop, with short notice and your own accounts throughout. Then supply someone who prioritises, answers questions and accepts work.
Capped time and materials charges for effort, lets priorities change freely and sets a figure that cannot be exceeded without a further decision. Near the cap you extend, stop or reduce the remaining ambition. A cap controls the budget but not the outcome: at the ceiling, you have whatever was built. Fixed scope per phase prices each phase after the previous one has taught everyone something, so every estimate rests on better information.
Two other structures come up. Target cost with a shared overrun aligns incentives well but needs open-book trust, so it usually suits an established relationship. Milestone or outcome payments tie money to acceptance, which works when the acceptance criteria are objective. Whatever the model, assign intellectual property to the buyer on creation, define acceptance before work starts, state the warranty position and agree notice periods while nobody needs them.
Moving from fixed price to time and materials usually happens under strain, when change requests pile up or the specification turns out to describe the wrong system. Stop and re-baseline deliberately: accept what has been delivered, describe what remains in current terms, then restart on a bounded arrangement with a cap and weekly output. Drifting there through an ever-growing change process combines the overhead of one model with the uncertainty of the other.
Moving from time and materials to fixed price usually happens from strength. Once the system exists and the remaining work is well defined, it can be priced with a small margin, and from then on changes become variations again. In either direction, write down what is accepted at the switch, and keep repositories, cloud accounts and documentation in your control so nothing needs untangling.
Neither, inherently. A fixed price includes a margin for the risk the supplier carries, so a well-run time-and-materials engagement for the same scope usually costs less. It can also cost more, because only your governance bounds it. The real choice is a risk position: pay a premium for certainty, or carry the variance yourself and keep the premium.
When the scope is knowable and stable, when approval needs a total, when the work resembles something the supplier has built before, when procurement requires it, or when you cannot absorb an overrun. Discrete work fits especially well: a security assessment, a technical audit, a data migration, a defined integration or a discovery phase, where there is little to discover about what is being asked.
With four controls working together. A cap or not-to-exceed figure per phase, renewed by decision. Phases with decision points, so you re-approve with better information. Working software every week in your environment and repositories, so problems show in week two. And the ability to stop, with short notice and a handover position that holds at all times.
No. Under capped time and materials you pay for effort, priorities change freely, and an agreed figure cannot be exceeded without a further decision. Under a fixed price, the supplier must deliver the defined scope whatever it takes. At the cap you decide whether to extend, stop or reduce ambition, and you keep whatever was built. That suits uncertain scope and fits poorly when you need a specific result at a specific cost.
Agree the mechanism before you need it. Decide who may raise and approve a change, how quickly an estimate arrives, and what happens to the timeline. A change budget or a swap mechanism, trading equivalent work out of scope, removes friction from small adjustments. If you are designing an elaborate change process before work starts, the scope is probably not stable, and a phased or capped arrangement fits better.
Start a project
Tell us what you’re building and what it has to work with. We’ll tell you which option fits and why.
Or email [email protected]