Skip to newsletter
XTechStacksTECHNOLOGY · AI · STRATEGY · IMPACT
Menu
XTECHSTACKS WEEKLY

September 13, 2026

Your AI Agent Doesn’t Have a Salary. That Doesn’t Mean It’s Cheap

Why cost per business outcome may matter more than cost per token.

By Atul Yadav · 8 min read

Share this edition

AI agent operating costs shown as an iceberg: model costs above integration, evaluation, operations and governance.

Why cost per business outcome may matter more than cost per token.

For the last few years, enterprise AI cost conversations have revolved around a familiar number:

price per million tokens.

Teams compare model providers. They negotiate discounts. They shorten prompts. They add caching. They route simpler requests to cheaper models.

All useful.

But AI agents are changing the economics.

An agent doesn't necessarily make one model call and return an answer.

It can reason, retrieve data, invoke tools, call APIs, retry failed operations, ask another model for verification, launch sub-agents and repeat parts of the workflow before producing one useful result.

The result is a new cost stack:

Token cost → Agent-run cost → Workflow cost → Business-outcome cost

And I think enterprises are approaching a point where cost per token becomes one of the least interesting numbers in that chain.

The more useful question is:

How much did it cost the AI system to produce one successful business outcome—and was that outcome worth the money?

That is the emerging problem of AI Agent Economics.

Start with an accountable cost boundary

Before debating whether an agent is expensive, decide what its bill includes. A model invoice alone misses shared retrieval, tool execution, monitoring and human exception handling. This edition focuses on discovering and allocating those costs; the next edition evaluates the resulting cost per verified outcome.

For a first inventory, give each workflow an owner, environment and stable run identifier. Record resource use at the point it occurs, then reconcile it to the provider invoice. A missing allocation should remain visibly unallocated rather than disappear into a conveniently cheap workflow.

Agentic AI introduces a different cost structure

Imagine an enterprise claims-processing agent.

The employee sees something simple:

“Review this claim and recommend the next action.”

Behind the scenes, the workflow might look more like:

Claim received
      ↓
Document extraction
      ↓
Classification
      ↓
Customer-history lookup
      ↓
Policy retrieval
      ↓
Coverage validation
      ↓
Fraud-risk check
      ↓
Reasoning
      ↓
External API
      ↓
Exception detected
      ↓
Additional reasoning
      ↓
Tool retry
      ↓
Recommendation
      ↓
Human approval

Each layer can create cost.

Not only inference.

There may be:

model calls + context + reasoning + retrieval + vector/database queries + APIs + tools + retries + observability + infrastructure + human review.

And one of the most interesting characteristics of agent architecture is that the execution path can vary from one task to another.

Traditional software might execute a relatively predictable sequence.

An agent may decide that one claim needs five steps and another needs twenty.

That means architecture increasingly determines economics.

We can already see this in commercial agent pricing

Consider AWS DevOps Agent pricing.

At the October 22, 2026 source check, AWS lists $0.0083 per active agent-second for investigations, evaluations and on-demand SRE tasks.

AWS's own examples illustrate how quickly the unit changes with usage:

A small team running ten monthly investigations costs about $39.84/month.

An active team running investigations and on-demand tasks reaches about $343.62/month.

Its enterprise example—500 incidents, 40 evaluations and 30 custom SRE-agent tasks—reaches $2,365.50/month before considering some connected-service costs. (Amazon Web Services, Inc.)

None of those numbers is inherently expensive or cheap.

If a $4 agent investigation prevents an engineer from spending 45 minutes diagnosing an infrastructure incident, it could be exceptionally valuable.

If hundreds of unnecessary investigations run continuously, the economics change.

Again:

cost without outcome tells us very little.

A worked allocation ledger

Illustrative example, not customer results or a vendor quote. A support workflow has 1,000 runs in a month. Its directly measured model bill is $120, tool/API charges are $80, shared retrieval is $60 and allocated platform/observability cost is $140. Twenty exceptions each take 15 minutes at an assumed $60 per staff hour, adding $300. No retry or tax costs are included.

Illustrative monthly cost allocation
Cost poolAllocation basisAssigned cost
Models$120 measured against workflow/run IDs$120
Tools and APIs$80 directly attributed requests$80
Shared retrieval$200 pool × 30% measured workload share$60
Platform and observability$700 pool × 20% chosen allocation share$140
Human exceptions20 × 0.25 hours × $60/hour$300
TotalSum once; reconcile pools separately$700

The ledger yields $0.70 per run, but says nothing by itself about whether those runs were useful. The shared-cost shares are assumptions for this example, not a universal allocation rule. Document the driver, period and owner; reconcile the unassigned 70% of retrieval and 80% of platform costs elsewhere. Do not add a chargeback to the underlying provider charge again. Unallocated spending and allocation changes should remain visible in the report.

