In the fixed price vs time and materials choice, neither contract protects you by default. Fixed price protects you when the scope is written down, stable and small, typically under 12 weeks of work. Time and materials with a monthly cap protects you when the product will change as you learn, which describes most new products.
Our position is simple. Most founders building something new should choose capped time and materials, after a short fixed-price discovery phase. CTOs with a tightly defined rebuild, integration or migration can use fixed price safely.
What each contract actually moves onto your side of the table
A contract type is a decision about who carries which risk. It is not a decision about who pays more. Once you see it that way, the choice gets easier.
- Fixed price: the agency carries the risk of cost overruns. You carry the risk that the scope was wrong.
- Time and materials (T&M): you carry the cost risk. You gain the right to change direction without renegotiating.
US federal buyers use the same logic. The Federal Acquisition Regulation, Part 16 reserves firm-fixed-price contracts for work with reasonably definite specifications. It allows time-and-materials contracts only when the extent of the work can't be estimated with confidence, and it requires a ceiling price. That ceiling is the part most private-sector T&M contracts forget.
A 30-minute discovery call is a quick way to see where the real risk sits in the contract on your desk before you sign it.
Fixed price vs time and materials, factor by factor
Delivery performance and quality
Under fixed price, the agency profits by finishing under budget. That pushes teams toward the narrowest reading of the spec, thinner tests and fewer refactors. Under T&M, the incentive flips: the team can spend a day fixing a flaky test suite without arguing about whose budget it comes from.
The trade-off is that T&M needs a client who reviews work weekly. Without that review, hours drift into polish nobody asked for.
Developer availability
Fixed-price projects are staffed to a plan. If the agency's estimate was tight, senior engineers often rotate off once the architecture is set. Juniors finish the build.
T&M lets you name the team and keep it. You can ask for one senior engineer at, say, 30 hours a week for six months, and see it on every invoice.
Cost
Fixed bids are not cheaper. Agencies add a risk buffer, typically 15 to 30 percent, to cover what they can't see yet. Change requests then add cost on top.
T&M has no buffer, so the base cost is usually lower for the same work. The danger is open-ended scope. A monthly cap, for example 400 hours or a set dollar ceiling, closes most of that gap.
Time to market
Fixed price front-loads time. A useful fixed bid needs a detailed spec, and writing one typically takes two to six weeks before any code ships. Every mid-project change then goes through a change-request cycle that can take days.
T&M can start building in week one and ship the first release earlier. That speed is only real if you prioritise ruthlessly, because nothing in the contract forces you to cut scope.
Ecosystem maturity
Both models are mature. Fixed price has decades of statement-of-work templates, milestone payment schedules and acceptance-test clauses behind it.
T&M caught up with tooling. Time tracking in Harvest or Toggl, tickets in Jira or Linear, and weekly burn reports give you the visibility that used to be missing. The Agile Manifesto made "customer collaboration over contract negotiation" the default for most product teams, and T&M fits that way of working.
Long-term maintenance
Fixed-price builds often hand over code that meets the spec but carries hidden debt. Shortcuts taken to protect margin show up later as slow releases and fragile tests. Maintenance is also a separate contract, so the team that knows the code may be gone.
T&M rolls naturally into a maintenance retainer with the same engineers. Expect to budget 15 to 20 percent of the original build cost per year for upkeep under either model.
Choose fixed price if, or choose time and materials if
Choose fixed price if
- You have a written spec with screens, user flows and acceptance criteria that both sides have signed.
- The work is bounded: a migration, an API integration, a rebuild of an existing app with known features.
- Your budget is truly fixed, for example a grant or a board-approved figure, and you would rather cut scope than overspend.
Choose time and materials if
- You are building a new product and expect to learn from real users after the first release.
- You want to keep the same senior engineers for six months or longer.
- You can give the team a decision-maker who reviews work and reprioritises at least once a week.
The outdated myth about each
Fixed price: "It caps my total spend"
It caps the price of the spec, not the price of the product. If the spec misses a payment edge case or an admin screen, that becomes a change request. On new products, final spend typically lands 20 to 50 percent above the original bid once changes are counted.
Time and materials: "It's a blank cheque"
That was true when invoices said "160 hours" and nothing else. A modern T&M contract can include a monthly ceiling, ticket-level time logs and a right to stop with two weeks' notice. With those three clauses, your exposure is one month of spend, not the whole project.
The mistake teams make most often
The most common mistake is signing fixed price for a product that has no real spec. A founder has a pitch deck and some wireframes. The agency quotes a fixed number to win the deal.
By month two, both sides are arguing about whether a feature was "in scope". The agency protects its margin. The founder feels nickel-and-dimed. The product suffers either way.
The reverse mistake is rarer but costly too. Teams sign open T&M with no cap and no weekly review, then discover three months later that half the hours went to features nobody tested with users.
How we decide this for clients
We don't pick a contract type before we understand the work. Our process usually looks like this:
- Fixed-price discovery first. A two- to four-week paid phase, typically $5,000 to $25,000 depending on complexity. It produces user flows, a technical architecture and a ranked backlog with estimates.
- Sort the backlog by certainty. Well-understood pieces, such as authentication, a Stripe integration or a data migration, can be quoted fixed. Uncertain pieces, such as a recommendation feature or a new onboarding flow, go into T&M.
- Cap the T&M portion. We agree a monthly ceiling and send a weekly burn report against it. If we're trending past 80 percent of the cap, you hear about it that week, not on the invoice.
- Keep the exit clean. You own the code and the repositories from day one. Either side can end the engagement with short notice.
For many clients the answer is a hybrid: fixed discovery, a fixed first milestone, then capped T&M. It costs a little more effort to set up. It removes most of the arguments that sink agency relationships.
FAQ
Is fixed price or time and materials cheaper for an MVP?
For a well-specified MVP, the two often land close, because the fixed bid's risk buffer roughly offsets T&M's flexibility. For an MVP with open questions, capped T&M is usually cheaper overall. You avoid both the buffer and a stream of change requests.
What should a time and materials contract include to protect me?
At minimum: a monthly hour or dollar ceiling, itemised time logs tied to tickets, named team members, and a termination clause of two to four weeks. Add a requirement for a weekly written status report. Those clauses turn T&M from open-ended into controlled.
Can I switch from fixed price to time and materials mid-project?
Yes, and it is common once scope starts moving. Close out the fixed portion against its acceptance criteria first, then start a new T&M agreement for the remaining backlog. Switching without that clean break usually leads to disputes about what was already paid for.
