Blog

Process automation in a business: what works without developers and where a person stays involved

Process automation means that a recurring workflow in your business starts on its own, runs through to the end and reports back with a result. Nobody on your team has to kick it off, work through it step by step and let everyone know afterwards. Many people say business process automation and mean the same thing. This article is about the question owners with a team ask: how much of this works in a business with 3 to 15 employees and no developers of its own, and at which points does a person stay involved?

What a process is, before you automate it

Before anything can run on its own, it has to be clear where it starts and where it stops. We define every process by five points:

  • Trigger: What starts it, a fixed schedule or an event, such as an incoming email.
  • Start: What exactly is on the table when the work begins.
  • Work: The steps, for each variant separately.
  • End: How you can tell the process is finished, and what it has produced.
  • Reporting: What you get at the end.

There's also a sixth part, the escalation path: if the AI employee is unsure, it sends the case to a person on your team. In a feedback session, the AI employee is trained on the new variant, and it's saved as a rule.

These points sound like a form to fill in. In our experience, though, this is exactly where automation often gets stuck. "Customer service" isn't a process. It's a whole area of work. "Accept a complaint by email and pass it on to the warehouse" is a process. Only once the start and the end are fixed can you check whether the automation has done its job.

Three ways processes get automated today

If you look into process automation, you'll come across three ways of working. They don't rule each other out, and they often run side by side. The first is fixed if-then rules that connect programs with each other. The second is click robots that copy what a person does in an on-screen form. The third is AI employees that can also read letters, emails and notices that look different every time. Our way is the third. With us, an AI employee is hired like a new member of staff, with a job description, a trial task and a permanent position. After that, it's led like a team, with fixed rules, reports and review steps. Which way of working fits which process is covered in Intelligent process automation: workflow tool, RPA or AI employee, and which fits when. What changes with AI compared to fixed rules is described in AI process automation: what changes with AI compared to fixed rules.

What you can automate in a business with a team

Businesses with a team have a lot of work that simply has to get done. It has a clear way in, recurring steps and a result you can check. In our experience, this mostly comes down to five activities, which are often linked within one process:

  1. Incoming: Letters, emails and downloads from portals arrive.
  2. Sorting: What is it? An invoice, a notice, an inquiry, a reminder, advertising?
  3. Matching: Which client, which case, which person does it belong to?
  4. Filing: It ends up in the place where your team looks for it.
  5. Reporting: Someone finds out what's done, what's still open and where there was an exception.

Which four kinds of process we usually tackle first in businesses with a team is covered in Business process automation examples: the four processes a business with a team tackles first.

Thinking or doing

Not every recurring task should run on its own. For every process, we ask one question: does someone need to think here, or does it simply have to get done? A quote for a new major client needs your judgment. Gathering the documents for it can simply get done. Work that needs thinking stays in conversation, with you or with an AI employee as a thinking partner. Work that simply has to get done goes onto the autonomy levels.

How to collect every recurring process in your business and sort them this way is covered in Creating a process map: an example and choosing process no. 1.

Where a person stays involved

Even with process automation, a person still checks in with us, at points fixed in advance. For this, a house rule applies at every level: we keep a human involved when decisions are about people, about money or about anything with legal consequences. The AI employee may prepare and put things together. A person decides and signs off.

Then there are steps that can't be taken back: a payment, a submission to a public authority, an email to a client. In front of a step like that, there's an approval point. The AI employee stops until a person explicitly says yes, for every single case. If no answer comes, nothing happens.

And then there's the escalation path. It comes into play when the AI employee doesn't recognize a case. It doesn't guess. It hands the case to a person on your team. So your team stays part of the workflow, just at different points than today: it answers the cases from the escalation path, signs off where a person has to say yes, and reads the reports. The goal is that your team only approves.

What works without developers, and what doesn't

The good news for owners without an IT department: the hard part of process automation is rarely the technology. Whether an AI employee can get access to a system can usually be sorted out. Whether your team can explain the rules decides whether the process will be running soon.

What works without developers is what your team can already do: show how it handles the process today, demonstrate every variant once, answer the uncertain cases, check runs and sign them off. The rules are written in plain language, from what your team explains while we watch. With us, you don't need to program. We build everything together in the 1:1, with ready-made AI employees as building blocks, and one person on your team looks after them with you.

