Fixed price vs time and materials for a software development project

Content authorBy Lincoln WoolseyPublished onReading time10 min read
A person examines software development documents at a metallic desk, surrounded by a softly blurred office in warm natural light.

Fixed price feels safe and time and materials feels flexible, but neither tells you what you’re committed to when the brief changes. Compare three ways to buy bespoke software: fixed price, time and materials, and a sequence of capped phases. For each, see what it commits you to and how an unplanned requirement plays out in practice. Then settle a short list of questions before you sign anything, while you can still change the terms.

Fixed price vs time and materials

The choice between fixed price vs time and materials is framed as a question about cost. Fixed price vs time and materials is a question about who carries the risk that the work turns out to be bigger than anyone thought, and who has authority to decide what happens next.

Three terms get confused. An estimate is a forecast and binds nobody. A ceiling is the most you've authorised someone to spend. A contractual commitment is a price your supplier is obliged to honour whatever the work costs them to deliver.

Fixed price software development only works when scope is bounded in writing and acceptance criteria say what "done" means. Time and materials contract software development needs spending controls instead, because the commitment is to a rate rather than an outcome. Capped phases limit what you've authorised at any one point without pretending the unknowns have gone away.

Choose by project conditions

Bright orange background with horizontal sections featuring white line icons and text blocks on decision-making and budget management.

Five conditions decide the fit, and none of them is the headline number. Start with how certain the scope is. Martin Fowler of Thoughtworks calls the belief that a signed scope caps your exposure a mirage, because the obligation is only as good as the specification behind it.

Then look at the rest:

  • Technical unknowns. Integrations with systems nobody has documented and data you haven't profiled, along with anything dependent on a third party's behaviour.

  • Feedback needs. If the thing being built has to be shown to users before the requirements settle, a locked specification will fight you.

  • Budget tolerance and the approval limit attached to it. A capital budget signed off once a year behaves differently from an operating budget reviewed monthly.

  • Who can actually decide. A model that needs weekly decisions fails if the only person who can make them is available quarterly.

Standish Group's CHAOS data found small projects succeeded 61% of the time against 6% for the very largest, which is the strongest practical argument for breaking work into pieces you can price honestly. Fixed price software development suits bounded, well-understood work. Time and materials contract software development suits work where the answer changes what you build next.

One more thing to settle first. The person who chooses the delivery method and the person who owns the budget have to be in the same conversation on fixed price vs time and materials before the model is picked, because every model below assumes a named approver with a known limit.

One change, three outcomes

Here's the project, described identically to three suppliers: a customer portal that exchanges order data with an existing enterprise resource planning (ERP) system. Scope covers the portal and the integration, along with user acceptance testing. The price and the dates look comparable across all three proposals.

Four weeks in, the integration work turns up something nobody wrote down. Order records in the ERP use a legacy product coding scheme, and roughly a third of them need mapping rules before the portal can display them correctly. A fact has surfaced. What happens next is the whole of fixed price vs time and materials, and the difference shows up in scope and approvals.

PMI's 2018 survey of 4,455 practitioners found 52% of projects experienced scope creep or uncontrolled change. The discovery itself is normal. The handling is what varies.

Ready to bring your ideas to life?

Book a free 30-minute discovery call with our team — we'll understand your objectives and advise how bespoke software, MVP development, or an extended team can help your business.

Fixed price software development

The first question is whether data mapping sits inside the written scope. If the specification says the integration covers order retrieval and the acceptance criteria describe a portal that displays orders accurately, there's a reasonable argument that mapping is included and the supplier absorbs the effort. If the specification is silent, it isn't included.

Where it falls outside, you get a change request. Someone prices the extra work and someone with authority approves it, so the contract price moves. The schedule moves too, because fixed price software development plans the sequence tightly and inserted work pushes everything behind it.

That's the honest trade in fixed price vs time and materials. You bought certainty about a defined thing, so anything outside the definition needs a decision before work continues. Which means the quality of your exclusions list matters more than the quality of the price.

Time and materials contract software development

Under time and materials, the mapping requirement goes into the backlog like any other item and gets estimated. No contract variation is needed. The forecast changes instead, because the hours reported against the project now point at a different total.

That's only safe if the controls are written down. Time and materials contract software development without them is an open tab, and fixed price vs time and materials becomes a genuinely unfair comparison. What should be in the agreement:

  • Burn reporting at a stated frequency, showing hours used and hours remaining against the forecast, along with what changed since the last report.

  • An approval threshold, so any item above an agreed size needs your sign-off before anyone starts it.

  • A stop-work trigger at a defined percentage of the budget, where work pauses until you authorise more.

  • A named approver on your side with a known spending limit.

