A UK SMB owner gets a phone call from a sales rep at a digital transformation agency. The pitch sounds compelling: a structured roadmap, multi-phase delivery, change management, a steering committee, ongoing partnership.
Eight months later, the SMB has paid £40,000 for a discovery phase, has a 60-page roadmap document on a shared drive that nobody opens, and has not shipped a single piece of working software. The team is frustrated. The budget is gone.
This is not a rare story. It is a structural one. "Digital transformation" as a phrase was invented in enterprise contexts where the multi-phase, multi-discipline approach actually fits. Selling that approach to a £5m UK SMB is selling a tool designed for a different problem.
This post is about why it usually does not work, and what UK SMBs should be looking for instead.
Where the phrase came from
"Digital transformation" entered business vocabulary through enterprise consulting in the 2010s. The original use case was real: large organisations with hundreds of legacy systems, thousands of staff, and decades of accumulated technical debt needed structured programmes to modernise.
Those programmes had specific characteristics: multi-year timelines, multi-team coordination, change management at scale, executive sponsorship, parallel workstreams across departments. Enterprise consulting firms built practices around exactly this shape of work, and they got good at it.
Then the SMB market got pitched. The same vocabulary, the same methodology, scaled down. Multi-phase, multi-team, multi-discipline approach applied to a 30-person company that does not actually have departments yet.
The result: SMBs paying enterprise overhead for problems that did not need it.
Why the model does not fit a £5m business
A £5m UK SMB usually has these properties:
- Twenty to fifty people, organised more by who-does-what than by formal department.
- The owner or MD is close enough to the operations to know which workflows are broken without needing a workshop to discover it.
- One or two specific operational pains that are eating measurable time per week.
- A budget for fixing it that maxes out somewhere between £10,000 and £50,000.
- A timeline pressure: this needs to be working in months, not years.
Apply enterprise transformation methodology to that and the mismatch is structural:
The discovery phase is too long. A two-month workshop programme to understand operations is overkill when the owner can already describe what is broken in a 15-minute conversation. The discovery is delivering a deliverable that is mostly already in the buyer's head.
The phasing is wrong. Enterprise programmes phase work because the change management requires it. A 30-person SMB does not have departments to coordinate or change-management cycles to manage. The phasing creates artificial gates that slow the work without protecting the buyer.
The deliverables are documents, not systems. The transformation methodology produces roadmaps, frameworks, and steering decks. SMB owners want working software. The methodology is optimised for the wrong output.
The pricing is wrong. Enterprise consulting prices reflect the cost of running a multi-team practice with sales, account management, and partner overhead. None of those costs add value to an SMB engagement; they are what makes the price ten times what an SMB actually needs.
The retainer structure does not fit. Enterprise programmes often run on quarterly retainers because the work is genuinely continuous. SMB engagements are typically discrete: one specific build, one specific outcome. A retainer for retained capacity that the SMB does not need is just a tax.
What a £5m business actually needs
Most SMBs in this size range have one or two specific operational pains that, fixed, would change the next year of the business. The right shape of engagement is:
- A short diagnostic to confirm what the actual pain is. Hours, not weeks.
- A scoped build that fixes the specific problem. Weeks, not months.
- A fixed price agreed upfront. Pounds, not phases.
- An exit point when the work is delivered. No retainer until there is something worth retaining.
The bureau's four-step ladder (free triage, paid audit, fixed-fee build, optional managed retainer) was designed for exactly this shape. So is most of what good UK freelance technical work looks like. So is what some smaller agencies do well.
What is not a fit for this shape: anything that begins with the word "transformation".
The five red flags
If you are talking to a consultancy and you hear any of these, the engagement is structurally wrong for an SMB:
1. "Discovery phase" as a separately-billable engagement. Especially if it is more than a week of work. The discovery is being charged because the consultancy needs to bill for the time, not because there is anything to discover that you do not already know.
2. "Roadmap" as the primary deliverable. Roadmaps are sales tools dressed as deliverables. They commit the consultancy to nothing while implying future work. An SMB engagement should produce a working system, not a document about a future system.
3. "Phased delivery" without a clear first phase that ships in weeks. If the first phase that produces a working output is six months in, the engagement is wrong-shaped. SMBs need wins fast enough to validate the approach.
4. "Steering committee" or "executive sponsor". These are enterprise governance structures. A £5m SMB does not need a steering committee for a project; it needs the owner to make the decision, the work to happen, and somebody to ship it.
5. Quarterly retainer as the default end-state. Retainers are where consulting engagements go to die. The work that genuinely deserves a retainer (running infrastructure, ongoing support) should be priced separately from the build. If the retainer is presented as the normal way the engagement continues, it is the consultancy protecting its revenue, not your operations.
What to look for instead
Three patterns that suggest the engagement is the right shape for an SMB:
Pricing visible upfront. If the consultancy publishes prices, that is a signal. It means they have done the work to scope what their typical engagement costs and they are willing to commit to it. Hidden pricing usually correlates with engagement structures that punish smaller buyers.
Deliverables described as outputs, not phases. "We will produce a written punch list with fixed-cost proposals for each fix" is an output. "We will conduct a discovery and assessment phase" is a phase. Outputs are what you can hold the consultancy accountable to; phases are billing structures.
A short, free first conversation that ends with a yes or no. A 15-minute call that ends with "this is or is not a fit" is a sign of confidence. A 90-minute discovery call that ends with "let us send a proposal next week" is a sign of a sales process.
The bureau does each of these by design. Most good UK technical freelancers do too. What is rare is the consultancy that wraps the same approach in transformation vocabulary and prices it 5x higher.
What if you are mid-engagement already
If you are reading this and recognising your current engagement, the practical question is what to do next. Two options:
Finish the engagement, then come back. If the discovery phase or strategy work is going to deliver something useful, finishing it produces a deliverable that the next step (a fixed-fee build with a different shop) can act on. The bureau will tell you honestly at the triage whether the deliverable you currently have is good enough to act on.
Cut your losses and start over. If the engagement has produced a roadmap that is 60 pages of generic advice and no scoping that the team trusts, finishing it adds cost without value. The bureau's audit (£2,500, 2 weeks) is faster and cheaper than continuing a transformation that is not heading anywhere.
The 15-minute triage is the cheapest way to find out which of those is the right call. The bureau will not pretend to be the right answer if your existing engagement is salvageable. Sometimes the answer is "let them finish, then ship the build".
What to do if you have not started yet
Skip the transformation vocabulary entirely. The right first conversation is short, free, and ends with a clear answer about whether what you need is a hire, a build, a small process change, or something the bureau is not the right fit for. The services pillar shows the five engagements the bureau runs and the price each one starts at. Compare that to whatever transformation proposal is sitting on your desk and the maths usually answers itself.