The SaaS Business Model

In the AI Story

The SaaS model worked because the assumption held. Writing enterprise software required large teams of specialized developers, years of effort, and millions of dollars of investment. No individual customer could replicate the effort, so paying the subscription was the rational choice. The subscription price represented a tiny fraction of what it would have cost the customer to build the software independently, which made the value proposition compelling from the customer's perspective while providing the provider with recurring revenue sufficient to fund continued development.

When AI made software cheap to write — when a competent developer with Claude Code could prototype an application in hours that would have taken a team months — the foundational assumption cracked. The subscription model did not lose its logic overnight. Enterprise software involves far more than code: data models, integrations, compliance certifications, security audits, customer support, accumulated institutional knowledge. But the market's repricing was not about the complete value proposition. It was about the marginal perception of value, and the marginal perception shifted when the market recognized that the code layer — the thing that had historically justified the subscription price — was approaching commodity status.

The repricing was differentiated rather than uniform. Companies whose value resided primarily in the code — applications that solved specific, bounded problems with software that could be described and replicated — faced existential pressure. Companies whose value resided above the code layer — in ecosystems, data, integrations, and institutional trust — saw their market capitalizations decline but their business models remain viable. The distinction between these two categories was not visible during the SaaS era, when both types of companies looked similar from the outside. The repricing revealed it with brutal clarity.

The SaaS model is not dying, but it is evolving. The companies that survive the AI transition will be those whose subscription pricing reflects genuine, defensible value above the code layer — the data, the integrations, the trust, the accumulated workflow assumptions that no AI can replicate in an afternoon. The companies that cannot articulate such value face a choice: migrate their value proposition above the code layer, be acquired for their remaining assets, or wind down.

Origin

The SaaS model emerged from the combination of cheap internet bandwidth (enabling cloud delivery), improving browser capabilities (enabling rich web applications), and the financial logic of subscription pricing (providing predictable recurring revenue). Salesforce, founded in 1999, is conventionally cited as the first major success, though earlier precedents existed.

Key Ideas

The model's foundational assumption was code scarcity. Software was expensive to write; subscriptions amortized the cost across many users.

AI broke the assumption. Code can now be generated at near-zero marginal cost, eliminating the economic justification for code-based subscription premiums.

Value bifurcation revealed what was hidden. The repricing separated ecosystem value from code value — a distinction invisible during the SaaS boom.

Survival requires migration above the code layer. Data, integrations, trust, and workflow assumptions remain defensible; pure code value does not.

The model is evolving, not dying. Subscription pricing remains viable for genuine ecosystem value; it is no longer viable as compensation for code-writing labor.

Debates & Critiques

Some analysts argue that the SaaSpocalypse was an overreaction — that the market panicked and will re-rate SaaS companies upward once the productivity gains from AI become fully visible in their own operations. Others argue that the repricing, if anything, understates the structural change and that most SaaS companies face years of continued pressure.