Agentic Operations
A new way of working
Agentic Operations · 202601
AI agents × business systems

From operators
to agents

How AI agents change the way we work with the business systems we already run, and what people do instead.

Executive briefing2026
Agentic Operations
01 · The old deal
Agentic Operations · 202602
How business systems work today

The software is fixed. People adapt to it.

01

CRM

Customer records, pipelines and cases in a platform such as Salesforce, with its own screens, fields and rules.

AccountsCasesPipeline
02

ERP

Orders, finance, stock and procurement, each with prescribed steps that must happen in the right order.

OrdersInvoicesStock
03

Ticketing

Requests and incidents routed by queue, category and status, all configured up front.

QueuesSLAsStatuses
The systemPrebuilt, deterministic, the same for everyone
→
So the operatorlearns its screens, its rules and its workarounds
Agentic Operations
01 · The old deal
Agentic Operations · 202603
The cost of that deal

Training never ends, and scale means more operators

Per personevery hire starts the training again
Per changeevery new release or rule retrains everyone
Twice the volume means hiring and training roughly twice the operators.

Onboarding time

New people take weeks before they handle the work on their own.

Turnover

When someone leaves, their skill leaves with them, and the training starts again.

Inconsistent use

Ten people follow the same process ten slightly different ways.

Workarounds

Spreadsheets and side notes fill the gaps the system doesn't cover.

Locked knowledge

The hard cases live in the heads of a few experts.

Hard to raise the bar

Getting everyone to the right skill level, and keeping them there, is the hardest part.

Agentic Operations
02 · The shift
Agentic Operations · 202604
Pull people out of the operating loop

Instead of people learning the system, an agent operates it

01 · READ

Reads the email

Understands the request, whatever the wording.

02 · FILL

Fills the form

Puts the right values in the right fields.

03 · UPDATE

Updates the record

Through the system's own interfaces.

04 · DRAFT

Drafts the reply

Ready for a person to check and send.

Stays the same

  • The CRM, ERP or ticketing system itself
  • Its data, rules and permissions
  • The process the business agreed on

Changes

  • Who clicks through the screens: the agent
  • Who has to learn the system: nobody new
  • What people spend their day on: decisions
Agentic Operations
03 · Skills
Agentic Operations · 202605
Skills become mountable

Write the expected skill once, then mount it on an agent

Training a person
Weeksper person

Classroom time, shadowing and correction, repeated for every hire, after every change, and lost with every departure.

Mounting a skill
Onceevery agent

The know-how is written down one time as a skill. Every agent that mounts it works to the same standard from its first task.

What becomes a skill:
SOPsManualsChecklistsBusiness rulesTemplatesExpert judgement, written down
Agentic Operations
03 · Skills
Agentic Operations · 202606
Scale without hiring

One skill, as many agents as the work needs

ONE SKILLMove-out notice handling
agent 1
agent 2
agent 3
agent 4
agent 5
agent 6
agent 7
agent 8
agent 9
agent 10
agent 11
… N
Illustrative · all running in parallel
01

In parallel

Volume goes up, you start more agents. Capacity follows demand, not headcount plans.

02

Improve once

Fix or sharpen the skill one time and every agent has it at once, with no retraining round.

03

No ramp-up, no drift

A new agent is fully skilled on day one, and agent number fifty works the same way as agent number one.

Agentic Operations
04 · People
Agentic Operations · 202607
People move up

From operating the system to deciding what it does

Agents
Read
Propose
Draft

The repetitive, rule-following work: reading inputs, keeping records current, preparing the next step.

People
Set the goalDecide what good looks like and which rules apply.
Review proposalsCheck what the agent suggests before it happens.
Approve what goes outNothing reaches a customer without a person's yes.
Handle exceptionsTake the unusual cases that need judgement and empathy.

Agents read, propose and draft. People decide.

Agentic Operations
04 · People
Agentic Operations · 202608
Before and after

What changes in the operating model

Before · people operateAfter · agents operate
Who operates the systemTrained staff, screen by screenAgents, through the system's own interfaces
How skill is acquiredTraining each person, over weeksWritten once as a skill, mounted on every agent
How you scaleHire and train more operatorsRun more agents in parallel
ConsistencyVaries by person, shift and experienceSame skill, same standard, every time
Change managementRetrain everyone, then chase adoptionUpdate the skill once; live everywhere
Where people spend timeRe-keying data and following stepsGoals, reviews, approvals and exceptions

The business system itself does not change. Only who operates it does.

Agentic Operations
05 · In practice
Agentic Operations · 202609
Use case · a tenant's move-out notice

Real cases are not deterministic. That is why the back office still needs people.

What actually happens
  • The tenant sends incomplete data: a date, but no time
  • The tenant changes their mind, twice
  • The employee updates the date after a phone call
  • Email, phone, letter: every case takes its own path
Unpredictable · non-deterministic
So people sit in the middle
InterpretWork out what the tenant actually means
OperateRe-key it into the system, step by step, for the admin
And make mistakesA wrong date, a missed rule, a reply forgotten
The business system
  • Fixed forms and fields
  • Fixed rules and statuses
  • Fixed steps, in a fixed order
Deterministic · cannot handle the mess, or handles it badly
Agentic Operations
05 · In practice
Agentic Operations · 202610
Use case · with an agent

The agent takes the non-deterministic part. People decide and audit.

Before
  • An employee reads every email and call note
  • Re-keys the dates into the system by hand
  • Checks the notice rules from memory or a manual
  • Writes each reply from scratch
The employee does every step
After · the agent
1 · ReadsEach email or call note: incomplete, changed, or unclear
2 · UpdatesThe one move-out form, logged and undoable
3 · Checks in codeThe notice rules: periods, deadlines, conditions
4 · ProposesThe next step, with the email already drafted
The employee
  • Decides on the proposed step
  • Audits what the agent changed: logged, undoable
  • Approves and sends
Decides and audits, instead of re-keying
Agentic Operations
06 · Guardrails
Agentic Operations · 202611
What keeps it safe

The agent is new. The controls are not.

01

Deterministic core

The system of record stays exactly as it is: the source of truth.

02

Same APIs, scoped

Agents act through the same interfaces, with permissions like any user.

03

Logged and undoable

Every change is recorded, attributable and can be reversed.

04

Human approval

Anything outward-facing waits for a person's approval.

05

Rules in code

Business rules are checked by code, not left to the model.

The model does

Reading, interpreting and drafting: the parts that need language.

The model does not

Decide on deadlines, amounts or eligibility, or send anything to a customer on its own.

Agentic Operations
07 · Getting started
Agentic Operations · 202612
How to start

Start with one process, prove it, then expand

Choose
1

Pick one process

High volume, clear rules, a lot of re-keying today.

Capture
2

Write down the skill

Turn the SOPs, rules and expert know-how into one skill.

Mount
3

Mount it on an agent

Give the agent scoped access to the system's APIs.

Control
4

Keep a human approving

Every outward step is reviewed until trust is earned.

Learn
5

Measure

Time per case, edits per proposal, errors caught, staff time freed.

Grow
6

Expand

Next process, same pattern. Improve each skill as you go.

Each step is small and reversible. The first process is the template for every one after it.

Agentic Operations
Next steps
Agentic Operations · 202613
The takeaway

Stop training people to fit the system. Teach the system once, through the agent.

Choose

Name one process to run with an agent this quarter.

Own

Give it an owner who writes and maintains the skill.

Guard

Agree the guardrails: scoped access, logging, human approval.

Decide

Review the results together, then decide what to expand next.