Hourly vs. project pricing: which should you use?
Charging by the hour feels safe — you get paid for time you spend. But it quietly caps your income and punishes you for getting faster: the better you get, the less you earn per job. Project pricing flips that. The catch is you have to scope well, or a fixed price becomes a fixed loss. Here's how to choose, and how to price a project without guessing.
When hourly makes sense
Hourly is the right call when the work is genuinely open-ended and you can't pin the scope: ongoing maintenance, "we'll figure it out as we go" consulting, retainers, or a new client where you don't yet trust the brief. Hourly protects you when the unknowns are real.
When project pricing wins
Once you can estimate the work reliably, project pricing is almost always better. It ties your fee to the outcome, not the clock — so if you deliver in 6 hours what you quoted at 10, you keep the upside. It also removes the client's anxiety about a ticking meter and makes your invoice a single, clean number.
Start from the hourly rate you actually need
Even for a fixed price, the math starts hourly: the rate that funds your income goal after costs, tax, and real billable hours. That's your floor. Quote below it and you're subsidising the client.
Estimate the hours honestly, then add a buffer
Guess the hours as truthfully as you can, then add 20–30% for revisions and the things you always forget. Optimism is the fastest way to turn a fixed price into unpaid overtime.
Sanity-check against the outcome's value
If your cost-based price is $2,000 but the work will make the client $50,000, you have room to price on value, not hours. Project pricing lets you capture some of that; hourly never will.
Quote the price, not the hours
Give the client the project number. Don't show your hourly rate or your hour estimate — that just invites them to argue the hours instead of buying the result. Keep the internal math internal.
Get your hourly floor first. Whether you charge hourly or per project, it all starts from one number. Our free rate calculator → does the income-costs-tax-hours math and gives you the floor to build every quote on. No signup.
The hybrid most pros land on
You don't have to pick one forever. The setup a lot of experienced freelancers settle into: project pricing for defined deliverables (the website, the logo suite, the audit) and an hourly rate for the fuzzy stuff (extra revisions beyond the agreed rounds, ongoing tweaks, ad-hoc requests). Best of both — predictable pricing where you can scope, protection where you can't.
If you'd rather hand a target income to a Claude Code skill and get your hourly rate or a project price back — with the math shown — that's /setrate, one of 7 in the Freelancer Pack.
See the Freelancer Pack — $27Common questions
Which is better? Project pricing once you can scope reliably (it rewards speed and outcomes); hourly for open-ended or unpredictable work.
How do I price a project? Hours × your real hourly floor, + a 20–30% buffer, sanity-checked against the outcome's value.
Do I reveal my hourly rate? Not on project work — quote the project price and keep the hours internal.