Founder dependency is the condition in which a business relies on one person for decisions, relationships, or knowledge that exist nowhere else. Owners describe it as a workload problem. Buyers treat it as a risk to be discounted, and lenders treat it the same way, which makes it a valuation problem long before it becomes a lifestyle one.
A Workload Complaint With a Balance Sheet Consequence
The usual framing is personal. The owner cannot take a holiday, cannot switch off, and answers questions at weekends that nobody else can answer. All of that is true and it is the least important part.
What matters commercially is that the business, as an object, cannot be transferred. A buyer purchasing it would be purchasing a set of relationships and judgments that walk out of the door on completion day.
Every experienced buyer knows this and prices for it. The discount does not appear as a line labelled founder dependency. It appears as a lower multiple, a larger earn-out, a longer handover, or a withdrawn offer late in the process.
The same logic applies to lending. Credit decisions weigh whether the business can service debt if the principal is unavailable. A business where that answer is no borrows on worse terms, whatever its profitability.
Owners rarely see any of this until they attempt a transaction. By then the condition has usually been building for years and cannot be corrected inside the timeline of a sale.
What a Buyer Is Actually Buying
A buyer is not buying revenue. Revenue is a description of what happened while the current owner was present. A buyer is buying the mechanism that produced it, and the question is whether the mechanism is separable from the person.
That question gets tested during diligence in ways owners find uncomfortable. Who holds the customer relationships. Who sets pricing. Who resolves a supplier dispute. Who decides whether a job is quoted at a discount and on what basis.
If the answer to most of those is the owner, the buyer is acquiring a job rather than an asset. Some buyers will still proceed, at a price that reflects the difference and with terms that keep the owner attached for years.
The most common structure in that situation is a deferred payment tied to performance after completion. Owners often read that as a sign of buyer confidence. It is more accurately read as a mechanism for transferring the dependency risk back onto the seller.
Reducing the dependency before a sale changes the shape of the offer more than it changes the headline figure. Cleaner terms and shorter tie-ins are often worth more to a departing owner than a marginally higher price.
There is a further consideration for owners who do not intend to sell. The same structural weakness that lowers a price also concentrates risk during illness, family emergency, or simple exhaustion. Nobody schedules those events around the operating calendar.
Where the Dependency Actually Sits
Founder dependency is usually described as a single condition. It is really four, and they need different remedies.
The first is relationship dependency. Customers and suppliers deal with the owner personally and would question whether to continue without them. This is the most visible form and often the least difficult to address.
The second is decision dependency. Choices above a certain size or ambiguity route to the owner because no rules exist for making them without one. Nobody has ever written down what a manager is permitted to decide alone.
The third is knowledge dependency. The owner holds context about why things are done a certain way, which supplier is unreliable in which season, and what happened the last time a similar situation arose. None of it is recorded.
The fourth is judgment dependency, and it is the hardest. The owner makes calls that genuinely require experience, and the experience took decades to build. This one cannot be documented away and has to be transferred through deliberate exposure over time.
A structured review of the signs that a business cannot run without its founder is useful mainly because it separates these categories. Owners who treat all four as one problem tend to apply the wrong remedy to three of them.
Separating them also reveals which ones the owner has quietly chosen. Some dependency is designed rather than accidental, because holding the key relationship or the final decision feels like security. That preference is understandable and it is the thing being priced.
Why Delegation Fails as a Remedy
The standard advice is to delegate more. Owners who try this usually find it does not hold, and they conclude the problem is the quality of their team.
The team is rarely the issue. Delegation fails because the owner delegates the task without delegating the decision that governs it. The manager can perform the work and must return for approval whenever anything varies from the ordinary.
That arrangement generates more interruption than doing the work directly. It also teaches the manager that judgment is not welcome, which produces exactly the passivity the owner then complains about.
Effective transfer requires defining the boundary. What can this person decide alone, what requires consultation, and what must escalate. Those boundaries need to be written and generous enough that the manager actually uses them.
The second failure mode is the reversal. An owner delegates, the manager makes a decision the owner would have made differently, and the owner overrides it. One override undoes months of transfer, because everyone now understands that the boundary is provisional.
Accepting a worse decision than the one the owner would have made is the price of the transfer. Owners who cannot tolerate that price will remain the constraint, and no organisational design will change it.
Building a Business That Survives an Absence
The work has a recognisable sequence and it takes longer than most owners expect. Beginning several years before any intended exit is normal rather than cautious.
The first step is documenting what happens rather than what should happen. Recording the actual practice, including the informal corrections, is more valuable than a tidy manual describing an idealised process nobody follows.
The second is establishing decision rights in writing. Each management role gets a defined authority, expressed as thresholds and categories rather than as vague encouragement to take ownership.
The third is transferring relationships deliberately. That means introducing the manager into the account, letting them lead the next several conversations, and having the owner become progressively less visible rather than disappearing at once.
The fourth is testing the arrangement under real conditions. A planned absence of two weeks, with no contact, reveals more than any amount of process review. Whatever breaks during that period is the actual dependency, and everything else was theory.
Many businesses lack the internal capacity to run this sequence alone. Structural work of this kind is one of the areas that organisational consulting engagements are built to cover. It is design work rather than advice, and it usually runs across several quarters.
The fifth element is removing the owner from routine communication paths. As long as customers and staff can reach the owner directly for ordinary matters, they will, regardless of what any document says.
Changing that requires the owner to redirect rather than answer. Every question answered personally reinstates the dependency the structure was built to remove, and the redirection has to continue long enough to change habits on both sides.
The Test and the Timeline
The diagnostic is simple and most owners avoid running it. Leave the business entirely for two weeks. No calls, no messages, no checking. Then examine what happened.
Three outcomes are possible. Everything ran, in which case the dependency is smaller than assumed. Things ran with visible strain, which identifies exactly where the gaps are. Or something material failed, which is unpleasant information and far better received now than during diligence.
The results should be treated as data rather than as a verdict on the team. A failure during the absence usually reflects a missing rule rather than a missing capability, and missing rules are cheap to fix once identified.
The timeline for correction depends on which of the four dependencies dominate. Documentation and decision rights can be substantially improved within a couple of quarters. Relationship transfer takes a year or more because customers adjust at their own pace.
Judgment transfer is the slowest and requires a successor who is present for enough real decisions to build their own pattern library. That cannot be compressed by effort, only started earlier.
The businesses most in need of this work are the ones whose owners have the least time to do it. That is the same fact stated twice. An owner consumed by daily operations cannot step back to build the structure that would free them. Breaking that loop usually requires treating the structural work as an actual project with a deadline, rather than as something to be attended to once things calm down. Things do not calm down on their own, and a business that cannot run without its owner will keep proving that point until somebody deliberately changes the design.
Frequently Asked Questions
How much does founder dependency reduce a valuation?
The effect varies by sector and buyer type and it is consistently negative. It appears through the structure of the deal as often as through the price, in the form of longer earn-outs, larger holdbacks, and extended handover commitments. Some buyers withdraw rather than discount. The cleanest way to understand the impact is that it converts a sale into a conditional sale.
How long does it take to reduce the dependency?
Documentation and decision rights can be materially improved within two or three quarters. Relationship transfer generally takes a year or more because customers accept a new contact at their own pace. Judgment transfer is slowest and depends on a successor accumulating real decisions. Starting several years before an intended exit is the sensible planning assumption.
What if there is no obvious successor internally?
The absence of a successor is itself a finding rather than an obstacle. Some of the dependency can be reduced through documentation and decision rules regardless of who is in post. Where a genuine capability gap exists, hiring for it is usually cheaper than the valuation discount it causes. That calculation should be run explicitly rather than assumed.
Is this only relevant to owners planning to sell?
No. The same structure that makes a business sellable makes it resilient to illness, absence, and sudden opportunity. Businesses that cannot operate without one person carry that risk continuously, whether or not a transaction is ever contemplated. The exit case simply makes the cost visible.
Does documenting processes actually help?
It helps when the documentation records what genuinely happens rather than an idealised version. Manuals describing a process nobody follows create a false sense of transfer and can make matters worse. The test is whether an unfamiliar competent person can follow the document to an acceptable result. Anything that fails that test needs rewriting rather than filing.
What is the first step for an owner who recognises this?
Run the absence test and record what breaks. Two weeks with no contact produces a specific list of dependencies that no amount of internal discussion would surface. That list becomes the work plan. Starting with the test rather than with a general improvement effort keeps the project bounded and honest.
No comments:
Post a Comment