Hourly vs. Project Pricing: How Should You Charge for Your Expertise?

At some point, almost every service provider confronts the same uncomfortable question:

Should I charge by the hour or by the project?

The usual debate around hourly vs. project pricing tends to produce strong opinions. Hourly billing is supposedly limiting. Project pricing is supposedly more sophisticated. Value pricing is sometimes presented as the enlightened destination we should all eventually reach.

I don't think it's that simple.

The better question is not, "Which pricing model is best?"

It's:

What kind of work am I actually asking the client to buy?

Because pricing works best when the structure of the price matches the shape of the work.

This is something I explore more deeply in The Price of Being True. Good pricing isn't simply about finding the highest number someone will agree to pay. It's about creating an arrangement that respects the value of the work, the realities of delivering it, and the relationship you're building with the client.

What Is the Difference Between Hourly and Project Pricing?

Hourly pricing charges clients for the time required to perform the work. Project pricing charges an agreed fee for a defined scope of work or deliverable.

Hourly pricing works particularly well when the amount of work is difficult to predict or changes frequently. Project pricing works well when the scope, responsibilities, and outcome can be defined with reasonable clarity.

Neither is inherently better.

The problem begins when the pricing model and the work don't match.

Hourly Pricing Sells Access to Capacity

Hourly billing gets criticized because it can appear to punish efficiency.

If something once took you five hours and experience allows you to accomplish it beautifully in two, why should becoming better at your work reduce what you earn?

That's a legitimate concern.

But hourly pricing isn't inherently unsophisticated.

Sometimes the client genuinely is purchasing access to your time and capacity.

Perhaps you're advising a team whose needs evolve from week to week. You're troubleshooting unpredictable issues. You're performing ongoing work where neither side can reasonably define the eventual scope.

In those situations, time may be the cleanest unit of exchange.

The mistake is not charging hourly.

It's using hourly pricing for work where time has very little relationship to the value being created.

Project Pricing Sells a Defined Piece of Work

Project pricing changes the conversation.

Instead of saying, "You are purchasing ten hours of my time," you're saying, "You are purchasing this clearly defined piece of work."

That can be better for both sides.

The client knows what the investment will be. You have an incentive to become more efficient. And the conversation can focus more on what is being created than how long you sit at your desk creating it.

But project pricing introduces a different risk:

uncertainty.

If the project you imagined turns out to be three times larger, your tidy flat fee can become very expensive for you.

That's why good project pricing depends on good boundaries.

Scope Creep Is Usually a Clarity Problem Before It's a Pricing Problem

The original version of this article warned about scope creep, and I still think that's important.

But I've come to see scope creep a little differently.

Sometimes clients knowingly ask for more than they purchased.

More often, the two sides simply had different mental pictures of what was included.

That's an infrastructure problem.

Before setting a project price, clarify:

• what you're delivering
• what isn't included
• how many revisions or iterations are included
• what you need from the client
• when you need it
• what happens if the project changes
• how additional work will be priced

A contract matters, of course. But the contract should document clarity that already exists rather than being the first place anyone discovers the boundaries.

Don't Calculate Project Pricing From Perfect Conditions

One piece of my old advice was to estimate the hours a project should take, multiply that by an hourly rate, and then add a buffer.

There's still some usefulness in knowing your internal numbers.

If you routinely price projects that require $5,000 worth of your capacity at $2,000, enthusiasm isn't going to fix the economics.

But I wouldn't recommend a universal multiplier.

Instead, consider the full cost of delivering the work.

How much direct work will it require?

How much communication?

How predictable is the scope?

How much thinking happens away from the visible deliverables?

Will other work have to be declined while you complete it?

What level of expertise does the project require?

What risks are you absorbing?

Your internal hourly rate can be useful for checking whether the project makes financial sense.

It doesn't necessarily need to determine what the client pays.

There Are More Than Two Pricing Models

This is another place where my thinking has expanded.

The choice isn't simply hourly or project.

A retainer may make sense when a client needs ongoing access, advice, or recurring deliverables.

A project fee may suit a clearly defined engagement.

Hourly or day rates can work well when the scope is uncertain.

Some expert services can be priced around the nature and significance of the engagement rather than the number of hours involved.

You can also combine models.

For example, a defined strategic project might have a fixed fee, while additional implementation outside the agreed scope is priced separately.

The objective isn't to graduate from one model to another.

It's to build a pricing architecture that fits the business.

Pricing Should Follow the Shape of the Work

This is the distinction I'd use when evaluating your own services.

Predictable work can support predictable pricing.

Variable work often needs variable pricing.

Ongoing work needs an ongoing structure.

High-leverage expertise shouldn't automatically be reduced to units of time.

Once you understand the shape of the work, the pricing decision becomes much easier.

You may even discover that different services within your business need different models.

That's not inconsistency.

It's coherence.

Your Pricing Model Also Shapes the Client Relationship

Pricing doesn't simply determine what you earn.

It quietly influences behavior.

When clients are paying hourly, they may hesitate before contacting you because every interaction feels metered.

With a project fee, they may assume anything remotely connected to the project is included.

With a retainer, they may expect ongoing availability unless boundaries are clear.

Every pricing structure creates incentives and expectations.

So when evaluating a pricing model, don't ask only:

How much could I earn?

Also ask:

What kind of working relationship will this structure create?

That question can save you considerable frustration later.

Choose the Model That Makes the Work Sustainable

There isn't one correct answer to hourly vs. project pricing.

There is only a model that fits the work better or worse.

Understand what the client is buying.

Understand the uncertainty you're carrying.

Define the boundaries.

Know your internal economics.

Then choose the pricing structure that allows you to deliver excellent work without quietly resenting how you've agreed to be paid for it.

Because a good pricing model should do more than help you close the sale.

It should create conditions in which both you and the client can succeed.

N.B. Post revised 2026.