Fixed price vs time and materials: which contract to sign?
Fixed price vs time and materials: how each contract shares the risk and handles change, the hybrid set-ups, and the questions to ask before you sign.


You have chosen a provider, the proposal is on your desk, and one line decides a lot: how the work will be billed. Fixed price vs time and materials is the classic choice, and a monthly plan is a third option that more and more projects use once the first version is live.
None of these models is cheaper by nature. Each shares the risk differently between you and your provider, and each works only under certain conditions. Here is how they compare, how each handles change, the hybrid set-ups that often work best, and the questions to ask before you sign.
Three ways to pay for a software project
Fixed price
The provider commits to delivering a defined scope for a price agreed in advance. You know your budget from the start. In return, the scope must be precise: written requirements, screens or examples, and clear acceptance criteria.
Fixed price software development suits projects whose needs are stable and well understood: replacing a known process, rebuilding an existing tool with the same features, or a small, well-bounded application.
Time and materials
With a time and materials contract, you pay for the time actually spent, usually on a day rate. The scope can move: you decide each week or fortnight what the team works on next, from a ranked list of work.
This model suits projects whose needs will become clearer along the way: a new product, a first version of a SaaS (software as a service) platform, or a tool whose users will only know what they want once they see it. It needs someone on your side who ranks the work and attends the reviews.
Monthly plan
A monthly subscription covers maintenance, hosting and improvements each month. The budget is spread evenly, and the software keeps improving. It is rarely the way to build a first version, but it is often the best way to keep a tool alive once it is in use.
Fixed price vs time and materials: who carries which risk
Every software project carries uncertainties: needs nobody wrote down, tasks that take longer than planned. The contract does not remove them; it decides who pays for them.
| Fixed price | Time and materials | Monthly plan | |
|---|---|---|---|
| Budget known in advance | Yes, for the agreed scope | No, only an estimate | Yes, per month |
| Who carries the overrun risk | Mostly the provider | Mostly you | Shared, within the plan’s limits |
| What it needs to work | A precise, signed-off scope | A ranked list of work and regular reviews | A clear list of what the plan covers |
| Flexibility on scope | Low: each change is negotiated | High: you reprioritise freely | Medium: within the monthly capacity |
| Your time needed | High at the start, then at acceptance | Steady throughout | Light, at each monthly review |
| Best for | Stable, well-defined needs | New products, uncertain needs | Running and improving live software |
Two consequences follow. A provider who takes on the overrun risk of a fixed price includes a margin for it: certainty has a cost. And a time and materials contract is only as good as the control you keep over it: without regular reviews, the budget drifts unnoticed.
Before choosing, read our guide to estimating a software project: the quality of the estimate matters as much as the contract type.
How each model handles change
Change is normal in a software project; what matters is how it is handled.
- Fixed price: a new request goes through a change process. The provider prices it, and you accept, refuse or move it to a later stage. This protects your budget, but too many changes turn the project into a series of negotiations.
- Time and materials: you swap one task for another in the ranked list. Nothing to negotiate, but the total grows if you add work without removing any.
- Monthly plan: new requests join the queue and are handled within the plan’s monthly capacity. Larger pieces of work are quoted separately.
Whatever the model, short iterations with regular demonstrations make change cheap. A precise software requirements specification reduces surprises, but never to zero. And whichever contract you sign, a simple routine to log, assess and decide on each request keeps scope creep in check.
Hybrid set-ups that often work best
Many projects fit no single model. These combinations share the risk more evenly.
A paid scoping phase, then a fixed price
A short first phase, billed on its own, produces the requirements, the main screens and a ranked list of work. The provider can then quote a fixed price that rests on facts rather than guesses.
Agile fixed price
The budget and the timeline are fixed; the exact content is not. You agree on a ranked list of features and the team delivers in short iterations, starting with the most valuable. You can swap a feature for another of similar size without a new contract. What is not reached within the budget waits for the next stage.
A fixed-price first version, then a monthly plan
You pay a fixed price for a first release limited to the essentials, then move to a monthly subscription for hosting, maintenance and improvements: a known budget to start, then a steady monthly cost while the software grows with real use.
Shipping a focused first release, then building on it, is a pattern that works. On the CRM/ERP for a Sydney law firm led by our founder, Anass Chabbab, in his previous role as IT director of DIGIIT Solutions, the first release went live in under 6 months; the tool then grew to more than 100 users and cut processing time by 40%.
A worked example
Illustrative example (fictitious figures). A training company wants a booking and invoicing tool with 20 features. After a short scoping phase, 12 are judged essential and well understood: they become a fixed-price first version. The other 8 depend on how trainers use the tool, so they move to a monthly plan after launch, re-ranked each month. The starting budget is known, and the uncertain part stays flexible.
Questions to ask before you sign
Use this checklist with any proposal, ours included.
- What exactly is included? For a fixed price, ask for the list of features, the acceptance criteria and what is explicitly excluded.
- How are changes handled? Who assesses them, how quickly, and on what basis are they priced?
- How often will we see working software? Every two weeks is a healthy rhythm; months without a demonstration is a warning sign.
- Who ranks the work, and how is progress reported? On time and materials, ask for a regular statement of time spent against the list.
- What happens after delivery? Warranty period, bug fixes, hosting, maintenance: covered by the contract, a monthly plan, or nothing at all?
- Who owns the code and the data? Make sure ownership, access to the source code and the handover of your data are written down.
- How do we stop if needed? Notice period, what is delivered at the time of stopping, and in what form.
The answers matter more than the label: a fixed price with a vague scope protects no one.
This article gives general, practical guidance as of October 2026. It does not replace advice from your lawyer: contract law differs from one country to another, including what a fixed-price contract commits the provider to, so have the clauses reviewed before you sign.
How we bill at AnazTech
We bill in three ways: at a fixed price, on a day rate or as a monthly subscription, and these modes combine well. Once we understand your needs, we send a detailed, costed proposal and explain which model we recommend and why. Our guide to the cost of custom software explains what drives the price itself. See also our custom software development and SaaS development services.
Frequently asked questions
Is time and materials more expensive than fixed price?
Not necessarily. A fixed price includes a margin for the risk the provider takes on, so you pay for certainty. With time and materials, you pay only for the time spent, which can cost less if the scope stays under control, or more if it keeps growing. The quality of the estimate and the regularity of the reviews make the difference.
What is an agile fixed price?
It is a contract where the budget and the timeline are fixed, but the detailed content can change. You agree on a ranked list of features, delivered in short iterations from the most valuable down, and you can replace a feature with another of similar size without renegotiating. You keep a known budget and the freedom to learn as you go.
What should a time and materials contract include?
At least the day rate, an estimate with its assumptions, how often time is reported, who ranks the work, and how often you review progress together. Add a ceiling or an alert threshold that triggers a discussion before the estimate is exceeded, the ownership of the code and data, and the conditions for stopping. A lawyer should review the final clauses.
In short
Fixed price vs time and materials is a question of who carries the risk. A fixed price needs a precise scope and protects your budget; time and materials needs your involvement and a ranked list, and gives you flexibility; a monthly plan keeps live software running and improving. Hybrid set-ups, such as a fixed-price first version followed by a monthly plan, often share the risk best.
Weighing up a proposal, or about to ask for one? Book a free 30-minute discovery call: we look at your project together and discuss which contract fits it best.
Related servicesCustom softwareSaaS products
Let’s talk about it on a 30-minute discovery call, free and with no obligation.
Get our next articles in your feed: follow AnazTech on LinkedIn.Follow on LinkedIn






