Enterprise AI agents are starting to look less like a subscription perk and more like a metered workplace bill. Simon Willison argues that OpenAI and Anthropic have found a version of product market fit through coding agents such as Codex and Claude Code, because companies are paying closer to API prices when employees use them heavily. The uncomfortable part is also the point: the bills are high because people are actually using the tools.
Table of Contents
The short version
- Heavy personal plans can make Codex and Claude Code look cheap compared with API-equivalent token usage.
- Enterprise AI agents change the business model because companies pay for team usage, contract terms, support, and usage controls.
- Hacker News readers mostly agreed the usage is real, but argued hard about whether the economics can survive open models, cheaper providers, and missing ROI data.
- The practical test is no longer whether a coding agent is impressive. It is whether a team can prove the agent is worth the tokens it burns.
What happened
Willison compared his own heavy usage of Anthropic Claude Code and OpenAI Codex with what the same token volume would cost at API prices. His estimate came to about $1,199.79 for Anthropic and $980.37 for OpenAI over 30 days, while he paid $200 total for two consumer plans.
That gap matters because the enterprise side appears to be moving in the opposite direction. Willison points to Anthropic’s shift from broad seat-based expectations toward $20 per seat per month plus API-style usage, and to OpenAI’s Codex rate card, which says April 2026 pricing moved toward API token usage rather than per-message pricing. Anthropic also announced Claude Code for Team and Enterprise plans, with admin controls and higher business limits.
The claim is not that every AI lab is suddenly healthy. It is narrower: enterprise AI agents give OpenAI and Anthropic a way to charge where the usage actually happens. Coding agents run longer jobs, inspect repositories, rewrite files, execute commands, and loop through fixes. That can consume far more tokens than a chat session.
Why this is worth watching: enterprise AI agents
Enterprise AI agents create a cleaner revenue story than consumer chat subscriptions. A consumer pays a flat monthly fee and may use far more inference than the plan costs. A company that rolls an agent into daily engineering work can be billed by usage, seats, support, and contract commitments.
That also explains why the sales motion looks old-fashioned. Willison scraped job listings and found large chunks of OpenAI and Anthropic hiring tied to enterprise sales, customer support, account management, and forward deployed engineering. The irony is useful. The companies selling automation still need humans to close enterprise contracts, handle security reviews, and keep customers from turning a runaway token bill into a cancellation.
For app and developer tool builders, the lesson is blunt. If an agent marketplace or coding platform wants durable revenue, discovery is only the start. Teams also need budgets, admin controls, usage reporting, and a way to tell whether the agent saved more money than it spent.
For more coverage of software teams, AI products, and developer platforms, see the IT & AI archive.
What Hacker News readers are arguing about
The Hacker News thread was huge and messy, which fits the topic. The most useful split was between “usage proves demand” and “usage does not prove sustainable economics.”
The bullish camp treated $200 per user per month as ordinary enterprise software pricing, especially compared with expensive engineering, CAD, cloud, or security tools. Some readers argued that the controversy itself proves the tools have entered real workflows. Nobody complains about a bill for software nobody uses.
The skeptical camp kept coming back to ROI. Several commenters asked whether companies can show more shipped product, better features, or higher engineering output, instead of more commits and larger token bills. One recurring objection was that a 20% to 40% productivity lift may fail to support the scale of infrastructure spending implied by trillion-dollar valuations.
A second line of skepticism was commoditization. Readers pointed to cheaper open-weight models, Chinese providers, caching, and alternative inference platforms. Their argument was not that Claude Code or Codex are useless. It was that API-priced usage may be a temporary window if “good enough” models keep getting cheaper.
There was also a pricing trust issue. Some commenters pushed back on the idea of “$2,000 worth of tokens” as if token list prices were an objective measure of value. That is a fair caution. List price, marginal compute cost, customer value, and investor narrative are four different things.
The practical read
Enterprise AI agents are a budget conversation now. If you run engineering, the next step is to avoid both blanket bans and unlimited access. Put them in the same category as cloud spend: useful, measurable, and dangerous when nobody owns the bill.
Track agent usage by team, task type, and outcome. Watch where agents save review time, test-writing time, migration effort, or support toil. Also watch where they create cleanup work. The argument for enterprise AI agents gets much weaker if the only metric is token volume.
For OpenAI and Anthropic, the next year is a proof period. They have signs of demand, enterprise contracts, and tools that people use all day. Now they need to show that usage can turn into durable margins before cheaper models and procurement teams squeeze the story.