How to Actually Calculate ROI on Business Automation

Not all repetitive work is worth automating. A script that saves an employee 10 minutes a week but takes 30 engineering hours to build and maintain is a net-negative project. Yet teams launch automation initiatives every quarter without running a basic back-of-the-envelope calculation.

A business automation project should only be funded if it satisfies one of three clear payback criteria: direct labor recapture, error risk reduction, or throughput latency removal.

The direct labor formula

Calculate the fully loaded hourly cost of the employee doing the task (salary, benefits, taxes, tools — roughly 1.25x base pay). Multiply by the hours spent per week, multiplied by 50 weeks.

If the build cost exceeds 50% of the annual recovered cost, you are likely over-engineering a problem better solved by a simple checklist or a standard spreadsheet template.

If an automated workflow fails once a month and takes two hours of developer time to unjam, it has consumed the time savings it was built to produce.

The three tiers of automation value

Tier 1: Labor Savings

Directly recaptures hours from high-wage staff

Tier 2: Error Mitigation

Prevents high-cost data entry mistakes and misbilled invoices

Tier 3: Speed to Lead

Decreases response latency from hours to seconds to lift revenue

Red flags that kill automation ROI

• Automating a process whose underlying business rules change every 2 months.
• Automating data entry between two legacy platforms with no webhooks or REST APIs.
• Building custom code for a flow that could be handled by a Zapier or Make recipe for $20/month.