How to automate business processes when you have a team: the path in six steps
Working out how to automate business processes sounds like a question about technology. In a business with a team, it's first a question of working together: who knows the process, who decides what goes first, who teaches the AI employee how it's done, and who signs it off? If you work on your own, you usually settle this with yourself. In a business with 3 to 15 employees, several people are involved, and each one has a different role. In this article, we describe the path we take with businesses, in six steps. For each step, you'll see what you do as the owner, what your team does and what the AI employee does.
Before you start: who's involved
With us, two people from your business are at the table from the start: you and one person on your team who looks after the AI employees. In the Owner Autonomy program, both of you join the 1:1 with Kevin every week.
This second person matters more than it might seem at first. They know the workflows from everyday work, they'll later answer the cases from the escalation path, and they can be the contact person named in an AI employee's job description. Without them, automating your processes ends up depending on you again.
Step 1: The process map with your team
It all starts with a list of every recurring process in your business: who does what, how often, how long it takes, how it starts, which system the work happens in and what's annoying about it.
- You, as the owner: draw up a first list, area by area, and tell your team openly what the questions are for.
- Your team: adds what you don't see. In short conversations, every person who does recurring work answers what they do daily, weekly and monthly, how it starts and how long it takes.
- The AI employee: isn't involved yet. It only comes in once it's clear which process it will take over.
How the process map is structured in detail and which questions you ask your team is covered in Creating a process map: an example and choosing process no. 1.
Step 2: Thinking or doing
Every entry on the process map gets sorted. Does someone need to think along here, or does it simply have to get done? Work that needs thinking stays in conversation. Work that simply has to get done goes onto the autonomy levels.
- You, as the owner: sort the entries and make sure not everything ends up under "doing" just because it feels like relief.
- Your team: says where it actually has to think while working and where it works by fixed rules. It often knows this more precisely than you do.
- The AI employee: still isn't involved at this point.
If something is unclear, it's often two processes in one. Then the entry gets split.
Step 3: Choosing process no. 1
Only the processes that simply have to get done go into the rating, by time, money, risk and feasibility. That produces a ranking. The ranking is a proposal, and the decision is made together.
- You, as the owner: decide with us in the 1:1 which process becomes no. 1. Nos. 2 and 3 get noted down for later.
- Your team: checks whether the chosen process can really be demonstrated, and names the person who handles it most often today.
- The AI employee: keeps waiting. Only once the choice is made is it clear which role it will get.
Which kinds of process, in our assessment, often come out on top in businesses with a team is covered in Business process automation examples: the four processes a business with a team tackles first. In the program, we lock in your process in writing by day 14 at the latest.
Step 4: Writing the process profile
Now process no. 1 gets described so that an AI employee can take it over. To do that, we first watch how your team handles it today and collect all the variants. That produces the process profile, our word for a process description: trigger, start, work for each variant, end, reporting, plus hard limits and the escalation path.
- You, as the owner: set the hard limits. What must the AI employee never do, and where does it need a yes from a person first?
- Your team: shows, on a normal day and with real input, how it handles the process, and explains out loud what it does and why.
- The AI employee: gets its job description. Role, tasks, permissions and limits are put in writing, along with the contact person on your team.
For the hard limits, a house rule applies with us: we keep a human involved when decisions are about people, about money or about anything with legal consequences. What a process profile looks like in detail is covered in How to document business processes: the template for handing a process to an AI employee.
Step 5: Training and sign-off
Now the AI employee comes in. It's trained the way a new person on the team is trained.
- You, as the owner: decide who gets the report, and at the end, you sign off too: which process, from when it runs on its own, with a name and a date.
- Your team: sits alongside and demonstrates every variant once. It answers the cases from the escalation path and explains them in the feedback session. After sign-off, it watches alongside for a while.
- The AI employee: learns one variant at a time, saves each one as a rule and sends anything it doesn't know to a person. It's signed off after four clean runs. After that, it runs side by side for a while, with someone who checks every result, and only then on its own with a completion email.
As long as your team checks every run, the process is at Autonomy Level 1, Assisted. Once it runs on its own with a completion email, it's at Level 2, Autopilot: it starts on its own on a schedule or trigger, runs through to the final report and hands anything uncertain to a person.
What comes after that with Level 3, Audited, and Level 4, Autonomous, is covered in The four autonomy levels: how a process in your business runs on its own.
Step 6: Reports and the monthly review
Our home page says when a process is done: when it starts without a nudge, runs through to the end and sends you a report. So that you can rely on that without following up, there are two things.
The report for each run. Without a report, you end up following up yourself, and you're back to managing every step.
After every run, the completion email shows what's done, what's still open and where there was an exception.
The monthly review. For every process, you can see which level it's on. Once a month, we look at it together and decide what comes next.
- You, as the owner: read the reports and decide in the monthly review which process comes next.
- Your team: signs off where a person has to say yes, and reports where it still had to step in.
- The AI employee: sends its report after every run and reports exceptions through the escalation path.
Then it's back to step 3, with process no. 2. What you should keep an eye on after automating is described in Keeping automated processes under control: reports, exceptions and the monthly review.
What the timeline looks like
How long the individual steps take depends on the number of variants and on how often the process comes up. In Owner Autonomy, the 90 days belong to one process. We work with guideline timings that we adjust in the 1:1:
- Month 1, map and lock-in: the process map with your team, locking in your process in writing by day 14 at the latest, then defining it by the five points and setting up access.
- Month 2, training: setting up the AI employee, walking it through every variant, testing the escalation path. Then the clean runs count, and your team watches in parallel.
- Month 3, sign-off and Autopilot: after four clean runs and about a month of watching in parallel, we sign it off. Goal after 90 days: your process starts on its own and reports back with a completion email.
- After that: once your process runs on Autopilot, the next one on your map is up.
The only commitment in all of this is what our guarantee says: if your process isn't running on Autopilot (Autonomy Level 2) after 90 days, Kevin will keep working with you at no extra cost, as long as you come to the 1:1 every week, complete the agreed actions and name one person on your team. Everything else is a goal.
What this looks like for us
At a tax advisory firm, we went through steps 4 and 5 for two processes: process profile, training and sign-off. The process map, sorting, rating and monthly review, meaning steps 1 to 3 and 6, are steps from our Owner Autonomy program. For the tax advisory firm, they aren't documented as separate work steps, so here we only describe the part that is documented.
Process no. 1 was filing digital tax assessment notices, up to 30 to 40 a day. First, Kevin watched the office team: which types of assessment there are and how each one gets filed. The notice process distinguishes around 45 rules.
Then the AI employee was trained, one type of assessment at a time, with someone sitting next to it. Anything it can't match with certainty goes to the office team by email, followed by a feedback session. It was signed off after four clean runs, and after that, the team watched alongside it for a while. Today, filing runs on its own, and Kevin gets completion emails.
Process no. 2 is the notices that arrive on paper. They reach the 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 a handoff: a task passes through two steps, and the AI employees hand it off to each other. Both processes are at Autonomy Level 2, Autopilot (as of September 2026).
The monthly review is a fixed part of Owner Autonomy. We don't have documented results from these monthly rounds yet. And Kevin is currently trying out the next step, Level 3, in his own business: 14 AI employees work there, and an AI manager reviews their work; that role is still on trial.
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 skip steps?
We advise against it. Without a process map, you often start with the most annoying process instead of the one with the biggest lever. Without a process profile, variants are missing, and the AI employee falls back on the escalation path at the first special case. The steps can be short. You shouldn't leave any of them out.
How much of my team's time does this take?
The most in steps 4 and 5, when watching, demonstrating and answering the first escalation emails. After that, it should get less: with every variant it learns, the AI employee asks less often. We can't give you a number of hours in advance. It depends on your process.
What if a process makes mistakes after sign-off?
Then it goes back a step. The case gets trained in, and your team watches alongside again until the runs are clean again. In the monthly review, the process is entered at the level it has actually reached.
Where do I start if I don't use AI at all yet?
Then the first step is smaller than a whole process. Kevin describes how to bring AI into a small business in the first place on his blog: Bringing AI to a Small Business. This article is about the next step: whole processes that run on their own. What process automation covers in a business with a team is in Process automation in a business: what works without developers and where a person stays involved.
Your next step
For us, automating processes means six steps, one process after another, with your team. If you want to know what that would look like in your business and which process goes first, we'll look at it together on a call.