Every startup has single points of failure. Most founders just don't know who they are.

You stress-test your code. You load-test your infrastructure. You model financial scenarios in your board deck. But have you ever stress-tested your team?

Somewhere in your org chart — probably in more than one place — there's a person whose sudden absence would break something critical. Maybe it's your CTO who holds the entire system architecture in their head. Maybe it's the sales lead who personally manages 70% of your pipeline. Maybe it's you.

The startup world calls this the "bus factor" — the number of people who could get hit by a bus before the project collapses. It's a crude metaphor, but the underlying question is deadly serious: which individuals represent existential risk to your company?

This framework helps you identify those people, quantify the risk, and build a plan to reduce it. It takes about an hour. The clarity it provides is worth significantly more than that.

Step 1: Identify your key persons

A key person isn't just someone with a senior title. They're anyone whose absence would create a cascading failure that takes months to recover from. Start by evaluating every person on your team across four dimensions:

Knowledge concentration

Who holds critical information that exists nowhere else? This includes technical architecture decisions, undocumented systems, vendor configurations, security credentials, and the context behind strategic choices. If this person disappeared tomorrow, how much institutional knowledge would leave with them?

In early-stage startups, this is almost always the CTO or lead engineer. They built the system from scratch. They know why that one database query is structured the way it is. They know where the technical debt lives and what will break if you touch it.

Relationship ownership

Who owns relationships that the company depends on? Investor relationships, key customer contacts, strategic partnerships, vendor agreements negotiated on personal trust. These relationships took months or years to build, and they don't transfer automatically when someone leaves.

Your CEO who personally knows every LP in your lead investor's fund. Your account executive who golfs with the CIO at your largest client. Your BD lead who has a handshake deal with a distribution partner. These people carry relationship capital that has real dollar value — and it walks out the door with them.

Revenue dependency

Who directly drives revenue? In startups, revenue is often highly concentrated around one or two people. Your top sales rep who closes 60% of deals. Your founder who personally sells every enterprise contract. The product lead whose roadmap decisions directly influence retention.

Map your revenue streams to specific individuals. If one person influences more than 30% of your revenue — through sales, customer relationships, or product decisions — that's a key person risk.

Technical irreplaceability

Who has skills or expertise that would take 6+ months to replace? Not just anyone who's good at their job — someone whose specific combination of domain expertise, technical skill, and company context makes them genuinely hard to replace at any price.

Your ML engineer who built the proprietary algorithm that differentiates your product. Your security lead with the clearance your government contracts require. Your firmware engineer who understands the custom hardware integration nobody else has touched.

73%
of startups have at least one person whose departure would stall the company for 3+ months

Step 2: The bus factor test

For each person you identified in Step 1, run this thought experiment:

It's Monday morning. This person is permanently gone — no two-week notice, no transition period, no ability to call them with questions. They are simply not here anymore.

Now answer honestly:

  • What breaks immediately? What systems, processes, or relationships fail within the first week?
  • What breaks within 30 days? What projects stall, what clients notice, what deadlines get missed?
  • What breaks within 90 days? What strategic initiatives collapse, what revenue churns, what institutional knowledge is permanently lost?
  • How long would it take to hire a replacement? Not just to fill the seat — to get that replacement to 80% of the departing person's effectiveness?
  • What would it cost? Recruiter fees, signing bonus, onboarding time, lost productivity during the transition?

If your honest answers to these questions scare you, that person is a key person risk. Write it down. We're going to score it next.

Step 3: Risk scoring matrix

For each key person you've identified, assign a score from 1-5 on three dimensions. Then multiply them together for a composite risk score.

Impact (1-5): How badly would their absence hurt?

  • 1 — Minor inconvenience. Work redistributed within a week.
  • 2 — Noticeable disruption. One project delayed by a month.
  • 3 — Significant setback. Multiple projects stall, revenue dips.
  • 4 — Major crisis. Key revenue at risk, investor concerns raised.
  • 5 — Existential threat. Company survival is in question.

Probability (1-5): How likely is an unexpected departure?

  • 1 — Deeply committed, no external pull, healthy, fully vested interest.
  • 2 — Stable but receives recruiter outreach regularly.
  • 3 — Moderately likely to be poached or has personal risk factors.
  • 4 — Actively being recruited or has health/lifestyle risk factors.
  • 5 — High probability of departure within 12 months.

