All Articles
StrategyNov 18, 202615 min

Fixed Price vs Time and Materials: How to Choose the Right Software Development Contract

The question is never which model is cheaper. It is who carries which risk, and whether that party can actually control it. This is the test I use before signing or advising on a development contract: what each model really buys you, what the evidence says about software budgets, the hybrids that work, and the clauses that protect you either way.

Michele Cimmino

CEO & Founder · Lasting Dynamics

Choose fixed price when you can describe the finished software precisely enough to test it before work starts, and nothing important will change while it is built. Choose time and materials when the scope will be discovered along the way, and you have someone on your side who can steer the work every week. For most business software the honest answer is neither in pure form: a short paid discovery at a fixed fee, then either a fixed price per phase or time and materials with a ceiling, then time and materials for the product's evolution.
That is the short answer. The longer one matters because the two models do not differ in price as much as they differ in who pays when the estimate is wrong, and software estimates are wrong often and by a lot. A fixed price does not remove that risk. It moves the cost part of it to the supplier and hands the scope and quality part back to you, usually without saying so.

Who this guide is for

You are a CFO, a CIO, a head of procurement or a founder-CEO, and an agency has just sent you a proposal, or two agencies have sent you two proposals on different models. Maybe you work in finance, insurance, healthcare or energy and need a budget the board can approve. Maybe you are a funded startup that cannot afford to run out of money halfway through an MVP. I have sat on both sides of this table, as the buyer and as the supplier, for close to twenty years. What follows is the method, not a sales argument for either model.

The Real Question: Who Carries Which Risk

Every software project carries the same handful of risks whatever the contract says: the work may cost more than estimated, the scope may change, the quality may disappoint, the market or the regulation may move, and someone has to spend time managing all of it. The contract model does not make those risks disappear. It decides who pays for each one. This is the map I draw before any other discussion:
RiskFixed priceTime and materials
Cost overrun on the agreed scopeSupplier (that is what you pay the premium for)You, unless there is a ceiling
Scope change during the projectYou, through priced change requestsYou, but changes cost only the hours they take
Quality under pressureYou: a supplier losing money cuts testing and refactoring firstShared: quality is visible and paid for, if you check it
Ambiguity in the requirementsContested: each side reads the gap in its own favourYou: ambiguity becomes hours
Management effortLower during delivery, much higher before signingHigher during delivery: someone must steer every week
Speed of adapting to new informationSlow: every change is a negotiationFast: you reprioritise the backlog
Read the table this way: a risk should sit with the party that can control it. A supplier can control its own productivity, so it can reasonably carry the cost of building a clearly defined thing. It cannot control your market, your regulator or your internal stakeholders changing their minds, so loading those risks onto a fixed price only means you pay for them twice: once in the premium, and again in the change requests.

The Five Contract Models You Can Actually Sign

Agencies talk about fixed price and time and materials as if they were the only two options. In practice there are at least five, and the hybrids are where most good contracts end up:
ModelYou pay forCost risk sits withWorks best whenTypical failure
Fixed price (lump sum)An agreed deliverable at an agreed priceSupplierScope is stable, specified and testableChange-request war; quality squeezed at the end
Time and materials (T&M)Hours or days worked at agreed ratesClientScope is discovered as you go and you can steer weeklyOpen-ended burn with nobody watching
Capped T&M (not-to-exceed)Hours worked, up to a ceilingShared: client up to the cap, supplier above itScope is mostly known but details will moveCap set too low, work stops at 90% done
Fixed price per phase or sprintA fixed price for each short, defined incrementSupplier, one phase at a timeA long project can be cut into releases of a few weeksPhases defined too large, so it becomes plain fixed price
Dedicated team (retainer)A team's capacity per monthClientOngoing product development with a stable backlogPaying for capacity without measuring output
Two terms that often confuse buyers. Cost-plus, common in construction and public procurement, reimburses the supplier's actual costs plus a fee; time and materials bundles cost, overhead and margin into the hourly or daily rate, so you never see the supplier's cost. And a dedicated team is time and materials with a monthly unit: the difference is commitment and continuity, not who carries the risk. I covered the dedicated-team model in detail in how to hire a dedicated development team.

What the Evidence Says About Software Budgets

