Framework Definition

The Software Phase Transition

Coined by Richard Ewing, AI Economist

Share:

Definition

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.

Why It Matters

When software creation is free, adding features without economic governance destroys enterprise valuation. Output is no longer a proxy for progress. For Chief Product Officers, this framework establishes why traditional sprint metrics fail in the AI era and guides the transition to unit margin accountability. For CTOs and engineering leaders, it highlights why unbounded AI code generation creates catastrophic technical insolvency unless paired with strict verification gates. For boards and investors, it separates teams that burn capital on feature sprawl from teams that preserve durable gross margins.

How to Calculate

  1. 1Audit developer capacity vs feature generation cycle times across teams
  2. 2Measure organizational complexity growth (interaction points, dependency sprawl)
  3. 3Evaluate unit margin contribution per shipped feature or autonomous loop
  4. 4Track Product Debt Index (PDI) to detect code carrying drag
  5. 5Transition team scoring from sprint story points to capital efficiency and risk reduction

Deep Dive on the Blog

Explore the latest analysis and practical applications of this framework on the engineering economics blog.

Search the Blog Archive →

Citation

To cite this definition:

Ewing, R. (2026). "The Software Phase Transition." richardewing.io.
https://www.richardewing.io/articles/frameworks/software-phase-transition

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