How do you calculate automation ROI? Estimate the benefit over a defined period, subtract all costs for that period, then divide the net benefit by those costs. For a small business, the difficult part is deciding what time savings are worth and including review, corrections, and maintenance.
The example below is a planning illustration in US dollars, not vendor pricing or a measured customer result. Guidance checked October 21, 2026.
What counts as a benefit?
Start with a measured baseline. Record how many times the task happens, how long it takes, what errors require rework, and who performs it. Repeat that measurement during the pilot, including the work needed to supervise the automation.
Freed time and cash savings are different. Saving an owner two hours may create time for estimates or customer work without reducing any bill. Value that capacity separately from an actual reduction in paid overtime or outside spending.
If you expect more sales, estimate the contribution after the costs of delivering the work rather than counting the entire sales value as profit. Avoid counting the same saved hour once as labor savings and again as extra job capacity. Business Queensland's sales planning guidance emphasizes costs, owner compensation, break-even, and return on investment; those distinctions matter when building an estimate.
Which costs should you include?
- One-time costs: setup, integration, data cleanup, training, and the team's implementation time.
- Recurring costs: subscriptions, usage, phone or messaging charges, and hosting where applicable.
- Operating effort: checking results, maintaining facts, investigating failures, and correcting records.
- Transition costs: running old and new processes together during a pilot and moving data if you stop.
Use the full quote. A low monthly platform price may exclude the integration or usage you need. Ask what happens when volume exceeds the allowance and who maintains the workflow when a connected system changes.
A worked time-saving example
Suppose a team completes 300 routine tasks a month. Each takes five minutes manually: 25 hours. The proposed workflow takes two minutes per task including review, plus three hours of monthly upkeep: 13 hours in total. The capacity released is 12 hours.
At an assumed value of $30 per hour, those hours are worth $360 a month in capacity. Subtract $150 in monthly software and usage costs for an estimated recurring net benefit of $210. Suppose setup costs $840.
Assumptions only: 300 tasks/month, 5 minutes manual, 2 minutes assisted including review, 3 hours upkeep. No observed savings are claimed.
What are payback and ROI in this example?
Simple payback: $840 setup divided by $210 recurring monthly net benefit equals four months, assuming the benefit starts immediately and remains stable. If recurring net benefit is zero or negative, this calculation does not produce a positive payback period.
Six-month planning ROI: benefits are 6 × $360 = $2,160. Costs are $840 setup + 6 × $150 = $1,740. Net benefit is $420. Dividing $420 by $1,740 gives about 24.1%.
That percentage values released capacity at the assumed hourly rate. It is not automatically cash returned to the bank. If the saved time does not reduce spending or support useful work, the benefit should be revised downward.
What if the assumptions are wrong?
Try a lower-volume case and a higher-review case. At 150 tasks a month with the same timings and three hours of upkeep, released time is only 4.5 hours. At $30 per hour that is $135 in capacity against $150 in recurring cost: a $15 monthly shortfall before recovering setup.
A decision that works only at your busiest possible volume is different from one that works through an ordinary month. Write down the conditions that would make you stop or redesign the workflow.
A worksheet for your own pilot
- Choose one task and a time period.
- Measure manual effort and errors.
- Measure assisted effort, review, and upkeep.
- Separate released capacity from cash savings.
- Add setup and recurring costs over the same period.
- Calculate net benefit, payback, and a lower-volume case.
Start with the first AI workflow guide if you need a pilot. For a specific inbox project, use the email assistant workflow. Bring measured effort and the full cost estimate to any discussion of an automation build.