BlogsSep 12, 2026

When AI agents become abundant, new ways of working become possible

The economics of agentic work formations

By Walid Negm

AI agents are becoming capable of reasoning, planning, using tools, coordinating and acting with increasing autonomy. It may be the biggest expansion in a generation of what can get done. Their reliability remains uneven, particularly across long and messy work, but the economic shift is already visible.

The obvious opportunity is to use agents to perform more of today’s work. The larger opportunity is to reconsider how the work itself comes together and is made to operate.

Every way of working has always had to answer two questions:

How does the work progress? What makes the result official?

And underneath the first, where the structure does not already answer it: What gives participants the go-ahead to act? On a set path, finishing one step starts the next and there is nothing more to say. On a shared board, different participants act under different conditions, and that is most of what there is to know.

Take a purchase request. A process might carry the coordination: validate the need, obtain bids, check budget and policy, select a supplier. A manager or a purchasing policy may give a buyer the go-ahead to commit within a spending limit. And the result becomes official when an authorized purchase order is issued and recorded in the company’s system of record.

Or take an insurance claim. The process might carry the coordination: verify coverage, assemble evidence, assess the loss, calculate the payment. A claims manager or a policy may give an adjuster the go-ahead to approve an exception or authorize payment within a limit. And the claim becomes official when the required decision is committed and the authorized payment is posted to the insurer’s system of record.

Change those answers and you change how the work operates. An agent might run the sourcing, a buyer might be granted temporary authority, or several independent judgments might be required before the order is committed.

Combine those answers with the people, agents and systems doing the work, and you have a work Formation.

AI did not invent Formation. It changes the economics of what we can form.

The economics of how work is organized

A purchase order does not only cost the work of raising it. It costs getting the work to happen, holding the request together, checking what must be checked before the company commits, and bearing the consequence if the result is wrong.

A useful way to express that is:

doing it + holding it together + checking it + controlling it + being wrong

C = E + Ce + R + I + pL

where being wrong is how often it fails × what a failure costs

TermWhat it includesPurchase-request example
doing itE — ExecutionLabor, agent and implementation cost, per role and per task.Validate the need, gather the bids, check the budget, raise the order.
holding it togetherCₑ — CoordinationContext assembly, model calls, duplicated reasoning, latency, reconciliation, and the cost of keeping participants aligned.The buyer pulling the request, the quotes and the budget line into one view; the extra calls if a second agent “helps” with supplier research; the wait while finance and the requester disagree.
verifying and settling itR — Verification and settlementGathering the evidence, checking it, and deciding the work is accepted — a direct function of what settles, and of how many participants must agree before it does. Doing the work is not settling it.A manager reviewing an over-threshold request; two approvers if it brings in a new supplier; reconciliation when the invoice arrives against the order. Review is not “being careful” — it is a function of what must be true before the company is allowed to commit.
controlling itI — ControlAuthority checks, policy evaluation, exception handling, fallback, monitoring and manual takeover — the recurring cost of enforcing what may happen, handling what falls outside the permitted envelope, and intervening when the arrangement cannot safely continue.The spending-limit check before the order is issued; the rule that blocks a supplier not on the approved list; the human who takes the request the agent cannot classify; the monitor watching for orders split to stay under the limit.
being wrongp×L — Failure exposureProbability times consequence. The term that decides whether a faster arrangement is actually a better one.Committing to the wrong supplier or the wrong terms — cost, delay, a contract dispute — or refusing a request the business needed: the stalled project, the missed delivery, the workaround purchase nobody controlled.

A group of agents can make doing it look cheap while making the overall work more expensive. More participants can mean more context, calls, waiting, reconciliation and review — and sometimes a more expensive mistake.

If you only count execution, you are not comparing arrangements. You are comparing one part of their bill. An arrangement-changing proposal should not be declared economically superior from execution savings alone; where it creates coordination, review, control or failure exposure the model cannot yet measure, the answer is not zero. It is that the economic comparison is incomplete.

Moving from one way of working to another also costs something once — integration, migration, training, redesigning policy and roles, rollout, adoption. That is change cost, and it sits beside the operating bill rather than inside it:

C = E + Ce + R + I + pL   what an arrangement costs to run
Ch   what changing arrangements costs, once
the case for the change = Δ(value − C) − Ch

A build-out you pay for once does not pre-pay the checking and controlling you will do on every case. Keep the one-time and the recurring apart, or the recurring quietly disappears into a number that was already spent.

The coordination cost function is moving

