Imagine this (an illustrative example): Tomas, the operations manager at a Vilnius accounting services firm, spent three days preparing a presentation for the owner. The topic: introducing process automation. He knew manual processes were taking too much time, he knew mistakes were costly, and he knew something had to change. But when the owner asked one specific question, “So how much will it pay back, and how fast?”, Tomas had no clear answer. The presentation ended with: “We'll think about it.”
Many operations and IT managers in Lithuania know this situation. Automation feels like the right call, but without concrete numbers it stays an abstraction that is hard to sell to a board or an owner. In this article I do not give you a theoretical overview but a concrete tool: an ROI formula, the five processes that pay back fastest, an illustrative example with numbers and a template you can fill in within 15 minutes and present to your boss tomorrow.
An important note: this article is for owners and operations managers of private limited companies (UAB) with 10–50 employees who already feel the weight of manual work but have never asked “will it pay back?” in numbers. If you are interested in specific automation tools (n8n, Make.com, Zapier), read our overview of n8n automation use cases.
Why some automation projects miss their ROI targets
In practice, a good share of automation initiatives at small and mid-sized businesses fall short of their original ROI forecasts. The reasons are usually not what people think: it is not a technology problem and not a bad choice of platform. It comes down to three systemic mistakes.
Processes that are too small and repeat too rarely. If a process takes 30 minutes a week and happens once a month, automating it returns only a few hours a year. Automation pays off most when a process repeats at least 3–4 times a week and takes at least 20–30 minutes each time. Below that threshold the return is marginal and the setup costs dominate.
Overpromising without accounting for setup time. Automation vendors will often show how much time you will save on day one after launch. In reality, choosing the tool, configuring, testing and training the team take 2–6 weeks, during which productivity temporarily drops. A proper ROI calculation has to include this “negative return” period.
Ignoring hidden costs. A Make.com license costs from about €10 to a few dozen euros a month (depending on volume; prices change). That looks cheap. But the hidden costs add up: consultant days for setup (€200–800), team training (2–4 hours per person), maintenance and updates (0.5–1 hour/month), fixing errors in the first two months. Put together, the real investment is often 2–3 times the license fee. That is normal, but it has to be in the ROI formula from the start.
The ROI formula: a practical calculator for managers
The standard return-on-investment formula, adapted for process automation:
Where:
- Time saved: the number of hours per month no longer needed after automation (not 100%, because some steps stay with a person)
- Hourly labor cost: the employee's gross salary ÷ 168 hours per month (the usual monthly norm)
- Total investment: one-time setup costs + license and support fees for the first 90 days
A concrete example. An accounting firm automates invoicing. Before automation: 3 hours a day × 22 working days = 66 hours/month of manual work. After automation: 10 hours/month (a person only checks for errors and signs off). Savings: 56 hours/month. The accountant's hourly cost: €1,800 gross ÷ 168 = €10.70/hour. Monthly return: 56 × €10.70 = €599. Total investment: €4,200 (setup + 3 months of licenses + training). Break-even point: €4,200 ÷ €599 ≈ 7 months. ROI after 90 days: (3 × €599 − €4,200) ÷ €4,200 × 100 = −52%. ROI after 12 months: (12 × €599 − €4,200) ÷ €4,200 × 100 = +71%.
NowWith automation
Issuing and checking invoices
Figures from the example: 66 hours of manual work become 10 hours of checking, saving 56 hours a month. The setup pays back in about 7 months.
This calculation shows why the 90-day ROI is often negative, and that is normal. The real question is not “will it pay back in three months?” but “how many months until break-even, and what will the return be in year two?”. For managers used to evaluating investments, this framing is far more convincing than an abstract “we'll save time”.
5 processes most likely to pay back within 90 days
Not every process is equally suited to be your first automation. Here are five that come up often in Lithuanian businesses, are clearly defined and give a fast, measurable return:
1. Segmenting and routing leads
Inquiries arrive every day from different channels: website forms, email, social media, referrals. The sales manager reviews them by hand, assigns them to sales reps and sets priorities. An automated flow (built on n8n or Make.com) collects them in one place, assigns each to the right rep based on predefined criteria (sector, size, location, budget) and sends the rep a reminder via Slack or email. Estimated savings: 1–2 hours a day for the sales manager, or 20–40 hours a month.
2. Cleaning and enriching CRM data
Outdated contacts, duplicates, incomplete records: how clean your CRM is directly affects sales performance. Manual cleanup often takes several hours a month and is done irregularly. An automated flow checks new records once a week, identifies duplicates and sends management a summary: what needs manual approval and what was cleaned automatically. For a 20-person sales team, the monthly value of the time saved can be roughly €150–300.
3. Issuing and tracking invoices
Invoicing is one of the most time-consuming admin processes: collecting data from the order system or CRM, generating the invoice, sending it to the client, tracking payment and sending reminders when it is late. An automated process (Make.com + the accounting system) does all of it without anyone stepping in: the invoice is generated from the deal data and emailed to the client, an automatic reminder goes out after 7 days, and after 14 days it is escalated to a manager. Depending on invoice volume, this can save up to several hours of an accountant's work a day.
4. Regular reports for management
Every week or month, management needs summaries: sales results, order fulfillment statistics, customer service metrics. Done by hand, that means opening 3–5 systems, exporting data, compiling an Excel sheet, formatting it and sending it. An automated flow pulls data from all sources, builds a structured report and emails it to managers every Monday morning. Estimated savings: 3–6 hours a week of an analyst's or project manager's time.
5. FAQ answers in customer service
Customer service teams often answer the same 20–30 questions over and over: opening hours, delivery times, pricing, warranties, return policy. An AI chatbot or an automated email filter with templates can answer a large share of these questions automatically and pass more complex ones to a person with context. Estimated savings for a customer service specialist: 1–3 hours a day, and response time for customers drops from hours to minutes.
More on process automation: business process automation service.
Illustrative example: an accounting firm, €4,200 invested → ~€4,400 returned in 90 days
Take, for example, an accounting services firm with 8 employees serving 60 small business clients. The main problem is invoicing and payment tracking. Two accountants spend about 5 hours a day on these processes: creating invoices from the data clients submit, sending them, checking payments in the system and writing reminders to late payers.
Before automation. 5 hours/day × 22 working days = 110 hours/month for both accountants together. The accountant's hourly cost: €12/hour (€2,000 gross ÷ 168 hours). Monthly cost of this process: 110 × €12 = €1,320. Per year, that is €15,840 just in manual invoice administration. On top of that: an average of 4–5 invoice errors a month, which take extra time to fix and strain client relationships.
The solution: Make.com + Airtable + email integration. A typical solution is an automated invoice flow: clients submit their monthly data through a structured Google Forms form; Make.com automatically generates the invoice from that data and the agreed price list; the invoice is emailed to the client as a PDF; the system tracks payment status and sends an automatic reminder after 7 days; if it is still unpaid after 14 days, it is escalated to a manager with the full history. One accountant only does the final quality check: 15–20 minutes a day.
- 1Client submits monthly dataGoogle Forms
- 2Invoice generated from the price listMake.com
- 3PDF invoice sent to the clientEmail
- 4Reminder after 7 days, manager after 14The flow tracks payment status.
- 5Accountant only checks15–20 minutes a day
The investment. Consultant work and configuration: €2,800. Make.com license for 3 months: €120. Airtable license for 3 months: €90. Team training: €600. Error fixing and support in the first 3 months: €590. Total: €4,200.
Expected result after 90 days. Manual work in the invoice flows would drop to about 15 minutes a day instead of 5 hours. Savings: ~4.75 hours/day, 104 hours/month. Monthly return: 104 × €12 = €1,248. Return over 90 days (3 months): 3 × €1,248 = €3,744. Additional return: fewer invoice errors (from 4–5/month to 0–1/month) would save ~3 hours/month of corrections, another €36/month or €108 over 90 days. Total return over 90 days: €3,744 + €108 + fewer late payments (roughly €550 per quarter from better tracking) = €4,402. Net return: €4,402 − €4,200 investment = +€202 over 90 days. ROI: +4.8%. After 12 months, ROI exceeds 70%.
This example shows clearly that the 90-day ROI will be small, but already positive. The real return comes in year two, once all setup costs are covered and the system runs with minimal maintenance cost.
Classic ROI mistakes: what managers most often forget
Even a well-prepared ROI presentation can fall apart because of one forgotten factor that the owner or CFO spots immediately. Here are the four most often ignored costs:
Training and the adoption period. An automation flow can work perfectly from a technical point of view, but the team has to learn to use it, trust its results and change their work habits. The first month after launch often means lower productivity, because people check both the manual and the automated process in parallel until they trust the system. Budget for 2–4 hours of training for every employee who uses the system, and roughly up to ~50% slower execution of that process for the first 2–4 weeks.
Maintenance and updates. Automation flows are not “set and forget”. When third-party systems update their APIs, when business rules change, when new exceptions appear, the flows need maintenance. Plan for 0.5–2 hours a month of technical support (or consultant fees if you do not have the skills in-house).
Handling errors and exceptions. Even well-configured automation creates a queue of “unconfirmed cases”: non-standard data, system outages, unusual situations the logic did not cover. A person still handles these. In the first two months, handling errors can take 1–3 hours a week, and that is a cost the ROI model should reflect too.
The cost of alternatives you gave up. The time you spent setting up and managing automation could have gone into other projects. This is the idea of opportunity cost. It should not stop you from automating, but it should remind you that the right process to pick is the one with the highest return, not just a positive one.
ROI template: a 12-row Google Sheets file you can prepare in 15 minutes
Here are the specific rows to fill in when you present an automation business case to your boss. You can calculate each one in 5–10 minutes with your company's data:
- A1: Process name (e.g. “Issuing invoices”)
- A2: Hours per day done manually (e.g. 2.5 hours)
- A3: Working days per month (e.g. 22 days)
- A4: Monthly manual hours: A2 × A3
- A5: Employee hourly cost (gross ÷ 168)
- A6: Current monthly cost of the process: A4 × A5
- A7: Expected savings after automation (%, e.g. 80%)
- A8: Monthly return: A6 × A7
- A9: One-time setup investment (consultant + configuration)
- A10: Monthly running costs (license + support)
- A11: Break-even point in months: A9 ÷ (A8 − A10)
- A12: 12-month ROI (%): ((12 × A8 − A9 − 12 × A10) ÷ (A9 + 12 × A10)) × 100
This template lets you prepare clear projections for every automation candidate in your company in 15 minutes. When you put three or four of these calculations on one slide, your boss sees not an abstract “automation is good” but a concrete table for prioritizing investments: which process breaks even fastest and which gives the biggest 12-month return.
When automation is NOT the right answer
An honest ROI presentation is stronger if it also states clear limits: when automation simply will not pay back. This builds your credibility with your boss, because you show you understand not only the potential but also the risks.
The process takes less than 2 hours a month. If a process repeats rarely and takes little time, the setup costs will always outweigh the return. Automate what repeats often, not what annoys you occasionally.
The process is chaotic and changes every week. Automation needs clear, stable process logic. If the process looks different every time, if the rules keep changing, if exceptions are the norm, standardize the process manually first and only then automate it. Automated chaos is just faster chaos, not a solution.
Rare, seasonal work without enough volume. A process that happens only once a year (for example, the annual report) and takes 8 hours: investing in automating it may only pay back after many years. Prioritize frequently repeated, clearly defined processes.
The process requires nuanced judgment. Automation is great for rule-based, structured processes. But processes that need a lot of discretion, cultural awareness or relationship context, such as handling an angry customer or a sensitive negotiation, are better left to people.