Acceptance in this model happens continuously rather than at the end, which is why the reporting has to be good enough to act on.

Capped delivery phases

A capped phase commits you to a ceiling for a defined slice of work and nothing beyond it. The Cabinet Office guidance for government buyers makes the same point about managing commercial exposure through fixed-price sprints "contracted for in phases rather than contracting for the entirety of the requirement on a fixed-price basis at the outset". Central government buys this way in practice through statements of work priced as capped time and materials on the Digital Outcomes framework.

The mapping discovery lands differently here. The work either fits inside the current phase ceiling or it doesn't. If it fits, it's delivered and the knowledge feeds the next phase estimate, which is the point of the discovery phase described in the GOV.UK Service Manual.

If it threatens the cap or a milestone date, you have a decision. Defer the mapping to the next phase or raise the ceiling, with the option to drop something else from this one. Fixed price vs time and materials leaves that decision implicit. Capped phases force it into the open on a schedule.

Show the cost calculation

Numbers make this concrete. A piece of work estimated at 100 hours, charged at £80 per hour, comes to £8,000. An approved change of 20 hours adds £1,600 and brings the total to £9,600.

These figures are illustrative. They aren't Evolved Ideas rates or market benchmarks, and they exclude tax. UK supplies of professional services carry the standard VAT rate of 20%, so your actual commitment is the net figure plus whatever tax treatment applies to your organisation and jurisdiction.

The important part isn't the arithmetic. Under time and materials contract software development, that £1,600 only becomes real when someone with authority approves it, and no calculation of this kind authorises anyone to exceed a cap. A ceiling is a hard limit.

Ready to bring your ideas to life?

Book a free 30-minute discovery call with our team — we'll understand your objectives and advise how bespoke software, MVP development, or an extended team can help your business.

Compare contract controls

Price is the least interesting clause in the agreement. These are the ones that determine what actually happens when the project meets a surprise. The McKinsey and University of Oxford study of more than 5,400 large IT projects found they ran 45% over budget on average while delivering 56% less value than predicted, and most of that damage is governed by clauses like these rather than by the rate card.

ControlFixed priceTime and materialsCapped phases
AssumptionsWritten into the specification and pricedStated in the estimate, revised as facts emergeRestated at each phase
ExclusionsThe single most important list in the contractLess critical, since work is authorised item by itemDefined per phase
DependenciesNamed, with dated consequences if lateBillable time continues while you're blockedCan consume the phase ceiling
Client responsibilitiesAccess, data, sign-off windowsSame, plus attendance at reviewsSame, plus the phase gate decision
ContingencyHeld by the supplier inside the priceHeld by you, outside the forecastHeld by you, between phases
ReportingMilestone progressBurn against forecast at stated intervalsSpend against the ceiling
ChangesFormal change request, priced and approvedBacklog item above an approval thresholdAbsorbed, deferred or escalated
MilestonesPayment triggersReview pointsPhase gates with a stop decision
OwnershipAssignment on paymentAssignment on paymentAssignment per phase
TerminationUsually for cause or convenience with noticeNotice period and payment for hours workedAt any phase boundary
HandoverDefined deliverables at acceptanceAgreed documentation and knowledge transferAt the end of each phase

Fixed price software development lives or dies on the exclusions row. Before signing, settle the currency and the actual rates, along with the tax treatment that applies to you.

Ownership deserves a second look. Under section 11 of the Copyright, Designs and Patents Act 1988, the author of a work is its first owner, and paying for software doesn't by itself move that. Assignment has to be written.

Discovery and feedback

Most of the risk in fixed price vs time and materials comes from one gap: the business knowledge sits in your head and the delivery plan sits in someone else's. Workshops close that gap before money is committed. Our technical discovery and scoping work exists to turn what you know into work somebody can plan and price.

On conveybuddy, a platform connecting mortgage advisers with conveyancing firms, Evolved Ideas ran a series of workshops in January 2024 to translate the founder's industry knowledge into actionable insights, then delivered in sprints with regular feedback. Harpal, the founder, described the effect in the published case study: "with any project nothing is going to go perfectly, but this approach lets you identify gaps quickly and correct misunderstandings before they derail the project."