The reason this decision matters so much is that software estimates do not fail gently. They fail with fat tails: most projects overrun a little, and a meaningful minority overrun catastrophically. The research is old enough to be cited everywhere and has not been contradicted since:
FindingNumberSource (date)
Average cost overrun across 1,471 IT projects27%Flyvbjerg and Budzier, Harvard Business Review (Sep 2011)
Share of those projects that were 'black swans'1 in 6, with 200% average cost overrun and almost 70% schedule overrunFlyvbjerg and Budzier, HBR (Sep 2011)
Large IT projects: budget, time and value versus plan45% over budget, 7% over time, 56% less value than predictedMcKinsey with the University of Oxford, 5,400+ projects (2012)
IT projects that go so badly they threaten the company17%McKinsey with the University of Oxford (2012)
Which projects carry the highest overrun riskSoftware projects run the highest risk of cost and schedule overrunsMcKinsey with the University of Oxford (2012)
When the US government allows time and materialsOnly when it is not possible to estimate accurately the extent or duration of the workFAR 16.601 (current text)
When the US government considers fixed price suitableWith reasonably definite functional or detailed specifications and a fair price establishable at the outsetFAR 16.202-2 (current text)
Two conclusions follow. First, the expected overrun is not the problem; the tail is. A fixed price is valuable precisely because it can protect you from the tail, but only if the supplier can absorb it, and a small agency that hits a 200% overrun on a fixed price does not absorb it: it renegotiates, cuts quality or disappears. Second, the US federal rules, written by one of the largest buyers of software in the world, reach the same conclusion I do: the model follows from how well the work can be specified, not from preference.
Note the date of the evidence. The big studies are from 2011 and 2012, before most companies worked in short iterations. Iterative delivery makes overruns visible earlier; it does not make estimates more accurate at the start. That is exactly why the contract structures that work best today commit money in short increments.

What Fixed Price Really Buys You

A fixed price buys budget certainty for a defined deliverable. That is worth a lot when the board needs a number, when the project has a hard regulatory deadline, or when you lack the people to manage a supplier week by week. The US federal acquisition rules describe it well: the price is not subject to any adjustment and it places on the contractor the maximum risk and full responsibility for all costs and the resulting profit or loss (FAR 16.202-1). What the proposal does not tell you is what that certainty costs:
  • The risk premium. A competent supplier prices the tail into the quote. You pay for the average overrun whether it happens or not. Suppliers who do not add a premium are either very sure of the scope or have not understood it.
  • The specification you must write. A fixed price is only as fixed as the document behind it. Producing a specification that a stranger can price and test takes weeks of your best people's time, and it is usually underestimated more than the software.
  • The change-request economy. Every gap and every new idea becomes a priced change, negotiated one at a time from a position where you cannot switch supplier. Some agencies win fixed-price bids low and make their margin on changes.
  • The quality squeeze. When the supplier starts losing money, the first things to go are the ones you cannot see in a demo: automated tests, documentation, security hardening, refactoring. You inherit the bill later as maintenance cost.
  • Adversarial incentives. On every ambiguous line, the supplier's interest is the cheapest reading and yours is the richest. The relationship turns into contract interpretation at the moment you most need collaboration.
Fixed price works well for things that have been built many times before and can be described completely: a data migration with a known source and target, a website with defined templates, an integration against a documented API, a clearly bounded internal tool. It works badly for anything where users, the market or a regulator will teach you something during the build.

Michele's take

When an agency gives me a fixed price for a product it has studied for an hour, I read it as a bet, not a price. The question is not whether the number is low but what the supplier will do on the day it realises it is losing that bet. In my guide to software development outsourcing I estimated that only a minority of software projects are truly suited to fixed price; nothing I have seen since has changed my mind.

What Time and Materials Needs From You

Time and materials is the honest model for work you cannot fully specify: you pay for the effort actually spent, the supplier has no reason to inflate the estimate or to fight your changes, and you can reprioritise every week. Its weakness is just as clear. In the words of the US rules, a time-and-materials contract provides no positive profit incentive to the contractor for cost control or labor efficiency, which is why appropriate surveillance of the contractor's performance is required (FAR 16.601). In a private contract that surveillance is your job, and it needs:
  • A product owner with authority on your side, who can say yes and no to scope within days, not weeks.
  • A weekly burn report showing hours by person and by feature, compared with the estimate for that feature.
  • A prioritised backlog so that if the money runs out, it runs out after the most valuable things are done.
  • A shared definition of done, including tests, review and deployment, so that hours buy finished work and not demos.
  • The right to see and change the team: who is billing, at which seniority, and the option to replace someone who is not productive.
  • A ceiling with an early warning, so that the burn never becomes a surprise in the monthly invoice.
If you cannot provide the first two, do not sign pure time and materials. You will pay for activity rather than progress, and you will not know until it is too late. Either name an owner first, or use a capped model and a fixed-price discovery until you can.

The Scope Certainty Test

Here is the test I use. Answer five questions about the work you are buying, honestly, and count the yes answers. It takes twenty minutes with the person who will own the project, and it settles most of the debate before anyone negotiates rates.
  1. Testability: could you write acceptance criteria today for at least four fifths of the scope, precise enough that two people would agree whether each one is met?
  2. Stability: will the requirements survive contact with real users, or is part of the point of the project to learn what users need?
  3. Integrations: are the systems you must connect to known, documented and accessible, with test environments the supplier can use from week one?
  4. Comparables: has the supplier, or anyone you can ask, delivered something substantially similar that the price can be checked against?
  5. Freeze tolerance: can the business live with the scope frozen for the duration of the contract without losing something important?
