A workflow that saves 20 minutes but needs 15 minutes of checking hasn't created much leverage

A lot of automation ROI discussions stop at "time saved."

I think there's another cost small teams should measure: **verification work**.

If an automation saves 20 minutes but a manager still spends 15 minutes checking whether the CRM was updated, the message went out, the record was created once, or the right person owns the next step, the workflow has not created much leverage.

For recurring operational workflows, the before/after baseline I find useful is:

• manual touches per item
• repeated status checks / follow-ups
• exception and duplicate rate
• missed-step / rework cost
• cycle time
• manager verification time

Then I add an acceptance test for the **outside result**, not just "the workflow ran":

• exactly one correct result happened
• unresolved exceptions remain visible
• a human owner / next action exists when automation cannot decide
• the result can be verified without opening three other tools

A simple model is:

**labor avoided + failure/rework cost avoided + capacity gained - automation/maintenance/review cost**

For small teams, the biggest benefit is often not "this task now takes 30 seconds instead of 5 minutes."

It's that nobody has to keep asking:

"Did this actually happen?" "Who owns it now?" "What happens next?"

What do you measure after shipping an automation besides time saved?