Fixed Price or Time and Materials? Choosing a Software Contract Model
Fixed price, time and materials, or a staged mix: who carries which risk in a software contract, when each model works, and the clauses that keep a project under control.
The short answer
Fixed price works when the scope can be described and accepted in writing: a defined first release, clear acceptance criteria, known integrations. Time and materials works when the work is discovery, research or continuous improvement. Most serious products use both: a fixed price for each defined stage, and a retainer or capped hours for change and support.
Weighing this for your business? Request a project review

Our take
Axiom Forge fixes scope, price and acceptance criteria in writing for each stage and estimates additional work separately before it starts. You always know what the next payment buys.
In this article6 sections · 4 min
Every software project has uncertainty. The contract model decides who pays when reality differs from the plan. Under a fixed price the supplier carries the estimate risk and protects itself with a precise scope. Under time and materials you carry it and protect yourself with visibility and the right to stop.
Neither model is cheaper by nature. A fixed price contains a risk margin. Time and materials contains no risk margin and, unless you agree a cap, no ceiling.
| Fixed price | Time and materials | Staged fixed price | |
|---|---|---|---|
| Best for | A release that can be specified | Discovery, research, ongoing change | Products built in defined stages |
| Estimate risk | Supplier | Client | Shared, stage by stage |
| You must provide | Decisions and acceptance on time | Priorities every week | Decisions at each stage gate |
| Typical failure | Disputes about what was included | Cost with no finished release | Stages that are too large |
A fixed price needs three things: a scope that both sides can read the same way, acceptance criteria that can be tested, and a client who makes decisions on time. With those in place it gives a budget you can plan around and a supplier with a reason to finish.
It fails when the scope is a list of feature names. “Booking, payments and notifications” can mean two weeks of work or four months.
Paying for time is the honest model when nobody can know the scope yet: early discovery, research into a difficult integration, or the steady improvement of a live product. Asking for a fixed price there only produces a large safety margin or a later dispute.
It needs discipline on both sides: a weekly priority list, visible progress, a monthly cap and the right to pause. Agile methods such as Scrum formalise the rhythm: work is planned in short cycles, and each cycle ends with a usable increment that both sides can inspect.
A staged contract combines the two. A short paid first stage defines the product: journeys, scope, risks and a prototype. UK public-sector teams treat the first part of this, understanding the problem before anything is built, as a phase in its own right called discovery. Each release is then a fixed-price stage with its own acceptance criteria. After launch, support and improvement run on a retainer.
Each stage ends with something you can keep and a decision to continue. If the relationship does not work, you leave with usable results, not with half a product.
Change will happen. What matters is the mechanism. A good contract describes it in a few lines: a change is written down, estimated, approved, and only then built. Small changes can be absorbed by agreement, large ones move the price or the date, and nothing changes silently.
Whatever the model, a few clauses decide how the project feels in its hardest week. Contract law differs by country; this is general guidance, not legal advice.
- Acceptance: how a deliverable is tested and when silence counts as approval
- Payments: tied to accepted deliverables, not to calendar dates alone
- Ownership: rights transfer on payment; accounts and repositories in your name
- Warranty: how long defects are fixed at no charge after acceptance
- Exit: what you receive and what you owe if either side stops
Discuss your project with the founder
Is fixed price cheaper than time and materials?
Not by nature. A fixed price includes a margin for the supplier’s risk; time and materials has no risk margin and, without an agreed cap, no ceiling. Fixed price is cheaper when the scope is truly clear, and more expensive when it is not.
What is a change request?
A written description of work outside the agreed scope, with its estimate and its effect on the date. It is approved before the work starts, so that the budget never changes silently.
What should a payment schedule look like?
Payments should follow accepted deliverables: a deposit to start, then stages linked to results you can check. Avoid schedules where most of the money is paid before anything can be tested.


