Buying consultancy
What software & data consultants really cost in the UK
Most consultancies treat pricing like a state secret. Here are the actual market numbers — and how to buy consultancy so the day rate you pay reflects the person you get.
The market rates, plainly
UK rates for software and data consultancy in 2026 cluster into recognisable bands. Treat these as market observation, not our price list:
| Who you're buying | Typical day rate |
|---|---|
| Freelance developer / analyst (junior–mid) | £300–£500 |
| Senior independent consultant / specialist | £600–£900 |
| Boutique consultancy (senior-led) | £700–£1,200 |
| Mid-tier consultancy | £900–£1,500 |
| Big-name firm | £1,500–£2,500+ |
Project pricing follows: focused SME builds — a dashboard suite, an automation, an extraction pipeline — commonly land between the low thousands and low tens of thousands; substantial bespoke platforms run from tens into hundreds of thousands depending on scope. Hourly equivalents for ad-hoc work typically run £80–£180.
What the rate actually buys
The number that matters isn't the day rate — it's who is doing the day. The classic large-firm move is selling the partner and delivering the graduate: you pay £1,800 a day for someone learning on your project, with the margin funding offices and account managers. A senior specialist at £800 who has solved your exact problem five times is dramatically cheaper per unit of outcome, not just per day. Always ask: who, by name, does the work — and what have they personally shipped?
Fixed price vs day rate
Fixed price is better for you whenever the scope can genuinely be fixed: risk sits with the consultancy, and incentives align around finishing. Day rates are honest for discovery phases and evolving scopes — but should come with weekly visible output, not a monthly surprise. Be wary of anyone who refuses fixed pricing on a well-defined deliverable; it usually means they don't trust their own estimating. (Our position: fixed wherever fixable.)
The costs that hide outside the rate
- Onboarding drag — every new supplier learns your business on your clock. Fewer, better suppliers beats a rotating cast.
- Handover quality — undocumented work is a future invoice. Insist on documentation and code ownership in the contract; see our build-vs-buy guide on why ownership matters.
- The dependency model — some firms price the first project low and the exit high. Ask up front: "what does it cost to leave you?"
Where we fit in
Power Analytix builds exactly this kind of solution — scoped in writing, priced fixed, delivered by senior engineers. If you'd rather have it done than read about it, book a free scoping call.
How to buy well in five moves
- Write one page: problem, current cost, what "done" looks like.
- Ask who delivers, by name and track record — not which logo.
- Get fixed prices on fixed scopes; accept day rates only with weekly output.
- Put code, data and documentation ownership in writing.
- Start with a small paid pilot before any large commitment — competence shows fast.
Buy that way and the rate becomes almost secondary: you'll have made the expensive mistakes impossible.