Three options, one pattern
When a mid-market retailer's growth stalls (and if you're between £5M and £50M, the probability that it will at some point is near-certain), the response follows a predictable script.
Option one: the strategy consultancy. Senior people fly in. They interview your leadership team. They analyse your market position. They deliver a deck, often a good one, with frameworks, matrices, and a recommended roadmap. Then they leave. Your team, which was already stretched before the consultancy arrived, is now responsible for executing a strategy that was designed by people who won't be in the room when reality pushes back. Six months later, the deck is in a shared drive that nobody opens. The roadmap is 30% executed, at best.
Option two: the analytics platform. A vendor sells you a login. The pitch is compelling: unified data, pre-built reports, automated insights. The implementation takes longer than promised. Your team spends months configuring it, connecting data sources, learning the interface. A year later, the platform is technically live. Two people use it regularly. Neither of them is in the room when growth decisions are made. The data exists. The decisions haven't changed.
Option three: the custom dev shop. You hire engineers to build what you need. They're good at building. But they don't know retail well enough to challenge the brief. They build what you tell them, not what you actually need. They lack the commercial instinct to know which problem matters most, or whether the solution they're building will change a decision or just generate a report. Three months later, you have working code that solves a problem you've already moved past.
Each option delivers a piece of the solution. None of them deliver the whole thing. And the pattern repeats: consultancy, platform, dev shop, repeat, because nobody has combined the pieces into a single discipline.
The gap in the market
The gap isn't subtle. It sits between three capabilities that mid-market retail needs but nobody provides together:
Commercial thinking. The ability to understand a retail business at the level of commercial decisions, not technology architecture, not data models, but the actual choices that a Commercial Director or Head of eCommerce makes every week. Where to invest. What to cut. Which channel to prioritise. Which territory to expand. These decisions drive growth. Everything else is infrastructure.
Analytical precision. The ability to build the specific model, tool, or system that answers the specific question the business is facing. Not a generic dashboard. Not 130 pre-built reports. A precise answer to a precise question: where is margin leaking? Which customer segments justify acquisition cost increases? What would happen if we shifted 15% of spend from this channel to that one?
Embedded execution. The willingness to stay inside the business through implementation, adjusting, iterating, and making sure the solution works in the messy reality of a live retail operation. Not handing over a deliverable and disappearing. Not leaving a login and hoping the team adopts it. Staying until the number moves.
Strategy consultancies provide the first. Analytics platforms attempt the second. Dev shops deliver the third, sort of. Nobody combines all three. And that's the gap.
Why the category needs a name
Categories matter because they change how buyers think about their options. Right now, when a mid-market retailer's growth stalls, the buyer's internal conversation defaults to one of the three established options: "Should we hire a consultancy, buy a tool, or commission a build?"
That frame guarantees a partial solution. The buyer can only choose what the market offers. And what the market offers is three incomplete answers to a problem that requires all three capabilities working together.
Naming the category (retail growth engineering) does something specific: it gives the buyer a fourth option to consider. It says: there is a discipline that combines commercial thinking with analytical precision and embedded execution, scoped to the specific needs of mid-market retail.
This isn't marketing language. It's a structural description of what the work actually involves. Engineering, because the output is built: custom systems, models, and tools. Growth, because the measure of success is a commercial number that moves. Retail, because the domain expertise is non-negotiable.
What it looks like in practice
A retail growth engineering engagement doesn't start with a product demo or a proposal template. It starts with a diagnostic: what's actually happening in the business, where decisions are being made on instinct instead of evidence, and which problem, if solved, would have the most material impact on growth or margin.
From there, the team engineers the specific solution that the diagnostic reveals. This might be a margin model that disaggregates true profitability by channel, geography, and customer segment. It might be a demand forecasting system that accounts for the specific variables affecting a particular business. It might be a decision framework that connects analytical output to commercial action in a way that the existing tools simply can't.
The solution is built on the retailer's data, tested against the retailer's commercial reality, and embedded into the retailer's decision-making process. The team stays until the agreed metric moves. If it doesn't move, the engagement hasn't earned continuation.
The test
The simplest way to know whether you need retail growth engineering rather than a consultancy, platform, or dev shop:
Have you tried at least one of the three standard options and found that it delivered a deliverable but not a result? A deck that didn't ship. A platform that didn't change decisions. Code that solved yesterday's problem.
If the answer is yes, the issue isn't the quality of the option you chose. It's the structure of the options available. You needed all three capabilities: thinking, building, staying. And the market gave you one at a time.
That's the gap retail growth engineering exists to close. Not because the existing options are bad, but because mid-market retail deserves one that's complete.