1. Measure one complete workflow
Choose a process with a clear beginning and end, such as receiving an inquiry through assigning it to the right person with a prepared response. Count the weekly number of completed items and measure hands-on time across everyone involved. Include corrections, checking, and handoffs.
Use a representative sample across ordinary and difficult cases. Record the observation period and sample size alongside the estimate. A quiet week or a set of unusually easy examples can make the baseline misleading.
2. Estimate net time saved after review
Compare current time with the proposed process, including review and exception handling. A generated summary that saves drafting time but requires longer checking may have little net value. Apply an adoption assumption: not every eligible task will use the new workflow immediately.
The 52 ÷ 12 factor converts an ordinary weekly rate into an average monthly rate. For seasonal operations, use month-specific volume instead. Keep negative results visible: an automation that takes more staff time is not a time-saving improvement.
3. Keep three benefit categories separate
| Benefit | What it means | Evidence to collect |
|---|---|---|
| Recovered capacity | Staff hours become available for other work. | Before/after completion time and actual adoption. |
| Realized cost savings | Spending actually decreases, for example on avoidable overtime. | A reduction in the relevant cost records without moving the work elsewhere. |
| Incremental contribution | Additional business produces margin after its variable costs. | Attributed conversions, contribution margin, and a credible comparison. |
Do not add the value of the same recovered hour to both labor savings and revenue contribution. Choose the actual use of the capacity and account for it once. If staff remain on the same payroll and the extra time has no measured use yet, report hours recovered rather than cash saved.
4. Include implementation and operation
Implementation cost includes discovery, setup, integration work, testing, staff training, and migration where needed. Recurring cost includes hosting, API usage, software subscriptions, support, and ongoing maintenance effort.
If staff review is included in the new minutes per item, do not add that same review time again as a recurring expense. Do include maintenance work outside the measured workflow.
Net monthly capacity value = capacity value − recurring costs
Capacity-value payback = implementation cost ÷ positive net monthly capacity value
That payback is an economic capacity estimate, not proof of a cash return. For realized first-year ROI, use evidenced annual benefits less annual recurring costs and implementation cost, divided by implementation cost. If implementation cost is zero, the percentage is undefined; report absolute net benefit instead.
5. Worked example
Assume 100 items per week, 12 minutes per item today, and 5 minutes after automation including review. If 80% of items use the new workflow, the estimate is 9.33 recovered hours per week, or 40.44 hours in an average month.
At a loaded labor cost of $30 per hour, that represents $1,213.33 in monthly capacity value. Subtract $250 in monthly recurring costs for a net capacity value of $963.33. A $3,000 implementation would have an estimated capacity-value payback of 3.11 months.
These figures are illustrative assumptions, not Lexion client results. They do not establish that payroll costs fall by $963.33 per month. Actual savings or revenue effects need separate evidence.
Your workflow worksheet
Example inputs are prefilled. Change them to your own assumptions. Calculations stay in this page and are not submitted.
Capacity value is not cash savings. Count savings only when actual spending falls; count revenue only when incremental contribution is evidenced. Negative hours mean the proposed process takes longer. This estimate excludes revenue effects and is not a forecast.
6. Check what could change the decision
Run a conservative case with lower adoption, longer review time, and higher usage costs. Then compare it with your expected case. If the decision only works under the most optimistic assumptions, narrow the pilot or collect more baseline evidence.
After the pilot, replace assumptions with observed data from a comparable period. Record volume, completion time, exception rate, adoption, recurring costs, and any realized financial effect. Keep customer experience and quality alongside speed: faster processing is not useful when it creates more downstream corrections.
A checklist for your pilot brief
- Name the workflow owner and the beginning and end of the process.
- Record baseline dates, sample size, weekly volume, and time per item.
- Define the approval point and escalation path for exceptions.
- Set a success threshold for speed, quality, and adoption.
- List implementation cost, recurring costs, and who owns maintenance.
- Choose a review date and decide what would justify expanding, revising, or stopping.
Use or reference this guide
You are welcome to link to this guide when discussing automation business cases. Cite it as “Lexion, Workflow Automation ROI: Guide & Worksheet” and include the page URL. Describe the numbers as an illustrative example, not an industry benchmark.
For help turning the analysis into a pilot, explore workflow automation or AI consulting for San Antonio businesses.