The tools are in the stores. The results aren't.
Starbucks doesn't usually make news for what it quietly stops doing. But last week Reuters reported that the company had discontinued an AI-powered inventory counting system built by NomadGo — less than a year after rollout. The reason was straightforward and unglamorous: the tool kept getting it wrong. Store employees flagged persistent inaccuracies on basic tasks, including miscounting milk carton volumes and failing to reliably track back-of-house beverage syrups.
This is the kind of failure that doesn't show up in earnings calls. It shows up when a shift manager has to reconcile what the system says with what's actually on the shelf at 6am.
Token budgets don't survive contact with developers
Uber's situation is different in kind but similar in structure. The company gave thousands of software engineers access to Anthropic's Claude Code — one of the more capable AI coding tools on the market — and watched its entire annual AI token budget disappear in four months. Individual engineers were running up monthly bills between $500 and $2,000.
Uber is now describing that spend as increasingly hard to justify and says it will rethink its budgeting approach. That's a reasonable response. It's also a signal that enterprise AI rollouts need cost controls that most companies haven't built yet. Giving developers access to a powerful tool without usage guardrails is the operational equivalent of handing out corporate cards with no spending limits and being surprised when the bill comes in.
The ROI math is brutal for almost everyone
The financial picture behind these deployments is not encouraging. Investment bank Panmure Liberum modeled the returns on AI infrastructure spending across major tech companies and found that, under best-case assumptions, Microsoft's AI initiatives are returning -9% on investment. Google sits at -15%, Meta at -28%, and Oracle at -35%. Amazon is the only one in positive territory, barely.
These are best-case numbers. The actual figures, if the deployments continue to underperform, will be worse.
Regulation is arriving before the returns do
Illinois passed SB315, making it the first state to require independent third-party safety audits, risk disclosures, and incident reporting for large frontier AI developers. Industry groups flagged compliance cost concerns. That's a predictable response, but the law reflects something real: public and legislative patience with self-regulation is running thin.
In Pennsylvania, Republican lawmakers introduced bills to repeal tax breaks for AI data centers and give municipalities authority to impose 18-month construction moratoriums. A mid-May Gallup poll found more than two-thirds of adults oppose new AI data center construction — a majority said they'd rather have a nuclear plant nearby.
The political coalition that made large-scale AI infrastructure buildout easy is fracturing. That matters for capital planning, site selection, and the timeline on which any of these investments could realistically pay off.
What operators should watch
None of this means AI tools don't work. Some do, in specific contexts, with the right implementation. But the current moment is clarifying: the cost of a bad deployment is no longer just a write-off. It's a story. Anthropic has filed a draft S-1 with the SEC, which means the scrutiny on enterprise AI performance is about to get significantly more intense.
For operators, the practical question isn't whether to use AI tools — it's whether the deployment has clear success metrics, a defined budget ceiling, and someone accountable when the milk count is wrong.