Hourly to Project Rate Calculator: Turning an Hourly Rate into a Fixed Fee

Why the conversion goes wrong so often

Moving from hourly billing to fixed project fees is the standard progression in a freelance career, and for good reason. Clients prefer a known total. You stop being punished for working quickly. The conversation shifts from how long something takes to what it is worth. Everything about the model favours an experienced freelancer.

The failures come from the arithmetic, not the model. A fixed price is a bet on your own estimate, and three specific errors lose that bet repeatedly: leaving out the communication and project-management hours, leaving the revision count open, and dropping the risk buffer at the moment a client hesitates on price.

Done properly, the conversion is mechanical. Estimate the tasks, add the hours you always forget, multiply by a rate that already covers your costs, add a buffer sized to genuine uncertainty, and cap the scope in writing. Then check the effective hourly rate before you send it — that final step alone catches most underpriced quotes.

How to convert an hourly rate into a project rate in 5 steps

1. 01

   Break the project into tasks you have done before

   Estimate at the task level, never at the project level. 'Redesign the site' is unestimable; 'wireframes, six page designs, two rounds of revisions, handover' is a list you can price from experience. Estimating in pieces also exposes the tasks you have never actually done, which are where overruns live.

2. 02

   Add the invisible hours

   Kickoff calls, weekly check-ins, feedback rounds, email, project management, handover and documentation typically add fifteen to twenty-five percent on top of production time. Every freelancer knows these exist and most leave them out of the estimate anyway, which is why so many fixed-price projects end below the hourly rate.

3. 03

   Multiply by your hourly rate, then apply a risk buffer

   Base fee = total estimated hours × hourly rate. Then add a buffer sized to uncertainty: 10 to 15 percent for familiar work with a clear brief, 20 to 30 percent for a new client or unfamiliar stack, and 40 percent or more where requirements are still being discovered. The buffer prices risk you are absorbing on the client's behalf.

4. 04

   Cap the scope in writing

   A fixed price only works with a fixed scope. State deliverables, revision rounds, response times and what triggers a change order. Without these the client has bought unlimited work at a fixed fee, and no buffer survives that. The change-order clause matters more than the buffer percentage.

5. 05

   Sanity-check the effective hourly rate

   Divide the final quote by your realistic hour estimate — including the invisible hours but not the buffer. If the result sits below your hourly floor, the fixed price is too low regardless of how comfortable the total looks. This one check catches most underpriced project quotes before they are sent.

A worked conversion

Here is a complete conversion for a freelancer on a $95 hourly rate quoting a mid-sized project for a new client. Notice that the communication hours alone add over $1,100 to the correct price — this is the line most commonly omitted.

How much risk buffer to add

The buffer is not padding; it prices the estimation risk you are taking off the client's hands. Size it to how much you genuinely know about the work, and treat the top of the range as a signal that the project needs discovery rather than a quote.

Eight signs your project pricing needs fixing

Each of these turns a correct estimate into an unprofitable project. Three or more together usually means the scope document, not the price, is doing the damage.

• !Fixed-price projects consistently end below your hourly rate
• !Estimates are made for the project, not for individual tasks
• !Revision rounds are unlimited or unstated
• !You quote before understanding who approves the work
• !The buffer is dropped to win the job
• !Communication and project management time is never estimated
• !Change requests are absorbed rather than quoted
• !You have never compared a project's fee to its logged hours

The hours everyone forgets to estimate

Ask a freelancer to estimate a project and you get production time: the designing, writing or building. What reliably goes missing is everything around it — the kickoff call, the weekly check-in, the Slack thread that resolves an ambiguity, the feedback rounds, the file handover, the documentation, the invoice chase.

Across most project types these consume fifteen to twenty-five percent on top of production, and considerably more with committee clients or heavy stakeholder involvement. They are also the least compressible part of the work: you can build faster with experience, but you cannot make a client approve faster.

The remedy is to estimate them as an explicit line rather than hoping they fit in the gaps. Once communication is a percentage in your template, the correction happens automatically on every quote, and the projects that were quietly unprofitable become visible before you agree to them rather than after.

Scope control is worth more than the buffer

Freelancers tend to focus on the buffer percentage because it is the number in the formula. In practice, scope definition determines profitability far more decisively. A twenty percent buffer on an uncapped revision cycle disappears in a fortnight; a ten percent buffer on a scope with two stated revision rounds and a change-order clause holds comfortably.

Write four things into every fixed-price proposal: the specific deliverables, the number of revision rounds included, the client response time you are assuming, and the statement that additional work is quoted separately. None of this is adversarial — clients are generally reassured by clarity and unsettled by vagueness.

Then enforce it the first time it matters, politely and in writing: 'That sits outside the two rounds we agreed — I can add it for X, or hold it for phase two.' Absorbing the first small change is the decision that makes every later change free, and it is made almost always in the interest of goodwill that the client never actually asked for.

When to stay hourly instead

Fixed pricing is not universally better. It works when you have done comparable work enough times to estimate within about twenty percent, and when the deliverable can be described precisely. Neither condition is optional — a fixed price on genuinely unknown scope is the worst of both models, carrying the client's risk without the hourly billing that would compensate you for it.

Stay hourly for ongoing maintenance and support, for research and discovery, for the first engagement with a client whose working style you do not yet know, and for anything where the requirements are being discovered as the work proceeds. Hourly billing is not a junior pricing model; it is the correct instrument when uncertainty is the dominant factor.

A practical middle path is to run a small paid discovery phase, produce a specification, and quote the build as a fixed price from that document. The client gets a firm number, you get a scope you can defend, and the estimation risk drops to the point where a modest buffer genuinely covers it.

Frequently asked questions