Technical
Pricing Lessons From Twelve Months of Technical Consulting
Pricing is the hardest part of consulting. Undercharge and you burn out. Overcharge and you lose deals. I experimented with multiple pricing models this year and I have concrete data on which ones produced better outcomes for me and for clients. Here is the honest pricing retrospective.
The Models I Tried
- Hourly: $X per hour, tracked in Harvest
- Day rate: $Y per day, invoiced monthly
- Fixed fee: $Z per scoped project, paid on milestones
- Retainer: monthly recurring for ongoing work
I used all four this year. Each worked in specific situations. Each failed in others.
What Hourly Got Right and Wrong
Hourly was right for ambiguous scopes (audit, debugging, exploratory work). Hourly was wrong for well-defined projects where faster work was a feature, not a billing reduction. AI-assisted work made hourly structurally bad because my speed increased but my hourly rate stayed flat.
Why Fixed Fee Won Most Often
Fixed fee aligned incentives. I got paid for outcomes. The client got certainty on cost. AI tools let me finish faster without reducing the invoice. Everyone won except the assumption that more hours equals more value.
Hourly: speed hurts me
Fixed fee: speed helps meThat sentence is why fixed fee is my default now.
The Retainer Trap
Retainers sound great. Predictable revenue. Ongoing relationship. In practice, retainers need careful scope definition or they become open-ended support contracts that consume more hours than they pay for. I only use retainers with strict monthly scope caps now.
The Value Question
The pricing question that actually matters: what is this worth to the client? A platform that saves them $2,000 per month in admin time is worth more than eighty hours at any hourly rate. Value-based pricing is uncomfortable for technical founders. Practice it anyway.
What to Raise and How
I raised my rates twice this year. Both times I signaled to prospects before current clients. Existing clients at the old rate stayed at the old rate until the end of the current scope. No surprise invoices. Rate changes as a transparent policy, not a confrontation.
The Bottom Line
- Default to fixed fee for scoped work
- Hourly only for genuinely open-ended exploration
- Retainers only with strict monthly caps
- Raise rates regularly, transparently
- Price on value, not on cost-plus
A year of pricing experiments gave me real conviction on these. Your mileage may vary, but the experimentation is the lesson.
For a deeper framework, I recommend The Consulting Bible and Alan Weiss's broader body of work.
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