£2M to £20M: Why Scaling Brands Keep Hitting the Same Three Problems

A lot of brands scaling from £2M to £20M hit similar operational pains. They arrive at slightly different revenue points depending on the sector, but they arrive. Founders usually mistake them for strategy problems, product problems, or team problems. However they're operating-model problems, and they respond to operating-model answers.

The three: the founder becomes the operating system. The tooling stack designed for a smaller business breaks. And the growth engine that got you to £5M or £10M stops being the growth engine that gets you to £20M.

Each pain is predictable, each is solvable, each requires a different kind of operational work.

Pain 1: The founder is the operating system

Every approval above a certain threshold routes to the founder. Every hire needs their sign-off. Every customer escalation lands on their desk. The founder feels this as being needed everywhere. The team feels it as slow decisions and unclear authority. Both can be correct.

Why it happens: at £1M the founder is the operations. At £3M they still are. The architecture that could route decisions without them hasn't been built yet. Meanwhile the volume of decisions has grown ten times.

The common advice, "delegate more", doesn't work on its own. Delegation without an operating architecture creates fear-based bottlenecks somewhere else. The founder tells a director they can approve up to £X. The director gets nervous approving anything near that threshold. The decision routes back to the founder. Delegation only works when the architecture underneath is set and there's trust. A lot of founders think they can do it faster themselves. Early on, they're usually right. But every decision they keep also becomes one the team never learns to make. As the business grows, the goal isn't for the founder to make every decision faster. It's to build a business that can make good decisions without them.

The architecture has three parts. First, documented decision rights. For the ten, fifteen most common decisions the business makes, who owns them, at what threshold, and what triggers escalation (this can take the form of a RACI matrix). Second, escalation paths that are actually used, such as a weekly leadership review, a monthly business review. Not "text the founder." Third, a reporting and meeting cadence that lets the leadership team run the business without needing the founder mid-week.

What to watch for. If the leadership team can't name who owns a decision without pointing at the founder, the architecture isn't set. If the founder is spending more than a quarter of their time on operational firefighting, the threshold we've written about in Operations Break Three Times, the business hasn't been engineered to run without them.

Pain 2: Excel stops being enough

The finance close takes twenty days instead of five, three tools give three different customer numbers, forecasting is guesswork, half the inputs are downloaded to Excel, manipulated by hand, and re-uploaded elsewhere. Someone spends two days a month producing a report that gets read once.

None of this looks like a crisis, especially if the business is still growing, but every decision is being made on data (if anyone is looking at the data) that isn't reliable, and just producing the data is burning hours the team doesn't have.

The temptation is to buy the enterprise version of everything. Don't. Installing SAP at £10M is classic over-engineering, and we’ve written about the trap in You Can Over-Engineer Business Operations Too. Instead, install specific things in a specific order.

First: a financial close that reconciles. Accounting talks to operational systems automatically, bank feeds, inventory movements, payroll. If the close is taking more than ten working days, fix this first. Nothing else in the stack is trustworthy if the financial data isn't.

Second: a single source of truth for customer and revenue data. CRM properly connected to finance, unit economics measured with data that reconciles. It kills the "three tools, three answers" problem. Marketing spend decisions become defensible for the first time.

Third: an operational reporting rhythm. Weekly numbers, monthly business reviews, quarterly plans, not dashboards for the sake of dashboards, reports the leadership team actually uses. This is often overlooked, it’s very simple to put in place, but absolutely needed when you hit the £2M mark.

What NOT to install yet: enterprise ERPs, complex BI stacks nobody reads, bespoke integrations that need an engineer to maintain, CRM configurations more sophisticated than the actual sales process. Every one of them is over-engineering at this stage. The point of the tooling stack at £5-15M is reliable data with minimum operational overhead.

Pain 3: The growth engine that got you here runs out

The growth curve that took the business from £2M to £15M starts to flatten. Customer acquisition costs rise faster than customer lifetime value can absorb. Competitors have caught up on the feature that used to differentiate. Category maturity closes the room to grow inside the original definition. The revenue is still growing, but slower and more expensive.

Why it happens is structural, every growth engine has a natural ceiling. 

