Business process automation: examples, tools and costs
Business process automation means handing repetitive steps of work to software: moving data between systems, sending documents, reminders and checking that the numbers add up. People set the rules and handle the exceptions, and the system does the rest. Processes that are frequent, rule-based and easy to check pay back fastest.
In short
- Simplify the process first, then automate it. Automating a bad process only makes mistakes happen faster.
- The biggest gains sit where departments and programs meet: bank and invoices, order and warehouse, schedule and client report. That’s where people retype data by hand most often.
- Tools come in four levels: a feature of software you already use, an off-the-shelf app connector, custom code on a server, and AI for unstructured data. Start with the lowest level that’s enough.
- Work out the cost from hours: how long the process takes today, how long after rollout, and what an hour of work costs. If the saving is a few hours a month, the rollout won’t pay back.
- Automation that works has an owner, written rules, an event log and an alert when something doesn’t add up. Without them, six months later nobody knows why the robot did what it did.
Contents
- What is business process automation?
- Examples of process automation, department by department
- Which process automation tools should you choose?
- What it looks like in practice: processes I automated at Reefa
- How much does process automation cost? A worked example
- How do you roll out process automation step by step?
- How do you check that automation works after rollout?
- When doesn’t process automation pay off?
- Frequently asked questions
I’m writing as a practitioner. At Reefa, my cleaning company in Kraków and Katowice, I built the system that runs scheduling, settlements, documents and reports myself. Below are the examples, tool levels and way of costing it that I took from that. If you’re looking for which process to start with, read where to start with business automation.
What is business process automation?
A business process is a chain of steps that turns an input into a result: an enquiry into a quote, an order into a delivery, a bank transfer into a booked invoice. Automation means that some of those steps are done by software following written rules, without waiting for a person.
Three terms worth telling apart:
- Task automation. A single step happens on its own, for example an invoice is emailed to the client once it’s issued.
- Process automation. Software runs the whole chain of steps between people and systems, tracks deadlines and knows which stage every case is at.
- Process optimisation. Before you automate anything, you remove unnecessary steps. It needs no software, and it often gives the most.
The order matters: optimise first, then automate. A robot in a bad process repeats the same mistakes, only faster and more often. That’s why I start with a process map that shows the steps, roles, data and time.
Examples of process automation, department by department
The best candidates sit where departments or programs meet, because that’s where someone retypes data by hand. The table shows typical examples and what goes to a person.
| Department | What automation does | What stays with a person |
|---|---|---|
| Finance | Matches transfers to invoices and shows payments with no document | Explains exceptions |
| Credit control | Sends payment reminders on schedule | Talks to the debtor |
| Sales | Saves the website enquiry in the CRM and reminds you to reply | Quote and negotiation |
| Customer service | Generates and sends monthly reports on work done | Handles complaints |
| Operations | Collects hours, photos and location from field work | Decides when something is missing |
| Purchasing | Collects orders and chases late deliveries | Chooses the supplier |
| HR | Creates documents from the employee record and tracks gaps | Conversation and signature |
| Management | A daily summary of figures and items that need attention | Decisions |
What do they have in common? The result is easy to check, and the rules fit on one page. If every other step in a process is “it depends”, it’s not a good place to start. Better to give the person a better tool than a robot.
Which process automation tools should you choose?
Tools fall into four levels. Start with the lowest one that solves the problem, because every level up costs more to build and to maintain.
| Level | When it’s enough | Limitation |
|---|---|---|
| A feature of software you already use | Your invoicing app, CRM or shop has built-in rules and reminders | Works inside one program only |
| Off-the-shelf app connector (no-code) | Data needs to move between two or three popular apps | Fees per operation, weak error control |
| Custom code on a server | Lots of data, several companies or rules, a log and alerts needed | Needs someone to maintain it |
| AI for unstructured data | Documents, photos, free text that a rule can’t read | Low-confidence results need checking |
What I stick to when choosing:
- First check what your current software can do. Often it’s enough to switch on a feature you’re already paying for.
- A no-code connector is good for a trial and for simple flows. When a flow has more than a few steps and has to be right to the penny, I move it into code with an event log.
- I add AI only where data has no structure. Hard matches such as tax ID, invoice number or amount are done by rules. More on this in the piece on AI in accounting.
For when an off-the-shelf tool stops being enough and it’s worth building your own, see custom system or off-the-shelf tool.
What it looks like in practice: processes I automated at Reefa
At Reefa I mostly automated boring, frequent processes. Each one has a rule, a log and a notification when something doesn’t add up. The whole system is described in the Reefa system case study.
Money: invoices, bank and reminders
- Invoices sync daily from the invoicing app, and every morning I get a Telegram summary of who hasn’t paid.
- Bank reconciliation follows one rule: every transaction needs coverage, so income has an invoice and an expense has a cost document. On the first day of the month the system checks three businesses and sends me the uncovered items, marked red.
- Credit control has nine stages, from a reminder two days before the due date to day 60 after it, with ready-made letters.
Clients: a report nobody retypes
On the 5th of each month every client gets an email and a PDF listing the visits. Visits come from the schedule, and Polish public holidays are built into the calendar, so nobody assembles the report by hand from several sources.
Field work and purchasing
- Staff start and finish shifts in a Telegram bot, with their location at the site. When a shift doesn’t start, alerts go out after 20, 40 and 60 minutes.
- Material orders have a morning digest and escalation after seven days. The baseline before the change: on average 9.4 days passed from order to delivery.
The takeaway for your company: when you design an automation, the exceptions take the most work, not the typical path. For every process, write down what goes to a person, when and to whom.
How much does process automation cost? A worked example
With me, a process automation rollout costs from PLN 15,000 excl. VAT. A feature of software you already use, or a simple no-code connector, can be cheaper. The final cost depends on how many programs need connecting and how many exceptions the process has. You can work out whether it pays from three numbers: time today, time after rollout and the cost of an hour of work.
The company in this example is made up, and the numbers are an estimate. It sends 30 clients a monthly report on work done. Today one report takes 40 minutes; after automation, 5 minutes to check it. I take the full cost of an hour of work as PLN 70.
| Item | By hand | After rollout |
|---|---|---|
| Time on reports per month | 30 × 40 min = 20 h | 30 × 5 min = 2.5 h |
| Saving per month | — | 17.5 h, about PLN 1,225 (estimate) |
| Payback at the lowest rollout price (from PLN 15,000) | — | about 12 months, before maintenance |
That’s 17.5 h, about PLN 1,225 a month, and the rollout pays back in about 12 months before maintenance. One reporting process on its own isn’t enough for a quick payback. The sums change when the same system handles two or three processes that use the same data, such as scheduling, reports and invoicing. So count processes together when they share data. Put your own numbers into the savings calculator.
Add maintenance to the build cost: changes in the programs the system connects to, new exceptions, and the time of the person who checks the alerts. Prices and typical scopes are on the pricing page.
How do you roll out process automation step by step?
A rollout that still works a year later goes through six steps. The first two are the easiest to skip, and they decide the outcome.
- Process map. Steps, roles, data, time and exceptions in one table.
- Simplification. Remove steps that add nothing, and agree a single source for each piece of data.
- Rules in writing. What happens in nine cases out of ten, and who decides in the tenth.
- Build at the lowest tool level that’s enough, with an event log.
- Parallel running. For a month the old way runs next to the new one, and you compare results.
- An owner and alerts. One person is responsible for the process and gets a notification when something doesn’t add up.
For a quick picture of where your company stands, take the free AI readiness assessment. If you’d rather do steps 1–3 with someone from outside, the AI and process audit takes two weeks, ends with a process map with counted hours and a rollout plan, and costs from PLN 6,000 excl. VAT.
How do you check that automation works after rollout?
Measure four things, not just whether the automation runs. Record their values before rollout, then compare after a month of parallel running and again after a quarter.
| Measure | How to count it | What to watch for |
|---|---|---|
| Process time | Hours a month people spend on the process | Checking exceptions is work too |
| Start-to-finish time | Days from enquiry, order or transfer to the result | An average hides the single cases that got stuck |
| Exception rate | How many cases in a hundred go to a person | It rises when a program or supplier changes |
| Mistakes that got out | How many errors a client, accountant or supplier noticed | Such a mistake costs trust, not just time |
Write the before value down and date it. Without it, six months later nobody remembers how things were, and it’s hard to judge whether the rollout paid off. Check the exception rate every month, too. If it’s rising, the rules no longer fit reality; it doesn’t mean people are working worse.
A good automation is boring: it works the same way every day, and you only notice it when an alert says something doesn’t add up. If the team corrects its output by hand every week, go back to step 3 and rewrite the rules.
When doesn’t process automation pay off?
Automation makes no sense when:
- The process is rare. Something you do once a quarter is better written up as instructions.
- The process keeps changing. Let it settle first, or you’ll be rebuilding the automation every month.
- The data isn’t in any program. A notebook and one person’s memory have to become a simple form first.
- Nobody will own it. An automation without an owner breaks quietly, and the mistakes surface at the client.
- The saving is a few hours a month. A template or a feature of your current software is better.
Start with a list of the five processes that take the most time every week, and count the hours for each. Pick one that is frequent, has rules and is easy to check. How to choose and a 30-day plan are in where to start with business automation.
I run rollouts like this as part of the process automation service. A rollout costs from PLN 15,000 excl. VAT, and the scope depends on how many programs and exceptions are involved. Work out the saving in the calculator first, then book a 30-minute call: I’ll tell you straight whether a feature of the software you already use is enough.