It is half a workday. A long lunch plus a couple meetings. It can disappear on its own, honestly.
But when a business loses four hours because something breaks, the math gets weird fast. Not just revenue. Not just payroll. It starts leaking into customer trust, deadlines, and the kind of quiet stress that makes people update their resumes.
So this is a simple guide. No doom. No jargon. And when I do use a technical term, I will tie it to something normal.
The goal is one thing: help you estimate what a four hour disruption actually costs you, and what to do next.
First, what does “4 hours” even mean?
A four hour incident is usually one of these:
- Your website or checkout is down (you are open, but customers cannot buy).
- Your internal tools are down (customers can buy, but your team cannot operate).
- A key vendor is down (shipping, payments, email, ads, phones, scheduling).
- Data is locked or corrupted (you have access, but you cannot trust anything).
Those are different flavors of pain. Same clock. Totally different bill.
So before you calculate anything, write one sentence:
“For four hours, we could not ____.”
That blank is the whole game.
The 6 things you can lose in 4 hours (and how to estimate each)
1) Sales you would have made anyway
This is the obvious one.
Quick estimate:
- Average revenue per hour x 4
- Then multiply by the percentage that truly stops when you are down
Example:
- You average $2,500 per hour.
- If checkout is down, maybe 90% of that stops.
- Loss = $2,500 x 4 x 0.9 = $9,000
If your phones are down but the website works, maybe only 20% stops. Same revenue, different impact.
A small note. If you run ads, the loss is often bigger because the traffic still arrives, it just bounces. You paid to bring people to a locked door.
2) Payroll burn (you are paying people to wait)
Even when sales do not stop, labor can become… useless. Or worse, people scramble and create mistakes.
Quick estimate:
- Number of affected employees x loaded hourly cost x 4 x productivity lost %
Loaded hourly cost is just “hourly pay plus the extra stuff.” Benefits, taxes, overhead. If you want a simple analogy, think of it like the restaurant bill after taxes and tip. The menu price is not the total.
Example:
- 20 people affected
- $35 loaded hourly cost
- 50% of their work blocked
- Cost = 20 x 35 x 4 x 0.5 = $1,400
This part is easy to underestimate because people still look busy. They message. They refresh. They create workarounds. That is still not the actual work you hired them for.
3) Recovery time (the hidden “5th and 6th hour”)
A four hour outage rarely costs only four hours.
After things come back, there is catch up:
- Reprocessing orders
- Calling customers back
- Fixing duplicate entries
- Rebuilding reports
- Writing incident notes
- Cleaning up angry inboxes
Quick estimate:
- Add 25% to 100% of the outage time as recovery work
If you have never tracked this, start with 50%.
So a 4 hour disruption becomes 6 hours of impact across the company, even if the system is technically “up.”
4) Customer trust (the compounding cost)
This is the squishy one, and it matters a lot.
Trust loss shows up as:
- Refund requests
- Chargebacks (forced refunds through the bank)
- Support tickets
- Cancellations
- Fewer repeat purchases
- Lower conversion rate next week because people remember
A simple way to estimate is to focus on churn or lost repeats.
Quick estimate:
- Number of customers affected x % who do not come back x average customer value
If you do not track customer lifetime value, use a simpler stand in:
- Average order value x average repeat purchases per year
Example:
- 300 customers hit an error during the outage
- 5% never return
- Average value per customer over time is $400
- Loss = 300 x 0.05 x 400 = $6,000
This is why “it was only four hours” can still sting for months.
5) SLA penalties and contractual fallout (B2B especially)
If you sell to other businesses, you might have an SLA.
SLA (Service Level Agreement) is just a promise on paper, like a delivery guarantee. “We will be available 99.9% of the time” type stuff. If you miss it, there can be credits, refunds, or escalations.
Quick estimate:
- Check the contract for penalty terms
- Add the labor cost of account management and escalations
Sometimes the penalty is small but the relationship damage is huge. The customer starts shopping, quietly.
6) Risk and compliance exposure (when the incident is not just downtime)
If the four hours involves security, data loss, or payments, your cost categories expand.
Two terms you might hear:
- RTO (Recovery Time Objective): how fast you need to be back up.
- Analogy: how long it is acceptable for the restaurant kitchen to be closed before people leave.
- RPO (Recovery Point Objective): how much data you can afford to lose.
- Analogy: if your notebook gets ruined, how many pages can be missing before you cannot run the class.
If your RPO is 15 minutes but you lose 6 hours of data, you will pay for it in reconciliation, customer support, and sometimes legal concerns.
This is where you stop guessing and involve whoever owns risk in your company.
A simple worksheet: the “4 hour impact score”
You can do this in 10 minutes.
Fill in rough numbers. Do not chase perfection.
- Revenue loss: $____
- Ad spend wasted (if applicable): $____
- Payroll productivity loss: $____
- Recovery labor (catch up work): $____
- Customer credits/refunds/chargebacks: $____
- Expected churn / lost repeats: $____
- Contract penalties / SLA credits: $____
- Other hard costs (consultants, overtime, shipping fixes): $____
Total estimated cost of 4 hours: $____
Then add one more line that is not money:
What did we delay by 4 hours that matters next week?
A launch. Payroll run. A shipment cutoff. A sales demo. A compliance deadline. Those “calendar” losses hurt.
The three common scenarios (and what 4 hours usually costs)
Not exact numbers. Just patterns.
Scenario A: Ecommerce checkout outage
What happens:
- Revenue drops hard immediately
- Paid traffic gets wasted
- Support tickets spike
- Some customers do not return
What to watch:
- Hourly conversion rate and average order value
- Refunds and chargebacks over the next few days
- Email capture, because at least you can recover some sales later
Scenario B: Internal operations outage (inventory, POS, ERP, CRM)
ERP and CRM sound technical, but they are just:
- CRM: your customer address book plus notes. Like a digital Rolodex with memory.
- ERP: your operations brain. Inventory, purchasing, finance. Like the clipboard that runs the warehouse.
What happens:
- Revenue might continue, but fulfillment slows
- Errors rise because people use spreadsheets and memory
- Recovery time can be longer than the outage
What to watch:
- Backlog created (orders not shipped, tickets not answered)
- Error rate after recovery
- Overtime required later
Scenario C: Payment processor or vendor outage
What happens:
- You are “up” but cannot accept money
- Staff waste time troubleshooting things they do not control
- Customers blame you anyway
What to watch:
- Vendor status and incident history
- Your fallback option (backup payment method, offline invoicing)
Ok, now what? A practical way to reduce the damage
You do not need a massive resilience program to get real wins.
Here are the moves that usually give the biggest return.
1) Decide your “must not break” list
Pick 3 to 5 functions that, if down, create immediate serious loss.
Examples:
- Checkout
- Payments
- Order fulfillment
- Customer support inbox
- Inventory accuracy
Everything else is “annoying but survivable.” This stops you from over investing in the wrong areas.
2) Create one fallback for each must not break item
Fallback does not mean perfect. It means usable.
Examples:
- Checkout down: capture orders via a simple form, or take phone orders, or push customers to a backup product page
- Payment processor down: secondary processor, invoicing, or “pay by link”
- Support tool down: temporary shared inbox
If you have never tested your fallback, it is not real.
3) Set a realistic RTO and RPO for each critical system
You can keep it simple:
For each system, answer:
- How long can we be down before it becomes a serious business problem?
- How much data loss would create a mess we cannot clean up quickly?
That is your target. Then align backups, vendors, and internal response to it.
4) Write a one page incident plan
One page. Seriously.
Include:
- Who is in charge during an incident
- How to communicate internally
- How to update customers (status page, email template, social post)
- When to escalate to vendors
- What data to capture for the postmortem
A postmortem is just the debrief after a fire drill. What happened, what helped, what failed, what you change next time.
5) Track impact after the incident (not just uptime)
Most companies track “minutes down.” They should track:
- Tickets created
- Refunds
- Churn next month
- Overtime
- Backlog
That is how you prove the ROI of fixing the real bottleneck.
The point of this guide
Four hours can cost $500 or $500,000. Same duration, different business.
The best thing you can do is stop treating downtime like an IT problem and start treating it like an operations and revenue problem. Which it is.
If you want the simplest next step, do the worksheet once. With rough numbers. Then pick one critical system and add one fallback.
That alone tends to cut the next four hour loss into something smaller. And honestly, more survivable.
FAQs (Frequently Asked Questions)
What does a ‘four hour incident’ typically mean for a business?
A four hour incident usually refers to situations like your website or checkout being down, internal tools not working, a key vendor failing (such as shipping or payments), or data being locked or corrupted. Each scenario impacts your business differently but shares the same downtime duration.
How can I estimate the sales loss during a four hour outage?
To estimate sales loss, multiply your average revenue per hour by four, then adjust by the percentage of sales truly stopped during the outage. For example, if checkout is down and you average $2,500 per hour with 90% sales stoppage, the loss would be $2,500 x 4 x 0.9 = $9,000.
What is ‘payroll burn’ and how does it affect costs during downtime?
Payroll burn refers to paying employees who are unable to perform their actual work due to system downtime. To estimate this cost, multiply the number of affected employees by their loaded hourly cost (including benefits and taxes), by four hours, and then by the percentage of productivity lost. This often gets underestimated because employees may appear busy but aren’t completing their core tasks.
Why should I consider recovery time beyond the initial four hour disruption?
Recovery time includes additional hours spent after systems are restored to catch up on delayed tasks like reprocessing orders and fixing errors. This hidden impact can add 25% to 100% more time beyond the outage itself. Starting with an estimate of 50% extra time helps capture this ongoing cost.
How does a four hour outage impact customer trust and what are its consequences?
Outages can lead to refund requests, chargebacks, increased support tickets, cancellations, fewer repeat purchases, and lower future conversion rates. Estimating this impact involves calculating the number of customers affected multiplied by the percentage who won’t return and their average customer value. Even short disruptions can cause lasting damage to customer relationships.
What additional risks should businesses consider during a four hour incident involving security or data loss?
Incidents involving security breaches or data loss introduce risks related to Recovery Time Objective (RTO) — how quickly you must restore service — and Recovery Point Objective (RPO) — how much data loss is acceptable. Exceeding these objectives can result in costly reconciliation efforts, customer support challenges, and legal issues. In such cases, it’s crucial to involve risk management professionals immediately.
