Calculating ROI on Automation for Small Businesses

Most published automation ROI figures are averages from vendor surveys, or the vendor's own claims. They do not tell you whether a particular tool will pay for itself in your business. The honest way to find out is a short calculation with your own numbers: how often the task happens, how long it takes now, how long it would take with the tool, what an hour of that time is worth, and what the tool costs, including setup. This page walks through that calculation, the costs people leave out, and three worked examples with different outcomes.

If you want the arithmetic done for you, the free ROI calculator uses the same formula for invoicing and runs in your browser, with no built-in savings rates. For what manual invoicing costs task by task, see the cost of manual invoice processing model.

What formula should a small business use for automation ROI?

Use the same one for every candidate, so the results can be compared:

• Hours saved per month = tasks per month × (minutes today − minutes with the tool) ÷ 60
• Value saved per year = hours saved per month × cost of an hour × 12
• First-year cost = subscription per month × 12 + one-time setup cost + ongoing upkeep for the year
• Net first-year gain = value saved per year − first-year cost
• ROI = net first-year gain ÷ first-year cost × 100
• Payback = setup cost ÷ (value saved per month − monthly running cost)

ROI as a percentage can look dramatic when the subscription is small, so read it alongside two other numbers: the net gain in money, and the break-even price, the monthly cost at which the tool exactly pays for the time it saves. A tool that saves $320 of time a month breaks even at $320 a month; one priced at $20 has a lot of room for your estimate to be wrong.

Which costs do small businesses leave out?

The subscription is usually the smallest part of the first year. Add these before you calculate:

• Setup time. Learning the tool, entering clients or products, connecting accounts, and redoing a few tasks while you learn. Price it as hours × hourly cost.
• One-off fees. A contractor to build a workflow, an implementation package, or data migration.
• Upkeep. Off-the-shelf software is maintained by the vendor. A workflow you built yourself (between a form, a spreadsheet and an email tool, for example) breaks when one of those tools changes, and someone has to notice and fix it. Estimate the hours per month honestly.
• Per-user or volume pricing. Price the plan you would actually need at your volume and headcount, not the entry price.
• Transaction fees. If the automation changes how clients pay you (an online payment link instead of a bank transfer, say), processing fees can be larger than the time saved on big invoices. The cost of manual invoice processing model shows this with published Stripe and PayPal prices.
• Partial adoption. If only half of the tasks go through the new tool, because some clients insist on their own portals or staff keep old habits, only half the benefit arrives.

Worked example: three automations at one small business

Hypothetical example. Every input is an assumption, labelled so you can replace it. A five-person landscape design firm is considering three automations. Staff time is priced at $33 an hour, the loaded staff cost used in our manual invoicing cost model, derived from Bureau of Labor Statistics wage data plus benefits, which made up 30.0% of private-industry employer compensation costs in June 2026 (BLS Employer Costs for Employee Compensation, accessed October 2026). The owner's time is priced at $60 an hour, because the owner has client work to fill any hour saved.

What the table shows:

• A pays back fastest, because the task is frequent and each instance takes a lot of manual time. The subscription barely matters: at $33 an hour, a $20 plan breaks even if it saves less than one minute per invoice (20 ÷ 33 × 60 ÷ 45 = 0.8 minutes).
• B is worth doing, but only because the owner's freed hours turn into billable work. If those hours would not be billed, price them at the staff rate or treat the saving as free time, not money.
• C loses money in year one and takes over six years to pay back, because the task is small and the build and upkeep are not. It would only make sense if enquiry volume grew several times over, or if a missed enquiry cost real lost work, which the firm would have to show from its own records.

How sensitive is the answer to your assumptions?

Very, and mostly to the "after" minutes and to adoption, not to the price. Changing one input for automation A at a time:

Even the cautious cases are positive here because the base task is slow and frequent. The same sensitivity check on automation C makes no difference to the conclusion: it loses money in every reasonable case. Running the numbers this way tells you which assumption to test first. Time ten invoices in the tool's free plan before you trust the 7 minutes.

Should you count faster payment and fewer errors?

Only as a separate line, and only from your own records. The ROI calculator leaves them out deliberately because they vary too much between businesses to assume. If you do want to estimate them, do it like this:

