What Is Business Process Automation?
Business process automation means using software to carry out the repetitive steps in a process, such as copying data between systems, sending standard emails or creating documents, so people don’t have to. It can be as simple as connecting two apps or as involved as a custom system that runs a process across the whole business.
Take a website enquiry for example. Instead of someone creating a customer record, telling the right colleague and sending an acknowledgement, all three happen automatically when the enquiry arrives.
The goal isn’t to remove people from the process. It’s to remove the admin, so people spend their time where their judgement and experience count.
Which Business Processes Should You Automate?
The best candidates are repetitive, predictable, follow clear rules and happen often. Look for processes where:
- Staff enter the same information more than once
- Data is copied by hand from one system to another
- The same emails or documents are created again and again
- Tasks are assigned using simple, predictable rules
- Manual admin causes delays or bottlenecks
- Mistakes keep happening because of repetitive data entry
Volume matters. Saving two minutes on something done once a month isn’t worth much. Saving two minutes on something done hundreds of times a week is.
How Do You Work Out What a Manual Process Costs?
Multiply the time it takes by how often it happens and the hourly cost of the person doing it. Then add the time spent fixing the mistakes it causes.
As an illustration: if someone spends an hour a day retyping website orders into the accounts system, that’s 1 hour × 230 working days × £22 an hour, or around £5,000 a year, before counting any errors.
Compare that with the cost of automating it. If the automation costs less than a year or two of the manual cost, it’s usually worth doing. That figure also helps you decide which process to tackle first.
Why Should You Map a Process Before Automating It?
Because automating an inefficient process just makes it run faster. Processes often grow step by step as a business grows, and some of those steps are no longer needed.
Map what actually happens:
- Who starts the process, and what information do they need?
- Which systems are involved?
- Where are decisions made, and where do delays occur?
- Which steps actually add value?
You’ll often find steps you can remove altogether. The first question shouldn’t be “How can we automate this?” but “Why does this process work this way?”
A good example is a legal platform for completing Form E, the financial disclosure form used in divorce proceedings. The old process had solicitors copying client answers out of long email chains into the form. Rather than automating the copying, the platform changes the process: clients enter their own information through guided steps, solicitors review it, and the platform produces the court-ready form.
A process & systems review does this mapping across the business and ranks the opportunities by impact and effort, so you know which to tackle first.
What Does Workflow Automation Look Like?
Workflow automation links individual steps into a sequence that runs on its own. A manual enquiry process might involve someone reading the enquiry, entering it into the CRM, assigning it, sending a confirmation and setting a reminder to follow up.
Automated, it becomes:
Enquiry received → customer record created → team notified → task assigned → acknowledgement sent → follow-up scheduled
People still handle the parts that need them, such as replying properly to the customer. The same approach works for order processing, customer onboarding, approvals, internal requests, reporting and support tickets.
Do You Need Automation Software or Custom Software?
Start with the simplest option that does the job reliably. There are broadly three levels:
- Features you already pay for. Many CRMs, accounts packages and helpdesks have built-in workflows, rules and templates that go unused.
- Automation tools. Tools such as Zapier, Make or Microsoft Power Automate connect apps without building anything. They suit straightforward processes between popular systems.
- Custom integrations or software. These are needed when a process spans several systems, follows rules specific to your business, handles sensitive or critical data, or runs at high volume. Custom software can make those processes reliable where off-the-shelf tools struggle.
Steps that involve reading unstructured information, such as emails, PDFs or invoices, used to need a person. AI automation can now handle many of them, with someone checking the results.
Whichever level you choose, pick the technology to fit the process, not the other way round.
What Can Go Wrong With Automation?
Automations tend to fail quietly. A system changes, a connection breaks, and nobody notices until a customer complains. Over time, a business can also build up dozens of small automations that nobody remembers setting up.
To avoid that:
- Give every automation a named owner
- Set up alerts for when an automation fails
- Keep a simple list of what’s automated, where and why
- Have a manual fallback for anything business-critical
Where Should You Start?
Start with one or two processes, not everything at once. The best first candidates are high-volume and repetitive, with clear rules, few exceptions and a cost you can measure. Processes full of exceptions and judgement calls need more thought.
Measure the time spent and the errors before you automate, then again afterwards, so you know it worked.
Sometimes the answer won’t be automation at all. An existing system may just need setting up differently, or the process itself may need to change. Good automation starts with understanding the problem, then choosing the simplest technology that solves it reliably.
