AEVOMIND INSIGHTS — RESILIENCE
When your business software goes down: backups, uptime and the real cost

When the system a business runs on goes down, the cost is counted in people who cannot work. In an illustrative business with 20 staff, a 4-hour outage costs about 67.5 staff hours; a tested backup that restores in an hour cuts that to about 17. The government's 2025/2026 survey found 43% of UK businesses hit by a breach or attack, and only 25% with a formal incident response plan.
The short answer
When the system a business runs on goes down, the cost is counted in people who cannot work. A morning without the job system, the booking diary or the CRM stops most of the team, and the catching up afterwards adds more. The difference between a bad morning and a lost week is usually whether a recent backup exists, is kept somewhere safe, and has actually been restored before.
This article sets out the arithmetic of downtime, what uptime percentages really mean, how often UK businesses are hit by cyber attacks, and the questions to ask whoever runs your systems.
What uptime percentages really mean
Providers quote uptime as a percentage, which makes small differences look smaller than they are. A year has 8,760 hours. At 99%, a system can be down for 87.6 of them; at 99.9%, for about 8.8.

The arithmetic of a bad morning
Take an illustrative business with 20 staff, 15 of whom cannot do their main work without the system. A 4-hour outage stops 60 hours of work. Afterwards, each of the 15 spends half an hour re-entering what was done on paper: another 7.5 hours.
Illustrative inputs, not client data: 15 people × 4 hours = 60 hours stopped, plus 30 minutes each re-entering work done on paper; with a 1-hour restore, 15 hours stopped and 8 minutes each to catch up. Totals: 67.5 staff hours versus 17.0.
Show the data
| 4-hour outage | 1-hour restore from a tested backup | |
|---|---|---|
| Work stopped | 60.0 hrs | 15.0 hrs |
| Catching up afterwards | 7.5 hrs | 2.0 hrs |
That is 67.5 staff hours from one morning — about 0.42 of a full-time month at 162.5 hours. With a tested backup that restores in an hour, it is about 17. The arithmetic says the restore time matters more than the uptime figure on the contract, and lost sales, missed appointments and late deliveries come on top.

How often it happens
Outages come from many causes — a failed update, a provider’s fault, a deleted record — but cyber attacks are the ones that make the news. The government’s Cyber security breaches survey 2025/2026 found 43% of UK businesses identifying a breach or attack in the previous year, with phishing by far the most common, experienced by 38% of businesses.
Phishing works by getting someone to hand over a password. In our view, a second sign-in factor, with single sign-on so staff have fewer passwords to give away, is one of the most useful protections a small business can add — see sign-in and access control.

Backups that actually work
Most businesses back up. Far fewer have a plan for the day they need to use the backup.
- Back up automatically, at least daily for anything you could not re-type from memory.
- Keep a copy separate from the live system, so the same fault or attack cannot reach both.
- Test a restore on a schedule, and time it. That time is your real downtime.
- Write down who does what when the system is down: who calls whom, what happens on paper, how work is re-entered.
- Keep an audit trail so you can see what changed and when — see audit trails.
As more of the day runs through software — including AI, which the Office for National Statistics found 34.9% of businesses with ten or more employees using in June 2026 — an outage stops more of the business, and these steps matter more.

What to ask whoever runs your systems
- Where is our data held, and how often is it backed up?
- Is a copy kept separately from the live system?
- How long does a full restore take, and how much recent work could we lose?
- When was a restore last tested?
- What uptime do you commit to, and does planned maintenance count?
- How do we get all our data out if we leave?
Good answers to all six are what hosting, DevOps and support should mean. If your data is spread across several tools, each needs its own answers — one more reason to bring records together through a shared data layer, as we discuss in why businesses end up running a dozen disconnected tools.
Frequently asked questions
What does an hour of business software downtime cost?
Count it in staff hours first. In an illustrative business with 20 staff, where 15 cannot do their main work without the system, a 4-hour outage stops 60 hours of work and adds about 7.5 hours of catching up, 67.5 staff hours in all. A 1-hour restore from a tested backup brings that to about 17. Lost sales and missed deadlines come on top.
What does 99.9% uptime actually mean?
It means the system can be unavailable for 0.1% of the time: about 8.8 hours in a year of 8,760 hours, or roughly 44 minutes a month. 99% allows about 87.6 hours a year, and 99.99% under an hour. Ask whether planned maintenance counts, and what happens if the provider misses the figure.
How many UK businesses suffer a cyber attack?
The government's Cyber security breaches survey 2025/2026 found that 43% of UK businesses identified a cyber security breach or attack in the previous 12 months: 42% of micro businesses, 46% of small, 65% of medium and 69% of large businesses. Phishing was by far the most common type, experienced by 38% of businesses.
Do most UK businesses back up their data?
Most do. The Cyber security breaches survey 2025/2026 found 74% of businesses backing up data securely via a cloud service and 48% by other means. Far fewer, 25%, had a formal incident response plan. A backup that has never been restored is a hope rather than a plan, so test a restore regularly.
What should we ask our software provider about backups and downtime?
Ask where your data is held, how often it is backed up, and whether a copy is kept separately from the live system. Ask how long a full restore takes and how much recent work could be lost, when a restore was last tested, what uptime they commit to and whether planned maintenance counts, and how you get your data out if you leave.