For years I billed by the hour, because that's what everyone did and I never thought to question it. Then one day a client asked an innocent question that broke the whole model for me: 'So… the better you get at this, the less I pay? Doesn't that punish you for being good?'
He was right. And the more I sat with it, the more I realized hourly billing quietly sets the client and the developer against each other.
The perverse incentive nobody admits
Under hourly billing, slowness is rewarded. The developer who takes twice as long earns twice as much. Experience — the very thing that lets me solve in an hour what once took a day — actively costs me money. And the client, sensing this, starts watching the clock instead of the outcome. Trust erodes on both sides.
What value-based pricing changes
- You know the full price before we start — no anxious clock-watching
- I'm rewarded for being fast and efficient, not for dragging things out
- We both focus on the outcome, not the timesheet
- Using AI to deliver faster benefits you, instead of cutting my pay
That last point matters more than ever. If I can use modern tools to deliver your project in half the time, hourly billing would force me to charge you half as much for the same result — penalizing efficiency. A fixed, value-based price means those savings show up in speed, not in a smaller invoice for me and a worse deal for neither of us.
You're not buying my hours. You're buying the result those hours produce.
So now, almost every project starts with a free conversation and a clear, fixed quote. You always know the cost. I'm always rewarded for doing great work quickly. Everyone's pulling in the same direction — which is how it should have been all along.