Every owner has a list. Quotations take too long. Follow-ups are forgotten. Someone rebuilds the same report every Monday. Purchase requests wait in a chat group until the right person scrolls back far enough. Business process automation promises to fix all of it, and that is the difficulty. You cannot automate everything at once, and the order in which you start decides whether the first project pays for the second.
We are a product engineering team at Infopark in Kochi. We build business software and AI and automation systems for companies in India, the UAE and Australia. This guide is the advice we give before any build is discussed, including the cases where nothing should be built.
The short answer
Automate first the process that happens often, follows rules you can write down, has stayed the same for months, and costs you money or a customer when a step is missed. Fix the process on paper before you automate it. Start with one, finish it, and measure it. Leave rare tasks, judgement calls and anything still changing to people.
What business process automation means
Business process automation is software doing the routine steps of a process that people now do by hand. It has nothing to do with robots, and most of it involves no AI. The routine steps are usually of five kinds.
Capturing. An enquiry, an order or a request is entered once, through a form or an integration, instead of being retyped from a message.
Routing. The record goes to the right person according to a rule, such as branch, amount or product.
Reminding. The system notices that nothing has happened and tells someone, so nobody has to remember to chase.
Calculating and producing. Prices, taxes, totals and documents such as quotations and invoices are generated from the record.
Passing on. The finished record is posted to the next system, such as the accounts, without being keyed in again.
Seen this way, automation is modest. It does not replace the salesperson, the storekeeper or the accountant. It removes the copying, the chasing and the waiting that sit between them.
Four ways to automate, from cheapest to most involved
Automation does not always mean a software project. The cheapest route is often a feature you already own, and it should be tried first.
| Route | What it is | Suits | Where it runs out |
|---|---|---|---|
| Features you already have | Recurring invoices in the accounting package, email rules, form tools, reminders in the calendar, workflow rules in a CRM you already pay for. | A single step inside one tool. | Anything that crosses from one tool to another. |
| Connector tools | No-code services that watch for an event in one application and carry out an action in another. | Simple hand-offs between popular cloud applications, at modest volume. | Branching rules, error handling, and applications the tool has no connector for. |
| Packaged software | A product built for the whole process: an accounting package, a CRM, an HR and payroll product. | A process that looks much the same in every company. | A process that is specific to your trade or your way of working. |
| Custom software | A system built around your records, rules and approvals, connected to the tools you keep. | A stable process that is specific to your business and that many people work in every day. | Cost and time. It is the wrong choice for a process that is still changing. |
Most businesses end up using more than one row of that table. The mistake is to start at the bottom row when the top one would do.
How to choose what to automate first
The first process to automate is the one that scores well on all of the tests below, not the one that annoys the owner most. List your candidates and put each one through these questions.
How often does it happen?
A task done fifty times a day repays automation quickly. A task done once a quarter rarely does, however tedious it is. Count the occurrences for a fortnight before deciding. The count is often different from what people expect.
Can you write the rules down?
If the process can be described as a set of if and then statements, software can follow it. If the honest description is that an experienced person looks at it and decides, the decision should stay with that person. The steps around the decision can still be automated.
Has it stopped changing?
A process that was redesigned last month will be redesigned again. Automating it now fixes the current version in software, and every later change becomes a development task. Wait until the process has run the same way for a few months.
What does a missed step cost?
Some delays are an irritation. Others lose an order, hold up a dispatch or let a customer exceed a credit limit. Rank the candidates by what goes wrong when the process fails, not only by the time it takes when it works.
How many hand-offs does it have?
Work is rarely slow while someone is doing it. It is slow while it waits between people. A process with four hand-offs and a day of waiting at each one has more to gain than a long task one person completes alone.
Is the data already in one place?
Automation needs something to act on. If the information lives in voice notes, paper and memory, the first job is to capture it in a structured form. Our guide to when spreadsheets stop working covers that earlier step.
Processes that usually make a good first project
These are the processes that most often pass the tests above in the businesses we speak to. Yours may differ, which is why the questions matter more than the list.
Enquiry capture and assignment. Enquiries from the website, phone and messaging apps land in one list and are assigned to a named person, with a reminder if nobody responds. This is the starting point of most custom CRM builds.
Quotation to invoice. A quotation is generated from the enquiry, the order from the quotation and the invoice from the order, so nothing is typed twice.
Purchase requests and approvals. A request goes to the right approver by amount and department, with a record of who approved it.
Payment and renewal reminders. Customers are reminded on a schedule, and the reminder stops when the payment is recorded.
Recurring reports. The Monday report is produced from live data instead of being assembled from three files.
Leave and attendance. Requests go to the right manager and the approved result feeds payroll, a subject covered in our post on building or buying an HRMS.
When several of these belong to one chain, from order to stock to dispatch to accounts, the question is no longer about one automation. It is about an operations system, which our guide to custom ERP development covers.
What not to automate
Some processes should be left alone, and saying so early saves money.
A broken process. If nobody agrees on the steps, software will carry out the confusion faster. Agree the process on paper first.
A rare process. If it happens a few times a year, a checklist is cheaper than a system.
A judgement call. Pricing a difficult deal, handling a complaint or deciding whom to hire needs a person. Give that person better information and leave the decision with them.
A process that is about to change. A new product line, a new branch or a reorganisation will redraw it.
Conversations customers value. An automatic acknowledgement is useful. An automatic reply to a customer who wanted a person is not.
There is also a case for automating nothing yet. A young business that is still finding out how it sells and delivers should stay on spreadsheets and messages a little longer. The cost of manual work at low volume is small, and the freedom to change the process overnight is worth more.
Where AI fits
AI is useful for the steps that rules cannot handle, mainly reading and sorting unstructured material: pulling figures out of documents, classifying incoming messages, drafting a first reply for a person to check. For most business processes, plain rules do the larger part of the work. A rules engine, a better query or a fixed report is often cheaper and more reliable than a model, and we recommend one when it is.
How to run the first automation project
Keep the first project small enough to finish and specific enough to measure. The steps are the same whether the answer turns out to be a setting in a tool you own or a custom build.
Map the process as it is. Follow one real case from start to finish and write down every step, every person and every wait.
Measure it before you change it. Count how many cases pass through and how long each takes from start to finish. Without a figure from before, nobody can say afterwards whether the work paid off.
Remove steps before automating them. Some approvals and copies exist only out of habit. Take them out first.
Choose the cheapest route that works. Check the tools you own, then connector tools, then packaged products, then a build.
Pilot with one team. Run real cases through the new way of working while the old way remains available.
Measure again, then choose the next process. The second project is picked on evidence from the first.
When the route is a build, this is how our six-stage process from discovery to growth begins: a short discovery that ranks the candidate workflows by the effort each consumes today, so the first thing built is the one with the clearest return.
Frequently asked questions
What is business process automation in simple terms?
It is software carrying out the routine steps of a process, such as capturing a request, sending it to the right person, reminding them, producing the document and passing the result to the next system. People keep the decisions.
Which business process should be automated first?
The one that happens often, follows rules you can write down, has been stable for months and causes real loss when a step is missed. For many businesses that is enquiry handling, quotation to invoice, or purchase approvals.
Do we need custom software to automate a process?
Often not. Many single steps can be automated with features in tools you already own, or with a no-code connector. Custom software is justified when the process is specific to your business, crosses several systems and is used by many people every day.
Is business process automation the same as AI?
No. Most automation is rules: if this happens, do that. AI helps with steps that involve reading documents or free text. Many useful automations contain no AI at all.
Will automation replace our staff?
What it replaces is retyping, chasing and waiting. In the businesses we speak to, the aim is usually to handle more work with the same team and to stop losing orders to missed steps.
Conclusion
Business process automation works when it starts small and in the right place. Choose one process that is frequent, rule-based, stable and costly when it fails. Fix it on paper, remove the steps nobody needs, and use the cheapest route that does the job. Measure before and after. Leave judgement to people, and leave unsettled processes alone until they settle.
We are happy to go through your list of candidates and say which one we would start with, including when the answer is a setting in a tool you already own. Tell us which process is costing you most and we will start from there.
Human. Digital. Future.
