How We Price Development Work (And Why Most Consultancies Get It Wrong)

In fourteen years of consulting, we have experimented with every pricing model. Pure hourly billing is where most freelancers start and where many get stuck. The appeal is obvious: track time, send invoice, get paid. The problem is equally obvious: your income is capped by hours. Work faster, earn less. We experienced this directly when a project that should have taken 40 hours took 25 because we had gotten more efficient. We earned 37% less for delivering the same value, faster.

Fixed-price projects seem like the solution. But every fixed-price project we have done had scope creep. Not because clients are dishonest, but because requirements evolve as you build. We tracked 22 fixed-price projects. Average scope creep was 35%. Average actual hourly rate after creep was 28% below target.

Value-based pricing is the dream: charge based on value delivered. But it requires measurable, attributable business outcomes that software projects rarely provide cleanly. When we build a customer portal, did revenue increase because of the portal or the sales team's efforts? Attribution is hard, and ambiguity creates friction.

We settled on a hybrid: hourly billing within a monthly retainer structure. Our rate is $50 per hour, deliberately below market for our experience level. We can charge this rate and maintain our target income because we are fast. A project that takes an average developer 40 hours takes us 20-25 hours thanks to tooling, templates, and pattern recognition.

The retainer is the key innovation. Clients buy 20, 40, or 80 hours monthly. Unused hours bank for one month. This provides predictable revenue for us and predictable costs for clients. It eliminates the per-project estimation dance. The client has hours this month. We work on whatever is highest priority. If priorities shift, we pivot without change order negotiations.

Retainers fundamentally changed our client relationships. Under per-project billing, every scope conversation was implicitly a money negotiation. Under retainers, "can we add this?" becomes "is this the best use of our hours this month?" The dynamic shifts from adversarial to collaborative.

The failure mode is underutilization. If a client consistently uses 15 of their 40 hours, we proactively suggest reducing. A happy client on a 20-hour retainer is better than a resentful client on 40 who feels they are wasting money. Price based on value per hour, not hours worked. Get faster, use better tools, build templates. Moderate rate, high value delivery.