What an Hour Offline Really Costs Your Business
Most business owners can tell you their rent and their wages to the dollar. Far fewer can answer a question that matters just as much: what does an hour offline actually cost? Downtime is one of the most expensive things that can happen to a small business, and also one of the least understood. Here is why the bill is bigger than you think, and what to do about it.
Downtime is more than a dead server
When we picture downtime, we picture the dramatic version. The server fails, the internet drops, and the whole office grinds to a halt. That happens, but it is not where most of the cost lives.
The quieter version is just as damaging. The accounting system still runs, but takes two minutes to load every invoice. The Wi-Fi drops every fifteen minutes. Files open eventually, but slowly. Staff can technically work, just at a fraction of their normal pace. If a critical system is unavailable, or running so poorly that productive work is meaningfully slowed, your business is losing money to downtime, whether or not anyone calls it that.
Defining downtime broadly is the first step to seeing what it truly costs you.
The causes are broader than cyber
It is tempting to file downtime under cybersecurity and move on. Cyber incidents certainly cause outages, but they are one cause among several.
Hardware fails, and failure rates climb sharply once equipment moves past its warranty. Internet and telecom outages reach almost every business eventually. The 2023 Optus outage took mobile and fixed-line services offline for around twelve hours, affected more than 400,000 Australian businesses, and was estimated to cost the economy roughly two billion dollars. Cloud outages have become routine as more of our tools move to platforms like Microsoft 365 and Xero. In 2024, a single faulty CrowdStrike update crashed around 8.5 million Windows devices worldwide.
Then there is the cause SMEs are least likely to plan for: relying on one person. When a single staff member or contact manages every IT issue, a holiday, illness, or resignation can leave problems unresolved for days.
The costs you can count, and the ones you cannot
Direct costs are the easy ones to add up. Wages paid to staff who cannot work. Lost sales. Overtime to catch up. Emergency IT fees. They scale fast. In a forty-person office with a loaded staff cost of $45 an hour, three hours of downtime burns $5,400 in lost productivity before you count a single lost sale.
The indirect costs are harder to measure and often larger. Customer trust erodes when calls go unanswered and orders go unfulfilled. Reputation suffers when word gets around that a business is having IT problems, especially where reliability is part of what you sell. Add the missed deadlines, the frustrated staff, and the management time spent mopping up.
Across the country, the research firm Splunk estimates Australian organisations lose around $86 billion each year to unplanned downtime and cybersecurity incidents combined. To get a rough figure for your own business, divide annual revenue by about 2,000 working hours, add the wages of idle staff, then add recovery costs. Most owners are surprised by the result.
The most expensive outage is the one nobody measures
A single big outage gets remembered. The dangerous pattern is the slow accumulation of small events. Ten minutes lost to a frozen application. Twenty minutes waiting for the internet. An hour gone to a badly timed Windows update. None of it feels significant on the day, but across a year and across a whole team it adds up to a serious number.
This cost stays invisible for three reasons. Nobody is measuring it. It is spread across everyone in small amounts, so no single person feels the weight. And over enough months, owners and managers quietly normalise it, until the slow file shares and patchy network just feel like the way things are.
Resilience does not need to be expensive, it needs to be deliberate
The goal is not to eliminate failure. Something will always break somewhere. The goal is to reduce how often it happens, limit how long it lasts, and keep the business running while it is being fixed.
That means proactive monitoring so problems are caught early, routine patching so an unsupervised update does not take you down at the worst moment, and sensible redundancy so no single failure stops everything. It means tested backups and a real recovery plan, because an untested backup is not a backup, it is an assumption. And it means an IT partner with clear response time commitments, because the gap between a four-hour and a four-day response is often the gap between an inconvenience and a serious financial event.
A simple framework works for any SME. Identify the systems that would actually halt your business if they failed. Set realistic targets for how fast each one needs to recover and how much data you can afford to lose. Then invest in resilience in proportion to what downtime costs you. The aim is to spend less protecting the business than it would lose without the protection.
Downtime is not a technical problem. It is a business problem with a technical cause. The businesses that handle it well are not the ones with the biggest budgets. They are the ones that decided it was worth understanding and worth planning for.
If you are not sure what an hour offline costs your business, that is the first thing worth finding out. We can help you work it out and build a plan that fits.