You cannot judge whether automation is worth doing without a number for what the process costs today. Here is how to get one honestly.
5 min read · 2 September 2026
Most automation projects start with a problem, which is correct, but they should also start with a number. Not a precise forecast straight away; an honest estimate of what the process costs now. Without that figure there is no way to judge whether the project is worth doing and no way to know later whether it worked. ROI is not the boring last slide of the business case. It is the reason the project exists.
Measuring the current process before building anything gives you three things. You find out whether automation is even worth it, because some processes are not. You get a baseline that proves the project worked once it goes live. And you build the business case from evidence instead of enthusiasm, which makes the approval meeting much shorter. Teams that skip this step can only say we think it saves time. Teams that do it can say what time, whose time, and how much of it, which is a different conversation entirely.