Did It Actually Pay Off
Claim automation savings, then audit your own number.
the deduction ledger shows exactly which silent cost — review time, error rework, or tool spend — eats the claimed win, the same three culprits nearly every inflated ROI number hides
What goes in, what comes out
The learner claims a savings figure for an automation — hours saved times rate — and the sim then forces an audit pass: error and rework rate, human-review time actually spent, and tooling cost all get subtracted live from the headline number. The claimed and measured figures sit side by side and rarely match.
enter a claimed savings figure and its inputs, then step through the audit deductions
side-by-side claimed vs. measured ROI, with a running deduction ledger explaining the gap
automation type, claimed hours saved, error-rate assumption, review-time-per-error, tooling/API cost
Business L3 'Proving the Automation Paid For Itself' lab; B2B manager-portal ROI widget
Concepts click when you open the machinery.
Three labs are already live and free — the same hands-on style this playground brings to its module.