Skip to content
Resources · Blog

Fixed Price vs Time and Materials: How to Choose 

Fixed price moves delivery risk to the vendor; time and materials keeps it with you. What each costs, when each works, and the hybrid most projects use.

November 16, 2026 6 min read
Pricing ModelsProcurementDelivery Process

Choose fixed price when the scope can be written down in enough detail that you and the vendor would agree, feature by feature, on what is in and what is out. Choose time and materials when the product will keep changing as you learn, and you have someone who can set priorities every sprint. Fixed price moves delivery risk to the vendor and charges you for carrying it; time and materials keeps the risk with you and charges only for the hours worked. Most of the disputes we see between clients and software houses come from buying one model while expecting the behavior of the other: a fixed price on a scope nobody has pinned down, or open-ended hours with nobody watching the burn. We offer both at RNDSOL, and on most custom software projects we recommend a mix of the two. Below is how each model works in practice, what it costs on the same scope, when each one fails, and a short set of questions that settles the choice for most buyers.

How Each Model Prices the Same Work

  • What you pay for: fixed price buys an agreed outcome for an agreed sum; time and materials buys engineering hours at an agreed rate
  • Who carries overrun risk: the vendor, within the written scope, under fixed price; you, under time and materials
  • Changing scope: a change request with a price and a date under fixed price; reordering the backlog at the next sprint planning under time and materials
  • What the vendor needs first: a specification with acceptance criteria for fixed price; a prioritized backlog and a product owner for time and materials
  • How you track progress: milestones signed off against the specification, or hours and completed backlog items against a forecast
  • Where the money leaks: change orders under fixed price; unreviewed hours and slow decisions under time and materials

Is Fixed Price Cheaper Than Time and Materials?

Usually not, for the same scope, and the reason is arithmetic rather than greed. A vendor quoting a fixed price has to cover the work it can see plus the work it cannot see yet: an integration that behaves differently from its documentation, a report the specification describes in one line that turns into a week of work, a round of feedback from a stakeholder who joined late. That contingency is often in the region of 15 to 30 percent on the builds we see. Take a scope estimated at 20 engineer-weeks. At $35 to $55 an hour, the rates our cost calculator uses, that is $28,000 to $44,000 on time and materials if the estimate holds. A fixed quote for the same scope might land between roughly $32,000 and $57,000 once the contingency is in. If the estimate was good, time and materials was cheaper. If the scope grows by a third, the time and materials bill grows with it, while the fixed price stays put for everything inside the written scope. You are paying for certainty, so ask how much certainty the project has to start with. On a well-defined scope, the premium is small and buys a fixed number for the budget committee. On a vague scope, the premium is large and still does not buy certainty, because the missing detail comes back later as change orders.

When Fixed Price Works, and When It Fails

Fixed price works when three things are true. The scope is written down to the level of user roles, screens, business rules and integrations, with acceptance criteria for each. Someone on your side has the authority to accept or reject a deliverable without convening a committee. The work is bounded: a first version of a product, a separable module such as a customer portal, a rebuild of a system whose behavior is already known, or a defined list of fixes from a security review. The way to meet the first condition is discovery. Ours runs one to two weeks, is priced separately, and produces a requirements document, a proposed architecture, a clickable prototype and a fixed quote with a sprint-by-sprint plan, and you keep every deliverable even if you build with someone else. Paying for discovery before a fixed quote feels like an extra cost. It is the cheapest way to shrink the contingency, because the vendor is pricing a known scope instead of a guess. Fixed price fails when it is used to force certainty onto a product that has not found its shape yet. Each sprint review produces new ideas, each new idea becomes a change request, and the relationship turns into a negotiation about what the specification meant.

When Time and Materials Works, and What It Needs

Time and materials suits products that will keep changing: a platform with live users and a roadmap driven by what they do, a product after its first release, an integration-heavy project where the third parties are the unknown, or exploratory work such as an AI prototype, where nobody can promise accuracy before seeing the data. It needs two things from you. The first is a product owner who sets priorities at every sprint planning and answers questions within hours, because a blocked engineer bills the same as a productive one. The second is visibility. Ask for hours logged against named backlog items, a burn report at the end of every sprint, and a forecast of the remaining backlog in engineer-weeks, updated as the estimates change. On our engagements, budget burn sits in a shared tracker the client can open on any day, so nobody learns about overspend from an invoice. Many buyers also add a cap: time and materials up to an agreed ceiling per phase, with a review before any hour past it is billed. That keeps the flexibility to change direction and puts a hard stop on the downside.

The Hybrid Most Projects End Up Using

The contracts that work best change model as uncertainty falls. Discovery runs at a fixed price because its output is defined. The first version runs at a fixed price per milestone, against the scope discovery produced, with a small change budget agreed up front for the requests that will arrive anyway. After launch, the work moves to time and materials or a dedicated monthly team, because the backlog is now driven by users and nobody can specify it six months ahead. Most of our clients follow that sequence: fixed price for the MVP, then a monthly team once the roadmap opens up. Whatever mix you choose, write the switching points into the first contract, along with the clauses that matter under every model: code in your repositories from the first commit, IP that transfers as each milestone is paid rather than only at the end, and a defined handover period. Our software development contract checklist covers those clauses one by one.

Five Questions That Pick the Model

  • Can we write acceptance criteria for the whole scope today? If yes, fixed price is on the table; if only for the next month, start with paid discovery or time and materials
  • Who on our side will make product decisions every week, by name? If nobody, a fixed scope protects you from drift
  • How likely is the scope to change after the first demo? The more likely, the more a fixed price will cost you in change requests
  • Does the budget need a single approved number? If yes, fix the price of discovery and the first milestone, and cap the phases after it
  • What happens after launch? If the software will keep changing, plan the move to a monthly team before the first contract is signed

Have a project that needs this kind of thinking applied to it?