Direct answer: A fixed-price contract locks in one total cost for a defined scope, shifting estimation risk onto the vendor. A time-and-material (T&M) contract bills actual hours at an agreed rate, shifting that risk onto you in exchange for flexibility. Neither is universally better — the right choice depends on how well your requirements are actually defined before work starts.
Who carries the risk, under each structure
Under fixed-price, if a feature turns out harder to build than estimated, that cost overrun is the vendor's problem, not yours — which is exactly why fixed-price quotes carry a built-in buffer for uncertainty. Under T&M, if a feature takes longer than expected, you pay for the extra time — but you also are not paying an inflated buffer upfront to cover uncertainty that may never materialize. Fixed-price sells certainty; T&M sells efficiency, if the scope stays reasonably close to what was expected.
When fixed-price is the right structure
Fixed-price fits work with a genuinely definable scope: a marketing website, a mobile app with a clear feature list, a defined internal tool. It requires real upfront specification work — a vague brief with a fixed price attached is a setup for disputes, not protection. See our guide to writing a software brief for how to define scope tightly enough to get an accurate fixed quote.
When time-and-material is the right structure
T&M fits ongoing product work, early-stage discovery where requirements are still being figured out, and situations where you genuinely want to change direction as user feedback comes in without paying change-order overhead every time. This tension is old and well documented: the Agile Manifesto explicitly values “customer collaboration over contract negotiation” and “responding to change over following a plan” — the two things a fixed-price contract is structurally designed to prevent. That is not an argument against fixed-price; it is a warning that if your project genuinely expects to change direction, a fixed-price contract will convert every one of those changes into a commercial negotiation rather than a development decision. T&M is the natural billing structure behind a dedicated development team, where the whole point is ongoing, flexible capacity rather than a single fixed deliverable.
The hybrid: T&M discovery, then fixed-price build
For larger projects, a common and low-risk structure is a short, capped T&M discovery phase to nail down the actual requirements, followed by a fixed-price contract for the build phase once scope is locked. This avoids paying a large fixed-price uncertainty buffer for requirements a two-week discovery sprint could have clarified for a fraction of the cost.
Protecting yourself under either structure
Under fixed-price: get milestones tied to specific, testable deliverables rather than calendar dates, and confirm the change-order process in writing before signing. Under T&M: get a monthly or sprint spending cap with a required check-in before it is exceeded, and regular, reviewable progress reporting rather than an invoice with no detail behind it. Under both: the IP ownership terms need to be explicit regardless of billing structure — see our NDA and IP ownership guide for what that clause should say.
For how we structure both models in practice, see the international hiring page.
Sources
External references behind the figures and claims on this page. Rate bands and vendor pricing move — check the source before quoting a number.
- Manifesto for Agile Software Development
Agile Manifesto authors
The stated preference for "customer collaboration over contract negotiation" and "responding to change over following a plan" — the two things fixed-price structurally resists.
Frequently Asked Questions
A fixed-price contract sets one total price for a defined scope before work starts — the vendor absorbs the risk if the work takes longer than estimated. A time-and-material (T&M) contract bills for actual hours or days worked at an agreed rate — you absorb the risk if the work takes longer than expected, but you gain the flexibility to change direction without renegotiating a fixed number.
Fixed-price is lower financial risk for a well-defined scope, because the total cost is locked in regardless of how long the vendor actually takes. It shifts estimation risk onto the vendor, which is exactly why vendors price in a buffer for uncertainty — you are paying for that certainty. T&M is lower risk only when the scope is genuinely expected to change, because it avoids the change-order friction and markup that comes with re-scoping a fixed contract mid-project.
Usually because the requirements are not specific enough to estimate responsibly — an honest vendor will say this rather than quote a number that will need constant change orders later. If a vendor gives you a confident fixed price for a vague, undefined scope, treat that as a warning sign rather than reassurance; it usually means the price will grow through change orders once work begins.
Yes, and it is a reasonable structure for larger projects: run a T&M discovery/design phase first to define the scope precisely, then convert to a fixed-price contract for the build phase once requirements are locked. This avoids paying a large fixed-price buffer for uncertainty that a short discovery phase could remove.
A change order documents a scope addition or change outside the original specification, along with its added cost and timeline impact, and requires written approval before work proceeds. A trustworthy vendor issues change orders transparently and explains exactly what changed in the requirement to justify it — repeated vague or frequent change orders on a project that seemed well-specified at the start is worth questioning.
A capped monthly or sprint budget with a check-in before exceeding it, regular time/progress reporting you can actually review (not just an invoice total), and a defined process for re-prioritizing scope if the budget is running ahead of expected progress. T&M without any spending visibility is the structure most likely to produce a bad surprise.