← All Field Notes

Commercial case

How do you calculate ROI before automating a workflow?

A practical framework for estimating workflow automation ROI using volume, handling time, delay, rework, commercial leakage and ongoing cost.

The short answer

Calculate workflow automation ROI from an observed baseline: transaction volume, handling time, waiting time, rework, error cost and revenue leakage. Estimate the portion the proposed change can realistically remove, subtract implementation and operating costs, and state how recovered capacity will be used. Do not count every saved hour as cash.

Measure the current workflow

Start with a defined unit of work: one enquiry, quote, job, order, invoice, support request or reporting cycle. Measure how often it occurs and what happens from beginning to end. Separate active handling time from waiting time; automation may affect each differently.

Use system timestamps where possible, then test the numbers with the people doing the work. A clean average can hide the expensive exceptions, while a frustrating anecdote can make a rare issue look structural.

  • Volume per week or month
  • Hands-on minutes per item
  • Elapsed time between important stages
  • Error, rework and exception rate
  • Cost of delay, leakage or customer drop-off
  • People and software cost required to keep the process running

Translate the change into value

A practical annual value estimate can combine recovered capacity, avoided external cost, avoided rework and incremental gross profit. From that, subtract the recurring cost of software, models, monitoring and maintenance. Keep the assumptions visible and use a conservative, expected and upside case rather than one heroic number.

Recovered capacity is only valuable when the business knows what will happen to it. If four hours a week are released but nothing changes in staffing, throughput or customer response, the benefit is capacity—not a direct cash saving. Name the redeployment before counting the value.

Include risk and control costs

Automation can create new failure modes: incorrect decisions at scale, silent data drift, vendor dependency or exceptions that no longer reach a person. Include the cost of review, monitoring, fallback and change management in the business case. A workflow that appears slower on paper may be better if it keeps a consequential decision accountable and reversible.

Set the evidence gate before implementation

Agree the baseline, target and review date before building. Define the minimum improvement that makes the change worthwhile and the reversal trigger that would stop or roll it back. This turns ROI from a sales estimate into an operating measure the business can continue to own.

Working principle

The honest ROI case separates cash, capacity and revenue; includes ongoing control costs; and states exactly what evidence would prove the change worked.