Your Startup Has No Plan for If You Die (And That's a Problem)

You have a will. Maybe. You probably have life insurance. Your startup, however, has no documented plan for what happens if you get hit by a bus tomorrow. And neither does your co-founder. And neither does your lead investor, who's betting millions on a company whose entire strategy lives in one person's head.

This isn't morbid navel-gazing. It's the most predictable risk that almost no early-stage company addresses. And unlike market risk or technical risk, it's one you can actually plan for.

The Bus Factor Is Real, and It's Usually One

Ask any engineer about "bus factor"—the number of people who could get hit by a bus before a project fails—and they'll tell you it's the first thing you optimize for in any critical system. Redundancy. Documentation. Knowledge distribution.

Now ask a startup founder what their company's bus factor is. The honest answer for most seed-stage companies is one. Sometimes zero, if the surviving co-founder doesn't have the context to ship the next release.

The irony is painful. Founders obsess over uptime and failover for their infrastructure while building organizations with catastrophic single points of failure at the top.

What Actually Happens When a Founder Dies

Let's walk through the realistic scenario, because most founders haven't.

Day one: Chaos. Nobody knows passwords to critical systems. Nobody has authority to access the company bank account. The board can't legally make decisions because quorum requirements weren't designed for this. Employees don't know if they'll get paid.

Week one: The surviving co-founder (if there is one) is grieving while simultaneously trying to prevent the company from imploding. Investors are calling, asking questions nobody can answer. Key customers want reassurance that their vendor isn't about to disappear.

Month one: The estate is in probate. The deceased founder's shares are in legal limbo. Strategic decisions are frozen because nobody has clear authority to make them. Your best engineer just got recruited away because they don't know if the company will exist in six months.

This isn't hypothetical. It happens. And when it does, the lack of a plan turns a tragedy into a preventable company extinction.

The Four Documents Every Startup Needs

None of this requires expensive lawyers or complex structures. It requires sitting down for two hours and making decisions you'd rather not think about.

1. Succession Letter

This is a simple document—updated quarterly—that answers the question: "If I can't be reached for 30 days, what does the company need to know?"

Include: passwords and access credentials (stored securely), key relationships and how to reach them, pending decisions and your thinking on them, financial commitments and cash runway, and anything only you know that would break the company if lost.

This isn't a legal document. It's an operational one. Store it somewhere your co-founder or board member can access within hours of an emergency.

2. Emergency Authority Resolution

Your board should adopt a resolution—ideally when things are calm—that specifies who has authority to act if the CEO is incapacitated. This usually means temporarily elevating a co-founder or board member to act with CEO authority, specifying a timeline (30-90 days) before permanent decisions need to be made, and clarifying what decisions can wait and which can't.

This takes one board meeting to implement. The cost of not having it is a company paralyzed at exactly the moment it needs to act quickly.

3. Key Person Insurance

Key person life insurance is cheap for healthy founders in their 20s and 30s. A $1-2M policy costs a few hundred dollars a month and provides the company with cash to navigate a transition—recruit replacement leadership, cover runway while fundraising pauses, or execute an orderly wind-down if necessary.

Most VCs expect this after Series A but don't require it. Get it anyway. The premium is negligible compared to the protection.

4. Founder Share Provisions

Work with your lawyer to ensure your operating agreement or shareholder agreement addresses what happens to founder shares upon death. Common provisions include: company right of first refusal on estate shares, spousal or family continuity rights (or explicit exclusion of them), and clear valuation methodology for buyout scenarios.

The default in most states is that your shares pass through your estate like any other asset. This can create situations where grieving family members become minority shareholders in a company they don't understand, with interests that may conflict with the surviving team. Specify what you want before it matters.

The Conversation Nobody Wants to Have

The reason founders don't do this isn't complexity—it's discomfort. Planning for your own death forces you to confront mortality in a culture that idolizes young, immortal energy. It feels like admitting weakness.

It's the opposite. The founders who plan for catastrophe are the ones who've thought seriously about what they're building and why it matters. They understand that a company worth building is a company worth protecting from their own mortality.

This is also one of the most important conversations you can have with your co-founder. Not the death part specifically, but the broader question: what is each of us uniquely responsible for, and what would the other person need to know to carry on?

Most co-founder relationships operate on implicit trust and assumed knowledge. That works until it doesn't. The process of documenting your succession plan forces you to make that knowledge explicit—which makes your company more resilient even if neither of you ever gets hit by a bus.

What Investors Should Be Asking

If you're an investor reading this, start asking founders about their key person risk as part of due diligence. Not in a morbid way—just as a basic operational hygiene question alongside "what's your burn rate" and "who owns the IP."

The question reveals more than the answer. Founders who've thought about it demonstrate a level of organizational maturity that correlates with other good practices. Founders who haven't aren't necessarily bad operators—they just haven't been prompted to think about it. Prompt them.

For board members specifically: adding "emergency succession" as an annual board agenda item costs nothing and ensures the topic stays current. Key relationships change. Passwords change. The plan needs to evolve.

The Minimum Viable Plan

If this article prompts you to do exactly one thing, do this:

Write a document—right now, today—that answers the question: "If I were in a coma for 60 days starting tomorrow, what would my co-founder/board need to know to keep the company alive?"

Store it somewhere they can access it. Tell them it exists. Update it every quarter when you update your board deck.

That's it. That's the minimum viable succession plan. It's not comprehensive, but it's infinitely better than nothing—which is what most startups have.

You're building something designed to outlast you anyway. That's the point of a company versus a freelance practice. Act like it.

The founders who build companies that survive their own involvement—whether through exit, stepping back, or tragedy—are the ones who treat their organization as a system that needs to work without any single node. Including themselves.

Make the plan. Have the conversation. Then go back to building, with the peace of mind that comes from knowing you've handled the one risk that was entirely within your control.