
Gaurav Vashisht, Forbes Councils Member
· 2 min read
Measuring The Exact ROI Of AI : From Tokens To Tangible Value
Gaurav Vashisht has over 22 years of experience building and supporting finance and enterprise systems.
Enterprises can count every token their AI agents consume. Almost none can confidently say what they got back and showcase real, tangible and quantifiable ROI.
That is the state of AI measurement today: adoption charts climbing in every direction and no defensible answer to the only question that matters to a board, which is what the investment returned.
This is the central unsolved problem of AI ROI, and it is about to matter enormously because next year’s AI budgets are being set right now on the basis of adoption charts rather than return.
Why The Number Is So Hard To Get
Return needs a denominator. To know what an AI agent saved, you need to know what the work cost before.
This is where the trouble starts because nobody in the building agrees. Ask finance how long an invoice reconciliation takes, and they may say five minutes because they only see the approval click. Ask operations, and they may say five hours because they do the matching. Ask engineering, and they may say five days because they count the exceptions. Build an ROI figure on any one of those numbers, and the other two departments will dispute it. Disputed numbers do not get acted on.
The problem gets worse when the work is knowledge work. A developer fixes a bug with the help of a coding agent. The ticket says it took six days, but the developer handled 20 other tickets and attended a conference in between. The agent log says it took 30 minutes, but before opening the agent, the developer listened to podcasts, sat through team calls and consulted senior colleagues. The real effort happened outside of anything the tools can see. Undercount it, and you overstate what AI did. Developers know this, which is why they do not trust the numbers, which is why the numbers never get used.
Three Ideas That Close The Gap
The approach I have been developing to use in my own work takes each of these problems in turn.
Original source
This story was published by Forbes: Innovation and written by Gaurav Vashisht, Forbes Councils Member. SyncAI.news shows a preview; the complete article is on the publisher's site.
Read the full story on forbes.com


