Report

Inside the Agentic Enterprise

How to automate your organisation

For the people leading an agentic transformation. What an agentic enterprise is, why most AI programmes stall short of production and what the ones that work built instead.

16 minute read

TL;DR

Redesign the work, then let agents run it

  1. Intelligence is a commodity. Every competitor rents the same frontier models at the same price.

  2. Having it is not the same as gaining from it. Nearly every large organisation now uses AI and very few earn real value from it. What sets those few apart is the wiring they built around the model.

  3. The wiring is the redesign. Each workflow is written down step by step, with every step going to an agent, to plain code or to a person. One layer carries the work across your systems.

So automating your organisation is a design and engineering job: deciding where agents act and where a human stays in the loop, then building the system that runs it.

00 · Introduction

Everyone has the magic box

For a few pounds per million tokens you have the same frontier models as your fiercest competitor, improving at the same pace, on the same day they ship.

Which means the differentiator has moved from the model doing the automating to what it automates: your organisation. Every factory could buy electricity, and the winners were the ones that rewired around it.

Elsewhen blogWhy the model is not your moatModels converge and keep getting cheaper. The moat is the harness around them and the context it holds.Read the piece

The hard part is everything around the model: the business context the AI works in, the workflows it runs, the coordination of agents at scale, how your people teach it and the interfaces through which the work gets done. That layer, the one that joins a general capability to a particular business, is the only part nobody can sell you off the shelf.

Deployment is a settled question. Gaining from it is not. In McKinsey’s latest State of AI survey, nearly 90% of organisations use AI regularly, 37% can attribute any profit impact to it and 6% are earning material value. That 6% run the same models as everyone else. What sets them apart is that they run AI as one programme for the whole business, held to the P&L from the start. They decide where it will pay before they build, rebuild those workflows end to end along with the wiring that carries work between their systems and put as much into governance and their people as into the technology.

So this report is about the wiring. How your operating model becomes software you own, and what has to be built before agents can run anything end to end.

Adoption is the easy part

Almost no pilot returns anything measurable, and close to half never reach production at all. The technology is already inside almost every large organisation. MIT put the cause at what it calls the learning gap: AI never integrated into real workflows, structures and context.

95%
of enterprise generative AI pilots deliver no measurable return.
46%
of AI proofs of concept are abandoned before they reach production.
78%
of the US labour force already works at a firm that has adopted AI.

The AI Summit keynote: Inside the Agentic Enterprise

Watch the keynote

01 · Where this goes

What is the agentic enterprise?

An organisation where the work itself runs as software, with people directing it and making the decisions that carry weight.

The workflows that make up the business are codified and run by agents, coordinated and governed in one place, while the people who know the business set the direction, apply judgement and stay in command of what matters.

Today most enterprises look nothing like an agentic enterprise. They run hundreds of applications in silos, and the glue between them is manual: people rekeying data between systems, carrying context in their heads, moving each task to the next stage by hand. That manual glue is slow, hard to see into and easy to drop. It is also where most of the time and cost go.

The agentic enterprise replaces that manual glue with an engineered one, so the work flows reliably and the people in it spend more of their day on judgement, relationships and decisions, and less on the mechanics in between. That is the operating model running as software, with people firmly in the loop where it matters. A chatbot bolted onto today's ways of working does not get you there.

A chat input box on a pastel gradient
Elsewhen blogAI is more than a chatbotWhy the chat window is the least interesting thing you can do with a frontier model, and what replaces it.Read the piece

02 · Why it stalls

Why most of it never leaves the pilot

The dominant way most organisations consume AI has a ceiling, and it is lower than it looks.

Chat is often a poor interface for real work: it puts the entire burden of phrasing, context and follow-through on the person, one conversation at a time. And while putting a chatbot on every desk may feel like progress, the gain that matters arrives when the workflows themselves are redesigned around what agents can run.

Meanwhile tokenmaxxing, pouring tokens across the organisation and treating consumption as a proxy for value, is proving to be a measure of activity and little else.

A stack of coins with a rising line behind it
Elsewhen blogThe end of tokenmaxxingWhat happens when boards start asking what all those tokens bought.Read the piece

The market has started to price this in. Gartner counts roughly 130 genuine agentic AI vendors among the thousands claiming the label, and has a name for the rest: agent washing, the rebranding of assistants, RPA and chatbots as agents without the underlying capability. Buying activity and buying capability look identical on a slide. They diverge in production.

