Autonomy Level 4, Autonomous: the week-away test

For a small business owner on vacation, the destination is rarely the issue. The issue is the phone by the pool and the question of whether something at the business is being left undone right now. Inquiries, quotes, approvals, reports: in many businesses with a team, everything crosses the owner's desk. The team waits for them, and a week off is out of the question. That week is exactly the goal we work toward with you, one process at a time. At the end, there's a test whose result you can read in black and white: the week-away test. Pass it with a process, and that process reaches Autonomy Level 4, Autonomous. This article covers how the test is set up, what has to be in place beforehand, what still stays with you afterward and how we work with you to get there.

Why owners can't switch off on vacation

The obvious approach is to manage how reachable you are: name a deputy, set fixed times for calls, put the work phone in the hotel safe. That can save a week. The cause lies elsewhere, though: in the processes.

An owner can't switch off when a process depends on them. That's the case when one of three things is true:

• The process only exists in their head. Nobody else knows how the special cases go, so they get asked.
• Only they can approve. A quote, a payment, a reply to a client waits until they say yes.
• Only they can see whether something is missing. There's no report showing what's done and what's still open. So they check themselves, on vacation too.

How to spot this dependence in your own business is covered in more detail in When the business depends on its owner. For your vacation, it means: a week without you only gets quiet once the processes that normally cross your desk have another path. And whether they have one can be tested. That's the good news: all three causes can be fixed. The process moves out of your head into a process profile, the approval gets a deputy, and the report arrives on its own.

What Level 4 means

A process is at Autonomy Level 4, Autonomous, when it has passed the week-away test and keeps running even when you're away for a week. You then set the goals and handle exceptions.

The key word is "process". Level 4 applies per process, just like every autonomy level. In a test week, the processes that have been prepared for it are tested, and the result applies to each one individually: one passes, another doesn't. In this model, no business as a whole is at Level 4. The goal is a business in which one process after another passes the test. How the four levels fit together is covered in The four autonomy levels: how a process in your business runs on its own.

How the week-away test is set up

We describe the test the way it's laid out in Owner Autonomy. It has three parts: what has to be in place beforehand, what happens during the week and what the result looks like.

Before: what has to be in place

Before the test week starts, six things get checked off:

1. The processes to be tested are set. What gets tested is what was agreed beforehand, not whatever happens to come up that week.
2. The AI manager has delivered four clean morning reports in a row. It's the one that reviews the work during the test week and passes on exceptions.
3. Every approval point has a deputy, and the deputy knows it. An approval point is a spot where a person has to say yes explicitly, for example before a payment.
4. Escalations go to the deputy that week. Anything that can't wait until tomorrow lands with them, not with you.
5. The deputy has a fallback plan. It says where to look, how to restart a run and who takes over by hand in an emergency.
6. The technology the AI employees work on keeps running all week. Sounds trivial, but it's worth its own line.

The deputy is the person on your team who looks after the AI employees with you. They sign off in your place and take over if something fails.

During the week: what happens

The test week has five working days. During that time, you don't step into any of the tested processes: no checking, no restarting, no approving. You may read the morning report if you want to. The deputy is the one who acts.

The deputy keeps a log, one line per day and process:

The last column is the most important one. Every time a person steps in, it gets logged, and the number of interventions is the week's result. The AI manager can prepare the first columns. A person fills in the last one.

Afterward: passed or not

A process has passed the test when five conditions are met:

• It ran every day, as shown by its sign of life.
• Every exception went to the right person and is resolved.
• No case was left unfinished.
• No step that can't be undone went through without approval.
• You weren't needed.

If a process didn't pass, you have your to-do list for next month. Every human intervention has a cause: a missing rule, missing access or a missing deputy. That turns into an optimization run, and after that comes a new test. Level 4 only goes on the map with a "passed".

So even a test that isn't passed moves you forward. Afterward, you know exactly which spots are still holding you back, and you can fix them one by one.

Why Level 4 only comes after Level 3

The test needs two things that only exist at Level 3: an AI manager that reviews the work and passes on exceptions, and approval points that each have a deputy. Without a manager, nobody would notice during the test week if a run was missing. Without a deputy, the process would stall at the first approval point, because our rule is: no answer means no. How the reviewing role is set up is covered in Autonomy Level 3, Audited: who checks the AI when you no longer do?

