Picking fixed price vs hourly quote on the wrong project is how freelancers either eat 40 unpaid hours or lose a deal to someone who quoted a flat number. The choice isn’t ideological. It’s per project, and it lives or dies on how well you can predict the scope before signing.
Most freelancers I see default to one model and force every project into it. That’s the problem. The right call shifts project by project, and the quote itself needs a sentence or two explaining why you went with one over the other. Otherwise the client wonders, and a wondering client doesn’t sign.
The 20 percent rule for fixed price vs hourly quote
Here’s the rough test: if you can predict the hours within plus or minus 20 percent, fixed price is safe. If your honest estimate is “somewhere between 30 and 90 hours,” you do not have a fixed-price project. You have an hourly project that’s wearing a costume.
Examples that pass the 20 percent test:
- A 5-page WordPress site for a service business you’ve built 10 times
- A standard brand identity package (logo, palette, type, one-page guide)
- A 90-minute customer interview plus a written summary
- A monthly SEO audit with the same deliverable structure
Examples that fail:
- “Redesign our app” with no spec
- A consulting engagement where the next steps depend on what week 1 finds
- Custom integrations with an API you haven’t read yet
- Anything where the client says “we’ll figure it out as we go”
Why fixed price wins on defined work
Here’s what gets me about fixed price: it rewards your speed. If you’ve designed 40 logos and the next one takes you 6 hours instead of 12, you keep the upside. Hourly punishes the same skill. The better you get, the less you earn per project. That’s backwards.
It also kills the worst conversation in freelancing, the one where the client opens the invoice and goes “wait, 19 hours? For that?” Even if 19 hours was honest, the invoice becomes a debate. Fixed price removes the debate.
The client wins too. They get a number they can budget and approve internally. Hourly numbers terrify finance teams because the ceiling is unknown.
Why hourly wins on fuzzy work
When you quote a fixed price on truly undefined work, one of two things happens:
- You pad the quote 40 percent to cover risk, lose the deal to a cheaper bid
- You bid honestly, scope explodes, you work 80 hours for the price of 40
Hourly with a cap is the escape hatch. “I estimate 25 to 35 hours at 120/hr. I’ll check in if I’m trending toward the upper end.” The client gets transparency, you get paid for actual work, nobody is gambling.
Hourly also works when the client controls the pace. Anything where you’re waiting on their feedback, their content, their approvals, fixed price means their delays become your unpaid time.
The hybrid quote that closes more often
The cleanest move for most projects is a hybrid. Fix the parts you can predict, hourly the parts you can’t.
Example for a website project:
| Item | Pricing | Amount |
|---|---|---|
| Design and build (5 defined pages) | Fixed | 4,800 |
| Content strategy and copy review | Hourly, capped | 110/hr, max 1,100 |
| Post-launch tweaks (first 30 days) | Hourly | 110/hr, billed weekly |
The client sees a clear floor (4,800), a clear ceiling on the unknown work (1,100), and a defined hourly rate for anything after launch. Three numbers, three buckets. No surprises.
Language to put in the quote
Don’t just list a price. Explain the model in one sentence so the client doesn’t ask.
For fixed price:
“Fixed price covers the deliverables listed above plus two revision rounds. This pricing assumes the scope as written; additional pages or new directions would be quoted separately.”
For hourly:
“Hourly because the discovery phase will determine the actual build scope. I’ll send a weekly time summary and flag if we’re trending past the estimate before we get there.”
For hybrid:
“Fixed for the defined deliverables, hourly with a cap for the exploratory work. You’ll never see a bill larger than the cap without approving it first.”
Those sentences answer the questions the client was about to ask. They also signal that you’ve done this before.
What clients hear when you say “hourly”
Hourly has a perception problem. To a client who’s been burned, hourly means open-ended bills and developers who stretch a 2-hour task into 8. So when you quote hourly, you have to manage that perception in the quote itself.
What calms the fear:
- A range, not just a rate. “Estimated 18 to 25 hours” gives a number to budget against
- A cap with an approval gate. “I won’t exceed 30 hours without your written approval”
- A reporting cadence. “I’ll send a time summary every Friday with what I worked on”
Without those, hourly quotes lose to fixed-price competitors even when the fixed-price quote is worse.
What clients hear when you say “fixed price”
Fixed price has its own perception trap. Some clients assume fixed means “and anything else I think of is also included.” Your quote needs a one-line scope fence.
“Fixed price covers exactly what’s listed. New requests or changes outside this scope are quoted as a change order, no surprise charges, just a quick second quote for approval.”
That sentence does more for client relationships than any onboarding doc. It tells them upfront how change requests work, so when one comes (and it will), you’re enforcing something they already agreed to.
When to switch mid-project
Sometimes you quote fixed and the project mutates. The client adds a feature, then another, then redesigns the homepage three weeks in. You have two honest moves:
- Re-quote the new scope as a new fixed price (best if the new scope is also definable)
- Switch the remainder to hourly with a cap (best if the scope keeps shifting)
Don’t silently absorb the extra work. The client doesn’t know they’re hurting you until you tell them, and the relationship is fine if you raise it early. It only breaks if you stew for a month and then send a furious email.
The decision table
Quick gut-check for your next quote:
| Situation | Default to |
|---|---|
| You’ve done this work 5+ times | Fixed |
| Scope is one paragraph or less | Fixed |
| Client wants a number for their boss | Fixed |
| You’re guessing more than estimating | Hourly |
| The project depends on the client’s pace | Hourly |
| Discovery phase will define the build | Hourly + fixed hybrid |
| Long-term retainer | Hourly with monthly minimum, or flat retainer |
| Procurement requires line-item hours | Hourly |
The fixed price vs hourly quote decision usually takes 60 seconds once you’ve answered those questions honestly.
One last thing about your effective rate
Track this for a year: take every fixed-price project you finish, divide what you charged by the hours it actually took, and write down the number. Most freelancers find their fixed-price effective rate is 30 to 60 percent higher than their stated hourly rate. That’s the speed dividend.
If your effective rate is lower than your hourly rate, you’re underbidding fixed projects. Raise your numbers or switch those projects to hourly until you can predict them better.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