Organizations have historically designed work around two scarce resources: human attention and human judgment. That naturally favors defined processes and management. If the next action can be encoded in a process, nobody has to continuously watch and decide what should happen next. Where it cannot, a manager can make the call.

Consider a shared operational board. A shipment becomes late, inventory falls below plan and a customer commitment becomes exposed. Logistics, procurement, production and customer service can see the same changing state and respond when something relevant to their role occurs. With people, that can require several people to remain attentive, interpret what changed and decide whether to act.

Or consider a peer network. One participant raises an issue, another contributes evidence, another challenges the conclusion and another revises it until an explicit convergence rule is satisfied. Doing that with people for every case is expensive.

Organizations have therefore often simplified richer forms of coordination into alerts, queues, assignments, meetings and handoffs.

Reasoning AI changes those constraints. AI agents can remain available, observe changing conditions, interpret them, reason within stated boundaries and coordinate with others at a very different cost.

But coordination does not become free. The constraints shift toward context, computation, latency, verification, reconciliation, control and trust. Ten agents can still generate more work than they absorb. The scarcity moves.

A shared board, market, ledger or peer network can therefore become a viable design choice where previously it may have been uneconomic. Changing who performs the work and changing how the work is organized are economically different decisions.

The economics follow the work

The economic terms connect directly to how the work operates.

Work-system questionWhat it can change economically
Who does the work?Execution cost, capacity and throughput
How does the work progress?Execution and coordination cost
What gives participants the go-ahead to act?Monitoring, waiting, handoffs, contention and unnecessary activation — and the running cost of the authority boundary itself
What makes the result official?Review and commitment cost
What happens when it is wrong?Failure exposure

Review is not simply “being careful.” It follows from what must be true before the result can become official, including required evidence, agreement and reversibility.

Changing an arrangement can move several terms at once. A five-agent team may reduce human execution cost while increasing coordination, latency and review. One capable agent may cost less overall. Conventional software may cost less still. A deterministic route may win when the work is predictable or the consequences of failure are high.

A benefit is not a savings percentage

The commonest mistake in an agent business case is a chain of inferences that feels like arithmetic:

30% of the work moves to an agent → 30% more capacity → 30% lower cost → $X benefit

None of the later steps follows from the first. Allocation is only allocation. It says who performs the work. It does not say how fast, how well, or what it costs.

Capacity comes from the performer, not from the share of work handed over. If an agent genuinely processes two thousand purchase requests a day and the arrangement lets it serve the station, then the station’s capacity really is two thousand a day — a real operational gain, and the number came from a fact about the agent, not from the percentage. But capacity is not throughput. If forty requests a day arrive, roughly forty a day are completed. The agent has fifty times the capacity; the work is not fifty times larger.

An operational improvement is already a benefit. Capacity up, defects down, exceptions down, cycle time down, first-pass yield up — those are real whether or not anyone has put a dollar on them. What they are not is automatically a dollar. Economic benefit is the economic consequence of an operational improvement, and the model should say whether that consequence is expected, simulated or observed. It needs a causal link: more demand served, a hire avoided, rework hours not worked, a loss not incurred. Where that link is not known, the economic value is unmeasured. Not zero — unmeasured.

So an agent added to sourcing has two sides, and an honest case states both: what the deployment costs, and which properties of the work system it changes or is expected to change — processing time eighteen minutes to eleven, capacity, first-pass yield ninety-two to ninety-seven percent, exceptions eleven to six, span of control, or another operational outcome. Stating the cost precisely while leaving the reason for the agent vague is how a cost becomes a business case.

And with twenty agents, benefits compose the way capacity composes; they do not add. Two agents that each add fifty a day on a sequential route do not add a hundred. Two agents that each save a hundred review hours may be saving the same hours. The Formation is where those effects are reconciled — which is one more reason the Formation, and not the agent, is the unit whose economics are compared. Participant-, task- and role-level effects may be authored or measured bottom-up, but they must reconcile through the Formation before they become Formation-level economics; the same Formation can then roll into the economics of the larger work system.

We can now design work systems that operate differently

Work can progress through three broad coordination carriers: a known route, a directing participant, or an environment and rules through which participants coordinate without someone directing every move.

But the carrier alone does not define the arrangement. A handoff, market, committee, shared board and peer network can all use an environment and rules while differing in what gives participants the go-ahead to act and what makes the result official.

