Skip to content

Calculator

Exposure and ROI calculator

Hands-on tool · two minutes

Human risk exposure and ROI

Set your workforce and the incidents you saw last year. The calculator shows your exposure, the loss a human risk program avoids, the analyst hours it returns and a three-year view. Every assumption sits below the result, and you can change each one.

2,500 people
IndustryLabels the report; does not change the math

Incidents in the last 12 months that traced to a person

Pick the band you can defend. The result is a range from the low to the high end of each band.

Phishing clickA person clicked, opened or replied, and someone had to clean up.
Account takeoverAn attacker used a person’s credentials or session.
Business email compromiseA payment, payroll or invoice change requested by fraud.
Data mishandlingData sent, shared or stored where policy says it must not be.
Current program
6 h
Triage, investigation and cleanup by your own team.
$85
Salary, benefits and overhead for one analyst hour.
Not set
Your all-in budget: licences, people and content. Living Security pricing is never stated here.

Your estimate

$40k–$175k
Annual exposure
8–30 incidents × cost per incident
$12k–$88k
Expected avoided loss per year
30%–50% fewer incidentsat full effect
14 h–90 h
Analyst hours saved per year
worth $1,224–$7,650 at $85 per hour
1,075 → 525
People in risky cohorts
550 fewer43% of 2,500 today (assumption)

Three-year view

Year 1 at 50% effect, then full effect
$108k$27kYear 150% effect$108k$54kYear 2100% effect$108k$54kYear 3100% effect
  • Exposure without a program (midpoint)
  • Benefit: avoided loss plus analyst cost saved (midpoint; the mark shows low to high)

Three years: benefit $33k–$238k · set your program budget in the assumptions to see net and ROI

ROI = (three-year benefit − three-year program cost) ÷ three-year program cost. Benefit = avoided loss + analyst cost saved. The program cost is your own planning figure.

Share on LinkedIn

Every number you can change

Assumptions

Each default is a planning assumption with its basis. No market statistic is used. Change any value and the estimate updates.

  1. Fewer risky users after a human risk programassumption30%–50%

    Planning assumption. Source: Cyentia Institute, State of Human Risk report, as Living Security publishes it: organizations using the Living Security platform saw their share of risky users fall from 43% to 21% in a year. Your result will differ; it is applied to incident counts in proportion.

    30%
    50%
  2. Share of that reduction still open to a "training and simulations" programassumption100%

    Planning assumption: the 43% to 21% outcome describes programs that moved to a human risk platform from training and simulations. A behavior-based program already holds part of the effect, so the default is half; an existing platform, a quarter.

    100%
  3. Share of the workforce in risky cohortsassumption43% today, 21% after

    Planning assumption from the same published 43% to 21% customer outcome. Used only for the people count; it does not change the dollar figures.

    43%
    21%
  4. Cost of one phishing click incidentassumption$2,500

    Planning assumption for a response budget: cleanup, recovery and lost time, without your analysts' hours (counted separately). Replace it with your own figure; no breach-cost report is cited.

  5. Cost of one account takeover incidentassumption$15k

    Planning assumption for a response budget: cleanup, recovery and lost time, without your analysts' hours (counted separately). Replace it with your own figure; no breach-cost report is cited.

  6. Cost of one business email compromise incidentassumption$50k

    Planning assumption for a response budget: cleanup, recovery and lost time, without your analysts' hours (counted separately). Replace it with your own figure; no breach-cost report is cited.

  7. Cost of one data mishandling incidentassumption$10k

    Planning assumption for a response budget: cleanup, recovery and lost time, without your analysts' hours (counted separately). Replace it with your own figure; no breach-cost report is cited.

  8. Upper bound for "many (20+)"assumption40 incidents

    Planning assumption so an open band still gives a range. Set it to your real count.

  9. Analyst hours per incidentassumption6 h

    Planning assumption for triage, investigation and cleanup by your own team. Set it from your ticket data.

  10. Loaded analyst cost per hourassumption$85

    Planning assumption: salary, benefits and overhead for one analyst hour.

  11. Program cost per yearassumption$0

    Planning assumption for your all-in budget: licences, people and content. This is your number; Living Security pricing is never stated here.

  12. Year 1 rampassumption50%

    Planning assumption: a program reaches half its effect in the first year as sources connect and playbooks start, then the full effect in years 2 and 3.

    50%
  13. IndustryassumptionTechnology

    Labels the report and routes the follow-up. It does not change the math.

Work email

Get the board-ready PDF by email

Your inputs and this estimate are stored with your work email so the PDF can reach you. They are never published, and we do not sell your data.

No sales call unless you book one.

Next step

See the estimate on your own signals

A 30-minute session checks the estimate against your incident data and shows the platform on the demo environment.

Planning estimate from your inputs and the assumptions above. No market statistic is used, and no Living Security price appears. The reduction basis is a planning assumption from the Cyentia Institute's State of Human Risk report as Living Security publishes it (risky users fell from 43% to 21%); change it above to match your own program.

Book a demo