Recently, Uber's COO said AI costs are getting "harder to justify." Microsoft canceled most of its Claude Code licenses, citing spend. And according to Axios, one organization burned through half a billion dollars in a single month after failing to put usage limits on employee AI licenses.
By Neil Dhar | Senior Vice President, IBM Consulting
There's a term for the pattern that drove these situations: tokenmaxxing. The organizational push to use as much AI as possible, as fast as possible. It emerged from two years of competitive anxiety, where the pressure to adopt AI outpaced serious consideration of long-term ROI. In the absence of true metrics, organizations created usage leaderboards, which people quickly learned to game, and usage soon became a proxy for value.
The bill is starting to come due. And in most organizations, the CFO is the one holding it.
The cost structure hasn't caught up to the ambition
Most enterprises still don't have the financial models and discipline to accurately measure what AI costs them. They can track what they're paying for AI licenses, but few organizations have a reliable framework for attributing token consumption, compute, and spend to any real business outcome.
For the past few years, many organizations have been chasing the “AI dream.” It was seen as a technology initiative, rather than a business transformation, and nobody was asking whether the return on AI investments was showing up on the P&L.
According to research from the IBM Institute for Business Value, seventy-nine percent of executives expect AI to drive significant revenue by 2030. Only 24 percent know where it's going to come from. If you can't define the outcome, you can't measure the return. And you can't defend the spend to a board.
What disciplined AI adoption looks like
The fix isn't to cut, it's to focus. When AI is layered on top of existing workflows as a general-purpose productivity tool, token spend has no anchor. When it's embedded in a specific process tied to a specific outcome, the economics change.
First, every AI use case needs to connect to a specific workflow and a measurable outcome, with returns tracked in three-to-six-month increments. Like any other capital allocation, if it can’t deliver a 2.5x to 3x return, whether through time saved, better customer and employee experiences, or new revenue, pass on it.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online