# Automation ROI: how to check it pays off before you build

> How to estimate whether an automation pays off before you build it: time, volume, error costs, running costs, payback period and a worked example.

Source: https://morfalabs.com/en/blog/automation-roi-before-you-build

_Automation · 4 min read · Published October 30, 2026_

Most automation projects get approved on a feeling: this task is annoying, so surely a machine should do it. Sometimes that's right. Sometimes the task takes ten minutes a month and the automation takes longer to build than it will ever save.

## Short answer

Multiply the time one task takes by how often it happens and by the hourly cost of the person doing it. Add what errors cost you. Subtract the monthly running cost of the automation, then divide the one-off setup cost by what's left. That is the payback period. If it's longer than you'd be willing to wait, don't build it yet.

## The calculation, in plain words

Start with the manual cost. Time per task, times tasks per month, times the cost of an hour of that person's time. Use the fully loaded cost (salary plus the extras an employer pays), not just the salary figure.

Then add the cost of mistakes: how many tasks need correcting, how long each correction takes, and whether any error reaches a customer or a supplier. Now you have a monthly figure for doing it by hand.

The automation isn't free to run, so subtract its monthly cost: hosting, software fees, usage charges and a little maintenance time. What remains is the net monthly saving. Setup cost divided by net monthly saving gives you the payback period in months.

## A worked example with made-up numbers

These numbers are an example, not a quote and not a benchmark. Say your team enters supplier invoices by hand. Replace each figure with your own and the method still holds.

Say 400 invoices arrive each month and each takes 6 minutes to enter. A person costs $15 an hour, fully loaded. After automation, 10% of invoices still need a person to review them.

**Invoice entry: an example calculation (all numbers hypothetical)**

1. **Time saved:** By hand: 400 x 6 min = 2,400 min = 40 hours. After: 40 invoices x 6 min = 240 min = 4 hours. Saved: 36 hours x $15 = $540 a month.
2. **Errors:** Fixing mistakes takes 4 hours a month by hand, 1 hour after. Saved: 3 hours x $15 = $45 a month.
3. **Running cost:** Hosting, usage fees and upkeep: $85 a month. Net saving: $540 + $45 - $85 = $500 a month.
4. **Payback:** Setup cost of $4,000 divided by $500 a month = 8 months. Over the first 12 months: $6,000 saved, $2,000 ahead.

## Which processes to automate first

Not the most annoying one. The best first candidate is boring, frequent and rule based. If the same task happens hundreds of times a month and follows steps a new hire could learn in a day, the calculation above usually works.

Tasks that need judgment on every case, or that change rules every few weeks, are poor first choices. They cost more to build and more to maintain.

**Where to look first**

- It happens hundreds of times a month → Strong candidate. Volume is what repays the setup.
- Steps are the same every time → Good fit. Rules are easy to build and test.
- Errors are expensive or embarrassing → Worth it even at lower volume, with a person checking.
- It happens a few times a month → Probably not worth building. Write down the steps instead.
- The rules change every few weeks → Wait until the process settles.

## Costs people forget

The usual mistake is counting what the automation saves and not what it needs. Some of these costs are small. Some are the difference between 8 months and 18.

Don't forget the savings side either: time spent chasing errors that no longer happen, and the days a task used to wait because the one person who did it was away.

**What gets counted and what gets missed**

Usually counted:

- Time per task
- Volume per month
- The build or setup fee

Often forgotten:

- Someone reviewing the exceptions
- Fixing it when a connected system changes
- Usage fees that grow with volume
- Testing, monitoring and alerts
- Training people on the new process

## When it doesn't pay

If payback comes out at three years, or the saving depends on volume you hope to reach someday, wait. Put the money elsewhere, or do a cheaper version: a template, a checklist or a simple spreadsheet formula.

Be careful with the hours-saved argument too. Saving 36 hours a month only counts as money if those hours are used on something useful or let you avoid a hire. Otherwise it's a nicer Monday, which is fine, but a different kind of return.

## Questions people also ask

### What is a good payback period for an automation?

It depends on your business and how long the process will stay the same. As a rough habit, many owners want to see payback well inside a year, and treat anything beyond two years as needing another reason. Choose your own threshold before you start the estimate.

### How do I estimate the time a task takes?

Time it. Watch someone do the task five or ten times, including the interruptions and fixes, instead of asking them to guess. People usually remember the typical case and forget the awkward ones.

### Can you estimate the ROI for us?

Yes. We usually do it in a short call and a look at a sample of the real work. If the numbers don't work out, we'll tell you not to build it.

## Related service

[Workflow Automation](https://morfalabs.com/en/services/workflow-automation.md): AI workflow automation for approvals, quotations, purchase orders and onboarding. We link your email, ERP and CRM so routine steps run on their own.

## Not sure it pays off? We'll run the numbers with you.

- Email: [info@morfalabs.com](mailto:info@morfalabs.com)
- Web: https://morfalabs.com

## More articles

- [AI and blockchain by 2030](https://morfalabs.com/en/blog/ai-and-blockchain-future.md)
- [AI in business by 2030](https://morfalabs.com/en/blog/future-of-ai-in-business.md)
- [Are AI agents worth it?](https://morfalabs.com/en/blog/are-ai-agents-worth-it.md)
- [Stop your support AI making things up](https://morfalabs.com/en/blog/stop-ai-chatbot-hallucinations.md)
- [Zapier, n8n or a custom build?](https://morfalabs.com/en/blog/zapier-n8n-or-custom-automation.md)
- [Invoice entry without templates](https://morfalabs.com/en/blog/automate-invoice-entry-without-templates.md)
- [Choosing a software agency](https://morfalabs.com/en/blog/choose-a-software-agency.md)
- [Getting recommended by ChatGPT](https://morfalabs.com/en/blog/get-recommended-by-chatgpt.md)
- [Do you need a blockchain?](https://morfalabs.com/en/blog/does-your-business-need-a-blockchain.md)
- [Is company data safe in ChatGPT?](https://morfalabs.com/en/blog/is-company-data-safe-in-chatgpt.md)
- [New ERP or better integrations?](https://morfalabs.com/en/blog/new-erp-or-better-integrations.md)
- [Excel or a live dashboard?](https://morfalabs.com/en/blog/excel-reports-vs-live-dashboard.md)
- [Is your data ready for AI?](https://morfalabs.com/en/blog/is-your-data-ready-for-ai.md)
- [Native, cross-platform or web?](https://morfalabs.com/en/blog/native-cross-platform-or-web-app.md)
- [Agency or in-house team?](https://morfalabs.com/en/blog/agency-or-in-house-team.md)
- [Writing a software brief](https://morfalabs.com/en/blog/write-a-software-brief.md)
- [SEO vs GEO, side by side](https://morfalabs.com/en/blog/seo-vs-geo.md)

## Pages

- [Insights](https://morfalabs.com/en/blog.md)

## Other languages

- [العربية](https://morfalabs.com/ar/blog/automation-roi-before-you-build.md)
- [Français](https://morfalabs.com/fr/blog/automation-roi-before-you-build.md)
- [Español](https://morfalabs.com/es/blog/automation-roi-before-you-build.md)
- [Deutsch](https://morfalabs.com/de/blog/automation-roi-before-you-build.md)