Key person risk is the exposure a business carries when one person's absence — usually the founder's — stops revenue. Every company has it; most have never measured it. You can feel the dependency every time you take a day off and the messages start arriving by mid-morning, but a feeling is not a number, and a number is what changes behavior.
The fix is to treat your own availability like an insurance policy and audit it. List every function that would stop if you were out for two weeks. For each one, price the annual cost of a contractor or service that could cover it — that is the premium. Then estimate the revenue at risk if the function fails — that is the exposure. The gap between the two is your uninsured key person risk, and it is almost always concentrated in a handful of functions you have been meaning to document for months.
Key takeaways
- Key person risk is the revenue that stops when one person stops, and it stays invisible because no invoice ever arrives for it.
- The audit prices each function twice: the annual cost of covering it, and the revenue at risk if it fails.
- The gap between those numbers is your uninsured exposure, and the widest gaps are your first three moves.
- Documentation is not coverage; every function needs a decision to document, delegate, systemize, or eliminate.
Why key person risk hides so well
A function you do yourself never shows up as a cost line. It shows up as your calendar. Invoicing happens on Sunday because that is when you get to it. The escalation lands on your phone because nobody else knows what to say. The weekly numbers exist only in your head until a board or a lender or a client asks for them. The business looks lean from the outside. It is not lean — it is concentrated.
That concentration is the risk. You are not short of effort; you are short of alternates. Remove one person for two weeks and the functions they were quietly absorbing do not slow down politely. They stop, and they take revenue with them.
The key person risk audit, step by step
Step 1 — List every function that would stop if you were out for two weeks.
Be honest. Not "would be slower" — would stop. Think in verbs, not job titles: who invoices, who answers the escalation, who approves spend, who runs the weekly numbers, who handles the client who is about to churn, who fixes the integration when it breaks. Six to ten functions is a realistic list for a founder-run business.
Step 2 — Price the cover.
For each function, write the annual cost of the cheapest realistic cover: a part-time contractor, a service, a retainer, a virtual assistant working from a written process. That figure is your premium. It is not what it would cost to replace you — it is what it would cost to keep that one function alive while you are gone. If the only realistic cover is a senior hire, you have found a function that is over-architected around you.
Step 3 — Estimate the revenue at risk.
If this function went dark for two weeks, what walks out the door? Lost deals, late invoices, paused delivery, a client who starts shopping around. Use the conservative end of your range. An honest low estimate is worth more than an impressive high one, because the low estimate is the number you will actually act on.
Step 4 — Subtract to find the gap.
Revenue at risk minus annual premium equals the coverage gap. A function where failure costs far more than the cover is a function you are currently self-insuring with your own calendar. Some will come out negative — cheap to lose, expensive to cover. Those are not risks; they are candidates for elimination.
Step 5 — Rank by gap and act on the top three.
Sort by the widest gap and take the top three. For each, choose one of four moves: document it, delegate it to a named owner, systemize it into tooling that runs without a person, or eliminate it. Then attach a date to the move. Three moves with dates beats ten good intentions.
| Situation | What to do | Why |
|---|---|---|
| Function stops within a day, cover is cheap | Document and delegate first | Cheapest premium against the biggest exposure |
| Function stops, cover is expensive | Systemize with tooling before hiring | Shrinks the dependency before you add cost |
| Function survives a week but quality collapses | Write the SOP and hand it over | Keeps quality stable while you are out |
| Only you understand the function at all | Delegate to a named owner | A document alone leaves the dependency intact |
| Nobody would notice if it vanished | Eliminate it | It is a cost, not a hedge |
The mistake: turning the audit into a documentation project
Most founders list the functions, feel productive, and start writing SOPs for all of them. Documentation is step five, not step one, and it is not the same as coverage. A beautifully written SOP that only you can find is still a single point of failure. The audit's job is to tell you which three functions deserve attention this month — writing procedures for all ten is a way of feeling safe without becoming safe.
The second version of the mistake is assuming a hire is cover. If nobody has done the work and nobody owns the process, your premium estimate is fiction, and you will underprice the gap you are trying to close.
Where the numbers go
Two numbers per function, across six or seven functions, is napkin arithmetic. The point is not the napkin. It is the total. Add your coverage gaps together and you get an annual figure for what your own absence would cost — which is one specific slice of the larger drag on the business: the manual tasks, the urgent problems, the decisions that queue up behind you, the tools you pay for and never open.
The free RADAR bottleneck cost calculator at https://tools.exiuss.com/radar takes six inputs and breaks that drag down by category — weekly chaos cost, urgent problems, missed revenue, and wasted tools — so you can see how much of your annual Chaos Tax is pure single-point-of-failure exposure. From there it produces a chaos archetype, a sovereignty maturity level on the Survivor-to-Sovereign scale, and a prioritized 30-day recovery plan tagged Systemize, Delegate, Automate, or Eliminate. The calculator is free; the optional full written diagnosis is a one-time $7 if you want the executive analysis. Either route leaves you with the same shape as this audit: a short, ordered list with a move attached to each line.
You cannot insure a risk you refuse to name. Run the list, price the cover, and look at the gap. Then start with the widest one this week, before the next fire teaches you the same lesson. Begin at https://tools.exiuss.com/radar.
Quick checklist
- List every function that would stop if you were out for two weeks — functions, not job titles.
- Price the cheapest realistic annual cover for each: contractor, service, or trained assistant.
- Estimate the revenue at risk if that function went dark, and use the conservative end.
- Subtract the premium from the revenue at risk and sort by the widest gap.
- Assign each of the top three a single move: document, delegate, systemize, or eliminate.
- Put both numbers into the free RADAR calculator and compare the total to your overall chaos tax.