Published on June 3, 2026 · Updated on October 22, 2026
When enterprise AI starts costing more than humans: the economic turning point of May 2026
Microsoft removes Claude Code from its own engineers. Uber exhausts its 2026 AI budget by April. The "usage-based API" model meets accounting realities.
And with it, a fundamental question: can we still afford an AI stack when we don't control either the cost or the supplier?
1. The event
In May 2026, two weak signals became major warnings.
Microsoft has begun removing Claude Code licenses from engineers in its Experiences + Devices division (Windows, Microsoft 365, Teams), who must migrate to GitHub Copilot CLI by June 30, 2026, the end of its fiscal year. The official reason given is to unify the tools. According to the specialized press, the cost of intensive use played a role in the decision, just six months after deployment.
At the same time, Uber acknowledged, through its technical director Praveen Neppalli Naga in The Information, that it had consumed its entire 2026 budget for AI coding tools in four months only. The usage-based billing — tokens consumed, API calls, processing time — had exploded far beyond expectations. Result: a spending cap per employee and per tool.
These two cases are not anecdotes. They are the first visible signs of a structural reversal AI, which was supposed to reduce costs, is actually causing them to explode — invisibly, without limits and often irreversibly.
Key figures
2. The mechanism: why usage-based pricing is exploding
The dominant business model for enterprise AI today is based on a simple principle: You pay for what you consume.. Input tokens, output tokens, API calls, GPU time.
In theory, it's flexible. In practice, it's a trap.
Three factors converge to cause budgets to drift:
The price per token doesn't tell the whole story. Agent-based usage consumes enormous amounts: a coding tool that runs alone for hours accumulates millions of tokens. At Uber, the most intensive users were spending between $500 and $2,000 per month each.
An AI agent processing invoices doesn't consume the same amount of resources depending on whether it receives 50 or 500 documents per day. Yet no one bases an AI budget on peak workload. Teams only discover the bill at the end of the month.
In most large organizations, teams use AI tools without centralized validation. Each department subscribes to its own APIs, creates its own agents, and generates its own costs—without any visibility for the IT department. This phenomenon, called shadow AI, escapes all budgetary monitoring.
An annual budget consumed in a few months, just like at Uber. Without anyone seeing the downward spiral coming.
3. Dual Dependency
The problem of costs is only the visible part of a deeper issue: the dependence.
Technology dependence First, when a company builds its entire AI infrastructure around a single provider—OpenAI, Anthropic, Google—it ties its operations to that provider's decisions. Price changes, modifications to terms of service, performance degradation, model removal: the company suffers without recourse.
Even Microsoft, which has its own tools, had to choose between paying more and cutting off access. A small or medium-sized enterprise (SME) that relies on a single provider often doesn't even have that option.
Geographical dependence Next. Almost all consumer AI APIs pass through data centers located in the United States. This means that your customer data, your internal documents, your business processes pass through infrastructures subject to the US CLOUD Act.
For a Swiss SME, this represents a double risk: legal (potential non-compliance with the nLPD and the GDPR) and operational (Service may be interrupted in case of sanctions or regional access restrictions).
L'’agnosticism about models It is not a technical luxury. It is a condition for operational survival.
4. The sovereign and multi-model alternative
In light of these observations, an alternative model is emerging. It is based neither on a single supplier nor on opaque billing.
It rests on three pillars:
Sovereignty of deployment. AI is deployed directly on the client's infrastructure — on-premise or on a Swiss cloud (Infomaniak). The data remains within the defined scope.
Agnosticism on models. The architecture isn't tied to a single model. If GPT-4.1 becomes too expensive, we switch to Mistral, LLaMA, or an open-source model. That's the approach. multi-models : the value is in the orchestration, not in the engine.
Predictable, contractually agreed and capped cost. No token-based billing. No surprises at the end of the month. A clear subscription that covers deployment, maintenance, and upgrades.
This is the approach that Wiven has applied since its creation: AI agents deployed on site, integrated with existing tools (SAP, Abacus, Odoo), managed with the client — not a generic SaaS imposed from the outside.
5. Five questions to ask before signing an AI contract in 2026
These questions are not neutral. They reflect what we believe to be the defining criteria for a successful AI project. We are sharing them transparently so that every company can evaluate its options—including those outside of Wiven.
Billing model
Does my provider bill me based on usage (tokens, API calls, GPU) or on a predictable model? If it's based on usage: is there a contractual limit? What happens if my usage doubles in three months?
Data location
Where does my data pass through? Which datacenter, in which country, under which jurisdiction? Do I have a contractual guarantee that my data does not leave Switzerland?
Supplier dependency
What happens if my AI model provider raises their prices by 30 %? Changes their terms? Removes the model I'm using? Do I already have a technical alternative in place?
Ownership and portability
Do I own my AI agent, its prompts, and its training data? Can I migrate to another provider without starting from scratch?
Transparency of actual costs
What is the true cost of each deployed AI agent, including hidden costs (training, integration, maintenance, model evolution)? Does my provider give me this visibility?
The end of a certain naiveté
Enterprise AI is entering a new phase. One where productivity promises clash with accounting realities. One where CIOs discover their AI budget has been exhausted before the end of the first half of the year.
This turning point is not bad news. It's a opportunity to regain control.
The companies that will emerge victorious from this period are those that have made three clear choices: a cost model predictable, an architecture multi-models, and a deployment sovereign.
Not because it's trendy. Because it's the only way to build AI that lasts — without depending on a supplier, without being subject to their prices, and without compromising data security.
Sources
- Microsoft reports are exposing AI's real cost problem, Fortune, May 22, 2026.
- Microsoft's quiet Claude Code retreat and the real cost of enterprise AI, The Next Web, May 2026.
- Uber Burns Its 2026 AI Budget In Four Months On Claude Code, Forbes, May 17, 2026.
- Uber Blew Through Its 2026 AI Budget in 4 Months — Now It's Capping Employee Use, Inc., 2026.
- Current data protection law is directly applicable to AI, PFPDT, November 9, 2023.
To discuss your AI strategy, your actual costs, or your vendor dependency — let's talk.