Business process automation examples: the four processes a business with a team tackles first
If you're looking for business process automation examples, you quickly end up with a long list. Quotes, invoices, mail, inquiries, appointments, reports: in a business with a team, there's a lot you could tackle. The question is where to start. In this article, we describe four kinds of process that, in our assessment, usually fit first in businesses with a team. For each one, you'll see the trigger, what the AI employee does, what the person keeps doing, and what has to be in place beforehand. This is our assessment, based on Kevin's own business and on a tax advisory firm. It isn't a statistic about how businesses automate their processes. Whether one of the four comes out on top for you only shows once you've rated your own processes.
First: the process map and the choice
The four kinds don't replace the first step. It all starts with a map of every recurring process in your business: who does what, how often, how long it takes, how the work comes in, which system it lives in, and whether someone needs to think along or whether it simply has to get done. The processes that simply have to get done are then rated by four criteria: time, money, risk and feasibility. For process no. 1, we check three questions at the end. Can it run on its own by the end of the first month? Does it have no step that can't be taken back? Can someone on your team demonstrate it?
How to create the process map with your team and pick process no. 1 from it is covered in detail in Creating a process map: an example and choosing process no. 1. The obvious move is to start with the process that annoys you most right now. But that's often the one with the most exceptions, which makes it the hardest place to start. The four kinds below have the opposite in common: a clear way in, a clear end, and rules your team can demonstrate.
Four kinds of process that usually fit first
If you apply these three questions to the processes of a business with a team, the same kinds of process often come out on top, in our assessment.
1. Incoming mail and matching
Trigger: A letter arrives, scanned in the office or by a scanning service, or a document comes in as a PDF by email right away.
What the AI employee does: It picks up the document, reads it, recognizes what kind it is and matches it: which client, which property, which case. After that, the person responsible knows about it.
What the person keeps doing: They get the cases the AI employee can't match with certainty, and everything that needs a decision. Someone still scans the paper mail.
What has to be in place beforehand: Who on the team gets which mail, and a filing system that makes sense: folders, a document management system or your industry-specific software. If that doesn't exist yet, it gets defined first.
Incoming mail comes first because it arrives every day, follows fixed rules and is easy to measure. Today, it often depends on one person. If they're sick or on vacation, the pile just sits there.
2. Filing receipts and notices
Trigger: A receipt or a notice is in the inbox, digital or as a scan.
What the AI employee does: It recognizes what kind of document it is, enters the details that are needed and files it where your team looks for it, in the filing system you already have.
What the person keeps doing: They get anything that doesn't fit a known variant by email, explain the case in the feedback session and read the completion email.
What has to be in place beforehand: A list of the document types that come up, and for each one, where it belongs. The rare types count too. They're exactly the ones that cause trouble later.
Filing works well as process no. 1 because the end is clear: the document is in the right place, or it isn't. That can be checked on every run.
3. First replies to recurring inquiries
Trigger: An inquiry comes in, by email or through the form on your website.
What the AI employee does: It reads the inquiry, pre-sorts it (new client, existing client, complaint, appointment request) and prepares a reply that fits your business's rules.
What the person keeps doing: They sign off the reply. An email to a client can't be taken back. That's why, with us, there's an approval point in front of this step: the AI employee stops until a person explicitly says yes, for every single case.
What has to be in place beforehand: The rules your business follows when it replies, for example what a new client hears first and what happens with a complaint. Plus the person who signs off, and a deputy, so the replies don't pile up while that person is on vacation.
Even with an approval point, a lot is left over. The reading, sorting and drafting fall away. Your team only reads and says yes, or corrects. "Answering and sorting inquiries" is listed on our home page among the processes where it often starts.
4. Reports and summaries
Trigger: A fixed schedule, for example every Monday morning or at the end of the month.
What the AI employee does: It collects the numbers and the current status from the systems you use, summarizes them in a fixed structure and sends the report to the set recipients on the team, for example to you and to the head of a department.
What the person keeps doing: They read and decide. The report prepares a decision. It doesn't make it.
What has to be in place beforehand: A fixed structure that stays the same for every recipient, and for every number, the place it comes from.
Reports are a good start because they stay internal and don't change anything in your systems. A mistake in a report only has consequences once someone makes a decision based on it. That's why, with us, every line of a report points to its source, so you can look it up without having to ask. "Pulling reports together" is listed on our home page among the processes where it often starts.
What the four have in common
The four kinds of process aren't a list you have to work through. They show what to look for in your own process map:
- They come up often. Daily or weekly, so the AI employee quickly gets to four clean runs.
- They have a clear way in. A letter, an email, a date in the calendar.
- Their end can be checked. Filed or not, answered or not, sent or not.
- Their risk is low or covered. Either there's no step that can't be taken back, or there's an approval point in front of it.
- Your team can demonstrate them. The rules are in the heads of the people who handle the process today.
If you find a process with these five features that isn't listed here, it's just as good a candidate. A process that only you know probably doesn't belong at the start. It's harder to demonstrate, and that's usually exactly where the business depends on you.
When one of the four doesn't fit first
Even a kind of process that often fits can be the wrong one for you. Here are three cases where that happens:
There isn't enough of it. If only a few letters a week arrive at your business, it usually isn't worth it, unless you simply want to get the task off your plate.
There's no filing system that makes sense. An AI employee files things where your team looks for them. If there's no such place, one has to be defined first.
The reply depends on your judgment. If every inquiry is a one-off case that needs your assessment, the first reply is thinking, not doing. Then it stays in conversation.
What this looks like for us
At a tax advisory firm, the first two processes belong to two of these four kinds: filing and incoming mail. Process no. 1 was filing digital tax assessment notices. Up to 30 to 40 arrived there a day, and before, the office team needed about 2 minutes per notice. Looking back, the process fits the three questions above exactly: the notices arrived digitally, filing doesn't send anything outside the firm, and the office team could demonstrate the rules.
Process no. 2 was the notices that arrive on paper. They reach the firm's inbox by email. A second AI employee checks the inbox every 30 minutes, spots the emails with paper notices and hands them over to filing. That's incoming mail with matching, just for one particular kind of mail. Both processes are at Autonomy Level 2, Autopilot (as of September 2026).
The reason it became two processes was the way in. The digital notices and the paper notices start in different places. That's why there are two processes, with a handoff between the two AI employees.
In Kevin's own business, 14 AI employees work on tasks such as bookkeeping prep, leads and email. An AI manager reviews their work; that role is still on trial.
For first replies to inquiries and for reports, we don't have a client case yet that we can show here. That's why these two kinds are presented as our assessment.
Runs without me
Every two weeks, one process that runs without the owner: what came in, what the AI did, where a person decided. Two minutes to read.
Worksheet
Process Potential Check
With five questions and a first process list to fill in, you find the process that could run on its own first. Comes as a PDF by email once you confirm your sign-up.
Strategy session
In a 20-minute strategy session, you tell us where things get stuck. We'll tell you honestly whether an AI employee is a good fit for you.
Book a strategy sessionFrequently asked questions
Can I tackle all four at once?
We advise against it. With us, one process comes after another. Only once it's running does the next one follow. In Owner Autonomy, the 90 days belong to one process. Once it runs on Autopilot, the next one is up.
What if my most important process isn't one of the four?
Then your rating is what counts. The four kinds are a starting point for the search. If a different process comes out on top for you and passes the three questions, we start with that one.
Who decides which process is no. 1?
You and your team, together with us. The rating gives you a proposal, and the decision is made together. By day 14 at the latest, we lock in your process in writing.
What happens after the choice?
The process is defined by five points, the AI employee is trained and signed off after four clean runs. The whole road is described in How to automate business processes when you have a team: the path in six steps. What process automation covers in the first place and where a person stays involved is in Process automation in a business: what works without developers and where a person stays involved. And what a process looks like that starts on its own and reports back at the end is shown in Autonomy Level 2, Autopilot: the process starts on its own and reports back at the end.
Before automating: take a look at the process
Sometimes the process map shows that a process should first get simpler before it's automated, because three people do the same thing twice or a step no longer helps anyone. Kevin describes how he approaches this kind of process optimization on his blog: Process Optimization With AI: The Method.
Your next step
With us, automating business processes starts with the question of which process goes first and why. If you want to sort that out for your business, we'll look at your processes together on a call.