A useful review asks: Are all run IDs attributable? Do pool totals reconcile to invoices? Are development and production separated? Have cached calls, fan-out and human handling been double-counted? Only after these checks should an owner compare alternatives or set a budget.

A practical framework: DABOG

Organizations don't need another giant AI transformation program to begin doing this.

They need better instrumentation and operating discipline.

I would use five steps.

D — Discover

First understand the AI estate.

Map:

Agents → workflows → models → tools → APIs → data services

Many organizations will eventually discover that the model invoice represents only part of the real operating cost.

A — Attribute

Move from provider-level spending:

OpenAI = $200K

toward:

Business Unit
      ↓
Use Case
      ↓
Workflow
      ↓
Agent
      ↓
Model / Tools / APIs
      ↓
Cost

Without attribution, optimization becomes guesswork.

B — Benchmark

Do not benchmark cost alone.

Measure:

Cost + Quality + Latency + Success Rate

A cheaper workflow that fails more frequently may be economically worse.

This is where AI engineering and FinOps begin converging.

O — Optimize

Only after understanding the workflow should teams optimize.

Typical opportunities include:

Notice something important:

Most of these are architecture decisions, not procurement decisions.

G — Govern

Finally, establish economic guardrails.

For example:

Agent budget
Cost/run threshold
Retry ceiling
Context limit
Tool-call limit
Cost anomaly detection
Business-unit showback
Outcome KPI

The objective is not to prevent agents from spending money.

It is to prevent them from spending money without producing proportional value.

A budget review that produces an engineering action

Use DABOG as an editorial checklist, not an industry standard. Review one workflow with its engineering and business owners. Compare actual spending with the budget and approved allocation drivers; inspect the most expensive traces before imposing a blanket token cut. If retries dominate, address retry limits or idempotency. If shared retrieval dominates, review indexing, query volume and cache behavior. If human exceptions dominate, improve the decision boundary and escalation path.

The output should be an owned action with a baseline and a quality guardrail: for example, reduce duplicate tool calls while preserving the same accepted-case criteria. Reconcile the next period using the same cost boundary. Changing the allocation method and the architecture simultaneously makes the result hard to interpret.

The architecture I expect to emerge

Eventually I think organizations will need something resembling an Agent Economics Observatory:

BUSINESS OUTCOME
                          ▲
                          │
                        VALUE
                          ▲
                          │
Business Unit → Workflow → Agent
                          │
            ┌─────────────┼─────────────┐
            ▼             ▼             ▼
          Model          Tools          Data
            │             │             │
          Tokens         APIs        Retrieval
            └─────────────┼─────────────┘
                          ▼
                         COST
                          │
                          ▼
             COST PER SUCCESSFUL OUTCOME

Not another dashboard showing:

“You consumed 8.4 billion tokens.”

But something capable of saying:

“This workflow processed 18,400 claims, successfully completed 16,900, required human escalation on 1,500, cost $31,000 to operate and avoided approximately X hours of manual work.”

That is a conversation a CIO and CFO can actually have.

What technology leaders can do now

Instrument workflows, not just models. Capture model, tool, retrieval, retry and infrastructure costs at the agent/workflow level.

Measure success explicitly. Every production agent should have a definition of successful completion.

Connect AI telemetry to business telemetry. A technically successful agent call is not necessarily a successful business outcome.

Set economic guardrails. Control runaway retries, excessive context, unnecessary tool calls and poorly designed agent loops.

Optimize value, not simply cost. A more expensive agent can be the better system if it produces substantially better outcomes.

The bigger lesson

We spent the first phase of enterprise GenAI asking:

Which model should we use?

Then:

How do we build agents?

The next question may increasingly be:

Are these agents economically worth running at scale?

And answering that question requires more than a token dashboard.

It requires connecting:

architecture → execution → cost → outcome → business value.

The organizations that build that capability early will have an important advantage.

They won't simply know how much AI they're consuming.

They'll know where AI is actually creating economic value.

And that may ultimately be the metric that matters most.

A question for technology leaders

If your AI spending doubled next quarter, could you tell your CFO which business outcomes improved because of it?

If the answer isn't clear, I'd be interested in comparing notes on where the hardest gap is today—cost attribution, workflow visibility, outcome measurement or ROI.

XTechStacks Newsletter team

Editorial note

Reviewed October 22, 2026. The frameworks and worked scenarios here express XTechStacks editorial analysis; they are not formal industry standards, customer case studies or claims of executed production tests. Hypothetical figures are assumptions, and vendor announcements or research findings should be read within their stated scope. Product capabilities and prices can change. Corrections or questions can be sent through our contact page.

Atul Yadav writes XTechStacks Weekly about enterprise AI, architecture and practical engineering decisions. Earlier LinkedIn publication links are retained below where present.

Originally published in XTechStacks Weekly on LinkedIn on September 13, 2026. Read the original edition.

Share this edition

Keep a clearer view of what’s next.

Subscribe to XTechStacks Weekly for practical technology insight.