Guide · updated 6 November 2026
Fixed price vs hourly for freelance developers
Hourly pays you for every hour and leaves the risk of a long project with the client. Fixed price gives the client certainty and moves that risk to you. A fixed price pays better only while the work stays inside your estimate plus the buffer you priced in; the calculator shows exactly where that line is.
What would you earn?
Put in your estimate, your rate and the buffer you'd add to a fixed price, then drag how long the work really took.
Estimates miss in both directions; drag to see what each outcome does to each model.
| Client pays | You earn per hour | |
|---|---|---|
| Hourlyevery hour billed | $9,900 | $90 |
| Fixed price$10,800 agreed up front | $10,800 | $98 |
With a 20% buffer, fixed price pays at least your rate until the work runs past 120% of the estimate. Here it pays $8 an hour more than hourly.
When does a fixed price make sense?
When you can write the scope down precisely: deliverables you can list, acceptance criteria a client can check, and work you've done before so your estimate has a track record. Clients like it because they can budget; you can earn more than your rate when the estimate holds.
It works badly when the scope is still moving, when you're relying on a third party you haven't used, or when the client wants to steer week by week. In those cases the buffer you'd need makes the price look too high.
When is hourly better?
For discovery work, maintenance, retainers and anything where the client decides the next step as you go. Hourly is honest when nobody can know the size of the job yet, and it keeps you paid for the time a changing scope really takes.
The cost is that the client carries the risk, so they'll want regular reports, an estimate per task, and often a ceiling.
What do most developers actually do?
Fixed per milestone. Each milestone has its own price and acceptance criteria, so a surprise in one doesn't sink the whole project.
A paid discovery first. A short, fixed-price discovery turns the unknowns into a scope you can quote. The rest is then fixed or capped.
Capped hourly. Billed by the hour with a ceiling the client agrees to; you stop and ask before going past it.
Fixed, with the risk shown. A visible contingency line and a likely range, instead of padding every task, plus a priced change request for anything new. See how to handle scope creep.
How should a fixed-price proposal show the price?
Show the hours behind it. A fixed price with no breakdown invites haggling; one built from tasks and hours shows your reasoning and makes a change request easy to price later.
In Devposal a line can be a fixed price or hours × rate, the contingency is its own line, the likely range sits under the total, and optional extras let the client choose what to add, so the price explains itself.
Questions people ask
Is fixed price or hourly better for freelance developers?
Neither in general. Fixed price suits a scope you can write down precisely and work you've done before; hourly suits discovery, maintenance and anything the client steers as you go. Many developers fix the price per milestone and bill anything new as a change request.
How much buffer should I add to a fixed price?
Enough to cover how far your estimates usually miss on this kind of work. With a 20% buffer you earn at least your rate until the work takes 120% of your estimate; past that every extra hour lowers your effective rate. Showing it as a contingency line is clearer than hiding it in every task.
How do I work out my effective hourly rate on a fixed-price project?
Divide the fixed price by the hours the work really took. If you quoted $10,800 and it took 140 hours, you earned about $77 an hour, whatever rate the estimate assumed.
Can I switch from hourly to fixed price during a project?
Yes, at a milestone: once the unknowns are known, quote the remaining milestones at a fixed price. Switching in the middle of a milestone usually ends in an argument about what was already done.
Should I show my hours in a fixed-price proposal?
Usually, yes. Hours show the client how you got to the price and make later changes easy to price in the same terms. If you'd rather not, show the work broken into priced milestones instead.