Why Your Hourly Rate Is the Wrong Number to Optimise

There's a question that gets asked at every agency owner's panel: "What's the right hourly rate to charge in 2026?" The implicit assumption is that there is a right answer; the explicit response is usually a benchmark range with regional and seniority adjustments.

I've stopped answering this question, because it's the wrong question. Optimising the hourly rate is optimising the third-most-important variable in a pricing system that has a much more important first one.

The first is the structure of the pricing — hourly, day rate, role rate, value-based. The second is the role mix underneath that structure. The third, and only third, is the rate itself. Most pricing reviews I've sat in at other agencies focus the entire conversation on the third while ignoring the first two. That's where the money is leaking.

This piece is a practical case for moving most engagements off hourly pricing. It's not an argument that hourly is always wrong — there are engagements where it's the right choice — but it's the argument I wish someone had laid out for me when I was in my first year of running an agency, debating whether to push our hourly rate up by £15.

What the hourly rate hides

Take an estimate that lists 200 hours of engineering at £140/hour: a £28,000 quote.

The client sees a single number — £140 — and either accepts it, negotiates it, or rejects it. The negotiation, when it happens, happens at the hourly level: "we've got it benchmarked at £125 in this market, can you match?"

What the £140 figure hides:

• Whose hours are inside it. The estimate doesn't say whether the 200 hours are 50 lead + 150 mid, or 200 mid, or 100 lead + 100 junior. The hourly rate has been blended to absorb the role mix.
• What the agency's real cost will be on those hours. The agency's cost ranges from about £40/hour (a junior at full utilisation) to £85/hour (a senior with overhead and bench time). The £140 hourly is meant to cover the average, with margin.
• What happens if the client increases scope. The next 50 hours will be quoted at £140 too. The client doesn't know whether the marginal hour costs the agency £40 or £85. They're free to assume it costs £40 — and to negotiate accordingly.
• What the agency does when the work goes faster than expected. If the team finishes the 200-hour scope in 160 hours, the agency invoices £22,400 instead of £28,000. The agency has been punished for being efficient.

The fourth one is the pattern that quietly drains agencies. Hourly billing rewards inefficient teams. Efficient teams that deliver the same outcome in fewer hours invoice less. The compensation structure is upside-down.

What day rates fix

The simplest move is to switch from hourly to day rate. A day rate covers a full working day of a named role; below the day-rate granularity, time isn't tracked from the client's side.

For the same engagement: 25 days of engineering at £1,200/day = £30,000.

What changes:

• The "did you really spend 47 minutes on that?" conversation goes away. Days are a clean unit of accounting; the client cannot dispute fractional hours.
• Efficiency stops being punished. A team that finishes a day's work by 3pm has effectively earned more margin per day. The team can use the extra time on quality, on the next ticket, or on a small unbilled improvement that the client notices and remembers.
• The negotiating surface gets smaller. Day rates are harder to compare across agencies (because day length and inclusion of overhead vary), so clients have less leverage to negotiate.

What doesn't change: the role mix is still hidden. A "day of engineering" can still mean a senior or a junior. The conversation about role mix has to be moved elsewhere.

The day-rate switch alone, in our experience installing it across two agencies, lifted average margin per project by 4–6 percentage points. Most of that came from the disappearance of the per-minute negotiation and the small amount of unbilled "rounding" time in every project.

What role rates fix

A role rate structure prices each role separately: Lead at £1,800/day, Senior at £1,400/day, Mid at £1,000/day, Junior at £700/day, QA at £900/day, etc. The same engagement now reads as something like:

• 5 Lead days × £1,800 = £9,000
• 12 Senior days × £1,400 = £16,800
• 8 Mid days × £1,000 = £8,000

Total: £33,800.

What changes from a day-rate structure:

• The role mix is now declared. The estimate states explicitly which role does which work. The conversation with the client about price becomes a conversation about role mix, which is a conversation the agency wins more often than loses (see the role-rate estimating piece).
• The agency can defend the lead's involvement. Instead of absorbing senior time into a blended rate and hoping the project doesn't go off-plan, the lead's hours are explicit and defensible.
• The agency can correctly track variance. When a senior absorbs a mid's work, the variance is measurable against the estimate's role line. Margin reports can flag the variance the same week.
• Pricing negotiations get sharper. The client who wants the price down 10% has to engage with which role to cut, which is a quantitative conversation.

