Fixed price vs time and materials: how to choose for a software project

Published 2 October 2026


Quote a fixed price when the scope is written down to task level and your team has built something like it before. Bill time and materials when the scope will change as the work reveals it - an MVP, ongoing product work, anything that depends on code or systems nobody has seen yet. The question is not which model the client prefers, but who can carry the risk of being wrong, and whether the price pays for carrying it.

When the scope is only half known, which is the usual case for new software, do not pick one: run discovery on time and materials and fix the price of the build afterwards. This guide covers how to tell which situation you are in, and prices the same project all three ways.

The difference is who carries the risk

Both models start from the same estimate: the work broken into tasks, each with a low and a high number of hours. What changes is who pays when the actual hours land at the high end.

  • Fixed price. The client buys an outcome for an agreed sum. If the work takes longer, the agency absorbs it; if it goes faster, the agency keeps the difference. The price has to include the cost of carrying that risk.
  • Time and materials. The client buys hours at an agreed rate and pays for what is used. Overruns are the client’s, and so are the savings. The agency’s risk is reputational - a bill well past the estimate costs the next project, not this one.

Neither is more honest than the other. A fixed price moves the risk to the agency, which is right when the agency has built the thing before and knows what it costs. Time and materials leaves it with the client, which is right when the client is still deciding what the thing is.

When a fixed price is the right call

A fixed price works when most of these are true:

  • The scope can be written as a task list specific enough that a stranger could tell whether a request is inside it.
  • Your team has delivered similar projects, so the ranges come from experience rather than optimism.
  • There are few unknown dependencies: no undocumented vendor API, no legacy system to reverse-engineer.
  • One person on the client side can sign off the work.
  • The client’s budget genuinely cannot move - a board approval, a grant, a procurement process that needs a single number.

Marketing sites, store builds, a second integration with an API you already know: this is fixed-price work. The method is in how to price a fixed-bid project - price off the high end of the range, then add a 15-30% buffer.

When time and materials is the right call

Bill time and materials when the scope is going to move, and moving it is the point:

  • Early product work. An MVP is half an idea on day one. The client learns what the product should be by watching it get built, and every lesson is a scope change.
  • Ongoing development. Post-launch work, feature backlogs, maintenance - there is no finished scope to price.
  • Unknown code or systems. Taking over another team’s codebase, or integrating with something whose documentation nobody has tested.
  • A client who wants to steer. An in-house product owner reprioritising every two weeks cannot work inside a scope fixed in a contract.

If you would need a buffer above 30% to feel safe fixing the price, the work is time and materials, whatever the contract calls it.

The same project, priced both ways

Take an agency quoting a web app MVP from the Web App MVP template: 26 tasks across discovery, design, backend, frontend, billing and launch, adding up to 290-564 hours. The agency bills €75/hour.

Time and materials: the client gets a budget of €21,750-42,300 and pays for the hours used. The width of that range is honest - an MVP’s scope is not settled - but it is a hard sell to a client who needs one number approved.

Fixed price: price off the high end, 564 × €75 = €42,300. MVP scope is as vague as scope gets, so the buffer goes to the top, 30%: €54,990, call it €55,000. That is nearly €13,000 above the worst case of the time-and-materials estimate. It is not greed. It is what certainty costs when nobody yet knows what is being built.

What usually happens next is the worst of both. The client balks at €55,000, and the agency agrees a fixed €32,000 - the hours at the midpoint of the range. That is fixed-price risk at a time-and-materials price: every hour past the midpoint comes out of the margin, and MVPs run past the midpoint.

The hybrid: discovery on time and materials, the build at a fixed price

Split the project at the point where the unknowns are resolved.

  1. Discovery on time and materials. The template’s Discovery & Planning category is 20-44 hours: kick-off workshop, technical discovery, user stories, architecture. At €75/hour the client commits €1,500-3,300, not €55,000. The output is a written scope.
  2. Re-estimate the build against that scope. The remaining work was 270-520 hours. With user stories and an architecture on paper, the range narrows - say to 330-420 hours.
  3. Fix the price of the build. 420 × €75 = €31,500, plus 15% now that the scope is solid: €36,225, rounded to €36,500.

