The downtime figures you have read, $300,000 an hour or $5,600 a minute, come from surveys of large enterprises and a decade-old benchmark. They do not describe a 15-person company. Your real cost is smaller, calculable, and worth knowing: loaded pay for idled staff, the revenue you lose rather than defer, the labor to recover, and the customers who do not come back.

Why does the $300,000-an-hour figure not fit a small business?

The most-quoted number in this category is ITIC's. Its 2024 Hourly Cost of Downtime Survey polled more than 1,000 firms worldwide between November 2023 and March 2024 and found that a single hour of downtime exceeds $300,000 for over 90% of mid-size and large enterprises. Read the respondent list and the reason it does not transfer becomes obvious. Forty-five percent of those firms had more than 1,000 users, and only 27% were small or mid-sized businesses of up to 200 users. The headline average is weighted toward organizations nothing like a small shop. Even ITIC's smallest tier lands near $1,670 per minute, roughly $100,000 an hour, which is still an order of magnitude above what a small business actually loses.

The other number, $5,600 a minute, traces to a single 2014 Gartner figure. It is cited constantly and it is more than ten years old. In the same year, an Avaya study put the range at $2,300 to $9,000 a minute depending on company size and industry. A four-fold spread across one sample is the tell: the single number was never meant to be applied to your business. A figure that varies by that much is not a benchmark, it is a headline.

How do you calculate your own cost of downtime?

The honest method has four parts, and none of them requires a survey.

Start with idle payroll, the floor. Multiply the people who cannot work by the hours they are down by their loaded hourly cost, meaning salary plus benefits and overhead, not just wage. A 30-person office down for two hours at $60 an hour of loaded cost is $3,600. That is the number before you have counted a single lost sale, and for many small firms it already exceeds a month of IT budget.

Then add revenue, but only the part you actually lose. This is where enterprise math misleads small businesses most. A law firm or a dental practice usually defers revenue during an outage rather than losing it: the appointment moves, the invoice goes out a day late. A retailer or a restaurant with a dead point-of-sale loses it outright, because the customer walks. Count deferred revenue near zero and lost revenue at full value. Treating the two the same is how a business that bills $400,000 a year ends up quoting itself an enterprise number.

Third, recovery labor. Someone rebuilds, restores from backup, and re-enters what was lost, and that time is real even though it lands after the systems are back. For most small businesses the recovery tail runs longer than the outage itself.

Fourth, the customers who do not come back. This is the hardest line to quantify and the most important to name. One failed transaction rarely costs one sale. It costs the relationship, and a business that runs on repeat customers feels that far more than the idle hour.

Add the four and you have a defensible number. For that 30-person office, a two-hour outage might be $3,600 in idle payroll, a few thousand in lost or deferred revenue, half a day of recovery labor, and one or two strained customer relationships. That is real money, and it is worth preventing. It is also nowhere near $300,000.

Who is your outage actually coming from?

There is a point the enterprise reports miss entirely. For a small business in 2026, the outage that takes you offline is often not your own hardware. It is a vendor. Your point-of-sale provider, your booking platform, your managed-IT tools, or your internet carrier goes down, and you are offline for reasons no on-premise server would explain. In July 2026, an outage at NinjaOne, a widely used managed-IT platform, was the subject of an active r/msp thread, the kind where one vendor failing takes a roomful of small businesses offline at the same moment. The lesson is not to avoid vendors. It is to know which of your vendors can stop your business, and to decide who calls whom, where the backups live, and how long a fallback can carry you before the bad day, not during it.

The number that changes the decision

Calculating your own figure is not about feeling smaller than the enterprise headline. It is about sizing the decision in front of you. Once you know an outage costs your business, say, $4,000 in idle payroll plus a day of deferred revenue, you can judge whether the backup, the redundancy, or the managed IT that prevents it earns its monthly cost. That is the same comparison behind the in-house versus outsourced decision: not what downtime costs a Fortune 500, but what one hour costs you, multiplied by how often it happens. Six outages a year at $4,000 each is $24,000, and now the prevention has a budget it can be measured against.