Key person risk is the exposure a business carries when a critical function depends on one person — usually the founder. The useful way to hold it is as an insurance policy you are already self-funding: every function only you can perform is a policy you pay for in hours, stalled decisions, and revenue that waits on you. Most founders never price that policy, which is why it shows up as background stress instead of a number. Your key person risk premium is that number — the gap between what covering a function would cost you per year and what a two-week absence from it would cost you.
Key takeaways
- Key person risk is a policy you already self-fund in time, stalled decisions, and revenue that waits on you.
- Your premium for any function is the gap between the annual cost of covering it and the cost of a two-week absence from it.
- Coverage does not have to mean hiring; a runbook, a cross-trained teammate, or a contingency service all count, and the cheapest option usually wins.
- Cut the premium by working only the top three functions — document, delegate, or automate — then re-price the policy.
Why key person risk is a self-funded insurance policy
An insurer prices risk by asking two questions: how likely is the event, and how much would it cost if it happened? You can ask the same two questions about your own role without needing an actuary. The event is you being unavailable — sick, travelling, burned out, or pulled into a family emergency for two weeks. The cost is whatever stops moving while you are gone.
What makes it a premium rather than a worry is that you are already paying it. The uncovered policy charges you in rework, in deals that sit, in a team waiting for a decision, in the low dread at the back of any week you cannot afford to be ill. Pricing it just converts that charge into a figure you can act on.
The key person risk premium, step by step
1. Inventory the functions only you handle. Not your whole job description — the functions where a two-week absence causes real damage. Sales conversations, pricing decisions, approvals above a threshold, payroll and vendor payments, the one report everyone asks for. Keep the list short and honest. If someone else could do it with a day's notice, it is not on the list.
2. Price the coverage for each function. For every line, write down the cheapest realistic way to make it survive your absence: a part-time backup, cross-training an existing teammate, a written runbook with a named owner, a contingency service, or automation. Use annual cost, including your own setup time valued at what your hour is actually worth.
3. Estimate the two-week exposure. If you vanished for ten working days, what would it cost? Count the revenue that stalls, the commitments you would miss, the decisions that back up, and the hours of cleanup when you return. Estimate deliberately and round down — the point is to compare orders of magnitude, not to produce a forecast.
4. Subtract to get the premium. If coverage costs less than the exposure it removes, the difference is what you are overpaying to stay uncovered. That number is your key person risk premium for that function. Repeat for each line, then add them up.
5. Sort by premium and work from the top. You are not fixing everything. You are buying down the three largest premiums with the least expensive coverage available.
| Function only you handle | Cheapest coverage move | Effect on the premium |
|---|---|---|
| Sales calls only you can run | Document the offer, objections, and pricing logic; train one person on first calls | Removes the "nobody else can talk to buyers" stall |
| Approvals only you can give | Publish thresholds and name a backup with signing authority | Turns a two-week freeze into a decision that keeps moving |
| Reporting only you can produce | Automate the pull or write a runbook with a template | Converts a recurring time cost into a one-time setup |
| Vendor payments and admin | Cross-train a second person on the payment run with a checklist | Cuts a single point of failure without adding headcount |
A worked example, without the fake numbers
Picture a founder with three lines on her list: the sales conversation, the client onboarding approval, and the weekly reporting pack. She fills in her own figures — her costs, her exposure estimates — and the verdicts come out different, which is the point.
The sales conversation looks expensive to cover until she realises the coverage is a written offer document and two afternoons of training, while the exposure is every deal that would sit untouched for two weeks. The onboarding approval looks cheap to cover with a named backup and a threshold table, and it removes a stall that would block her team regardless of how well they sold. The reporting pack looks like a small premium until she notices she rebuilds it by hand every week — so the real coverage cost is mostly automation she should have done a year ago.
Then she re-prices all three after the coverage is in place. The premiums drop, and what remains is the honest shortlist of what still depends on her.
The mistake that hides the real number
Most founders price coverage as a salary and stop there. A hire is the most expensive possible answer, so the calculation comes back looking unaffordable and the subject gets dropped for another quarter. That is how a cheap problem stays expensive.
The second version of the same mistake is treating knowledge as coverage. A teammate who "knows where things are" is not coverage if they cannot make the call while you are unreachable. Coverage means someone other than you can complete the function end to end, without asking a question that could have been written down.
Cutting the premium: document, delegate, automate, eliminate
Every function on your list gets one of four verdicts.
Document it if the function is a decision you would repeat — the criteria, the thresholds, the exceptions. A runbook is the cheapest coverage you can buy, and it takes an afternoon.
Delegate it if someone already has the context and only lacks the authority. Most of these functions are delegation problems disguised as workload problems.
Automate it if the work is a repeatable pull, a report, a reminder, or a status update. Automation does not remove your judgment; it removes the part of the job that never needed it.
Eliminate it if the function exists because of a habit nobody has questioned. The cheapest coverage is the function you stop performing.
Where this fits into the bigger bill
Your key person risk premium is one line inside a larger cost: the price of running a business that depends on you being everywhere. EXIUSS calls that the Chaos Tax. Pricing your key person risk, then running the same calculation across manual work, urgent problems, missed revenue, and unused tools, tells you how much of your overhead is really self-insurance overhead.
You can do the arithmetic yourself, or use the free RADAR bottleneck cost calculator. It is a free five-step diagnostic that takes six inputs and breaks your annual cost down by category, then offers an optional one-time $7 full diagnosis with a chaos archetype, a sovereignty maturity level, and a 30-day recovery plan tagged Systemize, Delegate, Automate, or Eliminate. The point is not the report — it is the short list of three functions you finally stop self-insuring.
Quick checklist
- List the functions where a two-week absence would cause real damage, and nothing else.
- Price the cheapest realistic coverage for each one, including your own setup time.
- Estimate the two-week exposure in stalled revenue, blocked decisions, and cleanup.
- Subtract coverage from exposure and rank the lines by premium.
- Cut the top three with a runbook, a delegation, or an automation — then re-price.
- Run the numbers through the free calculator at https://tools.exiuss.com/radar.
