Automation ROI: A CFO's Field Notes
How to model and defend the return on an automation program, with the numbers that actually move a budget conversation.
June 10, 2026 · New Legacy AI
Every automation proposal eventually lands on a CFO’s desk, and the question is always the same: what is the return, and how confident are you in it? After dozens of programs, here is how we model it so the answer holds up.
Start with the manual baseline
Pick one workflow and measure it honestly: how many people touch it, how long each step takes, and how often it has to be redone. This baseline is the single most important number, and it is almost always worse than anyone expects.
Count three kinds of return
- Time returned. Hours that move from copy-paste work to higher-value work.
- Errors avoided. The cost of the rework, refunds, or escalations that automation prevents.
- Capacity unlocked. Volume you can now handle without adding headcount.
Be conservative on purpose
Model the return at 60% of the theoretical maximum. Programs that promise 100% efficiency lose credibility the first month they miss. A conservative number that you beat builds trust for the next initiative.
What good looks like
Most of the automation programs we run pay back in under two quarters, and the second project is easier to fund than the first because the first one delivered. The goal is not a single big win. It is a track record.
Want to model the return on a workflow you have in mind? Talk to our team and we’ll build the case with you.