BlogAI Economics
AI Economics10 min read read

The Generative AI Margin Squeeze

Leadership is demanding AI features, product teams are shipping them, and no one is calculating the unit economics until the cloud bill arrives.

By Richard Ewing·
Share:

The Generative AI Margin Squeeze: Why Power Users Destroy SaaS Economics

Across the enterprise software market, executive leadership is frantically demanding AI features, product teams are dutifully shipping them, and absolutely no one is calculating the underlying unit economics until the cloud infrastructure bill arrives. Venture capitalists and public markets are currently valuing generative AI startups exactly like traditional software-as-a-service (SaaS) businesses. In almost every case, this is a massive category error.

The Illusion of Infinite SaaS Margins

Traditional SaaS companies enjoy incredible financial use, typically boasting gross margins between 80% and 90%. The economic model is beautiful: you build the software once, and the marginal cost of adding a new user to the platform is effectively zero. Generative AI violently shatters this economic model.

When a user prompts a Large Language Model (LLM) inside your application to summarize a document or write an email, that specific query requires significant, highly expensive GPU compute. The marginal cost of usage is decidedly non-zero. The more your customers use the product, the more it costs you to run it. We call this structural paradox the Generative Margin Squeeze.

Synthetic COGS and the Power User Paradox

This introduces a terrifying dynamic into the SaaS playbook. In traditional software, a highly engaged power user is your greatest asset. They are your evangelists, they drive down your churn rate, and they easily justify your Customer Acquisition Cost (CAC). In a generative AI application, an unmanaged power user is a direct threat to your EBITDA.

If you charge a flat $20/month subscription for your SaaS product, but a single power user generates $30 worth of API calls to OpenAI, Anthropic, or your internal infrastructure, you instantly have negative unit economics. You are literally subsidizing your customer's AI usage. You are no longer a high-margin software company; you are a low-margin compute reseller.

The Evergreen Ratio: Defending Your Margins

To survive, AI product leaders must introduce aggressive Synthetic COGS modeling into their roadmaps. You cannot just measure daily active users (DAU) or user engagement; you must measure the exact compute cost of that engagement.

The solution is implementing the Evergreen Ratio.

The Evergreen Ratio is defined as the percentage of AI interactions that are served from a cached, pre-computed database versus those that require a live, expensive generation from the frontier model. If an overwhelming majority of your users are asking the AI to generate variations of the exact same output (e.g., summarizing standard quarterly earnings reports), you should not pay an LLM to reason through the problem from scratch every single time.

Leading organizations build interception layers (Deterministic Control Planes) that recognize routine queries and serve static, pre-approved assets. If your Evergreen Ratio is 0%, you are exposed to maximum financial volatility. The sweet spot for a highly profitable AI feature sits between 60% and 80% cached responses.

The Product P&L Test for AI

Before your team spends another six months building a Generative AI feature, force them to pass a rigid financial test:

  1. The Cost of Inference: Do you know exactly how many fractions of a cent it costs to run a single query through your chosen model architecture?
  2. The Margin Threshold: At what exact volume of user engagement does the feature flip from profitable to unprofitable? Have you instituted hardcoded fair-use caps or transition plans to consumption-based billing?
  3. The Value Prop: Does the AI fully automate the task, or does it just generate a sloppy draft the user must spend ten minutes editing? If human intervention is still required, you haven't eliminated labor costs - you've just shifted them.

If you cannot monetize your AI strategy through massive new revenue generation or specific, measurable cost mitigation, you are not building a product. You are conducting an incredibly expensive science experiment funded by your CFO.

Like this analysis?

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

Subscribe Free →

More in AI Economics

Related Canonical Concepts

AI Volatility Tax

The compounding gross margin penalty incurred when variable LLM inference query costs scale faster than subscription revenue, shifting server hosting into variable Cost of Goods Sold (COGS).

Read Concept →

Agent Kill Switch

A binary execution control mechanism that halts autonomous AI agent operations within 5ms when safety rules or environmental hash boundaries are breached.

Read Concept →

Deterministic Governance

The architectural pattern enforcing hard-coded, code-level execution gates and state verification outside the probabilistic LLM inference loop.

Read Concept →

The Product Economist

The executive discipline bridging engineering velocity, financial P&L contribution, and product margin strategy to prevent technical debt and AI COGS from destroying business valuation.

Read Concept →

The Negative-Carry Code Crisis

The systemic financial risk created when high-velocity AI code generation produces massive volumes of un-audited, low-trust technical debt that inflates ongoing maintenance OpEx beyond marginal value creation.

Read Concept →

Vibe Coding Debt

The engineering debt accumulated when developers accept AI-generated code based on superficial execution ("vibes") without understanding underlying architectural assumptions or edge cases.

Read Concept →

AI Governance

The enterprise control framework governing security, compliance, operational boundaries, and audit trails for autonomous AI models and multi-agent workflows.

Read Concept →

Shadow AI

Unmonitored artificial intelligence tools and autonomous agents deployed by employees without explicit IT or security oversight.

Read Concept →

AI Agent Sprawl

The uncontrolled accumulation and uncoordinated deployment of autonomous AI agents across an enterprise environment.

Read Concept →

Prompt Injection

