← Compare

Fixed price vs time and materials

Every software contract fixes something: the price, the rate or the team. What it fixes decides who carries the risk when the plan changes, and in software the plan always changes.

The short answer

Choose fixed price when the scope is small, clear and unlikely to change, and budget certainty matters more than flexibility. Choose time and materials when you expect to learn as you go and want to change direction without renegotiating. Choose a monthly team when the work is ongoing and you want the same people every month at a known cost.

Side by side

Fixed price

Time and materials

Monthly team

What is fixed

The price, for an agreed scope

The rate per hour or day

The team and its monthly cost

Who carries scope risk

The vendor, until the scope changes

You

You, with a known monthly ceiling

Changing the plan

A change request, priced and approved

Just reprioritise the work

Just reprioritise the backlog

Budget certainty

High, if the scope holds

Low unless you cap it

High per month

Best for

A defined project with a clear end

Discovery, new products, evolving scope

Ongoing products and backlogs

Fixed price

You agree what will be delivered, by when, and for how much. The vendor carries the risk of the work taking longer than planned.

It works when the scope fits on a page and nobody expects to change it: a marketing site, an integration with a documented API, a migration with a clear start and end.

It fails when the scope moves. Every change becomes a change request with its own price and delay. Vendors also price in their risk, so a fixed quote is usually higher than the same work on time and materials would cost if the plan held. Before you sign, ask how changes are priced and approved.

Time and materials

You pay for the hours the team works, at an agreed rate. You can change priorities at any time without renegotiating.

It works when you are building something new and expect to learn from users as you go, or when the work is hard to estimate in advance.

It fails when nobody is watching the hours. Without a budget cap and regular reporting, costs drift. Ask for a monthly ceiling and a weekly record of what was done.

The middle ground

Most teams end up combining models:

  • A fixed-price plan, then time and materials or a monthly team for the build. The plan pins down scope and cost before work starts; the build stays flexible.
  • Time and materials with a cap. You keep the flexibility, with a ceiling that needs your approval to pass.
  • A fixed-price first release, then a monthly team. The MVP has a clear finish line; the product after it doesn't.

How we price

We use the model that fits the work:

  • Scoped projects are built against a written plan, with features, timeline and price agreed before any work starts. Our MVP development guide shows how we scope them.
  • Product teams and augmented engineers are billed monthly, from the prices on our public rate card, for about 160 hours per engineer.
  • Every model includes a project manager and a Loud Report every Friday with what shipped, what is blocked and the hours, so you always know where the money went.

If you are also deciding whether to hire a vendor or add engineers to your own team, read staff augmentation vs outsourcing. Before you sign any contract, our staff augmentation contract checklist lists the clauses to check.

Questions

Straight answers on time, money, people and IP.

Is fixed price cheaper than time and materials?

Not usually. Vendors add a margin for the risk of the work overrunning, so the same work often costs more at a fixed price if the plan holds. Fixed price buys certainty, not savings.

How do I control costs on time and materials?

Agree a monthly cap that needs your approval to exceed, and ask for a weekly written record of what was done and the hours used.

What happens if the scope changes on a fixed-price project?

It becomes a change request: the vendor prices the change and you approve it before work continues. Ask how change requests are priced before you sign.

Which model does LoudlyDev use?

Both. Scoped projects get a written plan with the price agreed upfront; product teams and augmented engineers are billed monthly from our public rate card.

Rates, roles and guides that go with this page.

Hire out loud.

Or email admin@loudlydev.com. We reply within 4 business hours.

Book a 30-minute call