Why I Don't Charge by the Hour

Every consultant I know charges by the hour, at least at the beginning. It's the default. It feels safe. It feels fair — you pay for time, you get time. The math is visible and auditable.

I charged by the hour for about a year. Then I switched to flat fees and haven't gone back.

Here's why, and here's why I think it matters more than it seems.

The problem with hourly billing

Hourly billing has a structural flaw: it rewards inefficiency. If I can do your tech stack setup in 15 hours because I've done it forty times and I know exactly what to do, that competence punishes me. A slower consultant — or the same consultant two years ago, before all the practice — takes 30 hours and gets paid twice as much.

That is not a system that benefits you. It's a system where the price of my experience falls to zero for one of us, and it's not me.

The other problem is that hourly billing puts the cost uncertainty on you. You have a rough estimate, and you have the anxiety of watching the hours accumulate. Every email you send, every question you ask, every request for a small change registers somewhere as a cost you can't fully predict. That friction changes the relationship. You start rationing communication because you're worried about the bill.

What flat fees change

A flat fee inverts the incentives correctly. I quote a price for a defined scope of work. If I finish efficiently, I keep the margin. If something takes longer than I expected, that's my problem. The price is the price.

For you: the cost is known before we start. You can plan for it, approve it, budget it. There are no surprises in the invoice. You can email me with questions without it feeling like you're running up a tab.

For me: I have every incentive to be efficient, to use the right tools, to avoid scope creep, to do the work cleanly the first time. There's no hidden benefit to complexity.

What flat fees require

They require me to scope carefully. If I underquote a project because I didn't ask enough questions, that's on me. If the scope creeps because I wasn't clear enough about what was included, that's on me.

This is appropriate. I'm the professional. I should be able to say with reasonable confidence what a project like yours takes. If I can't, I'm not yet experienced enough to be charging flat fees — which is why I think most consultants start with hourly and only switch to flat after they have enough repetitions to estimate accurately.

The other thing flat fees require is a written scope. Not long — a page or two — but specific enough that both of us know what we're agreeing to. What's included, what's not, what the deliverable looks like. This protects both parties from differing expectations.

The one thing hourly is actually good for

Retainer arrangements, where the work is genuinely variable week to week, are better handled hourly or with a monthly block of hours rather than a flat fee. When you genuinely don't know in advance what the work will look like — and neither do I — a flat fee requires either a very wide contingency (which is expensive for you) or an underestimate (which is bad for me).

For most discrete projects — a tech stack setup, a subscription audit, an AI implementation — the scope is knowable enough that a flat fee is the right structure.

The short version

If I can do your project in ten hours because I know what I'm doing, you shouldn't pay for twenty hours to compensate for the fact that I'm good at this. That's the whole argument.

Flat fees are better for you when the scope is clear, better for me when I'm efficient, and produce a cleaner working relationship than one where every communication is registered as a cost.