Yes answersContract modelWhat to do first
5 of 5Fixed price for the whole deliverableInvest in the specification and the acceptance tests; check the supplier can absorb a bad overrun
3 or 4 of 5Fixed price per phase, or capped time and materialsCut the work into releases of a few weeks; fix price or cap each one, and fix the 'no' answers in the first phase
0 to 2 of 5Time and materials, after a paid discoveryBuy a 2-to-6-week discovery at a fixed fee; repeat the test at the end of it
The questions are not arbitrary. Testability and comparables are the same conditions the US rules set for fixed price: reasonably definite specifications and reasonable comparisons with prior purchases (FAR 16.202-2). Stability and freeze tolerance are about your business, which is why no supplier can answer them for you. Integrations are where most fixed prices I have seen break, because the supplier priced the API it was promised, not the one it found.

The Hybrid That Usually Wins: Discovery, Then Phased Commitments

Most business software scores three or four on the test. For those projects the structure that protects both sides is a sequence, not a single model:
  1. Paid discovery at a fixed fee (2 to 6 weeks). The output is a backlog with acceptance criteria, an architecture, an integration map with real access tested, and an estimate with a range. You own all of it and can take it to another supplier.
  2. First release on fixed price per phase or capped time and materials. Short phases, each with its own price or ceiling and its own acceptance. The risk of each phase is small enough for the supplier to carry honestly.
  3. Evolution on time and materials or a dedicated team. Once the product is live, the scope is decided by users and data every sprint; a fixed price at this stage only adds friction.

“Customer collaboration over contract negotiation.”

— Manifesto for Agile Software Development · 2001

The manifesto line is often quoted as an argument against fixed price. I read it differently: the contract should make collaboration cheap and negotiation rare. Short phases do exactly that. For startups the same logic applies at a smaller scale; if you are pricing a first version, start from what an MVP really costs and buy the discovery before you buy the build.

Which Model for Which Situation

SituationModel I would chooseWhy
MVP for a funded startupFixed-fee discovery, then capped T&MLearning is the purpose; the cap protects the runway
Replacing a legacy core system in a bank or insurerFixed price per phase with acceptance per phaseBudget approval needs numbers; hidden legacy rules make a single fixed price fiction
Project with a hard regulatory deadlineFixed price on a narrowly specified scope, T&M for the restThe deadline scope can be specified; everything else should not hold it hostage
Integration against documented third-party APIsFixed priceScores 5 of 5 when access and test environments are real
Ongoing product developmentDedicated team or T&M with a monthly ceilingScope changes every sprint by design
Data migration or bounded internal toolFixed priceBuilt many times before; source, target and rules are known
Location changes the economics but not the logic. A supplier in your own time zone and legal system makes time and materials easier to supervise and disputes easier to resolve, which is one of the practical arguments I made in nearshore software development for EU and UK companies.

Contract Clauses That Protect Your Budget in Either Model

  • A ceiling with notice: the supplier must warn you in writing when 75% of the cap or phase budget is consumed, with a forecast to completion.
  • A change-control procedure: every change request priced within a fixed number of working days, with its impact on the timeline, and nothing billable without written approval.
  • Acceptance criteria and a test period: what 'done' means for each deliverable, how long you have to test it, and what happens if it fails.
  • Payments tied to working software: milestones paid on accepted releases, not on elapsed time or delivered documents.
  • Repository and environment access from day one: the code lives in a repository you own or can read at any time.
  • Termination for convenience with handover: you can stop at the end of any phase, paying for accepted work, and receive code, documentation and credentials.
  • Named key people and a rate card: who will do the work, at which seniority, at rates fixed for at least twelve months.
  • Intellectual property on payment: rights to the code you paid for transfer to you, with a list of third-party components and their licences.

Red flags in a proposal

A fixed price for a complex product after a single call. No assumptions or exclusions listed. A change-request rate higher than the rate implied by the main quote. Milestones paid on documents rather than working software. No access to the code until final payment. A time-and-materials proposal with no estimate at all, or with a team whose names and seniority are not stated.

What the Law Says When Things Go Wrong

