It is Tuesday at 10 a.m. Your email suddenly stops. The invoicing system will not load. The phones do not ring, or they ring and go straight to nowhere. Nobody in the office can do the work they came in to do.
Most people think of this as annoying. It is much more than annoying. Every minute your systems are down, you are losing money in ways that do not show up on a single line of a report. That is the "hidden" part. Nobody hands you an invoice for downtime. You just quietly bleed.
What "downtime" actually means
Downtime is anything that stops your team from doing their job because a piece of technology is not working. The obvious version is a server crash or an internet outage. The less obvious version is your email getting slow, your file share becoming unreachable, or your point-of-sale terminal freezing during a Saturday lunch rush.
You do not have to lose everything to be losing money. If half your staff cannot open a document for an hour, that is downtime for those people.
The five costs, in plain terms
- Lost revenue. If customers cannot buy from you, or cannot reach you to try, that money walks. For a service business it usually means missed calls and skipped bookings. For an e-commerce business it is more direct: no site, no sales.
- Wages you are still paying. Your team shows up. You pay them for their day whether they can work or not. If ten people at an average $65,000 salary sit for one hour with nothing to do, that is about $325 out the door before you count anything else.
- The opportunity you missed. The prospect who almost signed and did not because your reply came two days late. The client meeting rescheduled to next month because the file could not be shared today. These are hard to measure and easy to underestimate.
- The cost of getting back up. Someone has to fix the problem. That is either an internal person pulled off other work, an outside vendor charging an emergency rate, or both. Rebuilding lost data, restoring from backup, and walking through what happened takes time and time is money.
- Trust you might not get back. Customers remember the day their thing did not work. If it happens more than once, they start to look elsewhere. This is the cost that keeps compounding after the technical problem is fixed.
Run the math for your own business
Rather than trust our example, do yours. Three inputs, one honest number. Nothing leaves your browser.
// Interactive: Downtime Cost Calculator
What one hour costs your business
Estimated cost per hour of downtime
for a team of 0
Want a written breakdown with the two or three moves most likely to move the needle? Run the full version and drop your details after results.
What the numbers usually look like
To give you a sense of the range before you run yours: a 20-person business with $65,000 average salary and $5 million in annual revenue lands at roughly $1,000 to $1,400 per hour on a typical downtime event. That is with recovery cost factored in but assuming most revenue is deferred rather than lost forever.
On a bad day, when the outage lands during a peak sales window and one client walks away over it, the same business can easily cross $5,000 in a single hour, and the departure cost is invisible for months.
The point is not the exact number. The point is that "we will just deal with it" is not free. It is one of the most expensive plans a business can have.
The cheapest downtime is the downtime that never happened.
Why "we will wing it" is a bad plan
When something breaks and there is no plan, three things happen in sequence.
First, panic. Nobody knows what to do first, so everyone tries five things at once and half of them make it worse.
Second, delay. The people who can fix it are not the people who first notice it, and the message takes an hour to travel from front-line staff to the person with the password.
Third, blame. When it is finally over, everyone has a different memory of what went wrong. Which means it will probably happen the same way next time.
A plan is not fancy. It is a one-page document that says: here is who to call, here is where the backups are, here is how we tell customers, here is who decides when to switch to the backup system. Businesses that write this down recover in a fraction of the time. Businesses that do not write it down keep paying the same hidden cost, over and over.
What actually reduces the risk
You cannot get to zero downtime. What you can do is make it rare, short, and boring.
- Real backups, tested. A backup you have never restored from is a hope, not a plan. Once a quarter is not too often to test.
- Monitoring that pages someone. The best time to hear about a problem is before your customers do. Good monitoring tools notice a server slowing down before it fully falls over.
- Redundancy where it counts. Two internet providers. A secondary payment terminal. A cloud-hosted version of the same tool. Redundancy is not paranoia, it is math.
- A written response plan. Names, phone numbers, decision points. Practice it once a year the way a school runs a fire drill.
- Regular patching. A lot of outages come from software that has not been updated in six months. The patch you postpone is the outage you schedule.
The takeaway
Downtime is not free just because nobody writes you an invoice. Every hour has a cost, and the cost is bigger than most business owners realize until they add it up. The cheapest way to handle it is to make it uncommon in the first place, and to have a plan for the day it happens anyway.
If you have never done the math for your own business, take twenty minutes and try. Take your annual revenue, divide by 2,000 working hours, and add the hourly wages of everyone whose job would stop. That is your floor. The ceiling is much higher.
Wondering what one hour would cost you?
We can run a quick review of where your business is most exposed to downtime, and what a realistic hourly cost looks like for your setup. No commitment, no sales call after.
Book a Free Strategy Session
