Business Process Automation or a New Hire
Business process automation comes down to four parts of one role. Three of them are work a system can carry: working out what was asked, finding what happened last time, and producing the document. The fourth, deciding what to do when a case is unusual, stays with a person. This article covers how to tell them apart before you write the job ad.
We have written about where a person still decides inside an AI system (opens in new tab). That article stayed inside a system that was already running. This one sits earlier, at the point where nothing is built yet and the choice is between a vacancy and a project.
How many different jobs sit inside one role?
Most companies reach this question when one person can no longer keep up. Open the job description you would write for them, and the tasks look like one continuous stream of work. They are not. Underneath, the same role usually holds four separate things: working out what was asked, finding what happened last time, producing the document, and deciding what to do when the case is unusual.
Those four need different things from a person. Patience and memory carry the first two. The third needs to know how the company writes to a client: the tone, what it promises and what it does not. The fourth needs the authority to commit the company on price, deadline or terms.
A job ad asks for all four in one person because that is how hiring works. A system does not have to take all four.
How has business process automation changed?
A rule-based tool took over the part of a job that looked identical every time. That is why the old version of this question was easy to answer: you automated what repeated, and you hired for everything else.
AI in operations reads what arrives rather than matching it against a fixed pattern. It handles the enquiry written in somebody's own words, the supplier registered under three different names, the form that came in with two fields missing. We set out what separates a system that works out what it is looking at from one that follows a written rule (opens in new tab) separately.
The practical effect is that the dividing line moved. Until recently, business process automation turned on whether the work repeated. Now it turns on whether the answer is already recorded somewhere in your company.
The hiring side has moved in the meantime too. According to the Bank of Lithuania, average gross monthly pay in Lithuania rose by about 9.3% year on year in the first quarter of 2026 (opens in new tab). A vacancy you open today is a commitment that gets more expensive every year it stays open.
What happens to each part when that person is away?
Working out what the client actually asked for. It takes reading a free-text email or form and spotting what was left unsaid: the quantity, the deadline, whether we have done similar work before. Enquiries sit unanswered, because a colleague cannot reply without knowing what exactly is being asked, and the client looks elsewhere in the meantime.
Finding how a similar case was decided before. It takes remembering how similar orders were priced and why, because the system does not hold that. The price then gets worked out again from the beginning, and the same job comes out at a different number than last time.
Writing the reply, the quote or the document. It takes knowing how the company writes to a client: the tone, what it promises and what it does not. Without that person somebody writes it their own way, and the client notices that the answer differs from the last one.
Deciding what to do when the case is unusual. It takes the authority to commit the company on price, deadline or terms. Nothing moves until the person is back, and that is exactly as it should be.
The first three are searching, remembering and drafting. A system can carry all three, because the material they need already exists inside the company. The fourth is different: no amount of extra data moves it, because it needs somebody with the authority to decide. Split the work along that line and most of the argument about what to automate disappears.
What does hiring buy that no system does?
A person takes responsibility, and that is where the comparison stops being close. When a decision turns out wrong, there is somebody who made it, who can explain why, and who will decide differently next time. A system produces an output and holds no position on it.
A person also notices what nobody asked them to notice. The client who sounds different this week, the supplier whose terms changed without an announcement, the number that looks wrong even though it passes every check. A system is not there for that.
So the honest question is a different one: what do you want the person you hire to spend their week on?
What we see in our own projects
We get paid when a company chooses business process automation over a vacancy.
In one manufacturing project we reworked how enquiries arrive and how a first price is assembled. The team did not grow. What grew was the amount of custom work it got through, and the measured figures for that project are on our case studies page (opens in new tab).
That project did not remove the person. It removed the part of the job that was searching, and left the part that was deciding. The same person answers more, and spends the week on the cases that are actually hard.
Frequently asked questions
Can AI replace an employee? Not as a whole unit. Job automation takes over parts of a role, usually the searching, the remembering and the first draft. The part that needs somebody to decide and answer for that decision stays where it is. Companies that treat this as a headcount swap end up with a system nobody owns.
Which parts of a job can business process automation take over? The parts whose answer already exists somewhere in the company: earlier quotes, past orders, correspondence, the price list. If a person would find the answer by looking it up or remembering it, a system can do that part. The part they would find by deciding stays with them.
How many people does workflow automation replace? That figure is the wrong thing to plan around, because the decision works at the level of tasks rather than headcount. In our own projects the team size stayed the same while the volume it handled changed. The useful question is how much of one role moves, rather than how many roles disappear.
Is automating cheaper than hiring? It depends on how often the work arrives and how much of it is retrieval. Where the job comes a few times a week and takes minutes, a person absorbs it and a system costs more to maintain than the work costs to do. Once the queue stops emptying, the comparison changes. We put a price on business process automation after an audit rather than before one.
What happens to the person whose work gets automated? In the projects we have run, they answer more and spend the week on the harder cases. Nothing we build removes the part of the job that needs a decision, so somebody still has to be there for it.
Who should hire a person instead?
Not every job is worth handing to a system. The three cases below are where the right answer is a new hire, and the last of them costs us work.
There is not enough of it. If the task comes up a few times a week and takes a few minutes, somebody absorbs it inside other work without noticing. A system built around that task would cost more than it returns.
The way of working is not settled. While a company is still deciding how it sets prices, what it answers and who approves a discount, there is nothing for a system to take over: it would fix a decision nobody has made yet. A person can work with an unfinished rule and apply it to the situation, and a system cannot.
The job is really a relationship. When the main task is calling an unhappy client and reaching an agreement, no system built around it changes the outcome. We have been asked to automate account management, and the honest answer there was to hire somebody good at it.
Where to start
Take the job description you would post tomorrow and go through it line by line. For each task answer one question: is the answer to it already recorded in the company, in past quotes, past orders, correspondence or the price list? If it is, mark that line. Leave the rest untouched, because those need somebody to decide and stand behind the decision.
Count how many lines you marked. If most are marked, you are about to hire a person to do retrieval, and business process automation has a clear answer in your case. When most stay unmarked, hire, and do it before the queue gets worse.
Get in touch (opens in new tab) and send us that marked-up job description. We will tell you which of those lines a system could not take over.
