Guides · long read, updated
Business process automation for a small business: map first, automate second, measure always
Business process automation sounds like a department. For a small business it is four decisions: what counts as a process, how to map it before touching it, whether a tool or a custom build does the job, and how to know it worked. This guide makes the four decisions in order and ends with the cases where the right answer is not to automate at all.
What counts as a process
A process is a path something takes through the company with the same steps every time: an enquiry to a reply, a booking to a reminder, an order to an invoice, a document to an archive. If the steps change every time, it is not a process yet; it is judgement, and judgement is not automated.
five ticks is a process ready to map; three or fewer is a conversation to have first
Mapping before automating
Every automation we have seen fail was built on an unmapped process: the owner described the ideal path and the system met the real one. Mapping means writing the path as it runs today, with the exceptions, in an afternoon, with the people who run it.
- 01Write the path as it runs today
Not the ideal; the real one, with the workarounds.
- 02Mark where it waits
A mailbox, a person, a spreadsheet. Waiting is where money leaves.
- 03List the exceptions
Every fifth case that needs a different rule. If there are too many, the process is not ready.
- 04Name the data
Where the price list, the calendar and the records live, and who keeps them true.
- 05Decide what stays manual
Complaints, money, health, judgement. Written down before anything is built.
Tools versus custom
Ready-made automation tools connect standard apps with standard steps and are right for standard flows. A custom build is right when the flow is yours: an exception every fifth case, a system without a proper connection, or data that has to move two ways. The honest answer is often both: a tool for the standard part and a small custom piece for the part that is yours.
Measuring the result
Automation without a number is a feeling. Before anything is built, record how the process performs today: how long a reply takes, how many enquiries get none, how many bookings are missed, how many invoices are late. After a month, record the same numbers. The comparison is the result, and it belongs in the plan, not in a promise.
When not to automate
Some of the best advice we give is to wait.
- The process changes every month: automating it now pays for the wrong version
- The data is not written down: write it first, then automate
- The volume is a few cases a week: a template and a habit are cheaper
- The problem is the offer, not the process: a faster reply to a confusing offer confuses faster
- Nobody will own it: a system with no owner becomes wrong quietly
What we do of this
Our part
We map the process with you on the first call, say whether a tool or a custom build fits, and build it one process at a time from €500, with the before-and-after numbers in the plan. When the right answer is to wait, we say so; the audit exists for exactly that.
Questions
Questions from readers
What is business process automation in a small company, in plain words?
A repeating path, such as enquiry to reply or order to invoice, handled by a system that drafts, reminds and files, with a person keeping the judgement. Map it first, build it second, measure it always.
Should a small business use automation tools or build custom?
Tools for standard apps and standard steps; custom when the flow has rules of its own, systems without a proper connection, or two-way data. Often both: a tool for the standard part and a small custom piece for yours.
How do you know if business process automation worked?
By measuring the same numbers before and after a month: time to reply, enquiries with no reply, missed bookings, days late on invoices. The comparison is the result.
Bring one process to the first call.
We map it together and reply with a fixed price or with the advice to wait.