Skip to content

Is That Day Rate Fair?

This gives a non-technical owner a directional read on whether a developer or agency day rate you’ve been quoted is in the fair range for what you’re actually getting. You put in the rate, the kind of work, the seniority, and roughly where the person’s based, and you get a sense of whether it sits low, fair, or high. It exists because the hardest thing about hiring technical help, when you can’t assess the work yourself, is telling a fair price from a bad one — and a bad one cuts both ways.

How to read your result

Read the band, not a precise figure — and treat it as directional, because that’s honestly what it is. Day rates move with seniority, location, specialism, and demand, and anyone who hands you a single exact “correct rate” is selling certainty that doesn’t exist. The useful read isn’t “the right number is X.” It’s “the rate you’ve been quoted sits roughly here, and here’s what that usually means.”

A rate flagged as high isn’t automatically a rip-off, and this is the part most benchmarks get wrong. The right question is never the rate on its own — it’s the rate against the value. A senior person at double the day rate who makes the right architectural call in week one and saves you a six-month rebuild is the cheapest hire on the table. A cheap developer building the wrong thing competently is the most expensive, whatever the number says. So a high flag is a prompt to ask what you’re getting for it, not a reason to walk.

A rate flagged as low should make you more cautious, not less — that’s the counterintuitive bit. Unusually cheap usually means junior, or rushed, or someone who’ll build exactly what you literally asked for without the judgement to tell you it’s the wrong thing. The cost of that doesn’t show up in the invoice; it shows up later, in the rebuild. A fair-band result is the one to relax about: it means the price isn’t where your attention should be — the work, the plan, and whether they’re solving the real problem is.

What I’d do about it

Whatever the band, the move is the same: stop benchmarking the rate and start benchmarking the judgement. The rate tells you almost nothing on its own. What you actually want to know is whether this person will push back when you ask for the wrong thing, whether they’ll build you the lean version that solves the real problem or the over-engineered one that bills more hours, and whether what they build is yours to own and extend or a tangle only they understand. Those questions decide whether the money is well spent. The rate is a footnote next to them.

There’s a worldview thread here worth being explicit about, because it changes what “good value” means. The best-value technical help isn’t the cheapest rate — it’s the person who builds you less, builds it to own, and leaves you with a simpler system than you’d have got from someone optimising for billable days. A developer incentivised by time-on-the-clock has a quiet pull toward more complexity, more tooling, a bigger build; a good one fights that instinct and ships the smallest thing that solves your problem. When you weigh a rate, weigh it against whether you’ll come out owning a lean system or renting a complicated one. The deeper version of how to judge that — how to read a quote and the person behind it — is the kind of call I make constantly, and talking it through is usually faster than any benchmark.

If the rate’s in the fair band and the judgement checks out, hire them and stop second-guessing the price.

What this won’t tell you

This benchmarks a price, not a person — and the person is what actually matters. A fair rate from someone who’ll build you the wrong thing is worse value than a high rate from someone who’ll build the right one. If you came here hoping for a single number to justify a decision you’ve already half-made, that’s the one thing it deliberately won’t give you.

Talk it through

If you’ve got a quote in front of you and you can’t tell whether it’s fair — or, more usefully, whether the plan behind it is — tell me about it. Twenty minutes reading the quote and the thinking behind it tells you far more than any benchmark, and it’s a cheap way to avoid an expensive hire.

Two related reads from my diagnostics: the build vs buy calculator helps you sanity-check whether you should be commissioning this build at all, and is your project at risk? is the check to run once work is underway. And if what you actually need is a whole team with a process and accountability behind the build, rather than a single rate to assess, that’s what my agency, Digital Royalty, is for.