The channel that worked at £2M, early D2C, one strong retail relationship, a viral product moment, a mission-led PR wave, doesn't scale linearly to £20M. Competition erodes early advantages. The playbook that produced the first £10M is often close to its limit somewhere between £15M and £25M.

Founders reach for strategy at this stage, either it's a new product line, a retail push, a B2B pivot or a new geography. These are usually the right ideas. Where most brands stall isn't in the strategy, it’s in how the strategy gets executed.

The failure mode is easily identifiable, the new thing gets launched as a side project bolted onto the existing business. Nobody asks how it reshapes the operating model, the customer segmentation, the margin mix, the brand positioning, the supplier concentration, the team structure and compensation.
Six months in, there are two parallel half-working structures inside one company. They compete for the same attention. They muddle the same brand. The core business has weakened while the leadership team was watching the new thing.

Worth keeping in mind here is the 70/20/10 rule: 70% of resources on the core business, 20% on adjacent growth, 10% on transformational bets. Most founders launching a new engine flip this without noticing. The new engine gets 40-50% of leadership attention. The core — still 90% of revenue — quietly weakens. Even when the strategy is right, the balance is wrong.

At this scale, strategy and operations should not be separate jobs. They're the same job, done at different zoom levels. The bridge between them is the operating model, what you own versus partner for, what margin structure you're running, who owns which decisions, how the team is compensated. Strategic decisions that don't get expressed in the operating model don't actually happen. They stay as PowerPoint decks or pilot projects that die slowly.

Most next-engine choices at this stage fall into three categories. Each one requires an honest operating-model reshape.

Product extension into adjacent categories. More than new SKUs. It reshapes the brand story customers hear, the supplier and forecasting structure the ops team runs, the warehouse and delivery infrastructure, and the segmentation model marketing uses to talk to different customers.

Channel expansion. D2C into retail, or retail into D2C, is not only a new sales route but also a different operating model, different margin economics, different customer relationship, different data, different team incentives. Doing the second channel with the first channel's operating model rarely works.

Market or segment expansion. A new geography, a B2B pivot, or a move upmarket is a different customer, different regulatory posture, different competitive set, often a different team. The question isn't whether the current team can enter that market, but whether the operating model can accommodate two customers, two go-to-markets, and two rhythms without fracturing.

Here's a pattern we see repeatedly. A mission-driven consumer brand builds strong early product-market fit around a hero product with a distinct impact story. It scales to £10-15M on D2C strength, retail curation, and mission-led earned media. Then three pressures land at once. The category saturates, everyone who wants the premium version already has one, well-funded newcomers arrive with better product features and heavier marketing budgets. The mission that used to be a genuine differentiator becomes table stakes across the category. The founder decides the answer is a new product line, a new market, or a B2B pivot. The launch happens, twelve months later the new thing is contributing a fraction of what was projected, the core business has slowed, the leadership team is trying to figure out whether to double down or pull back.

The strategy was usually right. It's the same failure mode described above, this time with a face and a timeline attached.

Most brands ask whether they can execute the new initiative. The question they should be asking is how it changes the operating model, and whether they're willing to make the changes it requires.

The three pains compound

They reinforce each other in the way that makes them harder to solve. The founder bottleneck slows the systems install. The founder is too pulled into daily decisions to sponsor a proper tooling programme. Weak data makes the next-engine decision harder. The leadership team doesn't have reliable numbers to evaluate the options. And the next-engine pivot pulls the founder further into day-to-day, exactly at the moment the business needs the leadership team to run without them.

Ideally the three are worked in parallel. In practice, starting with one and moving to the next also works. What doesn't work is treating them as unrelated problems. Founder-bottleneck architecture and the tooling stack can each be installed inside 90 days with the right operator in place. The next-growth-engine decision needs the other two underway before the strategic options can be evaluated properly.

Different angle on the same journey we've written about in Operations Break Three Times. The stages tell you when the pains arrive, the pains themselves tell you what the work actually is.

Where to start

If any of the three feels familiar — the founder in every decision, the finance close taking too long, the growth engine losing power — get in touch. We'll help you work out which is most acute and where the operational fix actually sits.

→ Get in touch