Blog→AI Economics
AI Economics8 min read

Most AI Projects Just Burn Cash. Here's How to Make Them Profitable.

An expert analysis on AI unit economics, the "Evergreen Ratio", and calculating the AI Volatility Tax to stop bleeding cash on inferencing.

By Richard Ewing·
Share:

The AI Profitability Crisis

In 2026, the era of deploying AI simply to boast about having "AI inside" is functionally dead. Executive boards are no longer accepting pure R&D burn without measurable unit economics. We have transitioned from the awe of capability to the brutal reality of the P&L.

There are two compounding liabilities that drag most AI projects into "Negative Carry" (costing more to run than they generate): The AI Volatility Tax and an abysmal Evergreen Ratio.

The AI Volatility Tax

Every non-deterministic AI inference carries a Volatility Tax. This is the hidden cost of human-in-the-loop verification required because probabilistic systems hallucinate. If your AI writes code 10x faster but requires your senior engineer to spend 4 hours auditing its outputs to prevent a production vulnerability, your AI feature has negative unit economics.

You must factor the labor cost of verification directly into the Cost of Goods Sold (COGS) for your AI features. The solution is the Execution Layer - a deterministic boundary that verifies and enforces strict schemas on LLM outputs before they are processed by your business logic. By shifting validation to code rather than humans, you minimize the Volatility Tax.

The Evergreen Ratio

If every query to your system requires a live inference from a Frontier Model (like GPT-4 Opus or Claude 3.5 Opus), you will bankrupt yourself at scale. Profitability is determined by the Evergreen Ratio: the ratio of Cached/Pre-calculated Responses to Live Inferences.

High profitability AI systems rely heavily on semantic caching, embeddings, and pre-computation. The most profitable AI systems are the ones that use the least amount of live AI execution in production. By driving your Evergreen Ratio up, you detach your revenue scaling from your compute scaling.


To measure your feature's economic viability, use the AI Unit Economics Benchmark (AUEB) or the Volatility Tax Auditor (VTA) tools. Read the full post on Built In.

Like this analysis?

Get the weekly engineering economics briefing - one email, every Monday.

Subscribe Free →

More in AI Economics

Canonical Frameworks

The Software Phase Transition

The Software Phase Transition models the structural breakdown of traditional product management as the marginal cost of writing software approaches zero. In the pre-AI era, developer bandwidth was scarce and expensive. Organizations operated in the Solid state: managing 2-week sprints, grooming backlogs, and writing exhaustive PRDs to ration engineering hours. As tooling improved, organizations transitioned into the Liquid state of adaptive teams with fluid prototyping. With generative AI and autonomous agent pipelines, code generation costs collapse toward zero, propelling organizations into the Gas state. In the Gas state, developer capacity is no longer the rate-limiting constraint. Unbounded code generation creates exponential organizational complexity, coordination tax, and margin collapse. This forces a fundamental leadership evolution: product leaders must transition from managing feature velocity to becoming Product Economists who govern capital, system architecture efficiency, and uncertainty.

Read Definition →

Cost of Predictivity

The Cost of Predictivity measures the variable cost of AI accuracy. Unlike traditional software with near-zero marginal costs, AI features have significant variable costs that scale with both usage AND accuracy requirements. As AI correctness increases, cost scales exponentially - not linearly. This is the fundamental economic challenge of AI products. Traditional software follows a simple cost model: high fixed development cost, near-zero marginal cost per user. Build the feature once, serve it to millions for pennies. AI products break this model entirely. Every AI query costs compute. Every inference requires GPU cycles. Every improvement in accuracy requires either more sophisticated prompts (more tokens = more cost), retrieval-augmented generation (vector DB queries + embedding generation), or fine-tuned models (massive training costs amortized over queries). The cost structure looks more like a manufacturing business than a software business. The exponential curve is the killer. Moving from 80% accuracy to 90% accuracy might cost 2x. Moving from 90% to 95% might cost 5x. Moving from 95% to 99% often costs 10-20x. This is because the easy cases are solved by the base model, and each additional percentage point of accuracy requires increasingly sophisticated (and expensive) techniques to handle edge cases. This creates what Richard Ewing calls the AI Margin Collapse Point: the usage volume at which AI feature costs exceed the revenue they generate. Many AI features that work beautifully in prototype (low volume, don't need high accuracy) become economically devastating in production (high volume, users demand high accuracy). The AI Unit Economics Benchmark (AUEB) calculator at richardewing.io/tools/aueb helps companies calculate their Cost of Predictivity and identify their specific margin collapse point before it hits their P&L.

Read Definition →
📊

Richard Ewing

The AI Economist - Quantifying engineering economics for technology leaders, PE firms, and boards.

⚡

Want to apply this to your organization?

Run a free diagnostic first. If the numbers concern you, book a session to build a remediation plan.

Richard Ewing: AI Economist & Capital Auditor