Compare manual and automated playbook execution, allowing for failures that fall back to manual, and find the break-even run count.
The failure path is what most automation business cases omit: a run that fails costs the automated attempt and then the full manual execution, so a playbook at 60% success saves far less than a naive comparison of six minutes against forty-five suggests. Break-even then tests whether the volume justifies the build. Playbooks are software with a maintenance cost, and automating a rare, fiddly workflow is a common way to spend forty engineering hours to save two — the break-even count is what stops that decision.
Playbook Efficiency
Effective minutes = success rate × (automated time + review) + (1 − success rate) × (automated time + manual time), because a failed run costs the automation attempt and the manual work.
Break-even point
Break-even runs = build hours × 60 ÷ minutes saved per run.
Effective minutes = success rate × (automated time + review) + (1 − success rate) × (automated time + manual time), because a failed run costs the automation attempt and the manual work. The failure path is what most automation business cases omit: a run that fails costs the automated attempt and then the full manual execution, so a playbook at 60% success saves far less than a naive comparison of six minutes against forty-five suggests. Break-even then tests whether the volume justifies the build.
Playbooks are software with a maintenance cost, and automating a rare, fiddly workflow is a common way to spend forty engineering hours to save two — the break-even count is what stops that decision.
This calculator takes 8 inputs: Manual execution time, Automated execution time, Playbook success rate, Human review time on a successful run, Runs per month, Hours to build and test the playbook, Maintenance hours per month, Fully loaded analyst cost per hour. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Above roughly 80% for anything where failure falls back to full manual execution. Below that, the failure path eats the gain and analysts start distrusting the playbook, which is worse than not having it — they redo the work anyway.
Always. Playbooks break when an API version changes, a field is renamed or a credential rotates. Two to four hours a month per non-trivial playbook is realistic, and a portfolio of fifty playbooks is a full-time engineering job.