Done right, the prize is the cost base itself, put to work. When agents run the workflows, operating expenditure stops being a fixed cost and becomes elastic capacity: the same spend produces more output each quarter as the system learns, and your people move up the value chain.

Want to know which of your workflows is worth wiring first?

Book a working session

03 · The lesson of past technology

You have to redesign the enterprise to gain from new technology

Having the technology has never been the same as gaining from it. The gains come from the redesign.

History is blunt about this. Electric motors reached factories in the 1880s, but for 40 years they barely moved the needle. Plants that pulled out the steam engine, dropped in one giant electric motor and left the layout untouched saw almost nothing.

Productivity exploded only in the 1920s, when factories were rebuilt around what electric power made possible: a small motor at each workstation, and machines arranged by the flow of work rather than crowded around a central driveshaft.

Economists call the lag between a technology arriving and its payoff the productivity paradox, and the lesson holds every time: the gains come from redesigning the work around the technology.

AI is at exactly this point. For most enterprises it has changed remarkably little, because they have bolted it onto workflows built for people. A copilot on a process designed for humans just runs the old process faster. The boom comes when the work itself is redesigned around agents.

The productivity paradox

Annual total factor productivity growth in US manufacturing. Electrification arrives in the 1880s. The payoff waits for the 1920s, when the factory floor is rearranged around what the technology makes possible.

1880192019602000Electric motor arrivesLittle change for 40 yearsFactories redesignedMachines arranged by the flow of work

04 · The redesign

Every workflow is an algorithm

If the gains come from redesigning the work, it pays to be precise about what the work is. All work is a series of steps to reach a goal, and every one of those series can now be codified.

Onboarding a patient, approving an invoice, closing the books, migrating a portfolio. Each is a workflow: a trigger, a set of steps, a point where someone decides, an outcome written back. An organisation is just a collection of them, thousands, layered and interlocking. That collection is your operating model.

For decades it lived in people's heads, in policy PDFs and in systems of record, because writing software to run it was slow and expensive. That constraint has gone. Coding agents now generate, test and ship software at a pace that was impossible 18 months ago, so any workflow can be codified and the operating model itself becomes something you build and own.

The Elsewhen Agentic AI Opportunities Workshop board
Elsewhen blogFind your first agentic opportunityThe workshop we run to pick which of your workflows to codify first, and the five tests we put each one through.Read the piece

Codifying a workflow means choosing who runs each step. The human in the loop belongs wherever a mistake is costly, regulated or hard to undo, and everywhere else the agent can act alone.

A company is a collection of algorithms

An enterprise is thousands of workflows, and every step in each one goes to an agent, to plain code or to a person. Redesigning the business means making that call step by step, across all of them.

One workflowApproving an invoice

  1. An invoice arrivesTrigger
  2. Read it and pull out the linesAgent
  3. Match it to the purchase orderCode
  4. Explain any mismatchAgent
  5. Approve the exceptionPerson
  6. Post it to the ledgerCode

One enterpriseEvery workflow, each with its own mix

and thousands more

05 · Build what you used to rent

The economics inverted

Once any workflow can be written as software, the old reason to rent your software falls away.

For 30 years the logic of enterprise software was simple. Building it was expensive and slow, so you rented it: a vendor amortised the cost of building once across thousands of customers and charged you per seat. That bargain made sense while code was scarce.

Code is now cheap, and the market has repriced accordingly. Through the first quarter of 2026 roughly two trillion dollars came off software market capitalisations. The trigger was the arrival of agents that could carry sustained, multi-step knowledge work, which is precisely the work per-seat software was sold to support. For the first time on record, software's forward earnings multiple fell below the wider market.

SaaS will survive, but the bargain has changed. Almost every incumbent now describes itself as agentic; strip the messaging and many are what they always were, databases that hold your data while you do the wiring. That was a fair trade when software was scarce. It is a poor one now that code is cheap.

The Salesforce logo on the side of an office building
Elsewhen blogThe case for leaving Salesforce, made by SalesforceBenioff says the browser is optional and the API is the interface. Per-seat pricing does not survive that.Read the piece
What the market pays for software, 2020 to 2026
2020–222022–242024–25H2 2025Q1 202684.1x43.2x33.6x31.2x22.7xBelow the wider marketfor the first time

