Somewhere in corporate America this week, a company burned $500 million in a single month on AI tools. Not because they were building something big. Because they forgot to set a spending cap on employee licenses.
The culprit has a name: "tokenmaxxing" (the corporate habit of maxing out AI usage without ever measuring whether it's actually doing anything useful).
One consultant told Axios a client’s employee was using their enterprise AI subscription to check the weather, while Uber’s CTO reportedly blew through the company’s full 2026 Claude Code budget by April, and their COO was not happy about it.
Amazon had to pull an internal AI usage leaderboard after employees started chasing token counts instead of actual work. And now WSJ says companies including Uber, Microsoft, Meta, and Salesforce are starting to ration AI access, limit who gets the expensive tools, and push employees toward cheaper options.
The bigger story is that AI is entering its “expense report” era. Google is already pitching cheaper models as a billion-dollar enterprise savings play, while Jellyfish found heavy Claude Code users burned about 10x more tokens than mid-level users, even though output rose only about 2x. Translation: the new workplace flex is using AI well enough that your CFO does not learn your name.
We've heard of burning money. We didn't think people meant it literally! Anyway, this has us thinking we need such a thing as a “minimum viable product token”, or mvpt, where you benchmark skills, tasks, models, and agents based on the mvpt required to complete the job.
For the last year, the easy story was adoption. How many employees are using AI? How many prompts are they sending? How many tokens are they burning? If the numbers went up, leadership could say the company was “AI-forward,” which is corporate for “please do not ask us what this did to revenue yet.”
Now the bill is arriving.
“Please don’t use AI just for the sake of using AI,” Amazon SVP Dave Treadwell told staff, according to Business Insider. But sir, that is LITERALLY what the employees were told to do...
Companies pushed people to use AI more. People used AI more. Now everyone has to prove the usage meant something. Uhhh.... what did you think was going to happen??!
What tokenmaxxing actually means
Tokenmaxxing is the habit of maximizing AI usage because the usage itself starts to look like progress.
A token is the little chunk of text an AI model reads or writes. A word can be one token, part of a token, or several tokens, depending on the language, punctuation, and formatting. The Claude Tokenizer link you shared is useful because it shows the thing most people never see: every sentence, bracket, quote mark, and line break has a cost.
That makes tokens feel wonderfully measurable. You can count them. You can chart them. You can rank teams by them. You can turn them into a leaderboard and watch employees sprint toward the number like someone put a Patagonia vest at the finish line.
The problem is that token usage measures motion, not value.
A team can burn tokens by refactoring a real codebase, summarizing customer tickets, generating sales research, or testing a production workflow. The same team can burn tokens asking a chatbot to check the weather, rewrite the same Slack message nine times, or run an agent in circles because nobody gave it a stop condition.
The meter moves either way.
The Reddit field report
The funniest version of this story came from a Reddit post in r/ClaudeAI from a user who said they burned through 1,156,308,524 input tokens in May and wanted to share what they learned.
The post is part guide, part confession booth, part warning label. It explains the basics: tokens are roughly four characters in English, non-English text can tokenize less efficiently, JSON is expensive because every quote, colon, bracket, and comma counts, and output tokens usually cost more than input tokens.
The advice is practical:
- Use cheaper models for simpler jobs.
- Put static instructions before dynamic content so prompt caching can help.
- Keep outputs short when you only need IDs, labels, or classifications.
- Use batch processing for non-urgent work.
- Set billing alerts and hard caps before an agent discovers its artistic passion for infinite loops.
Reddit, naturally, responded with the sympathy of a medieval village watching someone invent fire by hugging it.
“I touched the stove 900 times, here’s my guide to heat” is a mean comment, but as editorial framing, it is annoyingly efficient.
The useful part is the gap between the jokes and the lesson. A billion tokens sounds absurd until you realize how quickly agentic workflows can spend them. A normal chatbot answer has one request and one response. An agent can search, read files, call tools, inspect results, revise its plan, spawn subtasks, run tests, and repeat the loop. Every step adds context. Every step adds more tokens.
Claude 4.8 made the tradeoff visible
The timing matters because Anthropic just released Claude Opus 4.8, and the release makes the token tradeoff more explicit.
Anthropic says Opus 4.8 is available at the same regular API price as Opus 4.7, adds better performance, and gives users more control over effort. Lower effort should respond faster and use rate limits more slowly. Higher effort, including “extra” or “xhigh” in Claude Code, spends more tokens to chase better results.
That is a useful product change and a perfect metaphor for the entire market. AI work now has a gear shift.
The Reddit threads around Opus 4.8’s highest effort setting and “how good is it?” are mostly people joking about asking Claude to build GTA VI from scratch and watching their monthly quota evaporate. Under the jokes, though, is the serious operating question every AI-heavy team now faces:
Where should the expensive intelligence go?
One camp says to use the best model for planning, then hand execution to cheaper models. The other says a weak plan can poison the whole job, so the premium model should handle the highest-risk implementation work. Both are right in different contexts, which means the real answer is workflow design, not model loyalty.
Use the expensive model where judgment matters. Use cheaper models where repetition matters. Use automation where the task has a clear definition of done. Add humans wherever the cost of a confident mistake exceeds the cost of review.
The hidden tax is context
The practical token problem is rarely “one prompt was too long.” The bigger problem is context bloat.
Teams keep adding more instructions, more examples, more files, more chat history, more tool results, and more structured data. The prompt becomes a junk drawer with an API key.
Prompt caching helps when repeated requests share the same prefix. Anthropic’s prompt caching docs say the default cache lifetime is five minutes, cache reads cost 0.1x the base input token price, and a one-hour cache is available at additional cost. That can be a huge savings for repetitive workloads with long system prompts, but only when the workflow is built to reuse the same stable context.
Batch processing is another lever. Anthropic’s Message Batches API is designed for asynchronous work and charges 50% of standard API prices, with most batches completing in under an hour. That is perfect for evaluations, bulk classification, content analysis, and other work that can wait.
Then there is the less glamorous fix: stop sending giant structured blobs when plain text will do. The Reddit poster’s JSON warning is directionally important. Structured formats are useful when software needs to parse the result, but they can be wasteful when the model only needs to understand the content. If you are pasting a nested JSON object into a prompt because it feels professional, you may be paying extra for punctuation.
The research backs up the worry
This is why the tokenmaxxing backlash has teeth.
A recent arXiv paper, “How Do AI Agents Spend Your Money?”, studied token consumption in agentic coding tasks and found that agentic tasks can consume 1,000x more tokens than code reasoning and code chat. The authors also found that token usage can vary by up to 30x on the same task, higher token usage does not reliably mean higher accuracy, and frontier models tend to underestimate their own token costs.
That last point is nasty. It means you cannot always ask the agent whether the job will be cheap and trust the answer. The model may be a good worker and a bad accountant.
For companies, that creates a strange management problem. The thing doing the work also helps decide how much work to do. Without budgets, checkpoints, and clear success criteria, an agent can wander through compute the way a new intern wanders through office snacks: with confidence, curiosity, and no personal financial exposure.
Usage was the training wheel metric
The first phase of AI adoption needed usage metrics. Companies had to know whether employees were trying the tools at all.
That phase is ending.
Usage is still useful as a diagnostic. A team with zero usage probably has a training problem, a workflow problem, or a tool-access problem. A team with skyrocketing usage may have found a valuable workflow. It may also have found a leaderboard.
The better metric is useful work completed per dollar.
That sounds obvious, but it changes what companies measure. Instead of asking, “How many tokens did this team use?” leaders should ask:
- Which workflow did this replace or improve?
- How much time did it save after review and rework?
- How often did the output require human correction?
- What would this have cost through the previous process?
- Does the result improve revenue, quality, speed, compliance, or customer experience?
This is where the Amazon story matters. Shutting down a token leaderboard is not an anti-AI move. It is a pro-useful-AI move. The company is still tracking token usage for cost management, according to Business Insider. The shift is away from celebrating raw consumption as productivity.
The counterargument: some teams should spend more
There is a credible pro-tokenmaxxing argument, and it deserves more than a dunk.
For individual builders, startups, and elite teams, aggressive AI usage can be the fastest way to learn what the tools are actually good at. A startup with high revenue per employee might rationally spend more on AI if it compresses development cycles, raises output quality, or lets a tiny team compete with a larger one.
That argument gets weaker inside a large company where thousands of employees have access, incentives are blurry, and nobody knows which workflows are paying back the spend.
In other words, tokenmaxxing can be exploration when the person spending the tokens owns the outcome. It becomes theater when the person spending the tokens is optimizing for visibility, leaderboard position, or “AI adoption” vibes.
What companies should do now
The answer is discipline, not panic.
Teams should still experiment. Cutting everyone off because a leaderboard went sideways would repeat the same mistake in reverse. The goal is to make AI spending legible enough that good use can grow and waste can die quietly.
A sane token policy has a few parts:
- Budgets by workflow, not just by user. A customer-support summarizer and an open-ended coding agent should have different limits.
- Model routing. Cheap models handle simple classification, formatting, and extraction. Premium models handle ambiguous planning, high-risk reasoning, and final review.
- Output limits. Ask for IDs, diffs, labels, or short rationales when you do not need prose.
- Context hygiene. Send the model what it needs, remove stale chat history, and avoid dumping whole files when a targeted excerpt works.
- Human checkpoints. Long-running agents should pause before expensive branches, destructive actions, or major rewrites.
- ROI reviews. Every high-usage workflow should have a before-and-after comparison that includes rework.
The companies that get this right will spend a lot on AI. They will also know why.
What to watch next
The unresolved issue is whether enterprises can build better AI accounting before finance departments force crude limits on everyone.
That would be the worst version of the backlash. Some teams really should use more AI, especially when the work is measurable and the payoff is clear. Other teams need guardrails because “agentic” can become a polite word for “nobody knows when the meter stops.”
The next useful dashboard will look less like a leaderboard and more like a profit-and-loss statement for work: what the AI touched, what it cost, what changed, what broke, and what a human had to fix.
Until then, the age of “look how many tokens we used” is ending.
The age of “show me what those tokens bought” has begun.
