IT Outsourcing Offshore Development Software

Fixed Price vs Time and Materials: How to Choose for Software Projects

10 min read
Fixed Price vs Time and Materials: How to Choose for Software Projects

Buyers usually treat fixed price vs time and materials as a question about money. It is closer to a question about who carries the risk of not knowing. A fixed-price contract asks the vendor to carry the cost of everything the spec missed. A time-and-materials contract leaves that cost with you, and gives you the freedom to change your mind in return. Neither is cheaper by default. The cheaper one is whichever matches how much you know about the software today.

This guide covers what each contract fixes and what it leaves open, where the risk lands, a short decision rule, the hybrid structures most software work ends up using, and how to read each kind of quote. We are a software company in Hanoi and we work under both structures. What we care about is a contract that fits the project.

What each contract actually fixes

The clearest definitions come from the US Federal Acquisition Regulation, which has spent decades turning these ideas into rules. Under FAR 16.202-1, a firm-fixed-price contract sets "a price that is not subject to any adjustment on the basis of the contractor's cost experience." The contractor carries "maximum risk and full responsibility for all costs." A time-and-materials contract, defined in FAR 16.601, pays for direct labor hours at fixed hourly rates plus the actual cost of materials.

So a fixed-price deal fixes the price and the scope together, while a T&M deal fixes the rate and nothing else. The rest of the comparison follows from that.

Fixed price Time and materials
What is fixed Price and the scope it buys Rate per role. Total spend moves with effort.
Who absorbs a wrong estimate The vendor, until someone raises a change request You
How change works Change request, re-estimate, contract amendment Reorder the backlog. The next sprint picks up the change.
What you manage Acceptance against the spec Priorities, progress and the burn rate
Admin effort Heavy up front (spec, acceptance criteria), light during Light up front, steady during
Typical fit Defined deliverable, stable requirements Discovery, evolving product, ongoing work

Where the risk goes in each model

Fixed price moves cost risk to the vendor, and the vendor prices it in

A vendor who signs a fixed price adds contingency for what the spec does not say. Your quote then includes the vendor's estimate of uncertainty, and you pay for it whether or not the uncertainty shows up. Behavior matters more than the contingency. Once the price is locked, every gap in the spec turns into a negotiation. Is a forgotten edge case a defect, which the vendor fixes for free, or a new requirement, which needs a change request? A spec that is only mostly clear produces a steady stream of those arguments.

The FAR calls fixed price suitable when work rests on "reasonably definite functional or detailed specifications" (FAR 16.202-2). For software, that is a high bar. A Figma file is not a specification, and neither is a list of user stories without acceptance criteria.

T&M leaves cost risk with you, so you need oversight

The FAR is blunt about the other side. A T&M contract "provides no positive profit incentive to the contractor for cost control or labor efficiency," so the buyer needs "appropriate surveillance" of performance (FAR 16.601). In software terms, someone on your side has to compare what each sprint delivered with what it cost, and decide whether the next one is worth buying.

What you get in return is flexibility. The Agile Manifesto lists "customer collaboration over contract negotiation" and "responding to change over following a plan" among its four values. T&M lets a team work that way, because a change of direction costs a backlog edit instead of an amendment.

Fixed price vs time and materials: what each contract fixes and who carries the cost of a wrong estimate

The question that decides it: can you write the acceptance tests today?

A list of pros and cons rarely settles this. One question usually does: could you, right now, write the tests that would prove the software is finished? We mean the tests, not the code. For example: "A user can reset their password by email, the link expires after a set time, and the old password stops working."

If you can write those tests for the whole scope, fixed price is workable and often the cleaner choice. If you can write them for only part of the scope, split the work. If you cannot write them yet, a fixed price is a bet on someone's guess, and the vendor will price the guess conservatively.

Three more checks narrow it down:

  1. Do you have a product owner with time? T&M needs one person on your side who sets priorities every sprint and accepts finished work. Without that person, T&M drifts. Fixed price needs less of their time during the build and much more while the spec is written.
  2. Will the scope change after users see it? Products that face real users almost always change. Internal tools that replace a known process often stay put.
  3. How does your budget get approved? Some finance teams can only sign a number. That pushes toward fixed price or a capped T&M arrangement, covered below.

Decision tree for fixed price vs time and materials, starting from whether you can write the acceptance tests today

Hybrid structures that most software work ends up using

Pure fixed price and pure T&M are the two ends. Most real contracts sit somewhere between them.

T&M with a cap

The FAR requires a cap for government work: a T&M contract must include "a ceiling price that the contractor exceeds at its own risk" (FAR 16.601). Commercial software contracts usually call the same idea a not-to-exceed amount. You keep the flexibility of paying for effort, and the vendor commits to raising a flag before spend reaches the ceiling. A cap limits spend. It does not guarantee the team finishes the scope within it, so agree in advance what happens when the team gets close.