ArrangementHow does the work progress?What gives participants the go-ahead?What makes the result official?Example
Workflowsequence · decision · DAGRoutethe authored route — completing a step activates the nextlast step completesClaims processing
Manager → specialistsplanner · supervisor · leadDirecting participantthe lead, which assigns and redirectsthe lead accepts or synthesizes the combined resultInsurance claims review
Handoffrelay · ownership transferEnvironment + rulescurrent ownership, under the transfer rulesvalid transfer plus established assumption of ownershipClinical handoff
Task marketcontract net · biddingEnvironment + rulesthe allocation rule, meeting bidder choicesthe award is committedTask market
Committeeindependent judges · panel · ensembleEnvironment + rulesparticipation and eligibility rules — who may submit a judgmentaggregation rule produces a decisionInvestment committee
Shared boardblackboard · shared workspaceEnvironment + rulesshared state plus activation rules; no directorthe resulting state transition is validly committedInventory exception management
Governed meshpeer network · group chat · swarmEnvironment + rulesthe peer protocol's interaction rightsprotocol determines convergenceFraud network

These arrangements are not new. Some are decades old. What changes is the feasibility of putting increasingly capable software participants inside them, combining them at finer granularity, and using them where continuous human attention and judgment once made them uneconomic.

A swarm, for example, is not itself an arrangement — it names the participants rather than the coordination. It tells us that several autonomous agents take part, but not how they coordinate, when they may act or what makes their collective result authoritative. Specify those rules and the swarm becomes something concrete: perhaps a governed mesh, shared board or handoff.

Nor is environment-and-rule coordination an AI invention. Kanban is a familiar example: shared state and pull rules let participants coordinate without a manager assigning every next action.

AI and agentic operating models open a larger design space for work.

But possible is not the same as operable.

A different arrangement can change authority, policy, risk, review, accountability and failure modes. If work moves from a fixed route to an agent-directed team or shared environment, the organization has to know who may act, what authority they hold, what requires review, what happens when something fails, and what makes the result official.

The same applies if work changes arrangement while it is running. That is not a routing decision — state, responsibility, authority and settlement cannot simply disappear at the boundary, and two formations do not unknowingly act on the same state. The transition itself is governed work.

What a governed transition has to state

Why change?
What condition requires different coordination?
Who authorizes it?
Who may change how the work operates?
What must carry forward?
State · evidence · history · obligations · constraints · authority boundaries · invariants · settlement requirements
What happens to work already in flight?
Complete · cancel · transfer · reconcile
What authority changes?
Grant · retain · revoke · expire
What must settle?
What must be true before the old Formation ends?

Unstated, the transition still happens — it just happens as the residue of the first implementation, and unpicking that later costs a project.

The requirement and its implementation are different things. A legacy approval workflow may disappear while the requirement for approval remains. A human checklist may disappear while the invariant it enforced moves into deterministic code. “Payments over $25k need a second approval” is a requirement; the ERP workflow that enforces it today is one way of meeting it. Redesign may replace the mechanism; it does not silently erase the obligation. Every constraint, authority boundary, invariant and settlement requirement in the old design has to be explicitly preserved, modified, reimplemented or retired — and left unresolved, the transition is not ready.

The existing system is evidence

Existing work systems rarely come with a complete declaration of their constraints. Some are written in policy. Some live in approval chains, IAM roles, workflow configuration, code, database rules, exception paths and audit history. Some exist only as operating practice.

A redesign therefore begins partly as an extraction problem: identify candidate obligations from the current system, preserve their provenance, and distinguish what is authored, observed, inferred, regulatory or system-enforced.

Observed behavior is not automatically policy. An inferred control is not automatically an obligation. But neither should either disappear simply because the future design is generated from a cleaner model.

And capability does not settle those questions.

“An agent could do this” and “an agent may do this” are different questions.

A recommendation to pay a claim is not the payment. A diagnosis is not a discharge. A model’s confidence does not confer organizational authority — probability is not authority, and confidence is a property of the model rather than a grant from the organization.

Nor does authority transfer with the work. If a human who could approve a $10,000 purchase is replaced or augmented by an agent, the agent does not inherit that grant merely because it now performs the task. The future Formation must explicitly grant, narrow, reassign or withhold that authority.

A newly possible arrangement therefore still has to clear a harder test:

Can it operate reliably? Can we understand its economic and operational consequences? Can every applicable constraint, authority boundary, invariant and settlement obligation be accounted for in the proposed Formation? Does the value justify the cost, risk, governance and organizational change?

Sometimes a deterministic route will still win. Sometimes an agent-directed team, shared board or peer network will make sense where it did not before. The conceivable Formation space is larger than the production-ready Formation space.

Agentic AI is the generational capability event. Work-system redesign is the generational design opportunity.

The objective is not to make work as agentic as possible. It is to make how work is organized a deliberate choice again.