Business continuity plan for solopreneurs

A business continuity plan for solopreneurs is a short, practical document — plus an automated way to deliver it — that lets a chosen person keep your business running or wind it down cleanly if you suddenly cannot. It answers one question: if I disappeared tomorrow, what would someone need to know in the first week?

You do not need the enterprise version. Here is why, and what to do instead.

Why enterprise-style BCP does not fit you

Traditional business continuity planning is built for organizations: risk assessments, departmental recovery objectives, crisis communication trees, redundant infrastructure. A formal BCP for a mid-size company can run forty pages and take a committee to maintain.

A one-person business has a different risk profile. You have no departments to coordinate, no staff to communicate with, and no IT team to execute failover. What you have is a single point of failure — you — and a business whose entire operational map lives in your head and your accounts. The enterprise framework solves a coordination problem you do not have while ignoring the access-and-knowledge problem you do.

Your continuity plan should be sized to reality: short enough to write in an afternoon, clear enough for a non-expert to follow, and automated enough to arrive without anyone having to find it. The consequences of skipping this are laid out in what happens to your online business when you die — subscriptions billing a dead person’s card, 2FA-locked accounts, clients left hanging.

The practical 6-step plan

Step 1: Inventory your accounts and assets

List every account your business depends on: domain registrar, hosting, payment processor, business email, banking, analytics, social accounts, marketplaces, and the SaaS tools you pay for. For each one, note what it does and what breaks if it is lost. Do not write passwords in plaintext anywhere — the inventory is a map, not a key dump. Your handover packet (step 4) explains where the keys live.

A practical way to build this list fast: open your password manager and your last three bank statements. Every login you have saved and every recurring charge you pay is, by definition, something the business depends on. Most solopreneurs finish this step in under an hour and are surprised by the count — thirty to fifty dependencies is normal for a “simple” one-person business.

Step 2: Map your money flows

Write down what comes in and what goes out. Incoming: which clients or products pay you, through which platform, on what cycle, and whether any invoices are outstanding. Outgoing: every recurring charge, what it is for, and how to cancel it. Your successor’s first financial job is stopping the bleeding and collecting what is owed — this map is how they do it in days instead of months.

Step 3: Choose your successor and your trusted contact

These are two different roles. Your successor receives the handover packet and acts on it — ideally someone with enough business sense to execute instructions, not necessarily someone who loves you most. Your trusted contact is a verifier: the person the system asks to check whether you are actually unreachable before anything is released. Pick people deliberately, tell them they have the role, and decide whether your stated intent is continue the business, wind it down cleanly, or successor’s choice. The succession planning checklist goes deeper on choosing between a spouse, a business-savvy friend, or a fellow founder.

Step 4: Write the handover packet

The handover packet is the heart of the plan: the document your successor actually receives. It covers your accounts, money map, key relationships with contact details, and explicit instructions — what to do on day one, which clients to notify personally, what your intent is for the business. Write it for a smart person who knows nothing about your industry. For a full breakdown of what to include, see our guide on what to put in a business handover document.

Step 5: Set up automatic delivery

A plan in a drawer fails the timing test: too early is a security risk, too late is useless. Automatic delivery solves it. With Imok, your packet is encrypted in your browser with AES-256-GCM — zero-knowledge, so we cannot read it — and released to your successor only if you stop checking in: five days of email reminders, then a trusted-contact check, then a one-time reveal link. The full flow is on the how it works page. A manual “Release now” override exists if you ever want to hand over deliberately.

One critical detail lives in this step: because the encryption is zero-knowledge, your successor needs your passphrase to decrypt the packet, and Imok cannot recover it. Decide how the passphrase reaches them — held by your estate attorney, split with your trusted contact, or another arrangement you trust — and document that arrangement outside the packet itself.

Step 6: Review quarterly

Put a recurring reminder on your calendar. Each quarter: did any accounts change? Did money flows shift? Are your successor and trusted contact still the right people, and do they still have the roles? Fifteen minutes a quarter keeps the plan accurate; a plan written once and abandoned drifts toward fiction.

Copy-paste mini template

This is deliberately small. Paste it into your packet and fill it in:

BUSINESS CONTINUITY SUMMARY
Last updated: [date]

