Key-Person Risk in a Founder-Led Scaleup

Key-person risk is the financial and operational exposure a company carries because critical knowledge, relationships, and decisions live inside one person. In a founder-led €1M+ scaleup, that person is almost always the founder.

It is usually framed as a continuity risk. What happens if the founder gets hit by a bus. The bigger, more frequent cost is continuous: every week the founder is the bottleneck, the company under-performs its potential growth rate by 10–30%. The bus scenario is rare. The bottleneck scenario is daily.

In M&A diligence, key-person risk shows up as an explicit valuation discount or as a structural condition. Earn-outs, founder lock-ins, retention escrows. In growth rounds, it shows up more quietly: lower multiples, smaller round sizes, more aggressive board terms.

The honest read: a €5M ARR business with high founder dependency typically trades at a 20–40% discount to a comparable business with the dependency reduced. The dependency is reducible. The discount is therefore avoidable. Boards that treat this as a "soft" issue are leaving real money on the table.

Diligence teams look for five specific signals. A board can audit all five in one afternoon.

1. Customer concentration on the founder. Do top-10 customers reference the founder by name? Does the founder appear on more than 30% of sales calls? Is there a named second contact on every top account?
2. Hiring chokepoint. Who closes senior offers? If the answer is "the founder, always," that is a chokepoint.
3. Written decision rules. For the top five recurring non-routine decisions, is there a written rule, or does it live in the founder's head? If the latter, the company cannot scale that decision past the founder's bandwidth.
4. Founder absence tolerance. Could the company sustain current revenue for 14 days with zero founder input? 30 days? 90 days?
5. Founder biology. This is the one diligence teams miss. A depleted founder is a more dependent founder. They revert to control because recovery capacity is too low to delegate. (See HRV for founders for the underlying signal.)

Most "fixes" reduce the appearance of dependency, not the dependency itself.

• Hiring a COO does not reduce dependency if decision rules are still in the founder's head. The COO becomes a translator, not a decision-maker.
• A board offsite produces alignment and a deck. It rarely produces installed handoffs.
• A generic coaching engagement works on mindset. If the calendar, decision rules, and recovery do not change in parallel, mindset reverts in 3–4 weeks.

The thing that actually reduces dependency is repeatable handoff rhythm. Small, written, reviewed weekly, held under stress. Detail on the operational side is in how to reduce founder dependency in a scaleup.

A board can ask for four things on a 90-day timeline:

1. A named #2 in every function with written authority limits.
2. Written decision rules for the top five recurring decisions that currently route to the founder.
3. A named second contact on every top-10 account, introduced and active within the first quarter.
4. A 14-day founder absence test, scheduled and run, with a written post-mortem.

These are not vague asks. They are auditable. A board that requests them quarterly is doing the work of reducing key-person risk in the only way that holds. Founders frequently appreciate the structure. The dependency is rarely a thing they want, just a thing they have inherited from the company's growth.

If you are a board member or investor reading this about a portfolio company, the first move is the 14-day absence test. Cheapest, fastest, most honest diagnostic available. If the company cannot pass it, the dependency is the priority. Not the next hire, not the next round.

If you are the founder being read about, the Founder Mode Score is the same diagnostic from the inside. The Founder 1:1 program is the roughly 6-month installation that brings the four reductions above into operational reality.