The Solo Founder's Emergency Plan: Your Business Shouldn't Die With You

"Bus factor" is a software term: how many people need to get hit by a bus before your project fails?

For solo founders, freelancers, and one-person businesses, that number is often one. You.

If you're the only person with access to your hosting credentials, domain registrar, payment processing, and client files—your business dies with you. Your customers can't get support. Your team (if you have one) can't keep things running. Recurring revenue stops immediately.

This isn't paranoia. It's risk management. And it's one of the most overlooked aspects of running a business alone.

What Actually Happens When a Solo Founder Dies

A 2013 study found that founder death in the first decade of a company's existence has profoundly negative effects—even on well-run businesses. Startups are about 50% less likely to adapt and change after losing a founder.

For solo operations, it's worse. There's no succession plan because there's no one to succeed to. Everything—knowledge, access, relationships—lived in one person's head.

Here's what your family or business contacts face:

Day 1: Servers are running. Payments are processing. No one knows anything is wrong.

Day 3: Customers start asking questions. Support requests go unanswered. Something seems off.

Week 1: It becomes clear you're not responding. But no one can access anything. The business is a black box.

Week 2-4: Whoever inherits your estate begins trying to piece things together. They find your laptop—but don't know the password. They contact hosting companies—but aren't authorized on the account.

Month 2+: Legal processes begin. Probate may be required. Companies slowly respond to requests with death certificates. By now, customers have left. Revenue has stopped. The business that could have been sold or transferred is worthless.

The tragedy isn't just the lost business. It's that none of this needed to happen.

The Bus Factor Checklist

If you died tomorrow, could someone else:

Access your email?
Log into your hosting provider?
Access your domain registrar?
Log into your payment processor (Stripe, PayPal)?
Access your code repositories?
Reach your clients with account information?
Access your bank accounts and financial records?
Find contracts and legal documents?
Know which vendors need to be paid?
Understand how the business actually runs?

If you checked fewer than half of these, your bus factor is dangerously low.

Building a Business Continuity Document

The solution is documentation—but not just any documentation. You need a single document that gives someone else everything they need to either keep your business running or wind it down gracefully.

Section 1: Access Credentials

List every critical service with login information:

Service	URL	Username	Password/Notes
Hosting (DigitalOcean)	digitalocean.com	admin@business.com	[In password manager]
Domain (Cloudflare)	cloudflare.com	admin@business.com	[In password manager]
Payment (Stripe)	stripe.com	billing@business.com	[In password manager]
Code (GitHub)	github.com	username	[In password manager]
Email (Google Workspace)	admin.google.com	...	...

Include your password manager master password and recovery codes. Without these, the rest is useless.

Section 2: Infrastructure Overview

Explain how your business actually works:

Where does the code live?
Where is it deployed?
How do deployments work?
What databases exist and where?
What third-party APIs are critical?
What breaks if any of these fail?

Write this for someone technical but unfamiliar with your specific setup.

Section 3: Financial Overview

Bank accounts and access information
Credit cards used for business expenses
Recurring revenue (amount, source)
Recurring expenses (what, when, how much)
Outstanding invoices
Pending payments owed

Section 4: Client Information

Active clients and their contacts
What you're delivering to each
Any pending deliverables or deadlines
Where client files are stored

Section 5: Key Contacts

Accountant/bookkeeper
Lawyer
Key contractors or team members
Anyone who should be notified

Section 6: Instructions

What should happen?

Should someone try to keep the business running?
Should it be sold?
Should it be wound down?
Who should handle this?

Be explicit. Don't leave critical decisions to people who don't have context.

Where to Store This Document

The document is useless if no one can find it or access it.

Bad options:

On your laptop (password-protected, inaccessible)
In Google Drive (account may be locked)
In a physical safe (may not be found, may be outdated)
Emailed to your spouse (sitting in an inbox they may not check)

Better options:

In a password manager with emergency access enabled
With your lawyer (expensive, may be slow to access)
In a deadman switch

A deadman switch is particularly well-suited for this. Your business continuity document is encrypted and stored. If you stop checking in—because something happened to you—the document automatically delivers to your designated contact.

No one needs to know where to look. No one needs to guess passwords. The automation handles delivery.

Who Should Receive It?

Choose someone who:

You trust completely
Is likely to outlive you
Has enough technical competence to follow instructions
Will actually act on it

This might be a spouse, a business-savvy friend, a trusted contractor who knows your systems, or a co-founder equivalent who's not formally part of the business.

Consider having a primary and backup recipient. Life is uncertain.

Keeping It Updated

The biggest risk with business continuity planning is outdated information. You change hosting providers, update passwords, add new services—and forget to update the document.

Set a recurring reminder (quarterly works well) to review and update your business continuity document. If you're using a digital solution, updates are quick.

Some things that should trigger an immediate update:

New hosting or infrastructure
New payment processor or bank account
New major client
Any password change on critical services
Changes to key team members or contractors

The Emotional Resistance

Most solo founders resist this planning because it feels morbid—or because they're too busy.

But consider: you have insurance for unlikely events. You have backups for your code. You plan for server failures and security breaches.

This is the same thing. You're building resilience against a low-probability, high-impact event.

The time investment is minimal: a few hours to create the initial document, a few minutes quarterly to keep it updated. The payoff is knowing your business—and the people who depend on it—won't be left stranded.

The Minimum Viable Plan

If you do nothing else today, do this:

Open a text document
Write down your password manager master password and recovery method
List your three most critical services (hosting, domain, payment) with login info
Name one person who should receive this if something happens to you
Store it somewhere that person can access

That's fifteen minutes of work. It's imperfect, but it's infinitely better than nothing.

Then schedule time to build out the full business continuity document. Your future self—and the people who depend on your business—will thank you.

Killswitch provides encrypted document storage with automatic deadman switch delivery. Store your business continuity plan securely. If you stop checking in, your designated contact automatically receives access—no lawyers, no delays, no guessing where to find it.