Key person risk is the revenue your business would lose if you were suddenly unavailable. It is not a theoretical concern for a founder who is the only person who quotes jobs, approves refunds, and knows where the passwords live. It is a live liability sitting on your balance sheet, and it almost never gets priced.
Most founders address key person risk by promising themselves they will document things someday. That is not a plan. A plan has numbers in it. This article gives you a repeatable way to price the risk on each function you personally carry, compare that number to the one-time cost of handing the function off, and rank what to delegate first.
Key takeaways
- Key person risk on a single function equals the likelihood you are unavailable when that function is needed, multiplied by the revenue exposed while nobody else can run it.
- Your delegation dividend is the annual cost of that risk minus the one-time cost of delegating the function, and it tells you which handoff pays for itself fastest.
- Most founders try to delegate everything at once, get overwhelmed, and revert; the better move is to rank functions by dividend and delegate the top three.
- Once you know your total exposure, you can separate pure key person risk from all your other operational drag and decide what to fix first.
Why key person risk hides in plain sight
Key person risk is invisible because nothing breaks while you are present. The business runs, clients are happy, invoices go out. The risk only surfaces at the worst possible moment: the week you get sick, the week a family emergency pulls you offline, the week you finally take a real vacation.
That is what makes it dangerous. Unlike a bad hire or a failing product line, solo dependence does not announce itself with symptoms. It sits quietly in the fact that you are the only node in the network.
So the first job is not to fix it. The first job is to make it visible by putting a number on each function you alone handle.
The delegation ROI framework, step by step
Step 1: List the functions only you can perform
Be honest and be specific. Not "operations" but "pricing custom quotes," "resolving escalated client complaints," "running payroll," "choosing which vendor to use for fulfillment." Write down every function where the answer to "who else can do this?" is genuinely nobody.
Aim for a real list. Five to fifteen functions is typical for a founder who is still the Chief Everything Officer.
Step 2: Estimate the revenue at risk per function
For each function, ask: if this function stalled for a month, what revenue would be delayed, lost, or refunded? Use your own numbers from your own business, not industry benchmarks. If you do not know exactly, use a conservative range and note the assumption.
This is an estimate, not an audit. A rough number you actually use beats a precise number you never calculate.
Step 3: Estimate the probability of absence
Probability here does not mean a statistic about founders in general. It means your honest judgment about the coming year: how likely is it that you are meaningfully unavailable for a stretch of time long enough to stall this function? Illness, burnout, a family obligation, a death in the family, a period of travel, or simply a week where you are consumed by something else.
Express it as a fraction — for example, a one-in-four chance that you lose two weeks in the next twelve months. Multiply the fraction by the proportion of the year the function would be stalled.
Step 4: Calculate annual key person risk cost
Multiply the revenue at risk by the probability-weighted time exposure. That is your annual cost of carrying this function alone. Do it for every function on your list, then total them. That total is your key person risk exposure.
Most founders find the total uncomfortable. That discomfort is useful. It is the same discomfort the free RADAR calculator is built to surface at https://tools.exiuss.com/radar, which turns six inputs into a costed breakdown of where your time and revenue are leaking.
Step 5: Price the delegation
For each function, estimate the one-time cost of getting it off your plate. That might be a contractor's onboarding hours, the time to write a clear standard operating procedure, a tool subscription, or a combination. Include your own hours at a realistic rate.
Step 6: Subtract and rank
Delegation dividend equals annual key person risk cost minus one-time delegation cost. Rank your functions by dividend, highest first. The top of that list is your delegation queue.
| Situation | What to do | Why |
|---|---|---|
| High revenue at risk, easy to document | Write the SOP and hand off first | Fastest dividend, lowest build cost |
| High revenue at risk, hard to document | Hire a contractor and document alongside them | Risk is too large to leave waiting on perfect docs |
| Low revenue at risk, easy to document | Batch it later | Real but not urgent |
| Low revenue at risk, hard to document | Consider eliminating the function | Delegation may cost more than the risk |
The common mistake: delegating by discomfort instead of by dividend
Most founders delegate the task they hate most, not the task that carries the most risk. Those are rarely the same thing. The result is that they spend money and management attention on a low-stakes handoff, feel a brief burst of relief, and remain just as exposed as before.
Rank by dividend instead. It is less emotionally satisfying and far more effective.
How to start this week
Block one hour. List your functions, put a rough revenue-at-risk number and an absence probability on each, and price the delegation. Then take the top three and start the first one today — write the first page of the SOP, or post the contractor brief.
If you want the arithmetic done for you and a prioritized recovery plan attached, run your numbers through the free RADAR bottleneck cost calculator at https://tools.exiuss.com/radar. It is free, it takes six inputs, and it separates pure key person risk from the rest of your operational drag — then hands you a 30-day plan tagged Systemize, Delegate, Automate, or Eliminate so the highest-dividend handoff happens first.
The risk does not shrink because you ignored it. Price it, rank it, and start delegating the top of the list.
Quick checklist
- List every function where you are the only person who can do it
- Estimate revenue at risk and probability of absence for each
- Multiply to get annual key person risk cost per function
- Price the one-time cost of delegating each function
- Subtract to get the delegation dividend and rank highest to lowest
- Start the top three handoffs this week, beginning with the first
