What downtime actually costs a small business, and what changes.

The number most articles quote for downtime is wrong, but it is wrong in a useful direction. A four-hour outage during a small business's busiest order window of the week does not cost a million dollars. It costs the orders that did not happen in those four hours. The reason the number feels higher is that most articles address the enterprise case. The small-business case is less dramatic and more honest.

What a four-hour outage looks like, in dollars

Pick a shop that takes between fifty and two hundred online orders on its busiest day. The orders come in waves; one of those waves lands squarely between three and seven in the afternoon. A four-hour outage that overlaps that wave costs you the orders you would have taken — not all of them, because some customers retry from a phone, and some come back the next day. A reasonable midpoint for a small shop: twenty to forty missed orders, each worth somewhere between twenty and eighty dollars. The total is between four hundred dollars and three thousand dollars of revenue that did not happen, plus a small amount of trust you cannot invoice back.

What the cost moves by, when you find out faster

The number above assumes you find out about the outage from a customer. The customer's email arrives, you read it, you call your host or developer, the problem gets diagnosed, the fix starts. By the time you are debugging, the four-hour window is already half-over.

The same outage, found in two minutes instead of six hours, costs you about twenty minutes of revenue. Not because anything about the outage changed; the server still went down. The change is in the gap between "server stopped answering" and "a person who can fix it stopped doing what they were doing." Closing that gap is what you are paying for when you buy a monitoring tool.

The bought-time calculation

A monitoring tool that costs twelve dollars a month and shortens the average detection time from six hours to two minutes has to fire twice a year to break even. Most shops with any kind of online order flow fire it more often than that. The calculation is not a sales pitch — it is the literal sum of two numbers and one rate.

If you would rather see what a one-time outage really looks like for your shop without waiting for one to happen, run the free URL audit— it pings your home page, the cart, the checkout, and reports where the slow-points already live.

What monitoring does not do

It does not prevent the outage. It does not fix the host. It does not write the postmortem. It only tells you the truth about when the site stopped answering, and it tells you sooner than your customers would.

The honest pitch

SiteGuardian is one of many monitors that does this. What it does well is the boring part — it is cheap, it is small, it does not grow into a platform that needs its own dashboard. The full cost-of-downtime pricing tier is on the pricing page; the smallest paid tier is a one-time purchase for shops that want to own the watch once. The deeper comparison with Better Stack, the modern uptime-plus-incident management product, is laid out in SiteGuardian versus Better Stack.

Detection latency in the small two-minute range is what most ops literature ends up calling acceptable. For the modern take on incident timelines and on-call rotations that close the next stage of the response gap, see the comparison page referenced above.