A commercial insurance brokerage has been running for nineteen years. Four account managers handle day-to-day client relationships. A claims coordinator manages the paperwork when something goes wrong. The firm has a genuine book of business and a reputation built across two decades in a mid-sized market.
The founder still touches almost everything that matters. Every renewal above a certain premium gets her review before it goes out. A client who’s had a serious claim wants to hear from her personally, not whoever happens to answer the phone. When a prospective client asks an unusual question about coverage, the team’s instinct is still to walk down the hall and ask her.
Her staff aren’t incompetent. Her systems aren’t primitive. On paper, she runs a real business. Nineteen years in, she is still the person almost everything runs through.
The easy conclusion is that she’s the bottleneck. Delegate more. Learn to let go. Maybe she holds on too tightly, or maybe the team just isn’t ready yet.
That conclusion is usually wrong, or at least badly incomplete. It treats “the founder is involved in too much” as a single, simple problem with a single, simple fix. It rarely is.
“Just Delegate More” Misses What’s Actually Happening
When a business has outgrown its founder but nothing moves, the standard advice arrives fast: delegate, hire, document, let go. Sometimes that genuinely works. More often something stranger happens. The founder hands off a task, and a few weeks later the same work is somehow back on her desk, this time wrapped in a meeting and two more people waiting on her opinion before anything can proceed.
That isn’t a failure of delegation so much as a sign that delegation was never the actual problem. Giving someone a task is different from giving them the standing to decide alone. An account manager can draft a renewal competently. Whether she can decide, on her own authority, that a client’s risk profile has shifted enough to warrant different coverage, without checking first, is a separate question entirely. If nobody has ever answered that second question out loud, handing over the first task just moves the bottleneck one desk over. It doesn’t remove it.
This is the trap in making founder dependence personal. “I’m too involved” sounds like a character flaw, something about an unwillingness to let go. It’s usually closer to a staffing gap that has nothing to do with headcount: the business itself was never taught to do several specific things it has only ever watched her do.
Five Different Things a Founder Might Be Carrying
The Designed Business names this more precisely than “founder dependence” usually gets named. A founder who can’t step back typically isn’t carrying one thing. She’s carrying some combination of five, and each one needs a different fix.
Sometimes she’s carrying trust. Clients believe the recommendation because of her personally, built over years of direct contact, not because they trust the firm as an institution. An account manager can give the technically correct answer and still not be believed in the same way.
Sometimes she’s carrying judgment. The team can execute the process, but the harder interpretive call which risk is genuinely dangerous and which is boilerplate noise, which client question deserves a careful answer and which doesn’t still only happens reliably in one head.
Sometimes she’s carrying memory. She remembers why a particular client has an unusual policy exclusion from four years ago, which supplier underperforms on claims, which client gets anxious at renewal time and needs more reassurance than the paperwork strictly requires.
Sometimes she’s carrying standards. Everyone on the team knows a renewal review needs to be thorough. Nobody but her could actually describe, in enough detail for someone else to check their own work against it, what thorough means.
And sometimes she’s carrying courage: the willingness to tell a client their risk appetite doesn’t match reality, decline a deal that’s commercially tempting but wrong for the client, or push back on a renewal priced too aggressively just because a competitor undercut it. The team may see exactly the same problem she does. Only she feels entitled to say so out loud.
Collapsing all five into “she needs to delegate more” guarantees the wrong fix, because trust doesn’t transfer the way memory does, and memory doesn’t transfer the way courage does. A firm that tries to close a courage gap by writing a procedure manual will end up with a very well-documented version of the same stall.
What Thirty Days Away Would Actually Reveal
The Designed Business offers a sharper way to find out which of the five is actually in play, rather than guessing. It’s the book’s second diagnostic test: what does the customer lose if the key person disappears for thirty days?
Run it honestly against the brokerage. If she took a genuine month off, no calls, no check-ins, what specifically would happen?
Most renewals would probably still go out. The account managers know the clients, know the process, know how to draft a policy. That part of the business has already moved past her.
But a handful of larger renewals would likely stall, waiting for a sign-off nobody else feels authorized to give. That’s not a trust gap or a memory gap. It’s a courage gap wearing a process costume: nobody has been told, in words, “you can approve this without me,” so nobody does.
A long-standing client’s unusual exclusion from several years ago might get missed entirely at renewal, because the reason for it exists only in her memory, never in the client’s file. That’s a different failure, and no amount of delegated authority fixes it. What’s missing is information that was never written down, not permission that was never granted.
And if a serious new prospect, the kind who wants real reassurance before signing, gets handed to an account manager instead of her, the deal might simply be lost. Not because the account manager is unqualified, but because the client’s trust was never in the firm. It was in her, specifically, and nobody ever worked on moving it.
Three different outcomes from the same thirty-day absence. Three different diagnoses. Only one of them, the missing memory, gets fixed by better documentation. None of them gets fixed by “delegate more” treated as one instruction.
The Fix Has to Match the Form
This is the part that gets skipped when founder dependence is treated as one problem with one solution.
A trust gap closes slowly, by deliberately putting someone other than the founder in front of clients early and often, before a crisis forces it, so trust has time to attach to a second name.
A judgment gap closes by making the invisible decision rule visible: naming, specifically, what the founder is actually checking for when she reviews a renewal, until someone else can apply roughly the same test without her in the room.
A memory gap closes by building the habit of recording the why alongside the what, not just that an exclusion exists, but why it was granted, so the reasoning survives even when she isn’t there to supply it.
A standards gap closes by writing down what “good” actually means in concrete, checkable terms, rather than leaving it as a feeling only she recognizes.
A courage gap, probably the hardest of the five to fix with a document, closes through explicit decision rights: a rule that says exactly when someone else is allowed to say no to a client, decline a deal, or flag an underpriced renewal, without needing anyone’s personal bravery, because the business has already decided the answer in advance.
None of these fixes is “work less” or “trust your team more.” Each one is a specific, nameable thing currently sitting in one person’s head that has to move somewhere else.
A few honest questions
Which of the five- trust, judgment, memory, standards, or courage does your own business most obviously still run through you?
If you disappeared for thirty days starting tomorrow, what specifically would stall, and is that a gap in permission, in information, or in belief?
Has anyone on your team actually been told, in words, which decisions they’re allowed to make without checking with you first, or have they only ever learned by watching what gets overturned afterward?
The Founder Isn’t the Problem. The Undesigned Part Is.
None of this argues that a founder’s involvement never matters, or that a well-designed business removes judgment and leaves only procedure behind. Some things should stay personal: a particular eye, a particular relationship, a standard that genuinely deserves to stay scarce. The point isn’t to erase the founder from the business.
It’s to stop treating “I’m too involved” as a personal failing and start asking which specific thing the business has never been taught to carry. A founder who hears “you need to let go” for the fourth time and tries the same vague instruction again will get the same result as last time. A founder who can say, specifically, “this is a courage gap, not a trust gap,” knows exactly which fix to try next.
That’s the real difference between a business that eventually outgrows its founder and one that just keeps adding people around the same unresolved dependency.
If this pattern sounds familiar, Chapter One of The Designed Business, “The Business That Still Depends on You,” goes several layers deeper into exactly this breakdown. Worth the hour, read with your own business in mind.