Pricing · November 19, 2026 · 3 min read

Hourly vs Project Pricing: When to Switch

Hourly rates feel safe but cap your income and punish speed. When project pricing makes more sense, and how to make the switch without guessing.

By Amos

Ho -40 $ K&C · NO. 05

Most freelance designers start by charging by the hour. It is easy to explain, easy to calculate and feels fair to both sides. For some work, it stays the right model.

But hourly pricing has a built-in problem: the better and faster you get, the less you earn for the same result. At some point, the model that felt safe starts working against you.

What hourly pricing gets right

Hourly is a good fit when the scope is genuinely unknown:

In these cases, a fixed price would force you to guess, and a wrong guess costs you.

Where hourly breaks down

It punishes efficiency. A logo concept that took you ten hours five years ago might take four today, because of experience, templates and better tools. The client gets the same or better result. You get paid less.

It invites the wrong conversation. Clients start questioning hours instead of discussing outcomes. "Why did this take three hours?" is a hard question to win.

It caps your income. There are only so many billable hours in a week, and fewer than most people think once admin and sales are counted.

What project pricing changes

With a project price, the client pays for the result: a brand identity, a website design, a campaign. How long it takes you is your business.

That shifts the conversation to value. What is this identity worth to a company launching a new product? That number is usually well above your hours multiplied by your rate.

It also rewards everything you build over time: systems, templates, reusable components and faster decisions.

Signs it is time to switch

If three of these are true, you are ready.

How to switch without guessing

  1. Track your hours for every project type for a few months, including emails and revisions.
  2. Calculate your base price: typical hours multiplied by your target hourly rate.
  3. Add a buffer for revisions and the unexpected.
  4. Adjust for value: a logo for a local café and a logo for a funded startup are not the same project.
  5. Define the scope clearly, with revision rounds written in. Project pricing only works when the boundary is clear.

Your hourly rate does not disappear. It becomes an internal tool for checking your quotes, instead of the number the client sees.

A third option: a quote that grows with the feedback

There is a model between hourly and fixed that I like: a dynamic quote, where the price depends on how much feedback the client sends. The more rounds of revisions and comments, the higher the final price.

In practice it looks like this:

  1. The base price covers the work plus a set number of revision rounds, for example two.
  2. Each additional round has a fixed price, written in the proposal from day one.
  3. The client knows the rule before they start, so the extra cost is never a surprise.

It solves the biggest weakness of a fixed price, the endless "small tweaks", without going back to counting hours. And it changes how clients give feedback. When every round has a cost, they gather their notes, agree internally, and send one clear list instead of a stream of emails.

A hybrid that works

Many experienced freelancers use both: a project price for defined work, and an hourly rate for anything outside the scope. The hourly rate becomes the price of change, which also makes scope creep much easier to handle.

← All posts