If discovery took 36 hours (€2,700), the client’s total is €39,200 - about €16,000 less than the up-front fixed price, with the same certainty on the part that costs real money. The agency is fixing a price on a scope it wrote itself, and if the build lands at the top of its range, the effective rate is still €87/hour.

A fixed price is cheapest for both sides once the uncertainty has been paid for separately. And a client who will not pay for two weeks of discovery is telling you something about how the next six months would go.

Two models in between

Capped time and materials

“Time and materials, not to exceed €40,000” sounds like a fair middle. Look at who carries what: below the cap, the client pays actual hours and keeps the savings; above it, the agency works for free. That is the downside of a fixed price without the buffer that pays for it.

A cap is reasonable in two forms only: set where the fixed price would have been, or written as a trigger rather than a ceiling - “at 80% of the budget we stop, review, and agree what happens next.” The second is simply good budget reporting, and worth doing on every time-and-materials project anyway.

Fixed budget, flexible scope

A monthly retainer for a set team capacity: the client fixes what they spend each month, and the scope is whatever the top of the backlog fits into it. The client gets cost certainty, the agency carries no overrun risk, and the scope negotiation happens every sprint instead of once in a contract. It needs a client-side product owner who will make those calls; without one, it drifts.

Whichever model you pick, send the range

The estimate is the same document under every model - only what you do with the range changes. On time and materials, the range is the budget conversation: a client who agreed to 290-564 hours is not surprised by 480. On a fixed price, the task breakdown is what lets you cut scope instead of price when the client says the number is too high.

Estimake is built around that range. Every task carries a low and a high estimate, rates can differ by category, and the client gets a link showing the breakdown with the total as a range of hours and price. It does not track time: to report actual hours against a time-and-materials budget, you still need a time tracker. To see the level of detail first, the six worked templates show the full breakdown on each page.

Choose the model per project, not once for the agency. The risk is different every time, and the contract should say who carries it.

Frequently asked questions

Is a fixed price cheaper for the client than time and materials?

Usually not. A fixed price has to cover the high end of the estimate plus a buffer for what the estimate cannot see, so on the same scope it lands above the likely time-and-materials bill. The client is paying for certainty. That is worth it when the budget cannot move - a board approval, a grant, a procurement process - and poor value when it can.

How do I get a client to accept time and materials?

Make the budget visible before it is spent. Send the task breakdown with an hour range on every line, so the client sees the realistic total up front rather than an open cheque, then report hours against it every week. Most resistance to time and materials is fear of an unbounded bill; a range and regular reporting bound it.

What is a not-to-exceed contract?

Time and materials with a ceiling: the client pays actual hours up to an agreed cap, and the agency absorbs anything above it. It sounds like a compromise, but the agency carries the overrun risk of a fixed price without the buffer that pays for it. Accept one only with the cap set where a fixed price would be, or with the cap triggering a re-scoping conversation rather than unpaid work.

Which model is more profitable for an agency?

A well-priced fixed bid on familiar work can earn well above your hourly rate, because you keep whatever the buffer did not need. It can also lose money, which time and materials almost never does. Time and materials earns your rate, steadily. Agencies that do well on fixed prices are the ones that only fix the price on scope they understand.

Can you change the pricing model partway through a project?

Yes, at a phase boundary, and it is often the right move. The common pattern is discovery on time and materials, then a fixed price for the build once the scope is written down. The reverse works too: a fixed price for the launch, then time and materials or a monthly retainer for the changes that follow.

Estimate your next project in Estimake

Build the estimate with your whole team at once, keep every number a range, and send it to the client as a branded link. Free for your first estimates - no credit card.

Start estimating freeSee how Estimake works

Copyright © Estimake 2026.

Payments are processed by Paddle.com, our merchant of record.
Features