Founder Dependency: The Diligence Category Most Buyers Get Wrong

A risk note describes a condition. It does not tell a buyer what will stop working, when, or what it costs to replace. Owner dependency is not one risk, it is a set of distinct dependencies that happen to sit in the same person: customer relationships, pricing authority, technical judgment, supplier credit, and informal process knowledge.

Treated as one line item, it gets managed with one instrument, usually an earn-out or a transition period. Treated as a category, each dependency can be tested separately and addressed with the instrument that fits it.

We look for evidence rather than assurances. Which customers have a second relationship inside the business. Which decisions cannot proceed without the owner in the room. Which systems only one person can operate. What happened to performance during the owner's longest absence in the last two years.

Those questions produce documentary answers, and documentary answers can be verified during diligence rather than discovered during ownership.

Founder dependency and revenue quality are usually the same finding described twice. Concentrated relationships held personally by the owner tend to show up again in the QoE work as concentration, non-contracted revenue, or pricing that will not survive a renewal cycle.

Running the two workstreams together, rather than sequentially, is what makes the assessment useful before signing rather than after.

None of this is a reason to avoid owner-led businesses. Prepared sellers frequently reduce their own dependency before they come to market, and owner-independent operations is one of the readiness signals we track.

The point is narrower: name the category, staff it, and score it, so that the transition plan is built against findings rather than hope.