Skip to content

Autonomy ladder

Agents that earn autonomy

Our engineers build each agent for one workflow, and it starts by helping the person at the desk. The workflow moves up one level at a time, only after it has shown it can be trusted, and it can always be moved back down.

01 The five levels

Five levels, from recorded to autonomous

A level belongs to one workflow, not to an agent and not to your company as a whole. Sales order entry can be at Level 3 (Supervised) while AP invoice matching is at Level 1 (Assisted).

Illustrative example

The worked example below is sales order entry: a customer emails a purchase order, and it has to become a sales order in your ERP. A typical case, not a specific client.

  1. Level 0 Recorded

    People do the work. The software captures it as structured data.

  2. Level 1 Assisted

    People do the work. Agents draft, summarize and answer questions.

  3. Level 2 Prepared

    Agents prepare each transaction in full. A person approves every one.

  4. Level 3 Supervised

    Agents complete the work within set limits. People handle exceptions and spot-check.

  5. Level 4 Autonomous

    Agents run the workflow end to end. People set policy and audit.

  • A workflow moves up one level at a time, and only after a promotion review.
  • The workflow owner can move it down a level at once.
Fig. 1 The five levels. Each one is described below.

Level 0

Recorded

People do the work. The software captures it as structured data.

Sales order entry at this level

The order desk keys orders into a screen that records every field and every correction.

No agent is involved yet. The point of this level is the record it keeps: what a correct order looks like for each customer, where the corrections happen and how long an order takes.

The agent
None yet.
Your people
Do the work as they do today, on a screen our engineers build with them.
Reaches the ERP
Only what a person keyed.
Before moving up
The agent drafts from the same documents your people worked from, and its drafts are compared with what they entered. Nobody at the desk sees a draft until the review is passed.

Level 1

Assisted

People do the work. Agents draft, summarize and answer questions.

Sales order entry at this level

An agent reads the emailed purchase order and drafts the order. The order desk checks it and keys it.

The person still does the work. The agent saves them the reading and the looking up, and each difference between the draft and what was keyed is counted.

The agent
Drafts, summarizes and answers questions about the work on the screen.
Your people
Check the draft and key the transaction themselves.
Reaches the ERP
Only what a person keyed. The agent writes nothing to the ERP.
Before moving up
How often the agent's draft matched what the person keyed, field by field.

Level 2

Prepared

Agents prepare each transaction in full. A person approves every one.

Sales order entry at this level

The agent builds the complete order. A person reviews it and approves it.

Every order gets its own approval, and nothing is written to the ERP without one. The order desk's work shifts from keying to checking.

The agent
Prepares each transaction in full, with every check run and anything it is unsure of marked on the field.
Your people
Approve, correct and approve, reject, or pass it on to the person with the authority to decide. There is no approve-all.
Reaches the ERP
Nothing without a person approving it first.
Before moving up
How often a person approved the prepared transaction without changing it, and what they changed when they did.

Level 3

Supervised

Agents complete the work within set limits. People handle exceptions and spot-check.

Sales order entry at this level

The agent enters orders that match the price list and the credit limit. Mismatches go to the order desk.

Anything outside the limits goes to a person too, such as an order from a customer who is not on the list. From this level a person sees the exceptions and a sample, not every order. That is the biggest step on the ladder.

The agent
Completes the cases that are inside its limits and pass every rule.
Your people
Work the exception queue every day and spot-check a sample of what the agent completed.
Reaches the ERP
What the agent completed inside its limits, and what a person resolved.
Before moving up
What the spot-checks found in the work the agent completed on its own, and which errors surfaced later, such as a credit or a corrected order.

Level 4

Autonomous

Agents run the workflow end to end. People set policy and audit.

Sales order entry at this level

The agent owns order entry. The order desk sets the rules and reviews a sample.

People no longer work the order queue day to day. They decide the policy the agent follows and audit what it did. It does not mean every order: the rules still send some to a person, such as a first order from a new customer.

The agent
Runs the workflow end to end, including the routine problem cases your policy tells it how to handle.
Your people
Set the policy and audit a sample. They still receive what the policy reserves for a person.
Reaches the ERP
Everything inside the limits. The limits, the audit trail and the stop switch still apply.

02 Promotion reviews

Every step up takes a promotion review

A workflow moves up one level at a time, and only after a review. The review is held as soon as the workflow is ready, remotely if need be: enough real work has been measured against its threshold, and the workflow owner wants the next step. It does not wait for a calendar date.

  1. Check 01

    Measured accuracy on real work

    Against a threshold set with the workflow owner and written down before the level started. Nobody adjusts it after seeing the results.

  2. Check 02

    The cost of a wrong action

    What is the worst realistic mistake, how soon would someone notice and what would it take to put right. A workflow can pass on accuracy and still be held back here.

  3. Check 03

    Logged and reversible

    Every action is in the audit trail, and there is a written, tried way to put each kind of action right.

  4. Check 04

    Sign-off by the workflow owner

    The workflow owner decides. Our engineers bring the evidence. They do not make the call.

Three outcomes

  1. Promote. The new level starts with the limits written into the review record.
  2. Not yet. The review names what has to change, such as a rule, a data fix or more evidence for one group of customers.
  3. Stay for good. The workflow owner decides the current level is the right one for the long term.

