Business process automation: how to choose, map and measure a process before you buy a tool
Business process automation starts before the tool: how to list and score your processes, map the winner, name its owners and measure what really changes.
By Rokibul Hasan8 min read
- Automation
- Operations

Most automation projects get decided in a meeting, and usually for a weak reason: someone is fed up, a vendor gave a good demo, or a competitor announced something. Business process automation works better when the choosing comes first. Pick the process on evidence, find out how it really runs, give it an owner and take a baseline. After that, the tool is the easy part.
This guide is for owners and operations managers in small and mid-sized businesses who have a long list of things they would like to automate and no fair way to rank it. It walks through seven steps using a made-up 25-person services firm, so you can copy the method with your own numbers.
I build web apps, APIs, AI agents and integrations, and a clear process is the best brief a developer can receive.
What business process automation covers
A task is one action: send an invoice. A process is a chain of tasks with a start, an end and usually more than one person involved: from signed proposal to first client meeting. Business process automation means software running as much of that chain as makes sense, while people handle the exceptions and the judgement.
It crosses teams, which means it crosses opinions, and most of what follows deals with that. If you need the terms first, read what AI automation is.
Step 1: List processes, not annoyances
Ask each team to write down what they do repeatedly, in the form "from X to Y": from enquiry to quote, from accepted offer to first day, from month end to management accounts. One line each, with who is involved, how many times a month it happens and roughly how many hours it takes in total.
Ask the people who do the work. Managers describe the process as designed. The people inside it know about the spreadsheet nobody mentions.
If you run out of ideas, APQC's Process Classification Framework is a published catalogue of business processes, at version 8.0 since February 2026. Use it to spot what you forgot, not as a template.
Step 2: Cross out what should not be automated
Before any scoring, remove anything that fails one of these tests.
- It is about to change. A new system, a restructure or a new pricing model within six months would undo the work.
- Nobody can explain it. If three people describe three versions, settle that first.
- It rarely happens. Twice a year does not justify building, testing and upkeep. A checklist will do.
- It should not exist. In 1990 Michael Hammer called a Harvard Business Review article "Reengineering Work: Don't Automate, Obliterate", and the advice has aged well. If a report nobody reads takes a day each month, stop producing it.
- It needs accountable human judgement. Software can prepare the file for a hiring or disciplinary decision. A person makes the call.
Step 3: Score what is left
Give each process five marks from 1 to 5.
- Hours a month across everyone involved (1 is under 5 hours, 5 is 40 or more)
- Cost of a mistake (1 is a small annoyance, 5 is lost money, a lost client or legal exposure)
- How clear the rules are
- How digital and consistent the inputs are
- How well the systems involved support APIs
Value is the first two added together. Ease is the last three added together. Multiply them for the score. Here is our imaginary firm:
| Process | Value (hours + mistake) | Ease (rules + inputs + APIs) | Score |
|---|---|---|---|
| Client onboarding | 5 + 4 = 9 | 4 + 4 + 4 = 12 | 108 |
| Supplier invoice entry | 4 + 4 = 8 | 4 + 3 + 5 = 12 | 96 |
| Monthly client reports | 3 + 2 = 5 | 5 + 5 + 4 = 14 | 70 |
| Proposal writing | 5 + 4 = 9 | 1 + 2 + 2 = 5 | 45 |
| Holiday requests | 1 + 2 = 3 | 5 + 5 + 5 = 15 | 45 |
Proposal writing is what everyone complained about, and it scores poorly because the work is judgement. AI might draft sections of it later, but it should not go first. Holiday requests are the easiest item on the sheet and barely matter, yet that is the kind of process a tool demo likes to show.
The number itself means little. Its use is settling the argument in the room. Score together, with the people involved, and treat any disagreement of more than a point as a sign that nobody fully understands the process.
Step 4: Map the winner as it really runs
Sit with the person who does the job and watch one real case from start to finish. Keep the first pass high level: ASQ's SIPOC method stays at five to seven core activities, with what goes in and who receives what comes out. Then write down who does each step, where, how long it takes hands-on and how long it waits afterwards.
| Step | Who and where | Hands-on | Wait after |
|---|---|---|---|
| Signed proposal reaches operations | Sales, email | 5 min | 1 day |
| Client record created | Operations, CRM | 10 min | None |
| Billing set up | Finance, accounting software | 15 min | 2 days |
| Project and folders created | Delivery lead, project tool | 20 min | 1 day |
| Welcome pack sent, details collected | Account manager, email | 15 min | 3 days |
| Kick-off booked | Account manager, calendar | 10 min | None |
That comes to 75 minutes of work and seven days of waiting. The Lean Enterprise Institute's lexicon separates the time an order is actually being processed from the time it takes to move through the whole process, and this table shows why. Automating the keystrokes alone would save a few minutes per client. Removing the waits changes what the client experiences.
Then list the exceptions and how often they occur: a different billing entity, a returning client, a missing purchase order. If something happens in more than about one case in five, it is part of the process and needs its own path.
A whiteboard is enough for this. Formal notation such as BPMN can wait until you have many processes.
Step 5: Simplify it, then sort the steps
Change the process on paper before any software is involved. In our example, the three-day wait is the client returning a form. Collect those details when the proposal is signed and most of that wait disappears for free.
Then label each remaining step. A rule step needs only fixed logic, such as creating the client record from the signed proposal. An AI-assisted step needs something read or drafted, with a person reviewing it, such as the welcome email. A human step depends on judgement or a relationship, such as the kick-off conversation.
If most steps come out human, pick the next process on your sheet. AI-assisted steps need extra care, covered in how to add an AI step safely.
Step 6: Name two owners
A process with no owner decays. Every automated process needs two named people, who can be the same person in a small firm.
The process owner sits on the business side. They decide the rules, receive the exceptions and look at the numbers each month. The system owner keeps it running: accounts, credentials, alerts, upgrades and the notes explaining how it works. If an outside developer builds it, the accounts should be in your name and you should receive handover notes, whoever you hire.
Write down who gets told when it fails, who can switch it off and who approves a rule change. If nobody will put their name to those three lines, the project is not ready to start.
Step 7: Measure before and after
| Measure | What it tells you | How to get it |
|---|---|---|
| Lead time | How long the process takes, start to finish | Timestamps on the first and last step |
| Hands-on time | Staff time per case | Time five to ten real cases |
| Exception rate | How often it leaves the normal path | Count for a month |
| Error and rework rate | How often someone has to fix it | Count corrections and complaints |
Take these for at least a month before anything changes. Afterwards, count the time spent checking the automation and fixing its mistakes as well as the time saved.
For payback, use your own figures. Hours saved a month, multiplied by the loaded hourly cost, minus monthly running costs, gives the monthly gain. Divide the build cost by that gain to get months to pay back. As an illustration, if our firm saved 24 of its 40 hours at a loaded cost of $30 an hour and the tools cost $100 a month, the gain would be $620 a month.
Add the next process only when this one has numbers. Choose the tool to fit the map, not the other way round. A custom build is quoted from a brief, and my pricing page lists starting prices for websites, apps and marketplace tools.
FAQ
What is the difference between business process automation and workflow automation?
The terms overlap, and vendors use them loosely. Workflow automation usually means one sequence of steps, such as sending an approved form to the right person. Business process automation means a whole process from start to finish, often crossing several teams and systems and built from several workflows. In practice the difference is scope and ownership: a process needs someone responsible for the outcome as well as for the software.
Should we fix a process before we automate it?
Yes, at least on paper. Automation repeats what it is given, faster, so a needless approval or a missing field becomes a permanent feature. Map the process as it really runs, remove the steps that add nothing, then automate what remains. You do not need a perfect process. You need one that people agree on, that runs the same way most of the time, and that has someone who can decide the rules.
How many processes should we automate at once?
One, until it has numbers. Automating a single process from start to finish teaches you where your data is weak, how exceptions behave and whether people trust the result, and those lessons change how you approach the second. Running several at once splits attention and makes it hard to see which change helped. Larger firms with a dedicated team can run more in parallel, but each process still needs its own named owner and baseline.
If you have scored a process and want to know what it would take, send me a short brief: the map, the systems involved, volumes and who owns it. You can send it through the contact page, read about API and backend development, or see AI automation for small business if your first candidate is a back-office job.