That's also why the test doesn't come at the start. At Level 1 or 2, it's missing its prerequisites: nobody reviews the reports of all processes in one place, and the approval points don't have a fixed deputy yet.

What still stays with you afterward

Even after a passed test, a few things stay with you:

• The goals. What the process should achieve, how much and at what quality, is up to you.
• The exceptions. Anything the manager isn't allowed to resolve lands with you or your deputy.
• The approval points. A step that can't be undone gets an explicit approval from a person every single time with us, at Level 4 too. Whether that's you or your deputy is up to you.
• The monthly look. Once a month, we look at all processes together and decide what comes next. If a process slips back, the lower level gets entered.
• The work that needs your own judgment. AI employees you develop ideas and concepts with keep working with you in conversation. They aren't on any level and don't take a week-away test.

On top of that come all the processes that aren't there yet. So a week without you gets quieter with every process that passes, and it stays only as quiet as the processes you haven't tested.

What this looks like for us

The week without you is the goal. The road there is a series of steps, and we're already taking the first one: Level 2, Autopilot.

At a tax advisory firm, two processes run at Autonomy Level 2, Autopilot: filing digital tax assessment notices, and the notices that arrive on paper, for which a second AI employee checks the inbox every 30 minutes and hands the emails with paper notices over to filing (as of September 2026). Both start without a nudge, and filing reports back with a completion email. Anything the AI employee can't match with certainty goes to the office team by email. For these two processes, nobody files every single notice by hand anymore in day-to-day work. Only the cases from the escalation path still land with the office team. That's the foundation Level 3 and Level 4 build on.

In Kevin's own business, 14 AI employees are at work, and an AI manager reviews their work. That role is still on trial. Who has which role, Kevin describes in My AI Workforce: Fourteen Employees, One Boss. He tries new levels in his own business first, before they come to yours.

What we commit to and what the goal is

In Owner Autonomy, the road to a week without you is clearly laid out. In the first month, we map your processes with your team, pick process no. 1, train the AI employee and sign it off. Goal: it starts on its own and reports back with a completion email. In the second month, the goal is for process no. 2 to come on board. In the third month, the goal is an AI manager that bundles the reports into a morning report and flags exceptions. Then comes the test: a week without you. From Month 4 onward, the next process on your map is up every month.

We back the first part of this road with a guarantee: if your processes no. 1 and no. 2 aren't running on Autopilot after 90 days, Kevin keeps working with you at no extra cost, as long as you keep the agreement:

• You come to the 1:1 every week.
• You complete the agreed actions before the next 1:1.
• You name one person on your team who looks after the AI employees with you.
• You post your progress in the community every week.

Within the first two weeks, we agree in writing which processes are no. 1 and no. 2. The guarantee covers Level 2, Autopilot, for these two processes. Level 4 and the week without you are the goal we work toward with you after that. There's no commitment and no fixed date for it, but there is a clear road and a test that shows you in black and white where you stand at the end.

From the first test to stepping back

A passed test for one process is a start. If you think further, you end up asking how much of the day-to-day business still has to sit with you at all. The answer is a series of processes that reach Level 2, 3 and 4 one after another, with conditions at every step. What a road like that looks like is covered in Stepping back from your business, one process at a time.

Frequently asked questions

Do I really have to travel for the test?

The test measures whether you're needed that week. Where you spend it is up to you. What matters is that you don't step into any of the tested processes and that the deputy acts.

What if something urgent comes up during the test week?

Then the deputy acts, and the intervention goes into the log. That's exactly what the test is meant to make visible: where a process still needs a person, and why.

How long does it take until the first week-away test?

There's no commitment on that. In Owner Autonomy, it's set as a goal after the third month, after the manager. The only commitment is what the guarantee says: if your processes no. 1 and no. 2 aren't running on Autopilot after 90 days, Kevin keeps working with you at no extra cost, as long as you keep the agreement. Autopilot is Level 2; the week-away test belongs to Level 4.

Does a process stay at Level 4 once it has passed the test?

Only as long as it keeps behaving that way. Once a month, every process gets the level it's at then. If it slips back, the lower level gets entered.

Which process keeps you tied down on vacation?

If a process came to mind while you were reading, one that has you checking your phone on vacation, that's a good candidate for process no. 1. That's exactly where we start. On the call, we look at whether Owner Autonomy is a fit for your business, which process frees you up first and what the road to a week without you looks like for you. For the first round, we're taking on five businesses, and spots are filled through these calls.