The work flows on its own. A person stands only where the river forks.
Operating model

AI-native operations: design the work around the result, not the task

Why faster steps leave the old organisation in place, how to plan work from the result down, and the four numbers that decide how far to trust the system.

No status reports to read. One decision to make.

A manager gets a request, and AI helps sort it. The manager prepares an offer, and AI helps write it. The manager checks a status, and AI writes a short summary. The director needs a report, and AI formats it.

Every step is faster now. Yet the manager still carries the context from one system to the next, starts every action, watches whether it happened and puts the whole picture together by hand. The steps were sped up. The way the work is organised stayed the same.

That is an AI-assisted company. An AI-native company starts somewhere else: with the question of how the work should run at all, once a machine can do a large share of the thinking.

Check where your company is today

Five questions about one process you know well, such as handling a customer order from request to delivery. It takes two minutes.

Self-check · 5 questions

Is this process AI-assisted or AI-native?

Think of one process that runs every day: an order, a supplier payment, a customer request.

1 / 5 · The resultIs the expected result written down, with its deadline, limits and what counts as done, rather than only a list of tasks?

Your answers stay in this browser. We count only which button was pressed, never anything you type.

Most processes score one or two. That is the normal starting point, and it shows where to build first.

We automate the wrong thing

Faster pumps, and the buckets are still carried by hand.

The usual approach takes an existing process, finds one step that AI can speed up and adds a model there. Then the next step, and the next. Each tool helps, and none of them changes who holds the work together. That job stays with people: remembering what was promised, noticing what is late, deciding what happens next.

In an AI-native model the roles swap. People set the goals, the rules and the limits. A managing layer keeps the context, runs the connected actions, watches for anything going off course and brings a person in when a decision is needed.

Who carries the work between systems

On the left every handover between systems runs through one person. On the right the systems keep doing their own jobs, and only decisions travel up.

Plan from the result, not from the tasks

Every channel is drawn back from the garden it must reach.

Most companies are organised around tasks: call the supplier, check the payment, confirm the date, update the CRM, prepare the report. The owner does not need any of those actions. The owner needs a result, for example: the goods reached the customer on time, at the agreed margin and without unacceptable risk.

An AI-native process is designed from that result down. For each case the system works out what is already known, what is missing, which actions are allowed and which decisions need a person. Tasks do not disappear. They follow from the result, and they stop being the way the business is organised. People stop being the routers who must pass every step along by hand.

The loop every case runs

People own the beginning of the loop and its exceptions. The stations in between need nobody to pass the work along.

Example: one order at a trading company

A request for a delivery comes in. In the usual setup a manager starts a chain of actions: checks the customer, asks suppliers for terms, compares the offers, talks to the freight team, watches the payments, updates the statuses and tells the owner when something goes wrong.

In an AI-native setup the request gets its own digital case manager: an agent responsible for moving it forward. It keeps the state of the case and works out the next allowed step, without going beyond the rights it was given.

One order, three kinds of workers

The owner should not receive a list of tasks and overdue items. The owner should receive a decision, already framed:

The difference is that nobody has to keep asking the system what is happening. The system brings the situations that need a decision to the person who must make it.

One prepared decision, instead of a pile of reports.

This works only under three conditions: the data is confirmed, the AI’s rights are limited, and the system can say “I am not sure”. Without them, the result is not control. It is a convincing imitation of control.

Five parts of an AI-native platform

Each of the five parts answers a question that, in an AI-assisted company, a person answers from memory every day. If you took the test above, the parts your process is missing are marked.

Explore the five parts

What an AI-native platform is made of

What must be achieved?

The result for each kind of case, with its limits: the deadline, the cost, the quality and the risk that is acceptable. Without it the system can only follow tasks, and nobody can tell whether a case went well.

Example: a trading company

An order is done when the goods are with the customer on the agreed date, the margin is within the agreed range and the payment is matched.

\1

Four layers of an AI-native company

AI sits at the centre of coordination, not at the centre of the books. Anything that must be exact every time runs in ordinary software underneath it.

There is no need to replace those systems at once. That path is expensive and risky. It works better to build a managed layer of cases on top of them and widen its freedom step by step.

Read also · 11 minHow an AI agent earns permissions: read, advise, draft, record, executeThe fourth part in detail: five levels of permission and how an agent climbs them.

The organisation changes too

If the system can carry a large share of routine operations, a harder question follows: why keep an organisation built around passing information by hand?

Some roles exist today because someone has to carry information between departments, check statuses, remind people of what they promised, collect reports and notice when things do not match. Over time a manager’s job moves from coordinating by hand to looking after a portfolio of results, handling the exceptions and improving the rules the work runs by.

Cutting staff should not be the goal. The goal is to let the business handle more without coordination costs growing at the same pace.

The trap: autonomy for its own sake

A lot of movement, and nothing grows.

It is possible to build an impressive system in which dozens of agents talk to each other all day and the business gains nothing. So an AI-native process is judged neither by the number of agents nor by how independent they are. It is judged by four numbers.

\1

Five steps of freedom, and a ceiling

Freedom is given one step at a time, and the four numbers decide when. The ceiling does not move.

Your plan for this week

Your checklist

Steps for this week

0 / 0
    Take the two-minute test to make this list yours

    Ticks stay in this browser.

    Choosing agents, frameworks and tools comes later. The first piece of architecture is the operating model: people, agents and ordinary software as three kinds of workers, each doing what it does best. A company used to be an organisation of people who use software. An AI-native company becomes a system for reaching its goals, in which people, agents and software work together.

    Questions readers askAnswers written by the SORP team

    Pick a question and we will answer it here.

    Not on the list? Ask the team your question

    Was this article useful?

    Where to go next

    More from the blog

    Talk to us

    Step 1 of 3
    What would you like to do?

    Rather talk first? Book a 30-minute call