Glossary/Subprime Code Crisis
Richard Ewing Frameworks
2 min read
Share:

What is Subprime Code Crisis?

TL;DR

The Subprime Code Crisis is an analogy coined by Richard Ewing comparing the hidden risk in enterprise codebases to the 2008 financial crisis.

The Subprime Code Crisis is an analogy coined by Richard Ewing comparing the hidden risk in enterprise codebases to the 2008 financial crisis. Just as subprime mortgages were bundled into complex financial instruments that masked their true risk, technical debt is bundled into "working software" that masks its true maintenance cost.

The parallel is structural:

2008 Financial Crisis: Risky mortgages → bundled into CDOs → rated AAA → systemic collapse when defaults cascaded

Subprime Code Crisis: Technical debt → bundled into "working features" → rated as "shipped" → systemic engineering failure when maintenance costs cascade

The key insight is that technical debt, like financial debt, has a compounding interest rate. When maintenance costs exceed a threshold (typically 40-60% of engineering capacity), the system enters a death spiral where new features generate more maintenance than value.

Why It Matters

The Subprime Code Crisis framework explains why engineering organizations fail suddenly rather than gradually. Executives see a "working product" and assume the codebase is healthy — just as investors saw "performing loans" and assumed the mortgage market was healthy.

The Technical Insolvency Date calculator (richardewing.io/tools/pdi) is designed to detect the Subprime Code Crisis before collapse. It projects the exact quarter when maintenance costs will consume 100% of engineering capacity.

How to Measure

Calculate the percentage of engineering time spent on maintenance vs. innovation. If trending above 40%, the organization may be approaching a Subprime Code Crisis. The PDI tool provides a precise projection.

Frequently Asked Questions

How common is the Subprime Code Crisis?

Extremely common. Most B2B SaaS companies with 5+ years of development history are accumulating technical debt faster than they are paying it down. Many are already past the point of no return without intervention.

Related Terms

Need Expert Help?

Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.

Book Advisory Call →