$2tn

came off software market capitalisations in the same quarter, as investors repriced the sector.

Software had never traded at a discount to the wider market before. The index has since recovered, but the premium for being software has not.

Jevons paradox

William Stanley Jevons set this out in The Coal Question in 1865. When Watt made the steam engine more efficient, Britain burned more coal: factories built more engines and put them to entirely new uses, so total consumption rose. Make a resource cheaper to use and you expand demand for it.

So when software gets cheaper, enterprises buy more of it. Worldwide IT spending reaches $6.37 trillion in 2026, with software alone at $1.47 trillion, up 15.5% on the year even as the market marked the sector down. Enterprises are redirecting the software bill, from tools they rent towards capability they own.

Cheap software multiplies the role of software in the enterprise, and the organisations that gain are the ones that generate their own.

Cheaper to build, and more of it bought

Worldwide software spending, up 15.5% in a year, while the cost of producing it collapses.

2025$1.271tn
2026$1.468tn

Once your operating model is software, it behaves like software

What you generate is a description of how your business runs. A process that lives in a slide, a spreadsheet and four people’s heads cannot be versioned, tested or rolled back. Written down precisely enough for an agent to run it, the same process inherits every property software has had for 30 years, and the operating model turns from a deck into a deployable, composable asset.

This is the part no incumbent vendor will say out loud, because the logic of how your business works is the one thing a competitor cannot copy and a vendor cannot sell you. When the operating model itself becomes software, renting it from someone else is the last thing you want to do.

Properties a workflow inherits once it is code

Version it

Every definition of a process, kept, dated and attributable.

Diff it

See exactly what changed between two ways of working.

Test it

Run a change against real cases before anyone lives with it.

Roll it back

A bad change becomes a one-step revert.

Fork it

Branch a variant for a region or a business unit, and keep both.

Governance stops being a document audited after the fact. It becomes the rules the agents cannot break.

06 · The wiring

What an end-to-end agentic solution looks like

Whatever the use case, the same system sits underneath: the surfaces your people use, the agents that do the work, the coordination that keeps it honest, the context it reads, the systems it writes back to.

A single agent on a laptop is a demo. An enterprise running thousands of agent executions a day across finance, compliance and customer service is an operation. The same shift happened with cloud computing: running one server is trivial, running a fleet is a discipline of its own.

We call the reusable core under all of this the Productivity Platform. It is built once, owned by you and reused across every use case, so each new agent ships faster and cheaper than the last. It is model-agnostic, so as new models arrive they plug straight in and you are never tied to one vendor. Because you own the core, its value compounds with every use case.

Under the hood

What the platform is made of

The full picture

The five parts, wired into your business

CRMERPCDPContractsContent mgmtAgentBusiness contextLLMHeadless agentsOrchestratorSkills libraryGenerative UIWeb appDashboardChatUser3rd-party agent

End-to-end custom AI · One holistic solution · Owned by you

The Productivity PlatformWhat it connects

The AI Productivity Platform: the five building blocks in depth

Read the report

Start with one workflow

Nobody starts with all of it. You start with one of those algorithms running end to end, wired through the whole system, and you build only the parts that workflow touches. Prove that slice and the next one reuses most of it, which is where the compounding comes from.

Example workflows
Lead functionUnderwriting operations

Submission to quote

Underwriting

A broker submission lands as an email with attachments. The system reads it, pulls the risk data into your fields, checks it against appetite and returns a quotable file or a clear reason it cannot be quoted.

  1. Read the submission and every attachment, whatever format it arrived in.
  2. Pull the risk data into the fields your underwriters use.
  3. Check it against appetite, capacity and referral rules.
  4. Return a quotable file, or name exactly what is missing.
  5. Send anything outside appetite to an underwriter with the reasoning attached.

The first step is picking the workflow where this would hit hardest.

Book a working session

07 · A design decision

How far do you go with agents?

Autonomy works like a dial, and what it measures is how much the agent decides for itself. The right setting is a design decision, made workflow by workflow.

Agents take on the repetitive coordination and the busywork between steps, so the people doing the work have more room for the parts that need them: deciding what is worth doing, shaping new products and improving the workflows themselves. People stay in command wherever judgement is the point of the step.

