Contents

Fixed price suits work whose scope is clear in advance and will not change; Time & Materials suits products that are still taking shape, with requirements refined along the way. For most new products a hybrid works best: a fixed price for discovery and design, then development billed on actual time with an estimate, limits and weekly transparency.

Here is how each model works, where the risks hide and how to choose for your project.

How does fixed price differ from Time & Materials?

Fixed price is a set amount for a scope described in advance: the vendor takes the risk of a wrong estimate, and the client takes the risk that changes will need renegotiation. Time & Materials (T&M) means paying for the time actually spent at agreed rates: the client gets flexibility but manages the budget.

Criterion Fixed price Time & Materials
Budget Known upfront An estimate and range; the total is actual time
Requirement changes Via renegotiation and change orders Absorbed into the work without red tape
Who carries estimation risk The vendor, so they add a buffer The client
Specification needs Detailed and stable Scenarios and priorities are enough
Client control Acceptance at the end of a stage Continuous: demos and time reports
Typical projects Landing page, website, integration to spec MVP, product growth, support

When should you choose fixed price?

Choose fixed price when the result can be fully described upfront and will not change during the work. A corporate site built from finished designs, an integration based on a service's documentation or a data migration are good examples.

Conditions under which a fixed price works:

  1. There is a detailed specification or discovery output with scenarios and acceptance criteria.
  2. The client is ready to freeze scope until the end of the stage and move new ideas to the next one.
  3. The project is small or split into short stages, each with its own price.
  4. The vendor's team has done similar projects, so the estimate rests on facts.

Remember that a fixed price is almost always higher than a time-based estimate: the vendor builds a risk buffer into it. You are paying for predictability — sometimes that is worth it.

When should you choose Time & Materials?

Choose Time & Materials when the product will change as work progresses: after the first demos, user tests or new market data. For MVPs and product growth that is the norm, and a rigid scope turns every change into a negotiation.

Where T&M wins:

  • new products where hypotheses are tested along the way;
  • post-launch product development and support;
  • legacy code, where complexity only becomes visible once you dig in;
  • a dedicated team working within the client's process.

Two people shaking hands over documents Photo: Unsplash

How to control the budget under T&M

The client's main fear with T&M is a bottomless budget. It is addressed not by the pricing model but by transparency and rules:

  • an estimate of the full scope as a range, regularly compared with actuals;
  • a monthly hour cap, with any overrun agreed in advance;
  • weekly demos and a time report broken down by task;
  • a prioritised backlog: when budget runs short, you cut the tail, not quality.

Why is a hybrid model often the better deal?

A hybrid model is often the better deal because it fixes the price where the outcome is predictable and keeps flexibility where it will inevitably be refined. The client gets a clear entry point and does not pay for risks the vendor would build into a fixed price for the whole project.

How we usually structure the work:

  1. Fixed price for discovery: scenarios, prototypes, architecture and an estimate. More on what the stage includes in the discovery phase explained.
  2. A development estimate by scenario with a range, as in our MVP estimate breakdown.
  3. Development on T&M with a monthly cap, weekly demos and reports.
  4. Changes along the way are estimated before work starts and approved.
Example of a hybrid arrangement
  Stage 1. Discovery — fixed, 3 weeks; output: scenarios, prototype, estimate
  Stage 2. MVP development — T&M, estimate 1,400–1,700 hours,
           cap of 400 hours a month, demo every Friday
  Changes — estimated before work starts; the client decides

What traps does each model hide?

The main trap of fixed price is a vendor saving on anything the specification does not describe; the main trap of T&M is a lack of client oversight. Both work badly without someone who makes decisions and looks at results every week.

Fixed price traps:

  • a low price achieved by leaving out testing, launch and support;
  • disputes at acceptance when "done" is vaguely defined;
  • every change goes through change orders and new estimates;
  • a temptation for the vendor to hit the number at the expense of code quality.

Time & Materials traps:

  • the budget creeps up unnoticed if nobody compares actuals with the estimate;
  • the client loses focus and everything ends up in the backlog;
  • opaque reports — hours not tied to tasks and results.

When comparing vendor proposals, look at the scope, not just the model and the total — we covered this in how to choose a software development vendor.

In short

  • Fixed price is for stable, well-described scope; you pay for predictability.
  • Time & Materials is for products that will change; transparency and caps keep the budget in check.
  • "Fixed discovery + T&M development" suits most new products.
  • Under T&M, insist on an estimate range, a monthly cap, weekly demos and task-level reports.
  • Under fixed price, check that testing, launch and clear acceptance criteria are included.

FAQ

  • What is a retainer model?

    It is a monthly payment for a fixed number of hours or a fixed team. It is usually used for post-launch support and development: the client gets a predictable budget and the vendor reserves the people.

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

    Yes, usually at a stage boundary. It makes sense when changes are so frequent that renegotiating each one slows the work. The switch is recorded in an amendment with a fresh estimate of the remaining scope.

  • Why is a fixed price higher than a time-based estimate?

    The vendor takes on the risk of a wrong estimate and adds a buffer for unknowns. The vaguer the requirements, the bigger the buffer, which is why a fixed price on a loosely defined project is especially expensive.