Business name: [name]
What it does (2 sentences): [plain-language description]
My intent: [continue / wind down / successor's choice]

CRITICAL ACCOUNTS (where the keys live: [password manager / location])
- Domain registrar: [provider] — renews [date]
- Hosting: [provider] — runs [what]
- Payments: [Stripe/PayPal/etc.]
- Business email: [provider]
- Banking: [institution]

MONEY IN: [clients/products, platform, cycle, outstanding invoices]
MONEY OUT: [recurring charges and how to cancel each]

KEY PEOPLE:
- Successor: [name, contact]
- Trusted contact: [name, contact]
- Active clients to notify personally: [names, status]

FIRST-WEEK INSTRUCTIONS:
1. [e.g., Pause ad spend at...]
2. [e.g., Email client X about project Y...]
3. [e.g., Cancel or transfer hosting...]

WHERE THE DETAILS LIVE: [e.g., full SOPs in the encrypted packet]

Common mistakes to avoid

Writing it once and never updating it. Businesses change faster than plans. An inventory pointing at a registrar you left two years ago sends your successor on a scavenger hunt. The quarterly review is not optional — it is what keeps the plan real.

Storing it somewhere no one can reach. A plan in a locked drawer, an unlabeled folder, or a cloud doc no one knows exists is functionally identical to no plan. The delivery mechanism is part of the plan, not an afterthought — which is why automatic, trigger-based delivery exists.

Making it legally ambiguous. Your continuity plan is an operational document, not a legal instrument. Do not try to transfer ownership in it, and do not let it contradict your will. State your intent clearly, leave legal transfer to legal documents, and if the two seem to conflict, get an attorney to align them. Imok handles operations; it is not a legal will and does not provide legal advice.

Writing for yourself instead of your successor. You know what “the usual hosting setup” means; your successor does not. Every instruction should survive contact with a smart person who has never seen your business. When in doubt, add the extra sentence of context — the packet is read once, under stress, and there is no option to ask you a follow-up question.

Choosing people but never telling them. A successor who learns about their role from a dead man’s switch notification is starting from confusion at the worst possible moment. Both your successor and your trusted contact should know their roles, know the plan exists, and know the passphrase arrangement — while you are still here to answer questions.

Adapting the plan to your business model

The six steps are universal, but the emphasis shifts depending on what you run:

• SaaS and software products: weight step 4 (the handover packet) toward infrastructure — hosting, deployment, the status page, how to communicate with users during a transition, and the sequence for either keeping the service alive or sunsetting it gracefully. Your successor’s hardest problem is technical, so your SOPs carry the plan. See the SaaS owner use case.
• Client services: weight steps 2 and 4 toward relationships — project status per client, deliverables owed, refunds that may be due, and the exact wording you would want used when someone tells a client what happened. Your successor’s hardest problem is emotional and reputational, so the client context carries the plan. See the freelancer use case.
• Content, audience, and productized income: weight step 1 toward platforms — your email list, course platform, affiliate dashboards, and payment accounts are where the value lives, and they are scattered across providers with wildly different policies. Your successor’s hardest problem is discovery, so the inventory carries the plan.

In all three cases, the failure mode of “no plan” is identical; only the order in which assets decay changes.

How this plan fits with the rest of your planning

This continuity plan is one layer of a small stack, and it works best when the other layers exist:

• Legal layer: a will (and, where appropriate, powers of attorney) drafted with a professional. This decides ownership. Your continuity plan must never contradict it.
• Credential layer: a password manager holding actual logins, ideally with its emergency-access feature configured for your successor. The continuity plan explains where the credentials live; the password manager holds them.
• Operational layer: this plan — the inventory, the money map, the relationships, the instructions — delivered automatically by a dead man’s switch.

Each layer is weak alone. Credentials without instructions are keys without a map; instructions without credentials are a map to locked doors; and both without legal clarity can strand a willing successor. Together they form a complete answer to the question every one-person business should be able to answer: if I am gone tomorrow, what happens on day one?

Putting it together

Six steps, one afternoon of writing, fifteen minutes a quarter. The plan converts your absence from a slow-motion collapse into an orderly handover — and for most solopreneurs, the solopreneur use case is exactly the scenario Imok was built for: you keep full control while you are here, and your successor gets a complete map the moment it is needed, delivered automatically and unreadable to everyone else along the way.

Frequently asked questions