Most software contracts are governed mainly by what the parties wrote. But when the contract is silent, the general rules of the applicable law fill the gap, and they treat lump-sum and measured work differently. A few examples from the jurisdictions where I work most:
JurisdictionRuleWhat it means for you
United States (federal procurement)FAR 16.202-1: firm fixed price not subject to any adjustment. FAR 16.601: T&M needs a ceiling price the contractor exceeds at its own riskEven the public sector caps time and materials; you should too
ItalyCivil Code art. 1661: the client may order variations up to one sixth of the agreed total price. Art. 1664: unforeseeable cost changes above one tenth allow a revision of the part exceeding one tenthA fixed price is not frozen by default; agree in writing how changes and revisions work
SpainCivil Code art. 1593: a contractor on a lump-sum price (ajuste alzado) cannot ask for more because wages or materials rose, only for plan changes the owner authorised. LCSP art. 309: public service contracts may be priced by units of time or a lump sumChanges you approve informally can reopen the price; document every approval
Saudi ArabiaCivil Transactions Law (in force December 2023) art. 470: on measured work the contractor must immediately notify a significant increase in quantities. Art. 471: no extra payment for work needed to deliver the agreed designRequire early written notice of overruns in the contract, whatever the model
Two caveats. These rules were written mainly for construction and public procurement, and courts apply them to software by analogy, not automatically. And none of them replaces a contract that states the model, the cap, the change procedure and the acceptance criteria. Have your lawyer read the commercial schedule, not only the liability clauses.

Mistakes I See Repeatedly

  • Choosing the model before the scope. The model is a consequence of the Scope Certainty Test, not a policy.
  • Comparing a fixed price with a T&M estimate as if they were the same number. One includes a risk premium and excludes changes; the other does the opposite.
  • Signing time and materials without an owner. Nobody steers, the burn becomes the plan.
  • Buying a fixed price to avoid managing the supplier. You will manage it anyway, through change requests and disputes.
  • Skipping discovery to save a few weeks. The weeks come back as months of rework.
  • Setting a cap with no warning threshold. Work stops at the cap, usually just before the release.

A 30-Day Plan Before You Sign

  1. Days 1–3: name the owner. One person on your side with authority over scope and budget, and the time to use it.
  2. Days 4–7: run the Scope Certainty Test with that owner and write the answers down with the evidence for each yes.
  3. Days 8–12: choose the structure. Five yes: fixed price. Three or four: phases or a cap. Fewer: discovery first.
  4. Days 13–20: ask two or three suppliers to quote the same structure, with assumptions, exclusions, team names and the change-request rate.
  5. Days 21–26: compare like with like. Normalise the quotes for risk premium, exclusions and changes; check references on a project of similar size.
  6. Days 27–30: negotiate the clauses, not just the price. Ceiling with notice, change control, acceptance, repository access, termination with handover.

Conclusion

Fixed price versus time and materials is not a question of which model is safer. It is a question of matching each risk to the party that can control it. If you can specify and test the work and freeze it, a fixed price buys you real certainty and is worth its premium. If you cannot, a fixed price buys you a negotiation; pay for the hours instead, steer them every week and cap them. And for the large middle ground, buy a short discovery, commit in phases and let the evidence of each phase set the price of the next.

If you want a second opinion

I review development proposals and contract structures for CFOs, CIOs and founders before they sign: the Scope Certainty Test on the real project, a like-for-like comparison of the quotes, and the clauses worth fighting for. Sometimes the answer is that the fixed price on the table is a good deal.
Still deciding whether to build the software at all? The five-question score in my build vs buy software framework comes before any contract model.

AI-ready answers

Frequently Asked Questions

When should I choose fixed price instead of time and materials for software development?+

Choose fixed price when you can write testable acceptance criteria for most of the scope today, the requirements will not change during the build, the integrations are documented and accessible, comparable projects exist to check the price, and the business can live with the scope frozen. If all five hold, a fixed price buys real budget certainty. The US federal rules use similar conditions: FAR 16.202-2 considers firm fixed price suitable with reasonably definite specifications and a fair price establishable at the outset.

What are the hidden costs of a fixed-price software contract?+

A competent supplier prices the risk of overrun into the quote, so you pay a risk premium whether or not the overrun happens. You must also write a specification precise enough to price and test, every gap becomes a priced change request, and a supplier that starts losing money tends to cut tests, documentation and refactoring first. Overruns are common: Flyvbjerg and Budzier (HBR, 2011) found a 27% average cost overrun across 1,471 IT projects, with one in six overrunning by 200% on average.

How do I protect my budget in a time and materials contract?+

Name a product owner with authority on your side, require a weekly burn report by person and feature, keep a prioritised backlog, agree a definition of done that includes tests and deployment, and set a ceiling with written notice when 75% is consumed. A capped time and materials contract, also called not-to-exceed, shares the risk: you pay actual hours up to the cap and the supplier carries the excess. Even US federal procurement requires a ceiling price on time and materials contracts (FAR 16.601).

Independent contract review

About to sign a development contract?

I help CFOs, CIOs and founders choose the contract model from the real scope, compare quotes like for like and negotiate the clauses that protect the budget. No agency to sell you on: sometimes the right answer is the fixed price already on the table.

Let’s Talk