# How to Calculate Cost Per Outcome for AI Agents

Published 2026-08-11 · Brian Diamond

Track: finops

Segment: strategy

Cost per token is easy and insufficient. Finance cares about cost per outcome: the fully attributed AI labor cost to complete a defined business result — a resolved ticket, an underwriting memo, a reconciled invoice — versus the human baseline.

## Define the outcome

Pick a unit leadership already recognizes. Ambiguous outcomes produce meaningless unit economics. Document inclusion rules: retries, tool calls, human handoffs, and failed runs.

## Attribute the spend

Sum model, gateway, and tool costs for the workflow that produced the outcome. Attribute to the agent and owner. Without [chargeback-ready attribution](https://www.onaro.io/blog/ai-agent-chargeback-allocating-agent-spend), your denominator is fiction.

## Compare to the human baseline

Express AI cost per outcome next to fully loaded human cost for the same result. That is the CFO conversation — not a model leaderboard.

See also [What Is Agent FinOps?](https://www.onaro.io/blog/what-is-agent-finops) and [Measuring AI ROI Governance in Practice](https://www.onaro.io/blog/measuring-ai-roi-governance-in-practice).

Onaro Meridian is [FinOps for agentic AI](https://www.onaro.io/finops-for-agentic-ai): the system of record that attributes, controls and books what AI agents spend.

Canonical: https://www.onaro.io/blog/how-to-calculate-cost-per-outcome-for-ai-agents