Find where automation pays back first.

Enter six numbers for one workflow and the model returns a low, centre, and high annual value. The maturity scan is optional and separate: 3 questions in the quick pass and 10 in the full one, of which 7 carry weight. The scan cannot move the money, because the money comes only from the numbers you entered.

It is a projection from your assumptions, not a forecast. The centre case uses the automatable share you entered, the low case 0.7 times that share, and the high case 1.2 times it, capped at 95 percent. Those two multipliers set the entire width of the range and are printed beside it. Every annual figure uses 48 working weeks, values are floored and costs are rounded up, so each one sits at or below the exact arithmetic. When your run cost is larger than the value the share produces, the result is negative and the page prints it that way.

No. There is no industry average, no peer band, and no percentile anywhere on this page. An earlier version of this tool did carry an industry comparison; the numbers in it were invented, so the comparison and the data behind it were deleted in July 2026. Every figure you see is either something you typed or arithmetic over what you typed.

The scenario you built is saved with your address so we can follow up on it, and the worked breakdown then opens on this page: the derivation of each case, the same calculation across a spread of automatable shares, and one measurement per input. Nothing is emailed to you automatically, and there is no newsletter.

Usually not. Automation is normally wired on top of the current stack through native APIs or middleware, which is also what keeps the build cost you entered realistic.

Treat a workflow as operated software. Version the flow, name an owner, monitor failures, record the assumptions, and remeasure the baseline after any material change.

You do. The flows, credentials, and documentation sit in your accounts. We can operate them, or hand them to an internal owner.