Technical
Consulting Pricing: Four Months of Moving Away From Hourly
Hourly billing is the default in consulting for a reason: it is simple to explain and simple to invoice. It is also the worst incentive structure in the business. Four months of deliberately moving away from it has reshaped how I run my practice. Here are the lessons.
The Hourly Trap
Hourly billing rewards slowness. The longer you take, the more you make. Your client pays for your learning curve, your inefficiencies, and your occasional mistakes. They also pay for the tool that made you faster, which is absurd.
I never consciously milked hours. No serious consultant does. But the structure works against trust. Clients second-guess invoices. I feel defensive about time I spent thinking rather than typing. The whole relationship is slightly off.
The Shift
I now quote fixed scopes with clear deliverables. 'Build a content pipeline that publishes daily with bounce handling and analytics, delivered in three weeks.' Price attached. What I do inside that box is my business.
This aligns incentives. I get faster, I win. The client sees the outcome they bought. The work gets delivered.
The Framework That Works
For every engagement I now define three things upfront:
- Scope: what is in and out, listed specifically
- Deliverables: what changes hands at the end
- Success criteria: how we both know it worked
Engagement template I reuse:
Scope:
In: [3-5 bullets]
Out: [2-3 bullets clarifying exclusions]
Deliverables:
- Live production system
- Source code in client repo
- Handoff documentation
Success criteria:
- [measurable outcome 1]
- [measurable outcome 2]
Price: $X, due as [deposit/milestones/end]The Mistakes I Made
Early on I underestimated scope and ate the difference. Bad for me, bad for the client because I was grumpy about it. The fix: add a scope buffer and let the client see I will not bill them for changes within it.
I also quoted too low at first. Value-based pricing requires believing in your value. I was asking for hourly-equivalent amounts instead of outcome-equivalent amounts. Raising rates did not lose deals. It attracted better ones.
The move from hours to value is a mindset shift, not a pricing tweak. It took me four months to internalize. See Jonathan Stark's hourly-billing-is-nuts newsletter for a practitioner's take that helped me along.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read