A business plan for the day the internet drops

The website being up and the business being able to work are two different uptimes, and only one of them has a plan unless you wrote it beforehand.

Every owner can picture the wrong morning: the dashboard says the website is healthy, the servers show green, nothing anywhere reports a fault, and yet nobody in the company can do a single piece of work. The line into the shop is down, or the building's connection is, and with it goes the mail, the files, and the orders. This is the gap between two uptimes that sound like the same word: the website being up, and the business being able to work.

The first uptime belongs to hosting, and hosting companies sell it with contracts and percentages. The second belongs to the office: the router somebody rebooted last, the cable in the wall, the single connection the whole company shares. A company can run its own infrastructure flawlessly and still stop dead, because its perfect servers sit behind one door it does not control. The website survives the outage. The working day does not.

The honest plan is written before the outage, because nobody chooses well at that moment. It begins with an inventory that takes about an hour and answers most of the question. Which work dies without the line? Which work continues from the phones in everyone's pockets, on mobile data? Which decisions simply wait, and lose nothing by waiting? Companies that never wrote these three lists down discover them mid-outage, one discovery per lost hour.

Then the second path gets named in advance: the mobile hotspot kept charged, the second provider's line where the budget allows one, the agreement about where the team works from when the office has neither power nor signal. The specific choice matters less than the fact of having named one, because a plan that lives in improvisation is not a plan. It is a mood, and moods do not answer customers.

Then the paper on the wall: the handful of phone numbers that must survive the outage, printed where electricity is not needed to find them. The provider's support line, the landlord, the one colleague who holds the other key. And the customers' side deserves its own answer, because the outage is invisible to them: who picks up the phone when the office is dark, and what does the caller hear, a number that rang somewhere else, or a room ringing to no one?

The honest limit: this is a plan for an hour or a day. It carries the company across a dropped line and a dark office; it does not replace the infrastructure decisions about redundancy, backup connectivity, and where the systems should actually live. Those are larger questions with their own tradeoffs, and they belong with whoever runs the company's systems and the documentation of whatever providers are involved.

This is where we sit: we plan these contingencies with clients as part of what a website project actually implies, and we write the plan before the morning it is needed. The lists, the second path, the printed page: all of it is an hour of honesty now against a day of improvisation later. Guidance, not guarantees: no plan stops the line from dropping; a plan decides what your company does in the first hour after it does.