At $500k, being the engine makes sense. At $5m, it’s costing you sales.
In this article: Founder centrality isn’t a flaw at every stage. Early on, it’s almost the only way to operate – not a problem to be solved. This article draws the line between rational founder dependency and the problem it can become, shows how that line is crossed without realizing, and offers a stage-specific check for owners who aren’t sure which side they’re on.
Founder centrality isn’t a flaw at every stage. Early on, it’s almost the only way to operate – not a problem to be solved. This article draws the line between rational founder dependency and the problem it can become, shows how that line is crossed without realizing, and offers a stage-specific check for owners who aren’t sure which side they’re on.
— Being the engine at an early stage isn't a failure. It's the founder’s actual job.
Where the line is
The problem doesn’t begin when the founder becomes central. It begins the day that centrality persists past the stage that required it, as an unexamined default rather than a conscious choice. That’s meaningfully different than simply being hands-on – it’s staying hands-on after the business has grown past the point where it needs you to be.
The line is easy to miss. Nobody sits down and decides to keep personally making every call well after the business needs it. The business grows gradually. Revenue climbs each quarter. The team gets a little bigger. And the founder’s role, instead of shifting in proportion, does more of what it always did because
that worked, because nothing forced a recheck – and because the founder’s identity is wrapped in the business. Stepping back, even if conceptually desired, seems risky and can feel like being devalued.
— Centrality becomes a problem when it stops being a deliberate choice and starts being a condition no one calls out.
Why the recheck doesn’t happen on its own
The natural forcing function – revenue exploding, a key hire failing, a deal falling apart in diligence – usually arrives well after the line is crossed. By the time something visibly breaks, the pattern has been running for a year or more, in such a way that no single week felt like a decision point.
There’s a harder truth behind this: the behaviors that were useful early on – deciding fast, trusting your own read over anyone else’s, staying close to every client relationship – don’t feel different when they stop being necessary. They feel the same. The market rewarded them at one time, and the founder has no built-in way to suggest that period is over. “CEO disease,” the term coined by Daniel Goleman and his coauthors to describe how leaders become more insulated the more elevated their position is, almost ensures that no one around the founder will call it out.
Tasha Eurich’s research on self-awareness reinforces that likelihood: 95% of people believe they’re self-aware but only 10-15% actually are. Even when a founder is open to evolving how they lead, the space between their perception of what’s appropriate for the business and what the business actually needs is essentially a vacuum that the team won’t risk breaking into.
What ultimately happens is the business changes but the founder’s role doesn’t, and that disconnect is exactly what a buyer – or a successor, or the owner’s own bandwidth – will eventually be unable to accept.
— The business changes but the founder’s role doesn’t. Whether it’s a buyer, a successor or the owner’s own bandwidth, that disconnect will eventually be unacceptable.
How to navigate a transition
The relevant question isn’t “am I still involved” – involvement at almost any revenue level can be appropriate. It’s whether the type of involvement has evolved as the business has grown or whether it’s stuck in the same rut. The most straightforward approach looks at the three core kinds of dependency:
1. Bandwidth: from decisions to actual execution, examine how much the founder is either named to do it or is doing (or re-doing) what someone else technically owns.
2. Capability: look for areas where the founder’s judgement, know-how or domain expertise carry the load.
3. Relationships: identify customers, employees, vendors or other partners where the founder holds more of the relationship than the business does.
The goal is to move the business from relying outright on the founder to get things done and to stop calibrating to what/how the founder thinks. For the business to succeed, the team needs to do the work itself and handle things as it deems best.
That can be tall order. As the founder renegotiates their relationship to the business, some uncomfortable changes may have to be made – staffing changes, client handoffs to other team members, and undesirable consequences stemming from a team learning to make its own decisions. When a founder handles these correctly, they’re growing pains, not a reason to backslide into being involved again.
A SELF-CHECK FOR THE OWNER WHO ISN’T SURE
Of the three, bandwidth is the one you can check yourself without needing anyone else’s read on your capability or your relationships. Name the three decisions you personally made most often two years ago.
Are you still making them today at a business that’s grown since then, or has your role shifted to a different, higher-leverage set of decisions as the team took on the ones you used to make?
If the answer is the same three decisions at a bigger business, that’s your tell. Your job isn’t to stay the engine. It’s to know when to stop being one.
