Before we build anything for a client, we run the math. Not because we're trying to impress them with spreadsheets, but because the math tells us whether the project is worth doing at all. Some automations pay for themselves in six weeks. Others take two years. Knowing the difference before you start saves everyone money and frustration.
Here's the framework we use on every discovery call.
Step 1: Find the Actual Time Cost
Most business owners dramatically underestimate how much time a repetitive task actually takes. They'll say "it only takes 10 minutes" — but that's the focused-effort time, not the true cost. True cost includes:
- Time to do the task itself
- Time to context-switch back to what you were doing before
- Time spent on errors, corrections, and follow-ups
- Frequency: daily vs weekly vs monthly
A task that takes 10 minutes but happens 20 times a day and requires a context switch each time might cost 4+ hours of productive capacity. Log the actual time for one week before estimating.
Step 2: Calculate the Annual Cost
Once you have the real time cost, multiply it by the loaded hourly rate of whoever does the task. Loaded rate means salary + benefits + overhead — typically 1.3–1.5x the base salary for an employee, or your own billable rate if you're doing it yourself.
Example: A $60,000/year operations manager (loaded to ~$85,000, or ~$41/hr) spends 45 minutes per day on manual data entry between systems. That's 3.75 hours/week × $41 = $154/week × 50 working weeks = $7,700/year in labor cost for one task.
Most business owners don't think of it this way. They think of the salary as fixed — and it is. But every hour reclaimed from low-value work is an hour redirected to high-value work. That's the real return.
Step 3: Add the Error and Opportunity Cost
Manual processes have error rates. Data entry errors cause downstream problems: wrong invoices, missed follow-ups, bad reporting. Estimate the cost of those errors — both the time spent fixing them and any revenue lost.
Also consider opportunity cost: what could this person be doing if they weren't doing this? If a salesperson is spending 2 hours a day on admin instead of calling leads, that's a real revenue number, not just a time number.
Step 4: Compare Against Build Cost + Ongoing Cost
Automation has two costs: the build cost (one-time) and the ongoing cost (software subscriptions, maintenance). A typical mid-complexity automation project might cost $2,000–$4,000 to build and $50–$150/month to run.
The payback formula: Build cost ÷ monthly savings = months to break even. A $3,000 project saving $650/month pays back in under 5 months. After that, it's pure margin.
Using the example above: $7,700/year = $642/month saved. A $2,500 build cost breaks even in about 4 months. Every month after that, the business keeps $642 that used to go to a task that no longer needs doing.
Step 5: Factor in Scale
The most compelling automation ROI cases aren't about doing the same thing cheaper — they're about doing things at a scale that wasn't possible before. If your current process for following up on leads is manual and limits you to 30 contacts per week, automating it doesn't just save time. It removes the ceiling entirely. You can now follow up with 300 contacts per week with the same team.
That's not a 10x efficiency gain. It's a fundamentally different business.
When the Math Doesn't Work
Sometimes we run the numbers and tell a client not to build. If the task takes 20 minutes per week and the build cost is $3,000, the payback period is years. In that case, the better answer is often a simple checklist or a lighter-touch solution — not a custom automation.
The right automation is the one that pays for itself quickly and continues paying. Don't build for the sake of building. Build when the math is undeniable.