▶ Full Post Text
In April 2026, Bryan Catanzaro, vice president of applied deep learning at Nvidia, said something that shouldn’t have been controversial but absolutely was: for his team, the cost of compute is far beyond the cost of the employees.
That sentence should have ended the conversation about AI replacing human workers. It didn’t. Instead, companies like Meta, Microsoft, and Uber have doubled down, firing thousands of people to cut costs, then spending multiples more on AI infrastructure than they saved. Uber reportedly burned through its full year AI budget in 4 months. We’re watching a trillion dollar industry bet everything on a technology that, for most use cases, costs more than the thing it’s supposed to replace. And nobody’s really talking about what happens when the market figures that out.
The Numbers Tell a Story of Desperation
OpenAI reportedly spent over $5 billion on compute against roughly $4.9 billion in revenue in a recent fiscal period. They’re essentially breaking even on infrastructure before you account for salaries, rent, or R&D. Anthropic is valued near $1 trillion. Neither company is profitable.
And the pricing ceiling is real. If you raise API costs or subscription fees much higher, you hit the wage floor where hiring a human just makes more economic sense. That ceiling isn’t theoretical. It’s the structural limit on every AI company’s revenue model, and it varies by role and geography. A junior developer in San Francisco, a support rep in Manila, a content writer in Austin. Each one represents a different price cap the AI vendor cannot exceed for that function.
Where the Ceiling Actually Sits
A 2024 MIT study analyzed the economics of AI automation across job categories and found something striking: AI automation was economically viable in only 23% of roles studied. In the remaining 77%, the total cost of implementation, maintenance, and compute significantly exceeded human wages.
Run the math yourself. A junior developer in San Francisco costs roughly $100K to $150K annually, fully loaded. Heavy agentic API workloads for equivalent output, once you factor in prompt engineering, guardrails, error correction, and rework, can run $15K to $20K per month at scale. That’s $180K to $240K per year. You’re already above the human salary floor, and you haven’t hired anyone.
This is showing up in real budgets right now. IT departments are reporting AI spend that exceeds the salaries of the teams using it. Companies that cut headcount to fund AI adoption are discovering the replacement costs more than the people did.
The Pricing Shell Game.
Look at the pricing trajectory since these tools launched. Early free tiers gave way to $20/month subscriptions. API pricing has been restructured repeatedly across model generations. On paper, some per token prices have dropped. Claude Opus went from $15 per million input tokens to $5 across generations.
But the headline price drop is misleading. Newer tokenizers can use up to 35% more tokens for the same text. Usage based billing changes, feature level charges, and cache pricing add layers that make true cost comparison nearly impossible. The effective cost per unit of work has not fallen the way the sticker price suggests.
The pattern is clear: these companies are experimenting with pricing architecture because they haven’t found a model that works. They can’t raise prices enough to be profitable. They can’t lower them enough to escape the comparison against simply hiring someone.
“But Moore’s Law Will Fix It”
Some will argue falling compute costs save the model. Chips get cheaper, margins compress, volume makes up the difference. That’s technically true and it misses the capital problem entirely.
Infrastructure doesn’t decline to zero cost. Hyperscalers spent over $400 billion on data center buildout in 2025, with 2026 projections pushing toward $600 billion. That’s upfront capex that has to be financed through retained earnings, bank debt, or equity raises.
Here’s the problem: why would a bank finance, or investors buy equity in, assets they know will be obsolete or deeply depreciated in 2 to 4 years? If your newest GPU cluster is outdated by 2028, the debt servicing doesn’t disappear with it. And you can’t just stop upgrading. You have to keep buying faster hardware to stay competitive. So you issue more equity, take on more debt, and repeat. It’s a cycle of returning to investors and lenders to fund equipment that depreciates faster than it generates returns.Moore’s Law doesn’t solve that. It guarantees it.
The Valuation Math Doesn’t Close
Here’s where it breaks down for investors. Industry analysis suggests that if current costs and pricing held, AI companies would need close to $2 trillion in annual revenue by 2029 to justify the capital already poured into data centers. For context, that’s more than the combined annual revenue of Google, Microsoft, and Amazon.
That market doesn’t exist yet. And if it ever did, the pricing power to capture it wouldn’t, because the human salary ceiling kicks in first. Every dollar of price increase pushes more customers back toward hiring people.
You can verify the spending side yourself. Google discloses its capex in SEC filings and earnings calls. Microsoft, Nvidia, and the other public infrastructure players all report the buildout numbers. The spending is documented. The revenue that justifies it is projected.
So either these companies find a way to reduce infrastructure costs dramatically, they accept far lower margins than their valuations imply, or the market recalibrates. None of those outcomes supports a $1 trillion valuation under current business models.
So Here’s What I’m Asking
Where is the ceiling for your work? If Claude or GPT pricing doubled tomorrow, would your company keep paying, or start interviewing?
At what point do investors stop accepting growth narratives and start demanding profitability?
And does anyone seriously believe a company can sustain a trillion dollar valuation selling a product that gets less competitive every time they raise the price?
Curious what this community thinks, especially those of you running real workloads through the API. Your usage bills are the data point that settles this.