Ask most store owners how much an hour of downtime costs them, and you'll get a shrug, or a guess that's off by a wide margin. Not because they don't care, but because nobody's actually shown them how to calculate it. Here's the framework.
The simple formula
Start with your average revenue per hour during the time your site was actually down, not your daily average, since traffic and buying intent aren't flat across the day.
Revenue per hour × hours down × peak multiplier = real cost of the outage
The "peak multiplier" matters more than people think. An hour of downtime at 3am costs close to nothing. An hour of downtime during a promo, a payday weekend, or the two hours after an ad campaign goes live can be worth three to five times your average hourly rate, because that's precisely when buying intent is highest and least likely to wait around for your site to come back.
A worked example
Illustrative numbers, not a specific client, use your own figures in the formula above.
| Input | Value |
|---|---|
| Monthly revenue | ₦15,000,000 |
| Average revenue per hour | ₦20,800 |
| Outage during a promo (2 hours) | ₦41,600 base |
| Peak multiplier (promo traffic, 3x) | × 3 |
| Real cost of that outage | ≈ ₦124,800 |
That's one two-hour outage, during a single promo. Most stores don't have just one outage a year, they have a slow site every week that quietly costs a fraction of this in abandoned carts nobody logs anywhere.
Why most owners underestimate it by 3-5x
- Lost sales don't come back later. A customer who hits a down cart page during checkout doesn't wait and retry, they buy from whoever's site loaded, or they don't buy at all. Treating downtime as "delayed" revenue instead of "lost" revenue is the single biggest undercount.
- Wasted ad spend during the outage window. If you're running Meta or Google ads and the site goes down, you're still paying for every click that lands on a broken page.
- Trust erosion compounds. A customer who hits your site down once is measurably less likely to come back and try again, even after it's fixed. That's a cost with no line item, but it's real.
- Staff time firefighting isn't free. Someone's hours spent messaging a host's ticket queue, refreshing the dashboard, and fielding "is the site down for you too?" messages are hours not spent running the business.
Quick self-check
Do you actually know how many hours of downtime or severe slowness your store had last month? Most owners don't, because nobody's monitoring for it until a customer complains. If the honest answer is "I'm not sure," that's usually the real finding, not the exact naira figure.
The pattern matters more than the incident
A single dramatic outage is easy to notice and easy to get upset about. The bigger cost, for most stores we've looked at, is the slow creep: a site that takes 5-6 seconds to load on mobile isn't "down," but it's quietly losing a percentage of visitors before the page even finishes rendering, every single day, all year. That number is almost always larger than the one dramatic outage people remember.
If you want a real number instead of a formula, see what dedicated infrastructure changes, or read our comparison of shared hosting vs. managed hosting if you're not sure whether your current host is the actual bottleneck.