Fixed-price discovery, then a T&M build

A short, fixed-scope discovery phase produces what a fixed price needs: user flows, acceptance criteria, an architecture outline and an estimate. After that, the build can run on T&M with a far better forecast, or you can price parts of it fixed because they are now defined. Our offshore development center process starts the same way, with discovery and requirements before we form a team.

Fixed price per milestone

Here you cut the project into releases and price each release once the previous one is accepted. Each fixed price then rests on what the team learned building the last release. This works when the product can ship in meaningful slices.

A dedicated team on monthly capacity

For long-running products, the contract stops being about a project at all. You pay for a team's capacity each month and steer it through the backlog. It is T&M in spirit, with a stable team in place of a count of hours. We compare the people-based models in ODC vs dedicated team vs staff augmentation.

Four hybrid contract structures: T&M with a cap, fixed discovery then T&M, fixed price per milestone, monthly team capacity

How to read a fixed-price quote

A fixed price is only as good as the scope document behind it. When a fixed-price quote reaches you, from us or from anyone else, read these parts before the total:

  • The scope list. Does each feature come with acceptance criteria, or only a name? "User management" is a heading, not scope.
  • The assumptions. Every fixed quote rests on assumptions about integrations, data volumes, environments and who supplies content. Each one becomes a change request if it turns out wrong.
  • The change process. Who estimates a change, who approves it, and does work stop while it is priced?
  • Acceptance. Who tests, against what, within how many days, and what happens if you do not respond in time?
  • The warranty. How long after acceptance does the vendor fix defects at no charge, and how do you tell a defect from a change?

How to read a T&M quote

A T&M quote needs a different reading, and the rate card tells you the least.

  • The team plan. Which roles, at what allocation, for how long? A senior engineer at half time and a junior at full time produce very different results for similar spend.
  • The estimate and its range. A good T&M proposal still estimates the total and says how confident it is.
  • Reporting. What do you see each week: hours by person, work completed, budget burned against the estimate?
  • Control points. When can you resize the team, pause or stop, and what notice does each need?
  • The cap. Is there a not-to-exceed amount, and what happens as spend approaches it?

When you set an offshore quote of either kind against hiring at home, compare whole costs on both sides. Our comparison of software development cost in Vietnam vs the US, UK and Australia shows how salary, benefits and overhead add up, using public market data.

What changes when the team is offshore

Distance changes how each contract behaves. Under T&M, you pay for a slow answer in idle hours, so the product owner's availability matters more. Hanoi is on GMT+7. Singapore is an hour ahead and Sydney three or four hours ahead depending on the season, so decisions can happen inside a shared working day. From the US the overlap is thin. Written specs and a fixed daily call matter more there, and a vendor-side product lead is worth having.

Under fixed price, distance raises the stakes of the spec. A requirement you would clear up in a hallway conversation at home becomes a change request across time zones. Write down more than you think you need.

How we work under each model

At MOHA, a well-defined deliverable is a custom software development project with an agreed scope. Long-running product work runs as a dedicated development team or an offshore development center, where you pay for a team's capacity and set its priorities. When the scope is not settled yet, we build a prototype early and start full development once your requirements are confirmed, which keeps later changes small.

Draco Help shows what a well-bounded job looks like. It is a Romanian safety app that a MOHA team of three moved from Vue Native, which its creators had stopped supporting, to React Native. A migration with a known starting point and a clear finished state is the kind of work where you can write acceptance tests up front. Open-ended product development, where the next feature depends on what users did with the last one, belongs on a capacity model.

FAQ

Is fixed price cheaper than time and materials?

Not by default. A fixed price includes the vendor's allowance for uncertainty, and a T&M total depends on how well someone steers the work. For well-defined scope, the two often land close together, and fixed price needs less admin. For unclear scope, contingency and change requests usually make fixed price the more expensive path.

Can we switch from fixed price to T&M mid-project?

Yes, and teams often do when a fixed-price project hits a large change. Close out the fixed scope that was delivered and accepted, then continue the rest on T&M or a capacity model with the same team, so the context stays with the people who have it.

What is a not-to-exceed amount?

It is a ceiling on total T&M spend. The vendor bills for effort up to the ceiling and has to raise the issue before going past it. It caps your exposure without fixing the scope.

Talk to us about your project

If you know what you want to build and how settled the requirements are, you have enough to pick a contract structure. Contact us to discuss your project and which model fits it.

Contact us

Emily
Related Articles
AI Digital Transformation Software
AI IT Outsourcing Offshore Development
We got your back! Share your idea with us and get a free quote