ToolsDefensive & advisory
Incident cost estimator.
Put your own figures in and see what a bad week actually costs.
Runs in your browser. Nothing you enter is sent, stored or logged.
People and downtime
Staff who lose part or all of their working day.
Salary plus on-costs, divided into a day rate.
100 means fully stopped; 50 means limping.
Revenue and recovery
Leave empty if downtime does not touch revenue directly.
Incident response, forensics, legal, notification costs.
Penalties, hardware, make-goods.
Estimated cost of the incident
$7,800 for this scenario.
$7,800 in paid time lost
10 people, 3 days at 50% reduced output, at your $520 loaded day rate.
What the estimate leaves out
Attention pulled off every other priority for weeks, deals that quietly stall, insurance excess and premium movement, and the second incident if root cause never gets fixed.
Every number above comes from your inputs; nothing is drawn from industry averages. The defensible version of this exercise is a risk assessment against your actual systems and obligations.
What this does, and what it deliberately does not.
This estimator does arithmetic on figures you supply. It quotes no industry averages and invents no statistics; every number in the result traces to an input you set. Its job is to make the cost conversation concrete before an incident forces it.
Rather reduce the number than admire it?
Australia-wide, from our Brisbane head office. Someone will contact you as soon as possible.