The Unmapped Deputy: Stress-Testing Key-Person Dependency in Founder-Led Firms
Photo: UK founder led business succession planning org chart boardroom, via as2.ftcdn.net
Founder-led UK businesses tend to map succession around the founder. The board discusses what happens if the founder retires, falls ill or steps back after a transaction. That conversation is necessary, but it is rarely complete. The more immediate risk often sits with the second name on the org chart: the operations manager who has run the warehouse for eighteen years, the finance lead who knows every covenant, or the technical specialist whose relationships with clients and regulators are not written down anywhere. When that person leaves, the business discovers a dependency it never declared.
The founder is rarely the only dependency
Founders are visible, so they attract the succession planning. Long-serving deputies are quiet, so they attract the work. They hold process knowledge, customer history, supplier relationships and informal decision rights. In a small or mid-sized firm, that concentration can be more dangerous than founder dependency because it is not discussed at board level and is not reflected in valuation conversations.
A key-person audit is not a performance review. It is a continuity exercise. The question is not whether the individual is excellent; it is whether the business can operate, decide and retain value without them for a defined period.
Map roles, not names
Start with critical activities rather than job titles. For each activity, identify who performs it, who approves it, who holds the relationship and what would happen if that person were absent for two weeks. Include customer accounts, supplier negotiations, regulatory filings, payroll, credit control, pricing, quality systems, IT administration and any technical process that is not documented.
Then build a dependency map with three columns: activity, primary holder and tested cover. Tested cover means evidence, not an assumption. A named deputy who has never run the process is not cover. A finance director who says the management accountant could produce the board pack is offering an opinion; a board pack produced by the management accountant during the finance director's leave is evidence.
The single-point-of-failure test
Apply four tests to each material role. The absence test: arrange a planned two-week absence and observe what breaks. The decision test: remove the individual from an approval chain and see whether decisions stall. The customer test: check whether key clients ask for that person by name and whether anyone else has a relationship. The system test: confirm whether the role has unique access, knowledge or data that is not documented or shared.
Score each role red, amber or green. Red means no tested cover and a material continuity or valuation risk. Amber means cover exists but is untested or partial. Green means cover has been exercised and documented. The board should see the red list, not a summary that averages risk away.
Cover at board level
Board-level cover is more than an emergency contact list. It requires a named alternate for executive decisions, a documented delegation of authority and a chair or non-executive who can hold the organisation steady if the founder and a deputy are both unavailable. In founder-led firms, the non-executive director can be particularly useful here: not to run the business, but to insist that the dependency is tested and that the board has a plan.
This is also a governance issue. If a single individual can approve payments, release products, sign regulatory returns or commit the company to a contract without a second pair of eyes, the control environment is thinner than the org chart suggests.
A 12-month succession buffer
The aim is not to replace the deputy immediately. It is to build a buffer over four quarters. In the first quarter, complete the dependency map and identify the red roles. In the second, create documented procedures and assign understudies for the highest-risk activities. In the third, delegate real decisions, not simulated ones, and let the understudy run a customer negotiation or month-end close with support. In the fourth, test the arrangement through planned absence and report the results to the board.
Retention matters alongside succession. A long-serving deputy may be loyal but under-rewarded, or may be holding the business together without recognition. The audit should not become a reason to alienate the very people whose knowledge is being mapped. Discuss the exercise openly, frame it as resilience rather than replacement, and consider retention incentives where the dependency is material.
Valuation and transaction readiness
For owners considering a sale or investment in 2027, key-person dependency is a diligence issue. Buyers and investors will ask who runs the business after completion, whether the management team can operate without the founder, and what happens if the deputy leaves. A credible answer is a tested succession buffer, documented processes and a management team with real decision rights. An untested answer is a discount, a deferred consideration structure or a stalled deal.
A practical board agenda
Put key-person risk on the board agenda once a quarter, with a named owner and a simple dashboard: red roles, tested cover, planned absences, documentation progress and retention risk. Review it alongside financial performance, not as a separate HR item. The second name on the org chart is often the first name on the risk register once the board looks properly.
For founder-led UK firms, the objective is not to reduce the founder's importance. It is to ensure that the business is not carrying an undeclared single point of failure in the next office. A 12-month buffer is a modest investment compared with the cost of discovering the dependency after the individual has gone.