A vulnerability where adversarial user inputs are crafted to override the original instructions of a large language model.

Read Concept →

Inference Economics

The financial discipline of managing, projecting, and optimizing the per query token costs associated with running large language models in production.

Read Concept →

Technical Insolvency

The critical threshold where the operational cost of maintaining a codebase and resolving technical debt exceeds the engineering capacity available for new feature development.

Read Concept →

The Innovation Tax

The compounding maintenance burden and operational friction incurred when new technology is deployed without decommissioning legacy systems, effectively taxing all future engineering velocity.

Read Concept →

The Coordination Tax

The non-linear increase in communication overhead, alignment meetings, and process friction that occurs when scaling engineering organizations, ultimately degrading per-capita execution capacity.

Read Concept →

The R&D Ponzi Scheme

The systemic masking of growing software maintenance liabilities (OpEx) behind inflated velocity metrics and new feature launches, creating a fragile engineering economy that requires constant new capital to sustain.

Read Concept →

Feature Bloat Calculus

The analytical framework for determining the precise point where the ongoing maintenance cost of a software feature exceeds its marginal revenue value, necessitating immediate deprecation.

Read Concept →

The AI Margin Squeeze

The systemic erosion of traditional SaaS gross margins caused by the integration of generative AI features, as variable compute and API costs scale linearly or exponentially with user engagement, fundamentally altering software unit economics.

Read Concept →

The 10-Man Parity Rule

The principle that heavily AI-augmented teams of ten elite engineers can now achieve execution parity with traditional enterprise engineering organizations of over one hundred, fundamentally altering the economics of software creation.

Read Concept →

Zombie Code & The Sunset Protocol

Zombie Code refers to deprecated or unused features that continue to run in production, consuming maintenance budget, compute resources, and engineering focus. The Sunset Protocol is the structured mechanism for financial remediation through systematic deletion.

Read Concept →

DORA Metrics Financial Translation

The analytical process of converting standard engineering performance metrics (Deployment Frequency, Lead Time, MTTR, Change Failure Rate) into direct financial liabilities and capitalization impacts on the P&L statement.

Read Concept →

Canonical Frameworks

Technical Insolvency Date

The Technical Insolvency Date (TID) is the specific future quarter when an organization's technical debt maintenance will consume 100% of engineering capacity, leaving zero time for new feature development. Every software organization accumulates technical debt over time - shortcuts taken under deadline pressure, aging infrastructure, deprecated dependencies, and code that nobody understands anymore. This debt isn't free. It requires ongoing maintenance hours: bug fixes, security patches, dependency updates, and workarounds for architectural limitations. The critical insight is that maintenance burden grows faster than most leaders realize. If your team currently spends 40% of its time on maintenance and that percentage is growing 3% per quarter, you can calculate the exact quarter when maintenance reaches 100%. That quarter is your Technical Insolvency Date. At the TID, your engineering team is fully consumed by keeping existing systems alive. Feature velocity drops to zero. No new capabilities. No competitive response. No innovation. Your R&D investment becomes pure maintenance spend - you're paying innovation-era salaries for maintenance-era output. The concept draws from financial insolvency: the point where a company's liabilities exceed its assets and it cannot meet its obligations. Technical insolvency is the same idea applied to engineering capacity - the point where your maintenance obligations exceed your available engineering hours. Most organizations don't realize they're approaching the TID because they track technical debt qualitatively rather than quantitatively. Telling a board "we have technical debt" gets deprioritized. Telling a board "we are 8 quarters from technical insolvency - the point where we can no longer ship any new features" gets immediate action and budget allocation.

Read Definition →

Audit Interview

The Audit Interview is a hiring protocol that tests verification skills instead of code generation skills. In the AI age, the scarce human skill is not writing code - it's catching what AI gets wrong. Traditional coding interviews ask candidates to write algorithms on a whiteboard or in a shared editor. This was a reasonable proxy for engineering skill when humans wrote all the code. But in 2026, AI tools like GitHub Copilot, Cursor, and Claude generate code faster and often more correctly than human candidates under interview pressure. When Anthropic discovered that candidates were using Claude to pass their own coding interviews, it proved that traditional interviews are testing the wrong thing. They're testing a skill that AI performs better than humans under artificial conditions. The Audit Interview flips the model. Instead of asking candidates to generate code, it presents them with AI-generated code that contains hidden flaws - security vulnerabilities, logic errors, performance anti-patterns, edge case failures, and architectural problems. The candidate's job is to find the bugs, rank them by severity, and make a ship/no-ship recommendation. The protocol works like this: candidates receive a realistic code review scenario (500-1000 lines of AI-generated code with 3-5 hidden flaws). They have 10 minutes to review the code, identify issues, and present their findings. The evaluation scores 4 dimensions of engineering judgment: 1. Verification: How many bugs did they find? Did they catch the security vulnerability? 2. Prioritization: Did they correctly rank issues by severity? 3. Communication: Can they explain the risk to a non-technical stakeholder? 4. Judgment: Would they ship this code? Under what conditions? With what caveats? The free Audit Interview tool at richardewing.io/tools/audit-interview generates realistic AI-written code with calibrated flaws for interviewers to use immediately.

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