Business process automation: ten examples from small businesses

What business process automation is

Automation is a rule of the kind "when this happens, do that", carried out every time without anyone having to remember. When an enquiry arrives, store it and alert the team. When a customer has an appointment tomorrow, send a reminder. When an order is paid, issue an invoice.

It is not a robot and it is not AI. It is a connection between the software you already use: the website, email, a spreadsheet, a calendar, accounting software. The clearer the rule, the more reliably it works. If the task needs judgement rather than a rule, see what AI agents can do.

Five examples in front of the customer

• An enquiry from the website Before: the form sends an email to a shared inbox that someone checks when they remember. After: the enquiry is stored in a database, a row appears in a Google spreadsheet and the two people who answer get an email. If the email fails, the enquiry is still stored. That is how the site you are reading works.
• Orders from several channels Before: orders come in by phone, in chat and through the website, and someone copies them onto a slip for the kitchen. After: an order from the website appears straight away on a screen in the kitchen and prints as a ticket. A system like this runs in a delivery kitchen we built it for.
• An appointment reminder Before: the customer forgets and does not come, and nobody follows up. After: the day before, they get a text message or an email with a button to confirm or cancel, and the freed slot shows in the schedule.
• A quote that runs late Before: the enquiry waits until the owner finds time to put a quote together. After: the details from the enquiry fill in a quote template, the owner checks the price and presses "send".
• A follow-up Before: the quote has gone out and nobody remembers to ask the customer what they decided. After: if there is no reply after the agreed number of days, the system reminds the person responsible or prepares a short email for approval.

Five examples behind the scenes

• The same thing in several places Before: the customer's details are retyped from the email into a spreadsheet, then into the CRM, then into the accounting software. After: they are entered once and passed on everywhere they are needed.
• Invoices Before: every invoice is written by hand from the order details. After: a paid order creates a draft invoice in the accounting software, and incoming invoices are collected in one folder for the accountant.
• Reports and summaries Before: on Friday someone downloads data from three places and pastes it together in Excel. After: the report assembles itself and reaches the owner's inbox at the agreed time.
• Documents Before: documents from customers arrive as attachments that someone has to find, rename and fill in. After: every file is saved to the customer's folder with a clear name, and the data needed is pulled into a spreadsheet for checking.
• Questions only the owner can answer Before: the team interrupts the owner about prices, procedures and terms. After: the answers are written down in one place the team searches themselves. If the answer is missing, the question reaches the owner once, and the answer is added.

How to choose the first process

Do not start with the most complex process, but with the one that meets the four conditions below.

• It happens often Every day or every week. Something rare is not worth building for.
• There is a clear rule If two people on the team would do it the same way, it can be automated.
• Mistakes cost money A lost enquiry, a forgotten appointment, a wrong amount when retyping.
• The data is already digital In a form, an email, a spreadsheet or a program, not only on paper.
• Check with your own numbers The free 5-minute check goes through the same eight leaks and ranks them by what they cost you a year.

What not to automate

A process that still changes every week. Settle it first, then automate it. Decisions that need judgement about a specific person: a complaint, a discount, a refusal. And anything that goes out and cannot be undone without a person approving it: a payment, an email to every customer, deleting data.

Good automation also has three things: an alert when something breaks, a record of every run, and a manual way to keep working until it is fixed.

How we work

We build automations connected to the software you already use, and test them with real data before they go live. We start with a free 20-minute call. If there are several processes and it is not clear where to start, the €390 audit maps them and ranks what is worth building first.

• Custom automation What it includes and how the work runs.
• When you need an AI agent When the task needs judgement rather than a rule.