Replaceability (1-5): How hard would they be to replace?

  • 1 — Easily replaced. Large talent pool, minimal ramp time.
  • 2 — Replaceable within 1-2 months with moderate effort.
  • 3 — Difficult. Specialized skills, 3-6 month search and ramp.
  • 4 — Very difficult. Niche expertise, 6-12 month replacement cycle.
  • 5 — Essentially irreplaceable. Unique knowledge or relationships.

Composite score = Impact x Probability x Replaceability

Example: Scoring your CTO

Impact: 5 — Built the entire technical platform. Holds all architecture decisions. Only person with access to certain systems.

Probability: 3 — Gets recruiter messages weekly. Healthy but commutes by motorcycle. Vesting cliff approaching.

Replaceability: 4 — Deep domain expertise combined with startup-specific context. 6-9 month replacement timeline at minimum.

Composite score: 60 — This is a critical risk that needs immediate attention.

Interpreting your scores

  • 1-15: Low risk. Monitor annually. Standard team management applies.
  • 16-40: Moderate risk. Begin documentation and cross-training. Consider key man insurance for anyone scoring above 30.
  • 41-75: High risk. Immediate action required. Get insurance coverage in place, start knowledge transfer, build redundancy.
  • 76-125: Critical risk. This person's absence could end the company. Insurance is mandatory. Build a full contingency plan now.

Step 4: What to do with the results

Identifying the risk is step one. Reducing it is the actual work. Here are the four levers you can pull, roughly in order of speed and impact:

1. Insurance — the immediate financial backstop

Key man insurance doesn't prevent the loss, but it gives your company the cash to survive it. For anyone scoring 41+ on the risk matrix, coverage should be in place within 30 days. The cost is typically $50-$150 per month per person — trivial compared to the exposure.

Insurance buys you the one thing you can't create in a crisis: time. Time to recruit. Time to transition relationships. Time to stabilize the company. Without it, a key person loss becomes a cash crisis on top of an operational crisis.

2. Documentation — reducing knowledge concentration

Every key person should have their critical knowledge documented in a format that someone else could actually use. This means architecture decision records, runbooks for critical systems, relationship maps for key accounts, and documented processes for anything that currently lives only in one person's head.

This isn't about creating bureaucracy. It's about ensuring that the company's most valuable knowledge survives any single departure. Set a standard: if only one person knows how something works, it's not documented well enough.

3. Cross-training — building redundancy

For every critical function, at least two people should be capable of performing it at a baseline level. Your CTO's lead engineer should understand the system architecture well enough to keep things running. Your CEO's chief of staff should know every investor contact. Your top sales rep's account manager should have relationships with key clients.

Cross-training is slower than documentation but more resilient. A person who has actually done the work — even occasionally — can step in far more effectively than someone reading a runbook for the first time during a crisis.

4. Succession planning — preparing for the worst

For anyone scoring in the critical range, you need an explicit succession plan. Who steps into this role if the person is gone tomorrow? What authority do they need? What decisions can they make? Who do they call first?

This doesn't need to be a 50-page document. A one-page brief for each critical role — covering responsibilities, key contacts, immediate priorities, and decision authority — is enough to prevent paralysis in the first 72 hours.

The prepared scenario

Your CTO is in a serious accident and can't work for six months. Because you ran this risk assessment, here's what happens: Key man insurance pays out within 30 days, giving the company cash to hire interim technical leadership. The documented architecture decisions and runbooks allow the engineering team to keep shipping. The cross-trained lead engineer steps into an acting CTO role using the succession brief you wrote three months ago.

It's still hard. It's still disruptive. But the company survives and continues to execute — because you spent an hour identifying the risk and a few weeks reducing it.

Run the assessment. Then act on it.

This framework takes about an hour for a 10-person startup. Larger teams might need a half-day. Either way, the output is a clear, prioritized list of your people risks — and a concrete plan to address each one.

Most founders who run this assessment are surprised by what they find. Not because the risks are hidden — but because they've been so focused on product, revenue, and fundraising that they never stopped to ask: what happens if the person making all of this work is suddenly gone?

The answer to that question — and the plan you build around it — is the difference between a startup that survives adversity and one that doesn't.

If your assessment reveals high-risk key persons (and it will), book a 15-minute call to discuss coverage options. We work with startup founders every day to get the right protection in place — fast, affordable, and structured for how startups actually work.

Coverage subject to underwriting approval. Insurance products vary by state. Consult your tax and legal advisors for situation-specific guidance.