Completely normal — and completely unsustainable beyond a certain point. In the early stages, the founder being the single source of truth is a feature, not a bug. You move fast because the information lives in one place: your head. The problem is that this doesn't scale. As the business grows, the cost of that centralisation goes up. Every decision that needs your input is a decision that's waiting. Every problem that needs your context is a problem that's blocking someone.

What you're describing is the Founder Bottleneck — one of the four T pillar leaks in the PATH framework. The cure isn't working harder or communicating more frequently. It's structural. Decision rights need to move to the right level. Your team needs to understand not just what to do but the intent behind why — so they can make good decisions in your absence.

I usually start with the Vacation Test: if you disappeared for two weeks with no phone, what would break? The answer tells you more about the operational health of the business than any financial report. If the answer is "almost everything" — that's where we start.

Because talking about strategy and executing strategy are two completely different activities — and most leadership teams conflate them. The conversation in the boardroom is real. The alignment in that room is real. But by the time that strategy reaches the people who have to actually change their behaviour on a Tuesday afternoon, it has passed through three or four layers of interpretation, each one removing a little more specificity and a little more urgency.

What you're describing is Strategy Leakage. It's the P and A pillars of the PATH framework working against each other: the Purpose is clear at the top, but the Actionable translation into daily operations hasn't been built. The bridge exists in the slide deck. It doesn't yet exist in the workflow.

The fix is almost never a better strategy. It's a better translation layer — a mechanism that converts each strategic pillar into a specific operational change, with someone named as responsible for it, and a weekly friction-hunting session to find where it's hitting resistance. Most founders I work with have the first and are missing the second and third entirely.

You've hit what I call the Growth-Complexity Crossing. It's the point — usually somewhere between £5M and £20M — where the physics of your business change. Before this point, every pound of new revenue felt relatively clean. After it, every pound of new revenue costs more to generate and more to service than the last one. Operational overhead is scaling 1:1 with revenue, which means you're running faster to stay still.

The cause is almost always the same: the back-office infrastructure was built for a smaller business and has never been properly redesigned for the version you are now. You're running a £12M business on the processes, handoffs, and team structures of a £4M one. The debt has compounded. Growth has exposed the cracks rather than filling them.

The H pillar of PATH — Holistic Growth and Value Creation — is specifically designed for this moment. The question isn't how to grow faster. It's how to make the growth you already have more profitable. That usually means standardising the middle 80% of your operations, finding the revenue that's subsidised by operational overhead and either repricing it or cutting it, and separating the capacity your team uses for heroic effort from the capacity they use for repeatable tasks.

What you're experiencing is culture dilution — and it's almost always misdiagnosed as a people problem when it's actually a systems problem. The culture that made you good at 12 people was transmitted by proximity. Everyone was in the same room, absorbing the same behaviours, seeing the same decisions being made in real time. At 40 people, that transmission mechanism stops working. New hires don't get the osmosis — they get an onboarding deck and a Slack channel.

Culture doesn't scale through proximity. It scales through architecture. If you haven't coded your values into your daily operations — into how decisions get made, how feedback flows, how performance gets reviewed — then your values are aspirational posters, not lived reality.

The T pillar of PATH addresses this directly through feedback systems and structured learning rituals. The question I ask is: for each of your stated values, what is the operational expression of that value? If the answer is vague — if the value isn't visible in a calendar, a process, or a decision threshold — it isn't actually part of your culture. It's decoration.

This is the Strategy-to-Action Ratio problem. When operations aren't tightly mapped to strategy, you create what I call Kinetic Waste — your team is burning energy, but that energy is consumed by internal friction rather than market impact. The business is vibrating, not moving forward.

The reason this feels like it requires micromanagement is that there's no shared framework for what "right" looks like. Micromanagement is what happens when clarity is absent. The antidote to micromanagement is not less oversight — it's better architecture. When every task is tagged to a strategic pillar, when there are three — and only three — quarterly priorities, and when the weekly rhythm includes a friction-hunting session rather than a status update, people self-correct without needing to be managed.

In the A pillar of PATH, we call this the 1:1 Rule: every operational task should be traceable back to a strategic objective in one step. If it isn't, it's consuming prime energy without earning its place in the sprint. The fix isn't a performance conversation — it's a structural redesign of how work is prioritised and reviewed.

That's a fair challenge and I'd be suspicious of any advisor who didn't take it seriously. Most consulting doesn't stick for one of three reasons: the recommendations live in a document rather than in a system, the changes require the founder's daily attention to sustain, or the advice was correct in principle but disconnected from the operational reality of that specific business.

PATH is designed around a different assumption: the only change that lasts is change that is built into the architecture of how the business operates. Not a policy document. Not a workshop output. A process that runs, a decision right that is owned, a ritual that recurs. If we fix a leak, we fix it by installing a guardrail — something structural that prevents the same leak from reopening the moment the attention moves elsewhere.

