As AI becomes embedded across more of the technology stack, its costs are becoming harder to isolate. Spending may be distributed across cloud services, SaaS tools, private infrastructure and data centers, making a simple technology budget line an incomplete picture of the investment. For tech leaders, the challenge is connecting that fragmented spending to business results in a clear, consistent way.
The right metrics can help leaders determine whether AI investments are generating measurable value rather than simply adding cost or activity. Here, members of Forbes Technology Council share metrics tech leaders can use to evaluate AI spending against business outcomes and make more informed investment decisions.
Cost-To-Outcome Ratio
The key metric is the cost-to-outcome ratio benchmarked against the pre-AI baseline. AI costs span multiple platforms and environments, making tracking expenditures less useful than measuring outcome economics. Normalize total AI spend against the historical cost to deliver the same result. When the ratio improves quarter-over-quarter, AI is creating enterprise value, not simply funding an experiment. – Rajesh Gharpure, Persistent Systems Limited
Business KPI Per AI Agent
Total AI costs also include token usage, API calls, GPU usage and so on. Every agent should have an intended business KPI, and it should be measured against that. Total cost of ownership can be calculated based on the intent of the business case versus actual on-the-ground usage—usability, real impact on the ground and the cost of the agent across the layers. – Raja Shanmugam, TATA Consultancy Services
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
AI Value Per Lifecycle Cost
Track AI value realization per use case: measurable business value tied to the full lifecycle cost of designing, building and running each AI-infused workflow. Spend must be mapped with forensic precision to every use case, including frontier model iteration—for example, from Gemini 2.5 Flash to Opus 4.7 as evaluation improves—so pricing updates occur from the exact switch point, not averaged later, generalized across the portfolio, or recognized only after production. – Jayashree Arunkumar, Wipro
Revenue And Cost Impact
AI projects are designed to either increase revenue or decrease costs—ideally both. Revenue impact is easy to measure if you’ve put the right tools in place. It’s clearest when the AI project results in a new product line or SKU. In marketing projects, for example, one might measure an increase in leads, pipeline or marketing-sourced leads. Cost reduction is also measurable when that’s the purpose of the project, usually in the form of headcount reductions. – Steve Van Till, Brivo
Cost Per Successful Outcome
Tech leaders should measure total cost per successful outcome. The cheapest model can become the most expensive if it repeatedly gets a task wrong. Strong orchestration routes simple work to faster, cheaper models and complex work to models that can handle more reasoning, while factoring in retries, human intervention and coordination to ensure the business achieves the intended result. – Dan O’Connell, Front
AI Impact Margin
The real question is, “How much value was left after AI produced something?” Track the “AI impact margin”: the measurable business value created minus the full cost of the AI required to create it. Revenue gained or hours saved can look impressive until cloud, data, licenses, human oversight and rework are counted. – Prashanthi Nuthi, Enlace Health
Cost Of Delivered Intelligence
Traditional infrastructure unit economics largely measure the cost of providing capacity and its utilization—for example, cost per vCPU, cost per user per month or cost per server—whereas AI unit economics should ideally measure the cost of producing and delivering intelligence and business outcomes. While cost per token or cost per GPU-hour might still be useful, economic value generated through AI is a metric that might be more relevant. – Mrutyunjay Mohapatra, Alysian
Operational Performance Gains
Metrics should be tied to the operational problem AI was brought in to solve. For industrial companies, that could mean reducing machine downtime, cutting excess inventory, improving first-time fix rates, or increasing production capacity. Those are metrics businesses already measure, which makes it much easier to see whether AI is creating enough value to justify the investment. – Kriti Sharma, IFS Nexus Black
AI Value Yield Per Use Case
Tech leaders need disciplined judgment and frugal execution, with a metric like AI value yield per use case. AI cost should be judged by business value, not compute or token volume. Start with the business use case; quantify value across automation, revenue, risk reduction, regulatory impact and customer outcomes; and then compare it with the full AI cost across infrastructure, security, telemetry, controls and operations. – Saurabh Gupta
Net Margin Per AI Dollar
Stop tracking vanity “tokens processed.” The single metric that matters is net incremental margin per AI dollar: total realized operating yield (revenue lift and labor cost savings) divided by direct compute spend (cloud, tokens, SaaS). If this ratio isn’t well above 1, high-cost frontier models are eating your margin, and you’re funding expensive prompt loops instead of real leverage. – Neda Nia, Stibo Systems
Recurring AI Workflow Cost
Tech leaders should track whether the cost of recurring AI workflows declines over time. Much of enterprise work follows repeatable patterns, so the 50th version of a recurring task shouldn’t cost as much as the first. If it does, that’s a sign the system is repeatedly paying to reason through work it has already done. – Samir Dutta, Farsight AI
AI Tool Utilization
Track utilization of what you already paid for. Every enterprise is buying AI seats and provisioning agents that go dormant within 90 days. If half your Copilot licenses haven’t been touched this month, the outcome metrics don’t matter yet—you’re paying full price for zero output. Fix the utilization gap first. Then the cost-per-outcome conversation is worth having. – Nidhi Jain, CloudEagle.ai
Employee Time-To-Value
AI-driven employee time-to-value measures true business impact to prove business value. AI-driven employee TTV as a metric tracks how much faster a new or existing worker completes core tasks after adopting AI tools. If your AI spend on cloud, SaaS and internal hardware drops a specific process time from 10 hours down to two, you have clear, quantifiable evidence—through understanding the cost—that productivity gains can directly justify the infrastructure costs. – Mark Brown, The Mark of Security Ltd
Business-Funded AI Spend
A useful test is how much of the AI portfolio the receiving function would fund from its own budget. Central AI money hides weak value because the cost sits with a transformation program while the benefit is claimed locally. Ask each business owner to absorb the run-rate at renewal, and the honest answer arrives faster than any dashboard. – Anna Drobakha, Groupe SEB
Revenue Per Employee
The metric I’d watch is revenue per employee. As AI increases individual productivity, that should translate into greater business output without a proportional increase in headcount. If revenue per employee is rising as AI investment grows, you have a clearer line between that investment and measurable business value. – Josh Dunham, Reveel
Cost Per Completed Business Outcome
Tie the AI spend for each use case to a completed unit of business value, such as a resolved ticket, closed deal or approved claim. While there’s no single best metric, use something that both finance and product leaders can align on. – Ashish Agarwal, OMNIA Partners
Pre-AI Performance Baseline
Establish a baseline that’s captured before AI touches the workflow. At my former company, profiling ML models running on TPUs taught me that a measurement is only meaningful against what came before. Cost per outcome is the right metric, but most companies compute it with no pre-AI number to compare against, so it proves nothing. Measure the workflow now. The baseline disappears the moment you turn AI on. – Prashant Jalan, Guickly
AI Waste Rate
The metric I watch is the waste rate: the share of AI spend that produced work we didn’t keep, whether that’s drafts nobody shipped, code that got reverted or answers a person had to redo. Cost per successful outcome measures your wins and hides what the losses cost, and with nondeterministic systems, the losses are where the money goes. When that waste rate falls each quarter, AI is paying off. – Andrew Siemer, Inventive
Straight-Through Processing Rate
The metric I watch is straight-through rate: the share of AI work that finishes end-to-end with no human touch. It exposes what most AI budgets hide: the quiet rework after the model runs. If that rate climbs, the spend is buying real capacity. If people still fix everything, you are funding comfort, not value. Cost per outcome assumes the AI matters. – Ganesh Ariyur, Transform Smarter
AI Learning Yield
We track “AI learning yield”—the volume of critical business assumptions we validate per AI dollar spent. It measures our ability to rapidly pressure-test ideas, pivot capital to winning strategies, and capture strategic value alongside baseline ROI. – Kostiantyn Gitko, Devox Software