Fixed price vs time and materials: who carries the risk?
In fixed price vs time and materials, the difference is who carries the risk. With a fixed price, the builder agrees a set scope for a set cost and absorbs any overrun. With time and materials, you pay for hours worked, so you can change direction at will and carry the overrun yourself. Choose by how settled your scope is. We sell fixed-price builds, so weigh our view accordingly.
Reviewed by Anubhav Gupta, Bespoke Devs · Updated
Fixed price vs time and materials, side by side
| Compare | Fixed price | Time and materials |
|---|---|---|
| What you pay for | An agreed result | Hours worked, plus any costs |
| Who carries overrun risk | Mostly the builder | Mostly you |
| Changing your mind | Goes through a change request | Easy. You just pay for the time |
| Budget certainty | High, if the scope holds | Low, unless you set a cap |
| Work before starting | More, because scope must be written first | Less. You can start and work it out |
| Common failure | Arguments over what was “in scope” | A bill that keeps growing |
| Quality risk | Builder may cut corners to protect margin | Less pressure to rush, but less pressure to finish |
Which one fits your project
Choose fixed price if
- You can describe the first version on one page
- You have a set budget that can’t stretch
- You need a launch date you can plan around
- You don’t want to manage developers day to day
Choose time and materials if
- You’re still working out what the product should do
- You’re adding to a live product with changing priorities
- There’s a hard technical unknown nobody can estimate yet
- You can review work closely each week
How scope discipline protects a 15-day date
A short timeline holds only when the scope is closed before the build starts. Fifteen days gives no slack for debate. So we spend days 1 and 2 agreeing exactly what’s in, then you approve the designs before any code gets written.
After that, new ideas go on a list for later. That can feel strict in week two, when you’ve just thought of something good. It’s also why the date holds. Each new request has to compete with something already promised, and nearly all of them can wait until real customers have used the product.
We manage scope to protect the timeline, and we don’t pad the timeline to manage expectations. That’s the trade you’re making when you buy this way. You give up freedom to change things during the build. You get a known price and date.
What to put in writing
Whichever you pick, these details prevent most arguments.
- For a fixed priceA feature list with what each one does, what’s excluded, how change requests are priced, and what “done” means.
- For a time and materials contractThe hourly rate, a monthly cap, who approves going over it, and how often you get a report on hours and progress.
- For bothWho owns the code and when it transfers. See who owns the source code.
- A middle optionPaid discovery first, then a fixed price for the build. Time and materials with a cap also works. Both are common, and the cap is what makes the second one safer.
A quick sum
Here’s how fixed price vs time and materials can play out, with made-up numbers. A fixed quote is $8,000. A time and materials quote estimates 200 hours at $30, which is $6,000. The hourly option looks cheaper by $2,000, until scope grows by a third. Then it’s 267 hours and about $8,000, and you’ve carried the risk of it going higher.
Fixed quotes often include a risk margin, so you may be paying for certainty. Decide whether that’s worth it for your project. If your scope really is settled and your developer is reliable, hourly can come out cheaper.
When our fixed-price model is wrong for you
- You want to change scope freely during the build. Hourly work suits that better.
- You can’t yet say what the first version should do. Talk to customers first.
- Your project has a technical unknown that needs research. Pay for that as hours, and fix the price once you’ve got the answer.
Common questions
Yes. A fixed fee and a fixed price mean the same thing here. You pay one agreed amount for agreed work.
Either can go wrong. A fixed price can tempt a builder to cut corners, and hourly work can drift. Written acceptance criteria and a real review help in both cases.
You and the builder agree whether it replaces something in scope, gets priced as extra work, or waits. Agree how this works before the build starts.
Usually, yes. A monthly cap with an approval step keeps the flexibility and stops surprise bills.
Keep reading
- SaaS MVP developmentWhat’s included, what it costs and how a 15-day build works.→
- MVP features listWhat to include, what to leave out, and how to decide.→
- Can an MVP be built in 15 days?What has to be true for a 15-day build to work.→
- Freelancer vs agencyCost, timeline and risk compared, including when the freelancer wins.→
Tell us what you’re building.
Takes under a minute. We come back with a scope and a fixed price.
- Reply within 24 hoursA real person reads every brief.
- Fixed scope, fixed priceYou get a written proposal, no hourly billing.
- You own the codeFull ownership of code and assets at launch.