Bus factor of one: a continuity plan for solo founders

business security digital estate The Solo Founder's Emergency Plan: Your Business Shouldn't Die With You February 16, 2026 If you're the only one with access to your hosting, domains, and payment processing, your business has a bus factor of one. Here's how to fix it. "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 [email protected] [In password manager] Domain (Cloudflare) cloudflare.com [email protected] [In password manager] Payment (Stripe) stripe.com [email protected] [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…

This excerpt is published under fair use for community discussion. Read the full article at Killswitch.