The solo-business handover nobody plans for

You wake up ill on the morning of a launch. Customers are waiting for downloads, a coaching call is in the diary, and a payment question is sitting in your inbox. Nothing is technically broken, but every part of the business depends on you being able to open a laptop and remember what to do next.

Decide what needs covering

The aim is not to make your business run indefinitely without you. It is to prevent a short absence becoming a customer-facing failure. Begin by listing what could reasonably happen in the next seven days: a payment arrives, a buyer cannot find a file, a call needs cancelling, or someone asks whether an order has gone through.

1. 1Write down the customer promise for each product: what the buyer receives, where they receive it and how quickly you normally respond.
2. 2Mark the tasks that involve money, personal data or irreversible decisions. These need clearer instructions and a named person.
3. 3Separate urgent actions from actions that can wait. A failed delivery may need attention today; a request for a new custom product can wait until you return.
4. 4Choose the smallest acceptable service level for an absence. This might mean pausing launches, replying only to access problems and rescheduling calls.

Make payments understandable

Someone covering for you should be able to answer three questions without guessing: has the customer paid, what happens after payment, and where does a payment problem belong? Create a one-page payment note with the name of each offer, its price as currently displayed, the payment processor, the normal fulfilment route and the action to take when something does not match.

If you sell through store.fan payments, document the route from checkout to Stripe and explain what the covering person can safely check. store.fan takes 0% of sales, while Stripe's own processing fee still applies, and money goes straight to your own Stripe account. That makes the ownership of the money clear, but it does not remove the need to decide who can review payment information or handle a refund.

Put customer access in one place

Files are often the quietest source of handover trouble. A customer may have bought a workbook months ago, while the latest version is stored in a folder with a name only you understand. Use a simple inventory: product name, customer-facing description, current file or lesson location, delivery method and the last time you checked the link.

• Keep a customer-facing copy separate from drafts, experiments and old versions.
• Use names that describe the product and version rather than names such as final-final-2.
• Record which files must not be edited during an absence.
• Add a short instruction for replacing a broken link, but make changes only from an authorised account.
• If a product is delivered through store.fan, note the relevant product page and delivery path. Its digital downloads feature can keep delivery consistent, but your handover still needs to cover exceptions.

Write the customer message before you need it

A vague out-of-office message creates more questions than it answers. Prepare two or three short templates: one for a delayed reply, one for a missing download and one for a cancelled call or event. Say what is happening, what the customer should do now and when they can expect the next update.

Keep the message factual. For example: “I am temporarily unavailable. If you have purchased a product and cannot access it, reply with the email address used at checkout. For other questions, your message will be answered when I return.” Do not promise a response time that nobody has agreed to meet.

For scheduled broadcasts or promotions, list what is already queued and what should be paused. If you use store.fan email marketing, include the campaign name, its purpose and the stop decision. A person covering for you should not have to infer whether a message is a routine newsletter or a time-sensitive launch.

Choose access with care

The safest handover is not one where another person receives every password. It is one where they receive the minimum access needed for a defined period, with a clear way to contact you if the instructions do not cover something. Keep financial, customer and personal accounts distinct where possible, and record who has access and when it should be removed.

Test the handover while you are well

Ask the person covering for you to follow the document without verbal help. Give them a small test: find the current file, identify a fictional payment problem, locate the customer message and explain what they would escalate. Every question they ask is evidence that the instructions need one more sentence.

Store the handover where the right person can reach it, but do not place sensitive information in an unprotected document. Include the date it was last reviewed, the date access should end and the location of the current product list. When your storefront changes, update the handover at the same time. On store.fan, an iOS app can provide instant sale alerts, which may help you notice activity while away, but an alert is not a substitute for a response plan.