SaaSpocalypse (Minsky Reading)

In the AI Story

The SaaS business model was, for most of its history, a hedge position of remarkable elegance. A software company built a product; customers paid a recurring subscription; the subscription revenue was predictable, diversified, and self-sustaining. The income covered all obligations with comfortable margins. The model depended on a single underlying assumption: code is hard to write. The difficulty of producing software was the moat that protected the subscription.

The 2015-2021 SaaS boom progressively shifted positions from hedge to speculative. Valuations climbed from reasonable multiples of revenue to extraordinary ones — reaching 18.5 times revenue during the COVID-era peak. At those multiples, a SaaS company's valuation was no longer a bet on current cash flows; it was a bet on continued growth. The positions had become speculative: the income covered current obligations, but the valuation required refinancing through continued expansion.

The arrival of AI invalidated the underlying assumption. When a competent developer can describe a desired software application in natural language and receive a working implementation in hours, the difficulty of writing code — the moat that protected every SaaS subscription — does not merely narrow. It drains. The customer paying two hundred dollars per seat per month for a CRM because building an alternative was prohibitively expensive now has access to tools that make building an alternative a weekend project.

The February 2026 Anthropic blog post was the trigger, not the cause. The cause was the progressive erosion of the moat over the preceding two years, which had been invisible to the market as long as no specific event forced recognition. The blog post forced recognition by demonstrating a specific capability — COBOL modernization — that the market could no longer dismiss as aspirational. The recognition spread through the sector in weeks because the fragility had been building across the sector for years.

The repricing revealed the distribution of positions across the SaaS industry. Companies with genuine ecosystem depth — the data layer accumulated through two decades of enterprise deployment, the integrations connecting sales pipelines to marketing automation, the compliance certifications and audit trails that required years of institutional effort — survived the repricing with damage but maintained their fundamental position. They had been hedge positions all along, even if the valuations had drifted speculative. Companies whose value was always in the code — thin applications reproducible by a developer with Claude Code in an afternoon — faced existential repricing, because their positions had been speculative or Ponzi and the correction revealed the structure.

Origin

The term SaaSpocalypse emerged in the financial press during the early 2026 repricing. The event itself occurred across February-March 2026, triggered by Anthropic's COBOL blog post and accelerated by subsequent capability demonstrations that forced sustained recognition of AI's displacement of code production.

The Minskyan reading of the event is developed in the Opus 4.6 simulation of Hyman Minsky — On AI, Chapter 4, and in parallel analyses by Aswath Damodaran, Howard Marks, and other analysts applying Minsky's framework to contemporary technology markets.

Key Ideas

Trivial trigger, massive response. The Anthropic blog post was disproportionate to the trillion-dollar repricing it triggered — characteristic of Minsky moments.

Accumulated fragility. The underlying fragility had been building for years as AI progressively eroded the code-difficulty moat.

Position differentiation. The repricing distinguished companies with genuine ecosystem moats from those whose value was always in the code.

Speculative-to-critical transition. The event marked the passage from speculative positions (viable under boom conditions) to critical-stage recognition of what the positions actually were.

Sectoral rather than systemic. The cascade was contained within the SaaS sector rather than spreading to the broader economy — a partial rather than complete Minsky moment.

Debates & Critiques

Whether the SaaSpocalypse represented a full Minsky moment or merely a sectoral correction remains contested. Optimists argue that the event was specific to SaaS and that the broader AI economy remains structurally sound. Minskyans argue that sectoral Minsky moments can precede systemic ones and that the SaaS event may prove to be the first in a series rather than a contained correction.