Every freelancer has a war story for both sides of this argument. I have two, and they happened in the same month.
On the hourly side: a client I tracked time for down to the minute, where I solved in forty minutes a problem I'd have billed four hours for in my first year. My skills had doubled. My invoice had halved. I sat there staring at the timer thinking, so this is the reward for experience. A smaller cheque.
On the fixed side: a "simple" website quoted in one confident number, where the scope quietly doubled over six weeks of friendly little additions. I earned, when I finally did the maths, less per hour than my first ever job. Same month. Same freelancer. Two different ways to lose.
That's why this debate never dies. Both models have a trap in them, and the traps are different. The skill is knowing which trap a given project is holding.
Hourly: Honest, Simple, and Quietly Capped
Hourly's great virtue is fairness when the work is genuinely unknowable. Research, consulting, open-ended support, anything where neither of you can see the bottom of the task. You work, you bill the time, nobody gambles.
Its weakness is structural. Your income is capped by hours in a week, you get financially punished for every efficiency you develop, and some clients watch the clock like it owes them money, questioning a 25-minute block while happily paying a plumber's callout fee. Hourly also makes clients compare you to other hourly humans rather than to the result, which is a race to the bottom with your face on it.
Fixed Price: Where the Real Money Hides, Guarded by Risk
Fixed price flips everything. Now the client buys an outcome, not your hours. Get faster, and your effective rate climbs. Price the value well, and a two-day job can pay what a tracked month used to. This is where experienced freelancers' incomes actually jump.
But the risk moved too, onto you. Every unknown in the project is now your problem at your price. Fuzzy scope is not an inconvenience under fixed pricing, it's a direct donation. The freelancers who thrive on fixed price are not braver than you. They're just religious about three things: a written scope with a "not included" list, a change order habit for everything beyond it, and a price that includes a margin for the surprises they know are coming.
The Maths That Settles Most Arguments
Take a project you believe is 20 hours. At an hourly rate of $50, it's $1,000, and if it balloons to 30 hours you bill $1,500 and stay whole, while the client absorbs the growth.
As a fixed quote you'd say $1,250, pricing in some risk. If it lands at 20 hours, your effective rate is $62.50 and everyone is happy. If it balloons to 30 hours with no change orders, your rate collapses to about $41 and you're funding the client's learning curve. Same project, same work. The model, and how well you fence it, decides who eats the surprise.
Run the comparison on your own recent projects and the pattern of your year appears. If scope keeps growing on your fixed work, your fence is the problem, not the model. The Scope Creep Calculator exists to measure exactly that growth before you quote the next one.
The Hybrid Most High Earners Actually Use
Ask around quietly and a third pattern shows up everywhere. Fixed price for the defined core, the deliverables everyone can see and count. Hourly or day-rate for the fog around it: exploration, meetings, support, "can we just try" experiments. And a written rule connecting them, that anything new joins the project through a change order at the stated rate.
Some go further and sell days or weeks instead of hours. A day rate keeps the honesty of time-based billing but restores your dignity: nobody argues about whether Tuesday contained six billable hours or seven. Tuesday cost what Tuesday costs.
So Which One, For You, This Project?
Choose hourly when the scope honestly can't be known yet, when the client is new and trust is still being built, or when the work is support and maintenance that arrives in drips.
Choose fixed when the deliverable is countable, the client keeps saying "exactly like this one," and your scope document is tight enough to lean on. Newer freelancers often do better starting hourly while they learn how long things truly take, then moving to fixed once their estimates stop lying to them, carrying their hard-won numbers with them.
Whichever you pick, pick it on paper. The fee argument you have at the start, when everyone is friends, is the cheapest one you'll ever have. The one at the end costs money, sleep, and sometimes the client.
Price isn't a personality trait. It's a tool. Use the one the project is asking for.
Questions About Fixed vs Hourly
Can I switch a client from hourly to fixed later?
Yes, and it's a natural graduation. Once you know their work and your timings, propose it as a benefit to them: a predictable number, no clock-watching, same person. Most good clients prefer the certainty too.
What if a client demands fixed price on a fuzzy project?
Price the fog. Break the project into a small paid first phase with a fixed price, discovery or a prototype, after which the rest can be quoted honestly. If they refuse even that, the fuzziness is the point, and you should charge like it.
How do I raise my effective rate without scaring clients?
Move work from hourly to fixed as your speed grows, and let the outcome carry the conversation. A client who happily paid $2,000 for a result does not care that it took you eleven hours instead of thirty.
Do I need to track time on fixed price work?
Privately, yes, at least loosely. Your own records are how you learn what things cost, spot creep while it's still small, and quote the next fixed project like someone who's been here before.