When a solo founder got ill with no cover: a composite case study

This is a composite account, written for illustration and drawn from patterns that come up repeatedly in one-person businesses. It is not a real interview, and no individual, business or client is being described or quoted.

Five weeks, no plan

A solo founder had built a business that ran entirely through them, and had deferred a proper contingency plan to a quieter period. When the founder was signed off for what became five weeks, the business had no cover, no documented processes, and no arrangement with anyone who could pick up client work.

During the first week the founder tried to keep working from bed, which proved ineffective and slowed recovery. Emails were checked, attempts were made to respond to clients, and the situation worsened. In the second week working stopped, which is when the practical consequences began to arrive.

There was a distinct moment when continuing to work was abandoned: while in bed and feeling terrible, the founder had spent an hour trying to respond to a client email that was not important enough to justify the effort. That realisation led to an actual stop.

What broke first

Client work was not the first thing to fail. Most clients were considerably more understanding than expected once told plainly what was happening. What broke was everything that nobody was actively watching.

• Invoices went out three weeks late, which pushed a cash gap into the following month and forced a dip into savings
• Two enquiries went unanswered and went elsewhere, representing work that would have been taken
• A subscription renewed on a card that had expired, taking a service offline and affecting a client project
• A deadline slipped that could have been renegotiated easily in week one, but became a problem by week four
• A supplier sent a message that needed responding to, and by the time a response occurred, the supplier had moved on

The cash flow problem

The late invoices were the most damaging. The founder normally invoiced on the last day of the month, and clients tended to pay within two weeks. Expectation had been for money to arrive in the middle of the following month. Delaying invoices until three weeks into the month pushed payments out, so expenses had to be covered from savings.

This was particularly stressful because there was not a large reserve. Only about two weeks of expenses had been saved, which meant the late invoices created genuine worry about money on top of being unwell.

The enquiries that went unanswered were also frustrating. Two potential clients reached out during the week off. The emails were not seen until return, and by then the leads had moved on. These were not huge projects, but they represented income that would have been secured.

The conversation I dreaded

Telling clients provoked the most anxiety beforehand, and proved the least difficult in reality. A short, factual message — unwell, off for an estimated period, an explanation of what would happen to ongoing work, and a note about when the next update would arrive — produced sympathy rather than complaint from almost everyone. The one client who reacted badly had been a difficult relationship long before the illness.

The lesson learned was that most clients are more understanding than expected, and the key is being factual and clear rather than apologetic. Repeated apologies about being ill only make the interaction awkward. A simple holding message such as 'Unwell and off for about two weeks. Project on hold. Will update on Friday' is far better than an extended apology that centres on how terrible the situation feels.

Clients value clarity and consistency. Once an update schedule was promised — for example, an update each Friday — that schedule was followed even if the update was only 'still unwell, still off, will update again next Friday'. That consistency reduced client worry.

What I put in place afterwards

None of the fixes were expensive. Collectively they took about two days to set up.

• A single document listing logins, recurring payments, key contacts and what to do first — the thing that would have prevented most of the damage
• A reciprocal arrangement with two other freelancers to cover urgent client work either way, with a clear agreement about what counts as urgent
• Invoicing moved to automatic scheduling rather than a manual monthly task, so invoices go out even if the founder is not available
• A written holding message that a family member could send on the founder's behalf, so clients receive a response even if a personal reply is not possible
• A reserve target set specifically at essential costs for eight weeks, removing immediate financial stress while unwell

The contingency document

The contingency document is the most important thing. It is a single document that lists everything someone would need to keep the business running for a few weeks. It includes logins for email, project management systems, and any tools used. It records recurring payments and when they are due. It lists key client contacts and what each client is working on. It contains a 'what to do first' list that prioritises the most important tasks.

The document also includes a note about the founder's communication style and typical handling of tasks, so whoever covers can maintain the same level of service. Information about pricing and policies is included so common questions can be answered.

The document is kept updated quarterly. Every three months it is reviewed to ensure all information remains current. The review takes about an hour, a small price for peace of mind.

The reciprocal arrangement

An arrangement was set up with two other freelancers in the same field. If one of the group is unavailable, the others cover. The agreement defines urgent as anything that would damage a client relationship if not responded to within 48 hours.

Although the arrangement has not yet been used in practice, knowing it exists provides significant reassurance. It also means that if the founder needs genuine time off — a holiday, for example — cover is available.

Looking back

The uncomfortable truth is that the missing protections were known but deprioritised because they protected against an event that had not yet happened. Two days of preparation would have removed most of the damage. Illness is not a business-planning failure in itself, but being unprepared for it is a decision made by default.

This is not about paranoia or pessimism; it is about realism. Illness and accidents happen. If a business cannot survive the founder being away for a few weeks, that fragility is worth fixing.

Contingency planning is not solely about illness. It covers any kind of absence — a holiday, a family emergency, a conference. Having systems in place makes it possible to take time away without worrying about the business falling apart.