You become less dependent by finding out which tasks, client contacts and decisions currently run only through you, and then placing them, one by one, somewhere else: with a team member, a system or a documented process. That is not a matter of letting go harder, but of knowing exactly where the knot sits.
In a company with 50 to 300 employees, owner dependency is usually not the result of unwillingness to delegate. It arises because the owner was the fastest and most experienced link during the build-up phase, and that role was never formally transferred. The large client still calls the owner directly, the annual price agreements are still made verbally, and the most important supplier only knows the owner by name. That worked when the company was small. At 150 employees, it means a buyer, a bank or a successor sees a company that exists on paper, but in practice sits in one head.
The first step is not organisational but factual: which tasks, decisions and contacts currently run structurally through you, and which could also run without you if a process or a mandate had been established for it? That distinction is sharper than it seems. A quote that you sign because that is simply how it is done, is something different from a quote that you sign because only you can assess the margins. The owner dependency index makes that distinction concrete by weighing eight value drivers on exactly this point: how much of the company demonstrably keeps running without you being on top of it daily. The free test 'how sale-ready are you' gives an initial indication per driver in eight questions, including where the dependency on you is greatest.
In a company of this size, the heaviest dependency often lies with a small number of client relationships that the owner maintains personally. That is a different question from the spread of revenue across clients in general — for that, you can read what customer concentration is and why a buyer factors it in — but the two are connected. An account manager who joins meetings, a second point of contact who is structurally included in decisions, and agreements that are documented on paper instead of in the owner's memory: these are steps that do not weaken the relationship but broaden it. The client often notices little of this transition if it happens gradually; they only notice when the owner suddenly falls away and there is no one else who knows the agreements.
A second layer of dependency does not lie in relationships but in knowledge: pricing structure, supplier terms, the logic behind personnel decisions, the reason why a certain process is set up the way it is. In many companies with 50 to 300 employees, that knowledge exists nowhere on paper, it sits with the owner and with a handful of people who have been there since the beginning. Management information that only the owner can interpret is just as much a risk for a buyer or successor as a client who only knows the owner. Documenting this knowledge in procedures, dashboards or a transferable system is exactly the type of measure that also comes back when addressing the question what depresses the value of your company, because a buyer values a company based on what is demonstrably transferable and not on what the owner happens to know.
Reducing owner dependency takes time, simply because building trust and authority does not happen in a quarter. A client who has been used to reaching the owner directly for twenty years does not switch to an account manager within three months. That makes timing relevant: the earlier this topic is put on the table relative to a possible sale or transfer, the more room there is to do it gradually and without risk, something that is discussed in more detail when addressing the question when to start preparing for a sale. Anyone who only starts with this at the moment a buyer is already at the table often discovers that the problem has by then become visible in the figures and in the reactions of clients, and that is a more difficult point to start from.
The scan gives an indicative range and shows per value driver how sensitive that range is to owner dependency, without this being a valuation or appraisal. That makes visible where the greatest dependency lies and roughly what its effect is, as a first step before anything is adjusted. Owner dependency and the quality of management information are at their core a question about tasks: who does what, and what of that can be transferred to a colleague or to a system. Which tasks can be transferred to people and which to AI is mapped out by the work scan at ftetoai.com, as a follow-up step once this report has made clear exactly where the dependency lies.