Skip to content
DT Nova

Fixed price vs time and materials: choosing the contract model for a software project

Fixed price vs time and materials is the first commercial question in most software projects. One model fixes the total and the scope; the other pays for the work as it is done. Neither is right for every project. This guide explains how each model works, who carries which risk, the hybrid models in between, decision criteria, and the contract terms to check whichever you choose.

The short version

  • Fixed price moves the overrun risk to the supplier and freezes the scope.
  • Time and materials keeps the scope flexible and leaves the overrun risk with the client.
  • Fixed price needs a scope precise enough to price. If that does not exist yet, buy a discovery phase first.
  • Hybrids are common: fixed discovery, then capped time and materials sprints.
  • Ownership, acceptance and exit terms matter more than the pricing model.

Definitions

Fixed price (or fixed fee, lump sum): the supplier commits to deliver a defined scope by an agreed date for an agreed total, usually paid in milestones. If the work takes longer, the supplier absorbs it. If the client wants something outside the scope, a change request with its own price follows.

Time and materials (T&M): the client pays for the hours actually worked, at agreed rates per role, plus materials such as licences, hosting or third-party services. The scope can change at any time. The client steers by setting priorities and watching the budget.

Fixed price vs time and materials side by side

AspectFixed priceTime and materials
Who carries overrun riskSupplierClient
ScopeFrozen in the contractCan change every sprint
Budget certaintyHigh, if the scope holdsLower, steered by caps and reports
Price includesA risk bufferActual hours only
Preparation neededDetailed specification before signingA clear goal and a prioritised backlog
ChangesChange requests, priced one by oneNew items enter the backlog
Client effortHigh before signing and at acceptanceSteady throughout: priorities and reviews
Typical tensionWhat exactly was in scope?Is the team working efficiently?

Why software makes fixed price hard

A fixed price needs a scope precise enough that both sides would price it the same way. In software, much of the real work is discovered while building: integrations behave differently than documented, users react to the first version, data turns out messier than expected. The Manifesto for Agile Software Development (2001) put it as valuing "customer collaboration over contract negotiation" and "responding to change over following a plan". Those values fit time and materials work more naturally than a frozen scope.

That does not make fixed price wrong. It means a fixed price is only as good as the specification behind it. Our software requirements specification guide shows what a priceable scope looks like.

Hybrid models

  • Fixed price discovery, then T&M. A short fixed phase produces requirements, designs and an estimate. The build then runs on time and materials, with the estimate as the yardstick.
  • Capped T&M (not-to-exceed). Actual hours are billed up to an agreed maximum per phase. Reaching the cap triggers a joint decision.
  • Fixed price per sprint or milestone. Each small slice gets its own fixed price once it is understood well enough.
  • Fixed budget, flexible scope. The total is fixed; the client chooses what to build within it, in priority order.

Our guide to software development methodologies explains how these fit agile and staged ways of working.

Decision criteria

  1. How well is the scope known? A detailed, stable specification points to fixed price. A goal with many open questions points to T&M.
  2. How likely is change? Products in a market, or processes still being designed, will change.
  3. Project size and length. Small, short projects can be fixed. Long ones rarely stay fixed without many change requests.
  4. Your budget process. Some organisations need a fixed amount approved in advance. A cap or a fixed budget with flexible scope can meet that need.
  5. Your capacity to steer. T&M needs a product owner on your side who sets priorities every week.
  6. Trust and track record. A first project with a new supplier often starts with a small fixed phase.

A quick scoring test

Score each statement from 1 to 5. The higher column total points to the better model; close totals point to a hybrid.

Points toward fixed pricePoints toward time and materials
We have a detailed, signed-off specificationWe know the goal, not every feature
The scope will not change during the projectWe expect to learn from users and adjust
The project is small and shortThe project runs many months or has no fixed end
We need one approved amountWe can approve a monthly or phase budget
We have little time to steer during the buildWe have a product owner who can prioritise weekly