That's a statement about visibility. Workshops and iterative delivery surface the data-mapping problem in week four instead of week twenty. They don't guarantee a cost outcome, and nothing here implies particular pricing or availability.

Review before signing

Whether any of these controls bite depends on the agreement you actually sign and the law governing it. A stop-work clause that no one defined a trigger for is decoration. An approval threshold with no named approver is worse, because it looks like a control.

Fixed price software development carries specific exposure in the acceptance and change clauses. Time and materials contract software development carries it in reporting and termination. Flyvbjerg and Budzier's analysis of 1,471 IT projects in Harvard Business Review found one in six overran by 200% on average, and contracts are where that tail risk is allocated.

Have qualified legal and commercial advisers review the real terms in front of you. No article can tell you what your clauses mean.

Discuss the right fit

Scope certainty and the named decision owner decide the model, along with the approval limit. The headline number doesn't. Tell us where the unknowns sit in your project and who signs off spend, and we'll set out how we'd structure the work and why.

Any commercial arrangement remains subject to the terms Evolved Ideas actually offers. Speak to our team about scope, approvals and whether fixed price vs time and materials suits what you're building.

Ready to bring your ideas to life?

Book a free 30-minute discovery call with our team — we'll understand your objectives and advise how bespoke software, MVP development, or an extended team can help your business.

Compare the assumptions, exclusions, payment schedule, tax treatment, hourly rates for changes, acceptance process, and handover duties. Two proposals can show the same total while allocating different costs and responsibilities. Ask each supplier to price the same deliverables and state what happens when a dependency or approval is late.

Read the deliverables and acceptance criteria together, then check whether they describe the outcome your users require. The phrase fixed price vs time and materials matters less than the scope behind it. Review assumptions, exclusions, integrations, data handling, testing, and change rates before treating the quoted amount as a commitment.

Use discovery first when the project depends on undocumented systems, unfamiliar data, or unsettled user needs. A useful discovery should produce a prioritised backlog, recorded technical risks, agreed assumptions, and a decision about the next phase. That evidence gives you a better basis for a price or spending ceiling.

Yes, the contract can allow charges when a client delay prevents scheduled work, especially under time and materials. The agreement should identify required access, information, and review dates, then state the effect of a missed dependency. Ask for prompt notice before billable time accumulates and record revised dates in writing.

The supplier generally carries that extra cost when the work remains within the written scope and acceptance criteria. The client should still check whether an assumption or exclusion changes the position, because vague wording can create a dispute. Evolved Ideas can discuss the project structure. Contact us at https://evolved-ideas.com/contact-us/.

Schedule a Discovery Call

Book a free 30-minute call that works for you

You Might Also Like

Discover more insights and articles

A close-up of hands writing on documents at a wooden desk, surrounded by colorful post-it notes and a softly glowing laptop.

Membership website development: connecting members, events and CRM

An association’s public site and member portal often fail in the same way: they work on their own, but they no longer talk to the membership, payment, and event systems around them. Replacing either one is easier to commission when you start from seven requirements. Use them to set the scope first, then organise procurement around them, so every supplier responds to the same brief and the integration problems that prompted the replacement stay at the centre of the decision.

A focused programmer types on a laptop at a sleek black desk in a modern office, surrounded by multiple monitors displaying code.

Software intellectual property: 7 ownership questions before you sign

Paying for bespoke software does not automatically mean you own it, and the gaps usually surface when the relationship ends. Before you sign, settle seven questions about software intellectual property with your development partner and with qualified legal counsel. They establish what transfers to you, and what you need in practice to keep the system running if the partnership ends, such as source code, documentation, and access to the environments it runs in.

A business professional focused on coding at a sleek black desk in a modern office with natural lighting and an exposed brick wall.

5 .NET development companies for established applications

Choosing a firm to look after an established, business-critical .NET application is a risk decision, and the case studies on a supplier’s website rarely settle it. Five companies that work on this kind of system are reviewed here against their published case evidence, so you can see what each one has demonstrably done. A set of due-diligence questions and a controlled trial brief then let you test any of them, including firms not on the list, before you hand over the application.

A lively outdoor scene with more people interacting, enjoying the atmosphere, and engaging in various activities.

Software maintenance costs: what to include beyond the monthly retainer

A support proposal for live software can look reasonable on the first page and still hide the real commitment in the clauses around it. Read it line by line so the annual cost is visible before you sign. Separate what you’re buying access to, such as response times, coverage, and named expertise, from what you’ll pay to leave, including notice periods, handover work, and renewal terms.