The second difference is sequence. Most advisory work tries to fix everything simultaneously, which means nothing gets fixed properly. PATH identifies the binding constraint — the single pillar scoring lowest — and focuses on that first, completely, before moving to the next. The 30 Executive Insight posts I publish are a good way to test whether the thinking resonates before you commit to anything. Start there. If it doesn't fit your situation, I'll tell you.

The busy period is the symptom, not the reason to wait. Every founder I work with at your stage is in a busy period — that's not coincidence. The busyness is what happens when the operational architecture hasn't kept pace with the growth. The business is generating work faster than it's generating capacity to handle that work.

Waiting until it's less busy to fix the thing that's making it busy is the definition of the Founder's Trap. The quiet period rarely arrives on its own. It arrives when you build it deliberately.

That said, I don't ask for your time upfront — I ask for your clarity. The Stop the Leaks Assessment takes 10 minutes and gives you a diagnostic picture of which pillar is your binding constraint. That's the starting point. Once you know what's leaking most, you can make a rational decision about whether the timing is right to fix it. You might find the answer changes how urgent the question feels.

It's a diagnostic, not a brochure. The assessment scores your business across all four pillars of PATH — Purpose, Actionable Strategy and Process Optimisation, Team, and Holistic Growth — through a series of specific statements that you rate honestly from 1 to 5.

What you get out of it: a clear score for each pillar, identification of your primary leak — the pillar scoring lowest and therefore your binding constraint — and a 90-day sequencing guide for what to do about it. It also gives you the language to have a more precise conversation about what's actually wrong, which is often more valuable than the score itself.

The most common thing founders say after completing it is that they knew something was wrong but couldn't name it. The assessment names it. What you do with that is up to you. Some founders take the 90-day priority and run with it. Others book a discussion to work through it together. Either is the right answer.

You're delegating the task without delegating the context — and in some cases, without having built the system that makes the task delegatable. Delegation fails most often not because the person isn't capable, but because the handoff is incomplete. The founder knows why something matters, what good looks like, and what to do when it goes sideways. The team member only gets the what.

The T pillar of PATH separates delegation into three components: the decision right (who owns this, fully), the context (the intent behind the task, not just the task), and the guardrail (the process or policy that prevents the most likely failure mode). Most delegation covers the first and misses the second and third entirely.

Things fall through the cracks because the cracks exist in the system, not in the person. The question to ask every time something goes wrong under delegation is: what guardrail is missing that would have prevented this? Answer that question and install the guardrail. Do it consistently for six months and you will have built a team that executes without you — not because they've become better people, but because the system has become more complete.

It's the right question to ask and I'd be wary of any advisor who gave you a vague answer. The honest version: the ROI of fixing an operational leak is almost always quantifiable once you know what the leak is costing you. If your founder bottleneck is delaying decisions that slow down your sales cycle by an average of 10 days, and your average deal is worth £50k, and you close 20 deals a year — the cost of that leak is calculable. Fixing it has a number attached.

My job is to help you identify the number before we start. Part of the initial diagnostic conversation is establishing what the binding constraint is costing — in time, margin, and opportunity. That number becomes the benchmark against which the investment is measured. If we can't build a reasonable case that the fix is worth 5–10x the cost of the engagement, I'll tell you and we won't proceed.

The Stop the Leaks Assessment is the starting point. It's free, it takes 10 minutes, and it gives you enough clarity to have a meaningful conversation about whether the numbers stack up for your specific situation. Start there before you make any judgement about investment.

It means I was trained to distinguish between a hypothesis and a proof — between what feels true and what the evidence actually shows. That discipline is rarer in business advisory than you might expect. A lot of advice in this space is pattern-matching dressed up as insight: "I've seen this before, therefore do this." Sometimes that's right. Often it isn't, because the pattern isn't actually the same.

In practice, it means I don't accept symptoms as causes. When a founder tells me their team isn't performing, I don't recommend a performance management framework until I understand whether the root is a delegation gap, a clarity gap, a feedback gap, or something else entirely. Diagnosis before cure — that's the research science training applied to operational problems.

The other thing the Oxford background gives me is intellectual range. The problems scaling businesses face are multidisciplinary — they sit at the intersection of organisational psychology, process engineering, strategy theory, and human behaviour. Being comfortable across those domains, rather than just one, is what the PATH framework reflects.

It is a completely different business — and that's exactly the right instinct. The mistake most founders make is trying to scale the current business rather than architecting the future one. They hire more people into a broken structure, add more clients to a fulfilment system that can't handle them, and grow the revenue while growing the operational debt at the same rate.

The starting point is always the same: an honest assessment of your current operational health. Not your growth rate, not your pipeline, not your team size — your operational health. Which of the four pillars of PATH is your binding constraint right now? That's the leak that will prevent you from getting to £10M cleanly, let alone £50M.

The journey from £4M to £50M has three or four distinct inflection points where the business must be fundamentally redesigned — where the thing that got you here will actively prevent you from getting there. Most founders hit these walls without knowing they were coming. PATH maps them in advance so you can build the infrastructure before you need it, not after the crisis has arrived. That's the whole point of starting now rather than waiting until the pain is acute.