When you charge by the hour, you get paid more when you are slow and less when you are fast. A 30-hour project you estimated at $88/hr produces $2,640. If you finish it in 22 hours because you’ve done this exact type of work before, you earn $1,936. The client is not wrong to benefit from your experience — but you should not be penalized for it either.
Fixed-fee pricing breaks that dynamic. You quote a number, the client agrees, and how long it actually takes is your problem to manage — upside and downside both. That shift changes the math in your favor when you are efficient. It also creates a risk if you underestimate. The formula below handles both.
Fixed-fee project price:
Estimated hours × Hourly floor × Scope buffer
Three inputs. The first two come from your rate calculation (covered in How to Calculate Your Freelance Rate). The scope buffer is what converts a raw estimate into a defensible price.
No estimate is perfect. Clients request revisions. Feedback rounds take longer than expected. A design direction gets scrapped after two rounds. The scope buffer is a built-in cushion that protects you from normal estimation error without requiring a perfect forecast.
| Project type | Buffer | Why |
|---|---|---|
| Repeatable work (blog posts, design templates, standard reports) | 1.10 | Known process, defined output — your estimate is reliable |
| Custom deliverables (site builds, strategy documents, integrations) | 1.20 | Client feedback rounds add 1–3 hours per revision cycle |
| Complex or creative work (rebrands, custom software, discovery projects) | 1.30 | Discovery reveals new requirements; creative direction can shift |
For most project work, 1.20 is the right default. If you are consistently finishing projects well under the buffered estimate, you’re doing it right — that upside is yours to keep. If you are consistently running over the buffer, either your estimates are systematically optimistic or your scope-of-work is not tight enough.
Alex is a web designer. Her hourly floor is $88/hr (calculated from her target gross income, business costs, and billable hours). A client hires her to redesign a five-page website: new layout, updated copy integration, mobile optimization, and two rounds of revisions.
Alex’s estimate: 32 hours. The work is custom but not unusual — she’s done comparable projects before. She applies a 1.20 buffer.
| Step | Calculation | Result |
|---|---|---|
| Base price | 32 hrs × $88/hr | $2,816 |
| Apply scope buffer (1.20) | $2,816 × 1.20 | $3,379 |
| Quoted price (rounded up) | — | $3,400 |
Alex quotes $3,400 flat. The client sees a clear number; no weekly hour-tracking, no surprise invoices. Alex’s outcome depends on actual hours:
| Actual hours | Scenario | Effective rate | vs. Floor |
|---|---|---|---|
| 28 hrs | Finished efficiently | $121.43/hr | +$33.43 above floor |
| 32 hrs | Hit the estimate | $106.25/hr | +$18.25 above floor |
| 38 hrs | Ran long (one extra revision) | $89.47/hr | +$1.47 above floor |
| 45 hrs | Significantly over estimate | $75.56/hr | −$12.44 below floor |
At 38 hours she is still above her floor by $1.47 — which is why the buffer exists. At 45 hours the buffer is exhausted and she is working below floor. That scenario represents either a systematic estimation problem or a scope-of-work failure, not an argument against fixed-fee pricing.
The efficiency upside is real. If Alex completes this project in 28 hours because she has done five similar projects this year, she earns $121/hr against an $88/hr floor — a 38% premium for competence. At hourly pricing she would earn $88/hr no matter how fast she worked.
Fixed-fee is not always better. Use hourly when the project has characteristics that make estimation genuinely unreliable:
| Factor | Use fixed-fee when… | Use hourly when… |
|---|---|---|
| Scope clarity | Deliverable fits in one paragraph | Output depends on what you find |
| Client relationship | You’ve worked together before | New client, unclear expectations |
| Your experience | You’ve done this type of project 5+ times | This is a new category for you |
| Decision risk | Client has approved direction upfront | Direction may change mid-project |
| Timeline | Defined end date and deliverable | Ongoing, open-ended engagement |
When in doubt, start with a small hourly discovery engagement (“I’ll spend 4 hours mapping the project and deliver a scope document”) before quoting fixed-fee for execution. This is how you avoid quoting fixed-fee on a project you don’t understand yet.
Scope creep is the most common fixed-fee risk and the one freelancers handle worst. The failure mode is absorbing extra work silently, finishing the project over-hours, and then resenting the client. The client never knew there was a problem. You never told them. Nobody wins.
The right protocol is mechanical:
The scope-of-work clause that matters: Every fixed-fee proposal should include one sentence: “Work beyond the deliverables listed above is billed at $[change order rate]/hr and requires written approval.” Most clients have seen this clause before. It sets expectations without friction.
The fixed-fee formula gives you a floor anchored to your costs. It does not capture value. When your work has a measurable impact on the client’s revenue, the formula may produce a number that is well below what the market will bear.
The signal to consider value-based pricing: you can describe the client outcome in dollar terms.
In these cases the fixed-fee formula answer ($88/hr × 12 hours × 1.20 = $1,267) is real but not the ceiling. A client getting $4,320/month in recovered revenue from a $1,267 project is a bad deal for you. Value-based pricing anchors to outcome: “If this performs as expected, you recover $4,000/month. My fee is $2,400.” The client’s ROI is still strong; your effective rate climbs.
Value-based pricing requires that you can actually demonstrate the outcome, which requires tracking. Clients who do not share performance data with you are not candidates for value-based pricing — use the formula instead.
The Freelancer Tax Tracker Lite logs income by client and auto-calculates your quarterly estimated tax payment as you earn. Know where you stand before the June 15 deadline.
Before sending any fixed-fee quote, run through four questions:
Use hourly pricing when scope is genuinely open-ended or unknowable upfront: consulting retainers, ongoing advisory work, research phases where the output depends on what you find, and projects with new clients who may change direction mid-stream. Fixed-fee works when the deliverable is defined — a specific number of pages, a finished design system, a working integration. If you cannot write a clear scope-of-work in one paragraph, the project is probably too ambiguous for fixed-fee. Start with an hourly discovery engagement to define scope, then quote fixed-fee for execution once you both agree on what done looks like.
Three-step protocol: (1) Name it immediately when it happens. A quick email — “That additional section is outside our current scope. I can include it for an additional $X or we can defer it to the next phase” — is professional and expected by sophisticated clients. (2) Price change orders at a premium rate: your hourly floor times 1.25. At $88/hr floor, that is $110/hr for out-of-scope additions. Scope creep disrupts your schedule; the premium compensates for that disruption. (3) Use the experience to tighten your next SOW. If a client type consistently asks for the same additions, build them into the base scope going forward.
A fixed-fee project has a defined deliverable and a defined end date — the engagement closes when the deliverable is accepted. A retainer is recurring access to your time: a set number of hours or a set scope of ongoing work per month, billed in advance. Retainers suit clients who need ongoing work without restarting the project-scoping process each month. When pricing a retainer, use the same floor calculation but remove the scope buffer (the buffer compensates for estimation risk; a retainer scope resets monthly) and add a relationship premium of 10–15% for the guaranteed capacity you are holding. A retainer priced below your hourly floor — even slightly — will feel like a tax over time. Run the math before you agree to one.
Track actual hours on every project and calculate your realized effective rate: total fee divided by total hours. If the realized rate is below your hourly floor, the fixed-fee was too low. Many freelancers undercharge not because they ran the formula wrong but because they consistently underestimate hours by the same margin — their estimates are systematically optimistic. Track three consecutive projects and compare estimated hours to actual hours. If you are consistently running 30% over your estimates, raise your scope buffer from 1.20 to 1.30. The feedback loop from tracking is the most reliable way to calibrate both pricing and time estimates.
The Freelancer Command Center Pro tracks income and profitability per client. The Client P&L tab shows which clients are paying the highest effective hourly rate — and which are revenue traps. 11 tabs including Tax Prep, Tax Intelligence, and Mileage Log.