Solopreneur business continuity

Solopreneur business continuity means answering one uncomfortable question in advance: if you were suddenly unavailable — hospitalized, incapacitated, or worse — how would anyone keep your one-person business running, or wind it down properly? Imok is a dead man's switch built for exactly this. You write an encrypted handover packet once, name a successor, and check in regularly. If you stop checking in, the packet is delivered automatically. Your business stops depending on someone guessing what's in your head.

You are the single point of failure

When you're a solopreneur, there is no cofounder, no ops team, no assistant who knows where things live. Clients know your email address, not your systems. Revenue arrives through accounts only you can access. Every subscription, renewal, and recurring invoice runs on autopilot — against a card your family can't see, for services nobody else knows exist.

Without a continuity plan, here's what typically breaks:

• Clients are left mid-project, unsure whether you're coming back or whether their deposit is gone.
• Recurring revenue silently continues or silently dies — Stripe subscriptions, retainers, and invoices with no one to manage or cancel them.
• Domains and hosting lapse, taking your site, email, and reputation offline within months.
• Your family inherits a mystery: a laptop full of logins they can't access and no map of what the business even does.

This isn't about fear — it's about basic professionalism. You wouldn't run a company without backups. A one-person company without a handover plan is the same risk.

What to put in your handover packet

Your handover packet is a written set of instructions, encrypted in your browser before it ever reaches our servers. For a solopreneur, it should include:

• A key accounts list — the name and purpose of every business account (registrar, hosting, Stripe, email, bookkeeping), so your successor knows what exists. Store passwords in a password manager; the packet explains the map.
• Client handover instructions — active clients, project status, and a suggested message for notifying them.
• A recurring revenue map — where money comes from (Stripe, PayPal, bank transfers) and where it goes (subscriptions worth cancelling or preserving).
• Domain and DNS renewal notes — which domains matter, where they're registered, and whether to renew or let them lapse.
• SOPs for recurring work — the handful of processes someone must perform to keep things stable for 30–90 days.

How the switch works

Imok asks you to check in on a schedule you choose. If you miss your window, the state machine takes over: five days of reminders first, then a one-time notice to your trusted contact (which deliberately says nothing about the packet), and finally release — your successor receives a one-time reveal link that expires after 30 days or first use. Check in at any point during the reminder phase and everything returns to normal. A manual "Release now" override exists if you ever need it. Read the full details on how it works.

Your packet is protected with zero-knowledge encryption: AES-256-GCM with a key derived from your passphrase in your browser. The server stores only ciphertext. We cannot read your packet and cannot recover your passphrase — see our security page for the full specification.

Related reading

• What happens to your online business when you die
• How to write a business continuity plan as a solopreneur
• The cost of doing nothing
• Pricing

Solopreneur business continuity — FAQ