Hiring
Fixed price vs Hourly rate
Fixed price moves the estimating risk to the supplier and requires a written scope; hourly moves it to the client and requires trust. For a defined project fixed price is almost always better for the buyer — provided the scope is actually written down.
Side by side
| Compared on | Fixed price | Hourly |
|---|---|---|
| Who carries estimating risk | Supplier | Client |
| Requires a written scope | Yes, absolutely | No, which is the problem |
| Budget certainty | Complete | None |
| Handling change | A quoted change request | Just more hours |
| Suits exploratory work | Badly | Well |
| Incentive on the supplier | Work efficiently | Work thoroughly, or slowly |
When Fixed price is the right choice
- The deliverable can be described specifically enough to recognise when it is done
- You need budget certainty for approval or cash flow reasons
- You are comparing several suppliers and want comparable numbers
- The project is a build with a recognisable end point
When Hourly rate is the right choice
- The work is genuinely exploratory — debugging, research, or an audit whose findings are unknown
- Ongoing maintenance where the volume varies month to month
- A long relationship where scope evolves continuously and re-quoting each change is friction
- Small tasks where writing a scope costs more than doing the work
The failure mode of each
Fixed price against a vague brief becomes a change-request argument, and both parties end up resenting the document. Hourly with no cap becomes a project with no defined end, and the client discovers the total only in retrospect. Both failures come from the same root: nobody wrote down what was being bought.
The hybrid that usually works
Fixed price for the build, hourly for support afterwards, with the hourly rate stated up front. That gives budget certainty where it matters and flexibility where scope genuinely cannot be predicted, without pretending either model handles both.
What to insist on either way
A written scope, a payment schedule tied to something visible, a stated rate for out-of-scope work, and ownership transferring on final payment. Those four apply regardless of which pricing model you choose.
The verdict
Fixed price for a defined build, hourly for genuinely open-ended work, and the hybrid for most real engagements. The pricing model matters far less than whether the scope exists in writing.
If you want the full treatment
How much does a website cost, and what drives the number? covers this in about 4 minutes — free, ungated, written from client work.
Who wrote this comparison
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. Where a comparison involves something I sell, the page says so — and every comparison here has to name at least two situations where each side wins, because a comparison one option always wins is an advert with a table in it.