A failed drive, a deleted folder, a corrupted file share, a synced mistake that propagated everywhere. The work is gone – and now your whole team is redoing yesterday while today waits. Put in your numbers and see what one data loss event costs with, and without, backups that actually restore.
Estimates are fine. Everything updates as you type.
We add 30% on top for the real cost of employing someone (KiwiSaver, ACC, overhead).
Used to estimate income lost while your team is recovering instead of working. Leave at 0 to exclude it.
Without proper backups, you lose everything since the last copy that actually works – if there is one.
Recovery attempts, deciding what's gone, getting people working again – with no tested backup, this is guesswork.
one data loss event
restore from the latest snapshot, carry on
One data loss event, with and without backups that restore.
This model counts four costs of a data loss event: redoing lost work (lost hours × the share that must be recreated × 1.25, because reconstruction is slower than creation), disruption (75% of work stopped across the team while recovery is attempted), lost income (revenue pro-rated over standard working hours), and an indicative emergency recovery cost. The "with backups" column assumes monitored, tested backups: restoration within about two hours and no more than two hours of work lost per person. It deliberately excludes what can't be modelled: the work that is simply never recovered, the client deliverable that misses its deadline, and the fact that some businesses never reopen after catastrophic data loss. Backups only count if they're isolated from the systems they protect, monitored daily, and actually tested – a backup that has never been restored is a hope, not a plan. Figures are indicative; talk to us about what your data needs.
Almost every business believes it has backups. The ones that survive a data loss event are the ones that knew – because someone was watching the backups run every day, keeping copies isolated from the systems they protect, and restoring files regularly to prove the whole chain works.
That includes Microsoft 365. OneDrive and SharePoint sync your files – they don't protect you from deletion, corruption or ransomware, and Microsoft's own terms make your data your responsibility. That's why monitored backup, including Microsoft 365 backup, is built into every Tanglin agreement as standard – not offered as an extra a client can decline. The number above is what declining it actually means.
Data loss is one of the oldest and best-documented risks in business computing:
Sources: Datto/Kaseya State of the Channel and business continuity research; Microsoft 365 shared-responsibility documentation; industry backup and disaster-recovery surveys (2023–2026). Figures are international and shown for context; Tanglin's calculator above uses your own inputs in NZD.
We'll review what's being backed up, where it lives, and when it was last tested – and tell you plainly what would survive a bad morning. No obligation.
Request a Backup Review