How to price a fixed-fee project without losing money

When you quote a fixed fee, you’re buying risk.

The client knows exactly what they’ll pay. You don’t know exactly what you’ll do. Everything between your estimate and reality — scope creep, unclear briefs, extra revision rounds, client delays that extend your time — comes out of your margin. The client’s budget is fixed. Yours isn’t.

That asymmetry is the business case for pricing fixed fees higher than your hourly equivalent, not lower.

Why fixed fees are almost always underpriced

The intuitive approach is to estimate the hours, multiply by your rate, and that’s the price. The problem is that the estimate is almost always optimistic — the planning fallacy applies systematically to creative and knowledge work, where the underestimate averages 30 to 50%.

So you estimate 20 hours, the project takes 30, and your effective rate drops by a third. On a €2,000 quote at €100/hour (20 hours), a 30-hour reality means you earned €67/hour.

That error is recoverable once. It becomes expensive when it happens on every fixed-fee project.

Building the price correctly

Start from the realistic estimate, not the optimistic one.

Step 1: estimate hours based on the worst realistic case, not the best. Think about similar past projects. What did they actually take? Use that number, not the number from the one project that went smoothly.

Step 2: add a 30% buffer. Not because you’re slow, but because you’re human. The planning fallacy is structural. The buffer isn’t pessimism — it’s calibration.

Step 3: add a risk multiplier for scope ambiguity. A well-defined project with a client you know: ×1.0. A project with a clear brief from a new client: ×1.2. A project where the brief contains “we’ll figure out the details as we go”: ×1.5 or don’t quote fixed fee at all.

Step 4: price the certainty itself. Fixed fees are a service. The client is buying the ability to plan their budget. That has value beyond your time. 10 to 15% above the time-based calculation is a reasonable certainty premium.

The change order is non-negotiable

Once the project starts, scope changes trigger a new conversation, not silent absorption.

A change order is a short written confirmation: “You’ve asked for X, which wasn’t in the original scope. I can add it for €Y, extending the timeline by Z days. Confirm and I’ll proceed.”

The mistake most freelancers make is absorbing the first scope change to avoid the awkward conversation, then the second, then resenting the client by invoice time. The change order prevents that. Used consistently, it becomes unremarkable — clients learn early that changes have a price, and they scope more carefully as a result.

The change order must be in the original contract as a mechanism. “Work beyond the agreed scope will be quoted and approved in writing before execution” is one sentence that prevents most scope disputes.

When fixed fees actually work

Fixed fees favour specific conditions: a well-defined deliverable, a client you’ve worked with before or who has briefed clearly, and a project type you’ve delivered enough times to estimate accurately.

They work badly when any of those conditions are missing — particularly when the brief is vague. An ambiguous brief combined with a fixed fee is a transfer of uncertainty from the client to you. When scope does start expanding mid-project, the patterns in scope creep detection tell you when to raise it and when to absorb it. The client doesn’t know what they want, you don’t know what you’re building, but the price is fixed. That ends badly.

The alternative: a fixed-fee discovery phase that defines the brief, followed by a fixed-fee delivery phase priced from that definition. The client pays for clarity before committing to the larger number. You price delivery from a position of understanding.

Timescanner tracks your actual hours per project, so you can compare estimates to reality over time and calibrate your fixed-fee pricing from data. Works with any iCal-compatible calendar.