• Faster payment. Look at the average number of days your invoices took to be paid last year. If, after a few months on a tool with reminders and online payment, it falls, the money that is no longer tied up in unpaid invoices is a one-time cash release, plus interest you no longer pay on borrowing. Worked example: the firm bills $27,000 a month ($887.67 a day over a year). If its average payment time falls by 8 days, about $7,101 less is tied up in receivables. At 9% a year on its credit line (an assumed rate), that is worth about $639 a year in interest. Note that it is the measured change in days that matters, not a vendor's average.
• Fewer errors. Count last quarter's corrected invoices, credit notes and rejections, multiply by the time each took to fix, and compare with the same count after the change.

Keep these lines out of the headline ROI until you have measured them. A case that only works if payment speeds up is a case built on a guess.

How do you decide which automation to do first?

Rank candidates by net first-year gain and payback, not by how impressive the tool is. A practical order:

1. List recurring tasks that take at least 30 minutes a week, and how often each happens.
2. Time ten instances of the top five.
3. Check what off-the-shelf tools exist for each. A frequent task with a mature, cheap tool (invoicing, bank-feed categorising, appointment booking) usually beats a custom build.
4. Run the formula for each, including setup and upkeep.
5. Do one at a time, and re-time the task after a month. If the real "after" minutes are worse than your estimate, the second project can wait.

Review each automation once a year. Volumes change, prices rise, and a workflow nobody owns slowly stops working.

Where does InvoiceQuickly fit in this calculation?

InvoiceQuickly changes the outgoing-invoice tasks: creating, sending, chasing and recording payments on invoices you send. You type or say what to bill and it drafts an editable invoice you review before saving. On Pro ($9/month) it also emails invoices with the PDF attached, sends scheduled reminders, runs recurring invoices and adds a payment link from your own Stripe or PayPal account, and payments through the link are recorded automatically. Free covers 5 invoices, 5 clients and 3 AI drafts in total, which is enough to time ten real invoices before you put a number in the "with the tool" column. There is no setup fee.

It does not automate other parts of this calculation. It does not process bills you receive (accounts payable), connect to accounting software or bank feeds, or offer Zapier, an API or webhooks. So for automations B and C above you would need other tools. See the features overview, pricing and the invoice automation guide for what to automate first in invoicing.

When an ROI calculation is the wrong tool

• Low-volume tasks. If something happens a few times a month and takes ten minutes, the time saved is under an hour. Choose on convenience, not ROI.
• Tasks where a mistake is expensive. For payroll, tax filings or legal documents, the question is accuracy and control, not minutes saved, and a human should still approve the output.
• Processes that are about to change. If you are changing how you price, bill or deliver work in the next quarter, automate after the change, not before.
• Procurement-grade business cases. If a lender, investor or board needs the numbers, treat this as a first pass and add a proper time study, training, migration and integration costs. See how to use an ROI calculator to justify automation for building that case.

Frequently asked questions

How do you calculate ROI on automation?

Take the value of the time saved in a year (tasks per month × minutes saved ÷ 60 × hourly cost × 12), subtract the first-year cost (subscription, setup and upkeep), and divide the result by the first-year cost. Multiply by 100 for a percentage. Use your own timed tasks rather than a vendor's estimate, and calculate payback as setup cost ÷ monthly net saving.

What does a 20% ROI mean?

It means the automation returned its first-year cost plus 20% of that cost. For example, if you spend $1,000 in the first year and save $1,200 of time, the net gain is $200, and $200 ÷ $1,000 = 20%. The money value is often more useful than the percentage: a 20% return on $1,000 is $200, while 500% on $100 is $500.

What hourly cost should I use for my own time?

The rate you would actually earn in that hour, but only if you have paid work to fill it. If the saved hour would not be billed, the saving is real as free time, but not as money. For staff, use wage plus employer taxes and benefits, which made up 30.0% of private-industry compensation costs in June 2026 according to the BLS.

How long should automation take to pay back?

Off-the-shelf tools for frequent tasks often pay back their setup cost within months, because the vendor carries the build and upkeep. Custom integrations usually take longer, and in the worked example above one never pays back at its current volume. Work out your own payback from your setup cost and monthly net saving rather than relying on a general rule.

What is the biggest hidden cost of automation?

Upkeep on workflows you build yourself. Connected tools change, edge cases appear and someone has to notice when a step silently fails. Add a realistic number of hours per month as a running cost, and give each automation an owner who checks it.

---

More guides on running the billing side of a business are on the InvoiceQuickly blog. To time your own invoices on the Free plan, start free.