In PwC’s survey of US executives, 79% of companies have already put agents to work and two thirds report productivity gains from them, yet fewer than half are rethinking their operating model around what agents make possible. The work is deciding which workflows earn a human in the loop, and what that person is checking.

The autonomy dial

Most production systems we build sit across all three at once.

Taste, judgement and accountability are the scarce resources, and they stay firmly human.

08 · Agentic AI in the market

Put AI to work inside your business

Custom software is now cheap to build and yours to keep. Work nobody would have automated two years ago suddenly pays for itself.

The jobs coming to us are the ones where the money already sits: what the operation costs to run, what the licences cost to keep and the revenue these models make buildable for the first time.

Agentic operations

Automate what you do

Agents inside the workflows that cost the most time and money.

In production · Financial services

£14m

of operating cost saved, every year

A global credit management company onboards every new loan portfolio in weeks rather than months, with every account checked instead of a sample.

Read the case study

Agentic modernisation

Replace what you rent

The SaaS you rent, rebuilt as custom agentic systems you own outright.

In production · WPP

£17m

of planner time saved a year

Audience research that took weeks per brief now returns in seconds, on a system WPP owns outright, live in 62 countries.

Read the case study

Agentic growth

Grow what you sell

Products and services that were not buildable before these models existed.

In production · Travel and hospitality

£50m

a year in additional booking revenue, based on reported financial results

Customers describe the trip they want and get real options back in under 250ms, matched on meaning against live inventory.

Read the case study

Not sure which of the three you are? Let’s talk.

Get in touch

09 · How we start

A forward deployed squad

One workflow, picked because it costs you the most, running on your data.

Everything to this point is a set of design decisions: which workflows, how much autonomy, what the wiring looks like. What remains is who makes those decisions with you, and how fast they become running software.

Agents carry around 80% of the execution. Forward deployed builders do the rest and sign off on everything that ships. You own what is built, IP included, and you see the measured return before committing further.

Forward deployed

Inside your business

Our builders work in your environment, on your data, alongside the people who do the work. The people who scope it are the people who build it.

Small team

Senior, embedded, sized to the problem

Product, data science and AI engineering, working alongside the agents that carry the execution. No pyramid, no handover.

10 · Where this leaves you

What your competitors cannot copy

The advantage now sits in the architecture you build around the model.

That architecture is the context, the workflows, the coordination and the interfaces that turn a generic model into software that runs your business.

So treat it as a programme for the whole business: decide where AI will pay, rebuild those workflows end to end, fund governance and your people alongside the technology and hold every workflow to the P&L. Start with the one that costs you most, wire it through end to end, and each one after it reuses what the first one paid for.

Everyone has the same magic box, so the enterprises that win the next decade will be the ones that redesigned around it first.

Start with a conversation

Leon Gauhman

Leon Gauhman

Co-Founder and Chief Product & Strategy Officer

Book with Leon
Richard Henderson

Richard Henderson

Director of Business Development

Book with Richard

FAQ

Common questions

What is an agentic enterprise?

An organisation where the work itself runs as software. Agents carry whole workflows between systems while people set direction and make the decisions that carry weight, and the operating model is something the business owns.

Why do most enterprise AI pilots fail?

MIT NANDA found 95% of generative AI pilots deliver no measurable return, and put the cause at the learning gap: AI never integrated into real workflows, structures and context. The problem is the wiring around the model.

What is the difference between AI automation and agentic workflow automation?

Automation follows a fixed script and breaks when the input varies. An agentic workflow reads, reasons and drafts at the steps that need judgement, calls plain code where there is one right answer and routes to a person where the decision carries accountability. The coordination between those steps is the hard part.

What is human in the loop, and which workflows need it?

Human in the loop means an agent does the work and a person approves at set points, in the tool they already use. Autonomy works like a dial. Fixed, auditable steps can run deterministically, high-volume work where a wrong answer is cheap to undo can run autonomously and anything where the exceptions carry the risk keeps a person on the approval.

What is the Productivity Platform?

The reusable core every agent runs on: business context, headless agents, an orchestrator, a skills library and generative UI. It is built once, owned by the client and reused across every use case, so each new workflow ships faster and cheaper than the last.

How long does it take to see a return?

Elsewhen starts with one workflow running end to end and builds only the parts that workflow touches. The first one proves the return; the next reuses most of what the first paid for.