It still doesn't work entirely without technology. Someone has to decide where the AI employee runs, which access it gets and whether it may only read or also write. In Owner Autonomy, we sort that out with you. Your documents stay in your own filing system. We don't run servers for you. We help you set up the AI employees on your side. In the first sessions, we decide together where they run, which models they use and how far this can be set up in line with data protection rules.

The road to the first process

With us, the order is fixed. It's the same order in which the first month of Owner Autonomy runs.

  1. Process map: Together with your team, you collect every recurring process: who does what, how often, how long it takes, and whether it needs thinking or simply has to get done.
  2. Process no. 1: From that map, we pick the process with the biggest lever. It's rated by time, money, risk and feasibility.
  3. Process profile: The process is defined by the five points, plus variants, hard limits and the escalation path. The process profile is our word for a process description. How to write one is covered in How to document business processes: the template for handing a process to an AI employee.
  4. Training in four steps: watch how the team does it. Sit alongside and show every variant once. Remember and ask, through the escalation path and the feedback session. Sign off after four clean runs, then monitor side by side, then let it run on its own with a completion email.
  5. Levels: From then on, you can see which level each process is at.

The levels describe how far a single process runs on its own. At Autonomy Level 1, Assisted, the AI employee does its task when someone starts it, and your team checks every run. 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. After that come Level 3, Audited, and Level 4, Autonomous. All four, with their review questions, are covered in The four autonomy levels: how a process in your business runs on its own.

Only once a process is running does the next one follow. That turns process automation into a series of processes that each run on their own and are each checked on their own, one after another.

If you'd first like to see which individual tasks can be automated with AI at all, you'll find hands-on examples on Kevin's blog: Automating Processes With AI: 8 Examples. This article is about the road in a business with a team, where several people are involved in one process.

What this looks like for us

At a tax advisory firm, the first process was filing digital tax assessment notices. The notices that arrive on paper were added after that. Up to 30 to 40 digital notices arrive there a day, and before, the office team needed about 2 minutes per notice.

The notice process distinguishes around 45 rules, because there are many types of assessment, different types of tax, and letters from the city that look different from each other. First, Kevin watched the office team: which types of assessment there are and how each one gets filed. Then the AI employee was trained, one type of assessment at a time, with someone sitting next to it.

A second AI employee checks the inbox every 30 minutes, spots the emails with paper notices and hands them over to filing. Filing 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 reports back with a completion email. Anything the AI employee can't match with certainty goes to the office team by email, and the AI employee is trained on it afterwards. Both processes are at Autonomy Level 2, Autopilot (as of September 2026).

For incoming mail, the steps are the ones described above: letters, emails and portal downloads come in, get sorted, matched and filed, and someone gets a report at the end.

In Kevin's own business, 14 AI employees work in these roles:

  • Content
  • SEO
  • Video editing
  • Bookkeeping prep
  • Leads
  • Email

Each one has a personnel file, a fixed role and clear limits. An AI manager reviews their work; that role is still on trial. Kevin tries new levels in his own business first, before they come to yours.

Frequently asked questions

Is process automation the same as business process automation?

In everyday use, mostly yes. Both terms mean that a recurring workflow runs on its own. What matters more than the term is whether the start, the end and the report of the process are fixed.

Do I need new software for this?

Not for filing. An AI employee works with the filing system you have today: folders, a document management system or your industry-specific software. Whether your software can be connected is something we check on the call.

Does process automation replace employees?

It takes routine work off your team's plate: reading, sorting, matching, filing. The cases from the escalation path, the approvals and the decisions about people, money and legal consequences stay with your team. At the tax advisory firm, the office team still answers the cases the AI employee can't match with certainty.

How long until the first process is running?

Owner Autonomy has 90 days and one goal: your process runs on Autopilot, which means it starts on its own and reports back with a completion email. Our guarantee reads: 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. Anything beyond that is a goal, not a commitment.

Your next step

With us, process automation starts with a list of your processes. If you want to know which process in your business could be the first to run on its own, we'll look at it together on a call.