No numbers on this page

Thresholds are set for each workflow, with its workflow owner. We publish no threshold and no accuracy rate, because a threshold only means something for one workflow at one company.

Down is faster than up

The workflow owner can move any workflow down a level at once. It takes no review and no meeting. Moving back up takes a promotion review again.

03 Limits and controls

What bounds every agent from day one

Every agent has limits, only the access its workflow needs, an audit trail of every action and a stop switch. The emergency stop on a machine is a fair comparison: it is fitted on the day the machine is installed, not after something has gone wrong.

  • Limits

    Amounts, customer and supplier lists, time windows. The operations layer enforces them, not the agent. A case outside them becomes an exception and goes to a person.

  • Approvals

    The approver sees the source document next to the prepared transaction, the checks that were run and what the agent was unsure of. Every transaction gets its own approval.

  • Audit trail

    The record of every agent action, with its inputs, its decision and its result. If the record cannot be written, the action does not go ahead.

  • Stop switch

    Halts the agent at once. The work stays in its queue and people do it by hand. The workflow owner restarts it.

Two ways to pull an agent back

Two ways to pull an agent back
Control What it does Who can do it How fast To undo it
Stop switch Halts the agent. People do the work. Anyone the workflow owner has named, including the people who work the queue every day. At once. The workflow owner restarts the agent.
Move down a level Keeps the agent working with less autonomy, for example back to a person approving every transaction. The workflow owner. At once. A promotion review.

An agent that enters sales orders can read customers, items, prices and credit status. It cannot change a price list or raise a credit limit. A limit changes only with the workflow owner's sign-off, and the change is recorded.

04 Where it stops

Not every workflow should reach Level 4

Some stay at Level 2 or Level 3 for good, and that is a fine result. A workflow where one wrong action is expensive or hard to put right should stay where a person approves every transaction.

How far each workflow should climb the ladder
Workflow Highest sensible level Why
Sales order entry Level 4 An order is checked again after entry, and one caught before release can be corrected or cancelled.
Quoting, stocked items Level 3 At list or contract price and above the margin floor. Anything else goes to sales, already prepared.
Quoting, made-to-order parts Level 2. Level 4 is rarely right. A price is a commercial decision, and an agent does not read a drawing and decide how to make the part.
Supplier follow-up and keeping dates current Level 4 A wrong follow-up is a polite email sent a day early. A date change that puts a job at risk still goes to a buyer.
Releasing purchase orders Level 3 with tight limits, or Level 2 It commits money.
AP matching, invoices backed by a purchase order Level 3. Level 4 is possible. The rules already exist in your purchase orders and tolerances, and the ERP's own three-way match checks the work a second time.
Invoices with no purchase order Level 2, for good Approving spend is a manager's decision. The agent proposes the coding and a person approves every one.
Releasing payment Stays with people at every level A payment has no way back. Matching an invoice does not approve it for payment.
Production schedule changes Level 2, for good The schedule decides what machines and people do, and not every input is digital.
Cycle counts and schedule information Level 3 People count. The agent issues count lists and posts small adjustments that a recount confirmed.
Order-status replies by email Level 4 The agent reports facts your systems already hold and quotes only confirmed dates.
Returns Level 3 for authorizations. A person always approves the credit. A credit is money leaving, and it should follow goods that someone has seen.

A level belongs to one workflow. Its limits decide which cases the agent completes alone.

05 The people who do the work

What this means for your people

The digital work does get automated, step by step. We say so plainly, and we do not promise that nothing will change.

  • The keying shrinks. Checking, deciding and handling exceptions stay with your people and become most of the job. The hours that keying took are measured and shown to you, and what your team does with them is your decision.
  • They decide how it should work. The person who has keyed orders for fifteen years decides how the agent should key them.
  • Their corrections are the measurement. Each correction is counted, and those counts are what a promotion review looks at.
  • What they know becomes the rules. Which customer always writes the wrong unit of measure. Which ship-to address needs a liftgate.
  • They hold the controls. The workflow owner is one of your employees, and the people who work the queue every day can use the stop switch.

Tell them before we arrive

Tell the people who will be shadowed what our engineers are there to do: learn how the work is done, so that software can be built around it.

Say plainly that the aim is to automate digital work step by step, and that the people who do the work today decide how it should work.

06 What agents do not do

What an agent never does

The ladder applies to fully digital work: work whose inputs and outputs are all digital, such as emails, documents and ERP transactions.

  • Physical work. Agents do not pick, pack, count or move material, and they do not operate machinery.
  • Phone calls. Calls stay with your people. Agents work on the digital part: the email, the document, the ERP transaction.
  • An action with no way back, alone. Releasing a payment is never given to an agent alone.
  • Anything outside its workflow. An agent built for order entry does not answer an AP question because someone asks it to.
  • Change its own limits or its own level. Both belong to the workflow owner.
  • Approve its own work. Where a transaction needs an approval, the approval is always a person's.
  • Write to the ERP by a route the ERP does not support. Every write goes through the operations layer.
  • Act without a record. Every action goes into the audit trail.

Next step

Start with a call with an engineer.

Tell us which ERP you run and the three workflows that hurt most. That is the whole first conversation.