The automation ROI calculation that ignores opportunity cost

A typical automation business case compares two numbers: what the manual process costs today, and what the automation costs to build. If the second number is smaller, the project gets approved. This comparison is standard, easy to defend in a meeting, and consistently misses the number that actually determines whether the project was worth doing.

The missing number is opportunity cost: what the team could have built instead with the same engineering time. Automating a process that saves twenty hours a month is a worse use of a month of build time than automating a different process that saves eighty, and a business case that only compares build cost to the one process's savings never surfaces that comparison.

The fix is a simple addition to the standard business case: before approving any automation project, list the two or three other candidate processes it's competing with for the same engineering time, and estimate their savings using the same method. The project that looks best in isolation sometimes looks mediocre once it's compared against the alternatives it's actually displacing.

This doesn't require a sophisticated prioritization framework. It requires refusing to evaluate a single automation proposal on its own merits without asking what else that time could have bought, which is a habit most automation planning skips entirely.