Stop Selling Time. Start Selling the System.
Hourly billing punishes efficiency. Project-based pricing rewards outcomes.
Hourly billing has a structural flaw that no amount of good intentions can fix: it punishes efficiency. The faster you solve a problem, the less you earn. The more experienced you become, the less time each project takes, and the less revenue each project generates. Your expertise is literally working against your income.
A consultant who bills $250/hour and solves a problem in four hours earns $1,000. A consultant who bills the same rate but takes twelve hours (because they are less experienced, or less efficient, or more thorough than necessary) earns $3,000. The client pays three times as much for a worse experience. The slow consultant earns three times as much for inferior work. The incentives are exactly backwards.
Project-based pricing flips the model. You define the deliverable, set the price, and deliver it. If you finish in two days, your effective rate is exceptional. If it takes four days, it is still reasonable. The client knows the total cost before they commit. You know the revenue before you start. Both sides have certainty.
The transition from hourly to project-based pricing requires solving three problems.
First, you need to be able to scope accurately. This is the hardest part and the most common objection. "What if the project takes longer than I estimated?" This is a legitimate risk, but it decreases with experience. After delivering a dozen brand strategy projects, you know how long a brand strategy project takes. The uncertainty that justifies hourly billing in year one does not justify it in year five.
Second, you need to define deliverables clearly. "Strategy consulting" is not a deliverable. "A positioning document, a competitive analysis, and a 90-day implementation plan" is a deliverable. The more specific the output, the easier it is to price and the harder it is for the client to expand the scope without a conversation about additional cost.
Third, you need to resist the urge to track hours internally as a "check" on your pricing. This defeats the purpose. If you price a project at $8,000 and it takes you 16 hours, your effective rate is $500/hour. That is a great outcome. If you then feel guilty because you "only worked 16 hours," you are still thinking in hours. The client paid for the deliverable, not for your time. The deliverable was worth $8,000 to them regardless of how long it took you.
The psychological shift is significant. Hourly billing feels safe because effort equals income. More hours, more money. Project-based pricing feels risky because the income is fixed and the effort is variable. But the risk is one-directional: it only hurts if you are bad at scoping, and scoping improves with every project you deliver.
There is also a client-side benefit that consultants underestimate. Clients hate hourly billing. They hate watching the clock during meetings. They hate receiving invoices that itemise "email correspondence: 0.5 hours." They hate the uncertainty of not knowing what the final bill will be. A fixed project price removes all of that friction. The client knows the cost, agrees to it, and never thinks about it again until the deliverable arrives.
The consultants who charge the highest effective rates are not the ones billing the most hours. They are the ones who have productised their expertise into defined deliverables with fixed prices, who deliver faster than anyone else because they have done it dozens of times, and whose clients never ask "how many hours did that take?" because the question is irrelevant. The deliverable speaks for itself.
Build the system worth selling.
You cannot sell the system until it exists. The 12 Principals programme is the twelve month build that turns your expertise into productised, one-to-many infrastructure you own.
