February 5, 20266 min read

Stop Measuring AI ROI in Tokens and Licenses

Usage metrics aren't ROI. How to measure AI return on investment by outcome, feature, and customer.

Alina, CEO at botanu
Alina

CEO at botanu

"What's our AI ROI?"

Almost every time, the answer is some version of: "We spent $X on OpenAI and $Y on infra, and usage is up 30% month over month." That's not ROI. That's a cost report with a growth metric stapled on.

The Usage Trap

The legacy software model trained everyone to measure ROI in seats, licenses, and usage. How many users are active? How much compute is being consumed? Cost per seat?

AI doesn't work that way. A team of 10 can burn through $50K/month in inference running multi-agent pipelines at scale. A team of 1,000 might spend $2K on an internal Q&A chatbot. Usage volume says nothing about value.

A system that makes 10,000 API calls/month to achieve nothing is a waste. A system that makes 10,000 API calls/month and resolves 7,420 customer inquiries that would have required human agents? That's value.

Outcome-Based ROI

Real AI ROI looks like this:

  • Voice Agent: 3,180 resolutions/month, $6,300 AI cost, $18,200 productivity value. That's 2.9x return. Margin band: high.
  • Chatbot: 7,420 resolutions/month, $4,300 AI cost, $28,800 productivity value. That's 6.7x return. Best unit economics in the product.
  • Escalations: 1,800 resolutions/month, $1,500 AI cost, $4,200 productivity value. That's 2.8x return. Margin band: medium.

Three features. Three very different ROI profiles. Measuring "total AI spend vs total usage" hides all of this. It hides that the Chatbot has 6.7x ROI while the Escalation flow barely hits 2.8x. It hides that doubling down on Chatbot expansion generates way more return per dollar than investing in Escalations.

The Adoption vs. Cost Curve

ROI isn't static. It changes as adoption scales. In a healthy AI product, adoption goes up (more resolutions) while cost per resolution stays flat or decreases (efficiency gains, caching, model optimization). If cost is growing faster than adoption, ROI is degrading even though everything looks like it's "working."

This is the chart a board should see. Not "API calls went up 30%." Not "we added 500 users." Resolutions are growing at 12% MoM while cost per resolution stayed flat. That's real ROI.

Customer-Level ROI

It gets more interesting per customer. Acme Corp (Enterprise) does 4,200 resolutions/month at $3,100 in AI cost. Is Acme profitable at their contract price? Depends on what they're being charged per resolution.

Globex (Mid-market) does 2,600 resolutions at $1,400 in AI cost. Different features, different cost profile, different ROI. Measuring ROI at the product level makes those two accounts look the same: "active customers using AI." Measuring at the outcome level shows one has fundamentally better unit economics than the other.

What the Answer Should Actually Look Like

Next time someone asks "what's our AI ROI" the answer should include:

  • Cost per outcome by feature (not total spend).
  • Productivity value per outcome (not usage volume).
  • Margin band per feature (high, medium, low).
  • Trend (is cost per outcome going up or down as adoption scales).
  • Customer-level economics (which accounts are profitable at current pricing).

That's AI ROI. Everything else is just a bill.

StrategyAI ROI

Track cost per outcome across your AI stack

See how botanu gives engineering teams full visibility into workflow-level unit economics.