A founder I’ve known for years took two weeks off in August. Eighty staff, services-led, profitable, the kind of business everyone tells him he should be proud of. It was the first proper holiday in nine years. By day four his phone had three escalations he had to handle himself. Two of them were standard discount calls he had made a hundred times before. He came back from holiday more tired than when he left, and quietly furious. Mostly at himself.
He didn’t have a delegation problem. His senior team are good. They couldn’t act because they didn’t know what they were allowed to act on, and the answer to “what would the founder decide here” only lived in one head.
Why “trust your team” keeps failing
Almost every piece of advice given to founders in this position frames it as a personal problem. Step back. Trust your team. Get out of your own way. The advice fails because the underlying structure isn’t being addressed. The team can’t step in because there is nothing to step into. Senior people escalate because the rules of decision rights have never been written down, not because they’re underqualified. Trying harder to delegate doesn’t fix it.
The honest read on this comes from Legal and General’s SME research, referenced widely in the founder community: more than half of UK small businesses say they would stop trading within twelve months if they lost an owner, director, partner, or key person. Read that as the same group of business owners describing the same structural reality from the inside. They know they are the system. They also know how exposed that makes them, and that the exposure compounds the longer it sits unaddressed.
I’ve watched this play out a few times. The founder is acting rationally given the structure. The team is acting rationally given the structure. The structure is what’s broken.
The three layers of dependency
Founder dependency has three structural layers, and you can’t break the trap by fixing only one. The first is that decisions route back, because the team has no clear guidance on what they can decide alone. The second is that the founder’s judgement isn’t captured, because how you weigh trade-offs has never been written. The third is that decision rights aren’t defined, because nobody knows where their authority ends and yours begins.
The first layer is the most visible. A team member faces a discount request, a scope question, a hiring call. They escalate. Not because they are incapable but because the cost of getting it wrong, in their reading, is higher than the cost of asking. So they ask. The founder answers. The pattern teaches the team to ask again next time.
The second layer is the deepest. Even with the best intentions, a senior team member can’t substitute for the founder if the founder’s judgement on the most common high-stakes calls has never been written down. How do you decide when to walk away from a client? What’s your line on discounting? What makes a hire a yes versus a no? Those answers are taste rather than procedure, and the taste lives in your head until you put it on paper.
The third layer is the one founders skip because it feels political. Decision rights mean naming, in writing, what each role can decide alone, what needs a check-in, and what comes to you. Without that map, every senior person has a private theory of where the line is, and those theories tend to err on the side of escalating. Risk-aversion fills the vacuum where written authority should be.
Why services businesses get this worst
In a product business, processes can substitute for founder judgement on a wide range of operational calls. In a services business, the founder often is the system, because client trust, pricing calls, scope decisions, and quality standards all reflect the founder’s individual taste. The infrastructure work is harder, and skipping it is more tempting because the business looks like it’s running fine until it isn’t.
The agency owner observation in Spin Sucks captures the surface symptom: clients only want to work with the founder, and no one else on the team will do. They want one-on-one service from the person whose name is on the door. If you are in this situation, you already know it caps your growth and concentrates your risk. The structural fix is the same as everywhere else, the difference is that for services the work compounds slower because the founder’s judgement is genuinely part of the offer.
That doesn’t mean the work is optional. It means the timeline is longer and the founder has to commit earlier. Strategic Exit Advisors and the broader exit-planning literature put a number on it: founder-dependent services businesses commonly trade at 30 to 50 per cent valuation discounts versus systematised peers, because buyers price the integration risk into the offer. That discount is the cost of the missing infrastructure, made visible by the market.
What it actually takes to break the trap
The infrastructure that breaks the trap is unglamorous and specific. A one-page decision rights map, naming what the team can do alone, what needs a check-in, and what genuinely needs the founder, with examples from real cases. A written description of how you think about the half-dozen calls you make most often, with the trade-offs visible. A simple cadence for surfacing exceptions early, so the map updates as the business runs into edge cases.
None of that is glamorous and none of it is fast. The honest cost is six to twelve months of disciplined work, often during a stretch when the founder feels they don’t have the time. The reason founders skip it is rarely that they can’t see the value. It’s that the urgent crowds out the important, and the founder dependency makes the urgent more urgent.
Once the infrastructure is built, the compounding starts. Every additional decision the team makes without you is a unit of capacity returned to you, a unit of judgement compounding inside the team, and a unit of key-person risk taken off the L&G stat. The holiday starts working. The phone goes quiet for the right reasons, because there’s nothing to ring about, not because nobody dares ring you.
The founder I started with did the work over the following year. He blocked Tuesday mornings for it, wrote the calls he made most often into a shared document, and started naming, with each senior leader, the decisions they could now make alone. The next August he took three weeks. The phone rang twice. Once was a genuinely novel client situation that updated the map. The other was his deputy ringing to say happy birthday. The work that makes everything else easier is the work the urgent kept hiding.
