A business continuity plan is a written answer to one question: what keeps the business alive if you can't run it? For a solo founder, that answer fits on a single page — the three functions only you can perform, the revenue attached to each one, and the first move that takes you out of the middle of it. Most one-person businesses never write it down, so a two-week absence feels like an extinction event instead of an inconvenience.
Key takeaways
- A usable plan names the three functions that would stop revenue if you were unavailable and puts a rough annual revenue-at-risk figure beside each one.
- The number matters more than the wording, because without it every task looks equally critical and nothing gets fixed.
- Each function gets exactly one move — document it, delegate it, systemize it, or eliminate it — attached to a date.
- The plan is finished in 30 days and tested with a real absence, not perfected in a document you never reopen.
What a one-page business continuity plan looks like
One row per critical function, four columns: the function, what breaks during a two-week absence, the move you are making, and who or what takes over. That is the whole artifact. No risk matrix, no binder, no appendix.
The page works because it forces a decision per row. The failure mode is subtler than laziness: most solo founders write a description of their job instead of a decision about who covers it. A description reads well and changes nothing.
| Situation | What to do | Why |
|---|---|---|
| Only you can sell | Document the pitch and follow-up sequence | A written sequence lets someone else start conversations while you are gone |
| Only you can deliver | Systemize with a checklist and a shared file structure | Delivery quality stops depending on your memory |
| Admin piles up when you are busy | Delegate invoicing and subscription management | Cash keeps moving without your attention |
| The task should not exist at all | Eliminate it | Some functions survive only because nobody questioned them |
Step 1: Name the three functions that actually stop the business
Do not start from your task list. Ask instead: if I were unreachable for two weeks starting Monday, which three activities would stop money from coming in or stop clients from being served? For most one-person businesses the same three show up — new business and pipeline, delivery of the product or service, and the money stack of invoicing, payroll, tax and subscriptions. Write them in plain language, in the order they would hurt.
Step 2: Put a revenue number on a two-week absence
For each function, estimate the annual revenue that depends on it, then the share that depends on you personally inside a two-week window. Include the second-order costs: deals that go cold, clients who lose confidence, refunds, late fees, and the catch-up week waiting for you on return. You are not doing accounting here; you are sizing exposure. Round numbers you can defend beat precise numbers you invented.
Step 3: Price the single points of failure
Open the free RADAR bottleneck cost calculator at tools.exiuss.com/radar and run your six inputs — the hours that go into manual work, the cost of urgent problems, the revenue you are not capturing, and the tools you pay for and never log into. It returns an annual figure broken down by category. Then set your continuity numbers next to that total. A meaningful slice of what the calculator calls your chaos tax is really one thing: the business depends on one person who can get sick.
Worked example: a studio of one
This is an illustration, not a benchmark. A designer runs a studio alone with one part-time contractor. Her three functions are new business, client delivery, and billing and admin. In the two-week absence scenario, the pipeline goes quiet, two active projects stall, invoices go out late, and the contractor waits for direction that never arrives.
She writes revenue at risk for each row: the annual income tied to the function, multiplied by the slice that needs her hands specifically. Then she runs the calculator. The annual total comes back larger than the sum of her three continuity numbers, because the calculator also picks up the weekly friction she had stopped noticing — the rework, the chasing, the tools nobody uses. That gap is the point. Single points of failure are not a separate problem from daily chaos; they are the same problem seen from a different angle.
Her moves, one per row: document the new-business conversation into a one-page pitch and follow-up sequence; systemize delivery with a project checklist and a shared file structure; delegate invoicing and subscription management to the contractor's bookkeeper. Three rows, three moves, four weeks.
Common mistakes
- Planning for the dramatic event instead of the ordinary Tuesday. The likeliest reason you will be unavailable is not a catastrophe — it is illness, a family emergency, or a client fire that eats the week.
- Writing the plan as a description of your job rather than a decision about coverage.
- Trying to build all three rows at once and finishing none of them.
- Skipping the test. A plan that has never been tested is a wish with formatting.
The 30-day plan to make each function survivable
Week 1 — Measure. List the three functions, write a revenue-at-risk estimate beside each, and run the numbers through the calculator so you are working from one total instead of a vague dread.
Week 2 — Document. Write the SOP for the highest-exposure row. Capture what you actually do, in order, including the steps you think are too obvious to write down. The obvious steps are exactly where a handoff breaks.
Week 3 — Delegate or systemize. Hand off one recurring task to a person or a tool. Start with the task that is most repetitive and least judgment-heavy, because that is the one that can leave your desk fastest.
Week 4 — Test. Take two days genuinely offline. Log every question that reached you anyway; each one marks a gap in the page. Update the row, diarize a quarterly review, and re-run the numbers whenever your income or client count changes.
Quick checklist
- List the three functions that would stop revenue if you were unavailable for two weeks.
- Write one annual revenue-at-risk estimate beside each function, even if it is rough.
- Run those numbers through the free calculator at https://tools.exiuss.com/radar
- Assign each function one move: document, delegate, systemize, or eliminate.
- Write the first SOP for your highest-exposure function this week.
- Test the plan with two days offline inside 30 days, then update the page.
The page is not the deliverable — the absence you survive is. Be honest with the inputs, because the diagnosis only works if the numbers are real. If you want the deeper read, the full diagnosis is a one-time $7 and returns your chaos archetype, your sovereignty maturity level from Survivor to Sovereign, an executive analysis, and a prioritized 30-day recovery plan tagged Systemize, Delegate, Automate, Eliminate. If you would rather build inside the platform first, the 14-day EXIUSS trial is the other path, and the SOP and RACI tools draft from your own inputs rather than handing you blank templates. Start with the free calculator at tools.exiuss.com/radar, and stop letting one person be the whole plan.