Cost logic

We do not quote amounts here. The logic is the same in every market:

  • A fixed price equals the supplier's estimate plus a buffer for the risk it takes on. The less certain the scope, the larger the buffer.
  • Time and materials equals the hours actually worked. You pay no buffer, but you pay for every detour.
  • Change requests under a fixed price are priced one by one, often without competition.
  • Your own staff time counts in both models: writing the specification for fixed price, steering the backlog for T&M.

Our guide to custom software development cost covers what drives the hours, and the app development cost guide does the same for mobile projects.

Risks of each model

RiskFixed priceTime and materials
QualitySupplier cuts corners to protect its marginGold-plating features nobody asked for
ScopeDisputes over what was includedScope grows without anyone deciding it
BudgetMany change requests on top of the priceTotal cost unknown until the end
RelationshipEvery change becomes a negotiationDoubts about efficiency without good reporting

Contract checks for either model

  • Ownership. Under Article 2(3) of the EU Software Directive (2009/24/EC), the employer holds the economic rights to a program written by an employee in the course of their duties, unless the contract says otherwise. An outside supplier is not your employee, so the contract must transfer the rights or grant the licence you need.
  • Acceptance. Define how a delivery is tested and accepted. Under the Late Payment Directive (2011/7/EU), Article 3(4), national law must ensure that an acceptance or verification procedure between businesses lasts at most 30 calendar days from receipt of the work, unless the contract expressly agrees otherwise and this is not grossly unfair to the supplier.
  • Payment terms. Article 3(5) of the same directive sets 60 calendar days as the maximum payment period between businesses, with the same exception for express agreement.
  • Reporting. For T&M: hours per task and role, weekly or per sprint, against the budget or cap.
  • Exit. Source code, documentation and access handed over at any point, so you can continue with another team.

When fixed price is the right answer

  • A small project with a clear, stable scope, such as a defined integration or a website with agreed pages.
  • A discovery or prototype phase with a fixed length and agreed outputs.
  • A budget process that requires one approved amount, with a scope that can be described precisely.

When time and materials is the right answer

  • A product that will evolve with users and the market.
  • Work with many unknowns: legacy systems, messy data, new technology.
  • Ongoing development and maintenance with no fixed end.

Comparing quotes from several suppliers is easier when they price the same scope in the same model. Our guide on how to choose a software development partner covers that. Our software development service explains how we scope and run projects. Every guide is in the guides library.

Questions people ask

What is the difference between fixed price and time and materials?

In a fixed price contract the supplier delivers an agreed scope for an agreed total, and carries the risk of the work taking longer. In a time and materials contract the client pays for the hours actually worked at agreed rates, plus any materials or licences, and carries the risk of the work taking longer, but can change the scope freely.

Which is better for software development, fixed price or time and materials?

Fixed price suits small, well-defined projects where the scope will not change. Time and materials suits longer projects, products that will evolve and work with many unknowns. Many projects combine both: a fixed price discovery phase, then time and materials sprints with a cap or a budget alert.

Is fixed price really cheaper for the client?

Not necessarily. A supplier who carries the overrun risk adds a buffer to the price, and every change to the scope becomes a change request. Fixed price gives budget certainty, not a lower total. On a well-understood scope the difference can be small; on an uncertain one the buffer can be large.

What is capped time and materials?

Capped time and materials (sometimes called not-to-exceed) bills actual hours, but up to an agreed maximum for a phase. If the work is done in fewer hours, the client pays less. If the cap is reached, both parties agree what to drop, what to change or whether to extend.

Who owns the code in a fixed price or time and materials contract?

The pricing model does not decide ownership; the contract does. Under the EU Software Directive the employer gets the economic rights to programs written by its employees, but that rule does not cover an outside supplier. The contract should transfer the rights or grant the licence you need, whichever pricing model you choose.

Sources