Fixed Price vs Hourly: The Complete Freelance Pricing Guide

Every freelancer eventually picks a camp. Camp A: *"Never do fixed price — you'll get eaten alive by scope creep."* Camp B: *"Fixed price is the only way to make real money."*

Both camps are half right. Fixed price isn't a pricing strategy — it's a scope management strategy. Done right, it's the highest-margin work in freelancing: you get paid for 70 hours of effort while only spending 55. Done wrong, it's how you spend 90 hours on a project priced for 50, wondering where your month went.

The difference isn't luck or client quality. It's three decisions you make before you send the quote: scope, buffer, and change policy. This guide walks through all three — plus when fixed price is the right call, and when it's a trap.

Why fixed price is popular — and why it's dangerous

Why clients love it: certainty. "This project costs $7,500" is a decision they can make and budget for. "Well, it depends on how many revisions you want" is not. Certainty is a selling feature, and it's the reason flat-rate quotes win jobs against hourly estimates.

Why you should love it: the upside. You estimate 70 hours, you build it in 55, you still get paid for 70. Efficiency gains are yours, not the client's. You also stop tracking time in front of the client, which removes a whole category of awkwardness — nobody's watching the clock tick.

Why it's dangerous: you eat every overrun. The client has zero incentive to keep the scope tight — every addition is free to them. And "included" becomes a magnet for ambiguity: "I thought the CMS training was included," "I thought you'd set up hosting," "I thought…"

So the entire game is decided *before* the project starts. Here's how to play it.

Step 1: Price nothing until the scope is written down

You cannot price what you have not defined. This is the step everyone skips and the step that determines everything else. Before you estimate a single hour, write the scope down:

• Deliverables, item by item — "5-page marketing site with CMS," not "a website"
• Revision rounds — "2 rounds included; round 3 onward billed at the change rate"
• What's NOT included — the most valuable line in the document: hosting setup, copywriting, training calls, whatever you won't do for this price
• Communication — "Weekly progress call included; ad-hoc calls billable"
• Handover and support — "One training call included; support after launch at $X/hour"

This is the scope baseline, the foundation everything else sits on — the full definition and a template you can steal live here. The rule of thumb: if you can't summarize the scope in one paragraph, you can't price it. Scope creep happens exactly where this document is vague; the mechanism is worth understanding before you write yours.

Step 2: The pricing formula (with real numbers)

Here's a formula that works:

Quote = (estimated hours × your target hourly rate) × (1 + buffer), rounded up to a clean number

Worked example: a 5-page marketing site.

At your target rate of $85/hour: 70 × $85 = $5,950. Buffer at 25%: $5,950 × 1.25 = $7,438. Round up to a clean $7,500. That's your quote.

Why the buffer exists: it's invisible insurance. The client doesn't pay for a "buffer" — they pay $7,500, which is a perfectly reasonable price for the project. If you come in at your estimate, you made your rate. If you come in under, you keep the difference — that's the fixed-price upside paying out. If something genuinely surprises you, the buffer absorbs it instead of your weekend.

How much buffer? 15–20% if you've built this exact project ten times and your estimates are boring. 25–35% for a new stack, a new industry, or a client who can't answer a direct question. Anything that makes you squint at the estimate means more buffer, not less.

One rule: don't negotiate your buffer away. When the client says "can you do $6,500?", the reflex is to shave the price. But you'd be selling your insurance — pricing at your worst case with no protection. Counter with scope instead: *"I can get to $6,500 if we drop the CMS training call and one revision round — want me to send the updated scope?"* You keep your margin, and the client learns that price and scope move together.

Step 3: The change policy — the item that saves your project

The fixed price is fixed only if the scope is fixed. So before work starts, agree on what happens when scope moves. A change policy answers four questions:

1. What counts as a change? Additions, rework of delivered items, extra revision rounds, out-of-scope support, and changes of direction that discard finished work.
2. How is it quoted? An estimate, logged before work begins.
3. How is it approved? In writing — an email, or a click in the project tool.
4. How is it billed? As an add-on invoice, separate from the base price.

Put one line in your contract that does the heavy lifting:

"The fixed price covers the scope described in this agreement. Changes to scope are quoted separately and approved in writing before work begins."

That sentence turns "I thought that was included" from a fight into a non-event. The client's request lands outside the baseline → the change policy triggers → the client sees the estimate and approves or drops it. No negotiation, no awkwardness — the same system, step by step, with scripts.

When fixed price works — and when to run from it

Fixed price works when the deliverables have an end. Marketing sites, landing pages, design systems, brand identities, templates, migrations with a known schema — anything you can list on one page. The more you've done the same shape of project, the better the fixed-price game gets: your estimates get honest, your efficiency gets real, and your margin gets fat.

Fixed price is a trap when the work is open-ended. Discovery and research ("we'll know what we want when we see it"), ongoing support and retainer work, and any project where the requirements genuinely can't be known until you're inside it. If the client says "just make it good," you cannot price it — and any number you quote is a guess wearing a fixed price's clothes.

The escape hatch: phase the project. Bill the discovery or audit phase hourly — say $1,200 for a two-week discovery sprint — and then quote a fixed price for the build, once the scope is written down and the client has signed off on it. You get paid for the fuzzy part, and the fixed-price part rests on an actual document instead of a guess.

The common mistakes (and the fix for each)

1. Pricing before scoping. The fastest way to eat your own margin. Fix: no written scope, no quote — make it a rule.
2. No buffer. You're pricing at your worst case, then living it. Fix: 20–35%, always, and never give it away in negotiation.
3. No change policy. A fixed price with a floating scope is the worst of both worlds — you bear all the risk and get none of the upside. Fix: the contract line above, signed before work starts.
4. "Unlimited revisions." The single most expensive phrase in freelancing. It converts "one more tweak" from a cost into a right, and it's the on-ramp for exactly the creep that kills flat-rate projects. Fix: cap included rounds at 2, bill round 3 onward.
5. Using fixed price as a discount to win the job. You're not winning the job — you're buying it with your own margin, then hoping the scope stays frozen (it won't). Fix: price the project properly, then discount scope if you must compete — never the price for the same scope.
6. Not tracking time on fixed-price jobs. "It's fixed price, why would I track?" Because your next quote depends on the data from this one. You can't estimate project #7 without knowing what project #4 actually cost. Track anyway — privately, and it's the only way your estimates ever get honest.

The bottom line

Fixed price rewards the disciplined. Write the scope down, price it with a real buffer, and protect it with a change policy — and flat-rate work becomes the best margin game in freelancing. Skip any of the three, and you're gambling that the client will be more organized than you are. That's a bet you lose more often than you win.

If you're building your first fixed-price workflow, start with the scope baseline template in the docs and check what ScopeGuard's plans cost — the tooling exists so the discipline is easy instead of heroic. And when the client says "one quick thing," run it through the Scope Creep Calculator before you answer: see the real number, then decide.

*Related: What Is Scope Creep? · How to Handle Scope Creep Without Awkward Conversations · The Real Cost of "One Small Thing" in Freelancing (with Real Math)*