What Does an AI Agent Actually Cost per Case?
Enterprise AI cost controls and this week's agent announcements make unit economics urgent. A Canadian service team needs to count retries, review and rework alongside model usage.
Finance and service operations leaders
5 min read
30 October 2026
2 sources
Usage
Models + tools
→Operate
Infrastructure
→Review
Human time
→Correct
Rework + support
→Divide
Quality resolutions
Report unresolved and escalated cases alongside the unit cost.
A low cost per model call can hide an expensive cost per useful outcome.
- 01Count model, infrastructure, review and correction costs together.
- 02Use resolved cases as the denominator and report unresolved cases separately.
- 03Compare against the current process on the same case mix.
Why spend visibility is not ROI
This week's OpenAI–ServiceNow announcement illustrates how AI may move from answering questions into multi-step enterprise workflows. Anthropic's enterprise controls describe usage analytics and spend controls, but a usage dashboard alone cannot show whether a case was actually resolved or whether a person had to repair the result.
A Canadian insurer's administrative service team might pilot an assistant to classify incoming correspondence and prepare a response for review. The business should measure the entire handling process; the example is administrative and does not authorise automated coverage decisions.
Calculate the cost of a useful outcome
For a defined period, add model usage, orchestration and tool costs, allocated infrastructure, human review, corrections and relevant support. Divide by cases resolved to an agreed quality standard. Report abandoned cases and cases escalated to humans alongside that figure so the denominator does not conceal failures.
For example, if total pilot cost is $1,200 and 300 cases meet the agreed resolution standard, the observed cost is $4 per resolved case. This is an illustration, not a benchmark. A fair comparison requires similar case complexity, quality standards and accounting for the existing workflow.
Find the economics of the exceptions
Break the results down by case type. A low-cost model may be economical for straightforward classification but expensive when it repeatedly calls tools or sends ambiguous cases back for correction. Routing difficult cases to people or a different model can be sensible, provided the routing itself is evaluated.
Set per-workflow budgets and alerts, cap runaway retries, and inspect unusually expensive cases. Review quality, turnaround and staff workload with finance. Optimising cost without checking missed errors or customer outcomes can simply move expense elsewhere.
Use this before approving the work.
- 01Define a resolved case and its quality standard.
- 02Count review, rework, infrastructure and usage.
- 03Compare matched cases with the current process.
- 04Cap retries and review expensive exceptions.
Research and references supporting this article. Interpretation and recommendations are Thalenor’s.
The insurer and cost calculation are illustrative; Anthropic's cited control announcement predates this week's workflow news.
Published and reviewed on 30 October 2026. This article provides general technology and operational information, not legal, tax, medical or regulatory advice.