What would one bad day cost your business?
Find out in two minutes.
Enter a few numbers about your team and your data. You get an estimate of how long you would be down, what it costs, and how different recovery setups compare. The starting figures are examples for a 40-person company. Change them to yours.
Your business
What stops when the systems stop.
Your data and backups
What has to come back, and how it comes back today.
Assumptions you can change
These drive the comparison. Each one is an estimate, not a promise.
How long you would be down
Where the money goes (your setup today)
An estimate from the numbers you entered. It leaves out lost customers, fines and damage to your reputation, which can be larger.
Email me these results
We will send your numbers and the assumptions behind them, so you can share them with your team. Tick the box if you would also like us to check them against your real environment.
By submitting this form, you agree to our Privacy Policy. This site is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.
How we work this out
What an hour of downtime costs
Lost revenue per hour is your yearly revenue, times the share that depends on your systems, divided by the hours you are open in a year. Idle payroll per hour is the number of people who can’t work, times their hourly pay plus payroll taxes and benefits, times the share of their work that stops.
How long you would be down
Three things add up: the time to notice the problem and get help, the time to rebuild or boot a server, and the time to copy your data back. Copy time is your data size divided by the speed you really get, which is lower than the speed on your internet bill. Running from backup skips the rebuild and the copy. The backup starts as a working copy of your server while the original is repaired.
Work you could lose
If you back up every 24 hours, anything since the last backup is gone. We scale those hours to the hours you are open, then count the share that someone has to do again.
What the total leaves out
Lost customers, contract penalties, regulatory fines, overtime to catch up, and damage to your reputation. For many companies these are larger than the figures shown.
Two terms worth knowing
- Recovery time objective (RTO): how long you can afford to be down. The timelines above show the time you would really be down with each setup.
- Recovery point objective (RPO): how much recent work you can afford to lose. It is set by how often you back up.
Questions people ask
How accurate is this?
It is an estimate from the figures you enter and the assumptions shown under “Assumptions you can change.” The most useful step is to replace our assumptions with measured ones. That is what a technology assessment does: we measure your data, test a restore and tell you your real recovery time.
What does “run from backup” mean?
Your backup can start as a virtual copy of your server, right where it is or in the cloud, so people can get back to work while the original is repaired. With the setup we manage, the server is usually at the login screen within 10 minutes, often closer to 3. Other systems and users still need to be checked once it is running.
How do I lower the number?
Back up more often, keep a copy close by as well as online, make sure someone is watching for failures outside business hours, and test a restore on a schedule so the first time is not the real thing.
What do you do with the details I enter?
We use them to email your results and, if you ask, to schedule a technology assessment call. We do not add you to a newsletter. See our privacy policy.
Where to go next
- Network & Business Continuity: how we keep you running when something breaks
- Backup and recovery planning guide
- Request a technology assessment
Results are estimates based on the figures you enter. They are not a quote or a guarantee.