In founder-led businesses, the founder is often one of the organisation’s greatest assets. They carry an extraordinary amount of history, judgement, technical knowledge, customer trust, relationships and instinctive understanding of what “good” looks like.
They are also frequently one of the organisation’s greatest dependencies.
That isn’t necessarily a problem. In many businesses, founder dependence is simply the residue of success. The organisation grew because a talented, committed person made thousands of decisions, developed important relationships, solved difficult problems and set standards others came to rely on.
The question becomes more interesting as the business grows:
Is that dependence still deliberate – or has it quietly become a constraint?
Founder dependence does not always need to be solved by getting the founder out of the business – although sometimes that is exactly the objective. The founder may legitimately have reached the end of their capacity, passion, motivation or availability to be the primary custodian of the business as it grows. This is understandable and doesn’t always point to an underlying problem.
But in other cases, the founder’s exit would destroy some of the value the business is trying to protect. It could result in valuable relationships, IP, culture or know-how being lost in ways that are difficult or impossible to recover, and that could be a real blow to the growth potential of an organisation.
The challenge is understanding the difference. When is founder dependency a deliberate and meaningful contributor to business success, and when does it become something that needs to be addressed in order to allow the rest of the business the freedom it needs to thrive?
Founder dependence shows up in different ways
Recent Gallodium work has reinforced just how differently this issue can present.
In one growing specialist business, the founder had reached the point where stepping back from day-to-day involvement was itself an objective.
The organisation had grown. Other leaders were capable but, for various reasons, reluctant to step up in the presence of the founder. The opportunity was no longer simply to delegate more tasks, but to move from a business in which important decisions naturally flowed back to the founder towards one in which leadership was genuinely shared.
That raised questions well beyond job descriptions. Did other leaders have the authority to make decisions? Did they have the information they needed? More subtly, had enough of the founder’s judgement been shared that people could make good decisions without needing to recreate the founder’s thought process every time?
Those are very different problems. Giving someone authority is relatively easy, but transferring judgement is harder.
In another highly customer-facing business, the dependency looked completely different. The two founders had naturally developed distinct roles in the customer experience. One carried much of what happened behind the scenes; the other embodied much of the warmth and service customers experienced out front.
When they were present, the business felt unmistakably like theirs. When they weren’t, the service could still be perfectly competent. But competent wasn’t necessarily the same thing.
The risk was that something relational and cultural became more transactional in their absence. And that created a different transfer problem. The question wasn’t simply, “Can somebody else perform these tasks?” It was:
Can the organisation reproduce the experience the founders care about when the founders aren’t personally creating it?
That starts to touch on the importance of stories, induction, shared language, behaviours and examples. Those problems can’t be solved with a procedure manual alone.
A third founder-led organisation is considering a much more fundamental transition. Over many years, the founder has built a specialist business around deep expertise, personal reputation, trusted relationships and a very strong sense of professional standards.
At some point the founder wants to step substantially away. Becoming operationally redundant would not be an unfortunate side effect of growth, but a deliberate and planned milestone in the evolution of the business.
But that immediately creates harder questions. How much of what customers value belongs to the organisation, and how much still belongs to the founder personally? Which relationships can transfer? Which expertise can be taught or embedded? Which decisions can be handed over? Can somebody else lead the business successfully – and, importantly, do they actually want to?
And if some parts of the business cannot realistically survive the founder’s eventual departure, should they be reshaped, sold, discontinued or allowed to conclude? That is founder dependency at its most consequential.
These are three very different businesses, each with its own origin and growth story, but the underlying questions are surprisingly similar.
1. Which decisions still require the founder?
Sometimes decisions require the founder because only the founder has the formal authority to make them. That is often solvable through clearer decision rights, or a formal delegations matrix, or simple changes to business policies and rules.
More interesting is when other people technically have authority but still seek the founder’s view because they trust their judgement more than their own. That may point to a capability gap. Or an information gap. Or perhaps nobody has ever made the principles behind those decisions explicit.
If everyone needs the founder to answer the question, it is worth understanding whether the scarce resource is authority or clarity of thought.
2. Which customer relationships depend almost entirely on them?
A close founder-customer relationship can be an enormous competitive advantage. It can also become a vulnerability if the wider organisation never develops meaningful relationships with that customer.
But even here, diagnosis matters. Does the customer genuinely insist on dealing with the founder? Or has nobody ever deliberately introduced other people into the relationship? Does the founder feel personally responsible for protecting the customer? Does the team have enough knowledge and confidence to earn the same trust?
The goal need not be to remove the founder from important relationships. It may simply be to ensure that the relationship belongs to the organisation as well.
3. What knowledge still lives only in their head?
Founder knowledge is rarely just information. It contains patterns and history. It includes the exceptions and the judgement. The memory of why something was tried ten years ago and never attempted again. The instinct that a particular customer request sounds simple but will create a problem six months from now.
Writing procedures helps, but knowledge transfer is rarely solved by documentation alone. The more useful question is what is preventing that knowledge from spreading. Is it simply lack of time? Or perhaps a lack of capability in the people receiving it? Could it be more a lack of trust? Or has the founder simply never needed to explain something they can do instinctively?
Tacit knowledge usually has to be surfaced before it can be transferred. It often needs to be made visible to the business over an extended period of time before it takes root outside of the founder’s own head. And sometimes, it takes more than just time and visibility – trust, generosity, encouragement and support can be just as important.
4. What behaviours or standards disappear when the founder is not in the room?
Founder dependency intersects most obviously with culture in the moments when the founder isn’t present. Founders often reinforce standards without realising they are doing it. They notice things. They ask questions. They challenge compromises, and model how customers should be treated. Their presence communicates what matters.
The revealing question is what happens when they leave the room. If people behave differently, is that actually a problem? Perhaps the new behaviour is simply different – and equally good. But if quality, care, integrity or customer experience noticeably deteriorate, then something the founder personally carried has not yet become part of the organisation. That is worth understanding.
5. Does the team know what “good” looks like without checking first?
This may be the question underneath all the others, and it goes to the heart of what the organisation is trying to preserve as it grows.
The founder usually has an extremely well-developed internal definition of good. From inception and through the growth of their business, they have developed an instinctive understanding of good service, sound judgement, quality work, responsible commercial behaviour and how people should be treated.
But has that definition ever been made explicit? And does the team share it? If their version differs from the founder’s, that does not automatically mean the team is wrong.
The useful question is whether the difference matters. Some founder preferences are simply preferences. Others express something fundamental about the organisation’s values, reputation or customer promise. A growing business needs to know which is which.
The aim is not founder irrelevance
There is a temptation in discussions about scaling to assume the founder was capable enough to get the business this far, but has now reached the point where more experienced heads need to take over. That view can be too simplistic.
The objective should not automatically be to remove the founder from the various roles and responsibilities they fulfil. It should instead be to remove accidental dependence on the founder. Both words matter. The dependency needs to be understood and deliberate.
For some people, success means building an organisation that can operate without them at all. For others, the founder will continue to play an important role for many years because their expertise, relationships or leadership genuinely create value. Either can be a perfectly good outcome.
Taking deliberate steps to understand and address founder dependence means thoughtfully considering what should be transferred into:
capability – what other people need to learn and become confident doing;
systems – what should work consistently without requiring personal intervention;
relationships – where trust needs to extend beyond one individual;
culture – which behaviours and standards need to survive even when the founder is absent; and
leadership – where authority and judgement need to become genuinely distributed.
And perhaps just as importantly, it means deciding what shouldn’t be transferred. There may be things the founder does exceptionally well that remain valuable precisely because they are personal. There may be relationships where founder involvement remains commercially sensible. There may be quirks and preferences that the next generation of leaders should be free to change.
Scaling beyond the founder does not mean cloning them. It means working out what the organisation needs to carry forward without them.
What are you trying to protect?
This is where founder dependency becomes a Values-Led Growth question. Growth often creates pressure to professionalise, systemise and delegate. All of those things can be good.
But if they are done without first understanding what created value in the first place, a business can become very efficient at removing some of the things customers, employees and founders cared about most.
So before asking: “How do we make the business less dependent on the founder?”, there is a better question:
“What is the founder carrying today that the organisation still needs tomorrow?”
Answer that first. Then work out where it should live.