The price will typically be 8–15% higher than the equivalent blended hourly estimate. The first time you send a role-rate estimate to a long-standing client expecting an hourly one, expect a flag-up call. The honest answer is: the new structure is more transparent, the price reflects the actual senior involvement that the previous estimates were absorbing into a blended rate, and the project will run more honestly under the new model.

About 80% of clients accept the new structure within one engagement cycle. The 20% that don't are usually procurement-led and want hourly back; for those clients, the agency keeps a blended hourly option in reserve and prices it slightly higher to compensate for the visibility cost. (We'll come back to that.)

What value-based pricing fixes

The most aggressive move is to decouple price from time entirely. The client buys an outcome — a working e-commerce platform that processes £50m of GMV in its first year, a working CRM integration that saves the sales team 200 hours a quarter — at a price that reflects the value of the outcome rather than the cost of the time.

Value-based pricing has obvious upsides and a much more complex set of conditions for it to work:

• Upside: the agency captures a share of the value, which is often 5–10× the cost-based price. A migration that saves the client £400k a year can be sold at £80k–£200k rather than the £40k–£60k the time would have cost.
• Condition: the agency has to credibly own the outcome. If the client's success depends on factors outside the agency's control — internal politics, technical decisions made before the engagement, a parallel vendor's work — the value claim can't be defended and the price falls back to cost-based.
• Condition: the agency has to be willing to walk away when the outcome value is small. A £5k website redesign for a small client cannot be value-priced unless the £5k itself is meaningful to the client. Most agency value-pricing engagements live in the £40k–£500k range.

About 20% of our engagements are now priced this way. They're concentrated in two segments: bespoke integrations where the saved time has a defensible monetary value, and platform migrations where the cost-of-staying is high enough to anchor the price.

Value pricing is not the right answer for most engagements. It is the right answer for some. The mistake we see frequently is agencies trying to push every engagement into value pricing, which produces a high failure rate (clients balk) and a high mis-pricing rate (agencies over-claim value they can't credibly own).

The four-case decision

Which structure to use depends on the engagement. The simple rule we use:

This is not exhaustive. There are mixed engagements (a build with an ongoing retainer) where each component should be priced separately under the structure that fits it. There are exceptional cases (very small clients, very long-term partnerships) where the agency may default to a blended hourly rate as a relationship choice.

But for the average mid-market agency engagement — which is most agencies' bread and butter — the right answer is role rate for builds, monthly retainer for ongoing. Hourly billing should be the exception, not the default.

What to do with the rate-card conversation

The rate-card conversation that opens every agency's pricing review is usually a question of "should our hourly rate be £125 or £140 in 2026?" The answer this article points to is: ask a different question.

The questions that matter, in order:

• Are we billing this engagement type in the right structure? (hourly / day / role / monthly / value)
• If we're using role rates, is the mix on the estimate defendable, and would it survive an honest reading of who actually delivered last project?
• Is the rate per role adequate to cover the named individual's real cost plus margin plus our share of overhead?
• Only after all of these are answered: should the rates go up?

The fourth question is much smaller than the first three, both in the size of the change and in the size of the impact. Moving hourly rates up by 10% on a poorly-structured engagement is easier than restructuring the engagement, but the impact on profitability is much smaller. Restructuring an engagement from hourly to role-rate, in our data, lifted margin by 8–14 percentage points; pushing hourly rates up by 10% lifted it by 4–6.

If the partial answer to "should our rates go up" is yes, then yes — but if you've answered the first three questions first, you're operating from a much sharper position when the rate increase conversation happens with the client.

What this looks like inside Saldo

The reason we wrote our financial layer to read role-rate and real-employee-cost as separate numbers, rather than collapsing them into a blended hourly figure, is everything in this article. The role-rate vs employee-cost variance per project is the place where most of the margin movement happens at agencies on Jira. A system that doesn't surface that variance gives you a clean number that's wrong by 15–25 percentage points.

If you'd like to see your own engagements re-projected from blended-hourly to role-rate variance, on your real Jira data, Saldo is the layer I built. Pricing is at the pricing page; the founding-agency case study is two years of internal use at the agency where I built it as CTO.

The shorter version: stop optimising your hourly rate. Optimise your pricing structure. The hourly rate is the smallest variable in a system whose first variable nobody talks about.