Why Freelancers Should Stop Charging by the Hour

Hourly billing has one flaw that compounds the longer you use it: the better you get at your job, the less you can charge. A junior designer who takes 12 hours to build a landing page earns more on that project than the senior designer who does it in four. That is not a flaw you can optimize around. It is baked into the model.

You are selling outcomes, not time

Clients who hire you do not care how many hours it took. They care whether the landing page converts, whether the code ships on time, whether the copy says the right thing. The value you deliver exists independent of the hours you logged.

A consultant who advises a company to restructure a product line in a two-hour call has arguably delivered more value than one who spent 40 hours writing a report that says the same thing. Hourly billing treats both as unequal. Project pricing lets the outcome determine the number.

The ceiling problem

Hourly rates cap your annual income at a number that is roughly your rate times your billable hours. If you charge $100 an hour and bill 1,200 hours a year, you make $120,000 — and to grow past that you either raise your rate or work more hours. Raise the rate and you risk losing clients. Work more hours and you burn out. The ceiling is real and it arrives sooner than most people expect.

Project pricing does not eliminate that ceiling, but it shifts it. When you scope work accurately, build in a buffer for revision cycles, and price for the outcome rather than the clock, an eight-hour project can command what twenty hours used to pay. You get faster. Your rate per hour of effort rises. The business gets more efficient without requiring you to either work more or charge more by the hour.

How to price a project instead

The process is simpler than most people make it:

1. Define the deliverables precisely. A project price is a commitment, so the scope has to be exact. What are you delivering? In what format? By what date? With how many revision rounds included?
2. Estimate your time honestly — including the overhead that never shows up in an hourly estimate: briefing calls, feedback rounds, file prep, email back-and-forth. These are real hours that drain your margin in a project quote just as surely as they do in an hourly one.
3. Apply your target effective hourly rate to that estimate, then add a 15 to 25 percent buffer for the unexpected. That is your floor. If the value to the client is meaningfully higher than that number, price toward the value instead.
4. Put the number in writing with a clear scope and change-order language. The project rate is a promise about a defined piece of work — anything outside it is a new conversation.

When hourly still makes sense

Not all work suits project pricing. Open-ended consulting, exploratory research, ongoing retainers with undefined tasks, and anything where the scope shifts week to week is genuinely hard to scope upfront. For work that is open-ended by nature, hourly or a time-and-materials structure is honest and appropriate.

But most creative and service work is not actually open-ended. It only feels that way because committing to a number feels risky. That discomfort is better addressed by getting better at scoping than by leaving the price undefined and absorbing the risk of underpricing indefinitely.

Even if you convert every project to flat-fee pricing, track your actual hours. Knowing your real effective rate per project — what you earned per hour of effort — is the only way to know whether your project prices are working. HelmBill lets you log time per project even when the client never sees the clock, so you can price the next engagement smarter.