Home/Research/Specifications/The Evergreen Ratio
Canonical Research SpecificationLevel: Executive
Verified: August 2026

The Evergreen Ratio

30-Second Executive Definition

A financial diagnostic metric representing the ratio of fixed-cost software revenue (traditional SaaS features) to variable-cost AI revenue within a product portfolio. A high Evergreen Ratio indicates a stable, high-margin business with strong structural safety. A declining Evergreen Ratio signals that a company is becoming dangerously dependent on high-COGS AI features, exposing it to AI margin squeeze and severe valuation compression.

Trading zero-marginal-cost software for high-variable-cost AI is a dangerous economic bargain.

Why It Matters:

As traditional SaaS companies rapidly bolt on AI features, they are unknowingly altering their fundamental economic structure. They are trading high-margin, predictable revenue for low-margin, variable-cost revenue. If the Evergreen Ratio drops too low, the company ceases to be a highly valued software company and begins to look economically like a low-margin services or manufacturing business. Tracking this ratio is essential for maintaining enterprise value during an AI transition.

Who Should Care:
Chief Financial OfficersBoard MembersSaaS Founders
Infinite Relationship Navigator118-Node Sovereign Knowledge Graph

Multi-Hop Causal Traversal Engine

Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.

Current Traversal Path (1 Hops Traveled):
AI EconomicsRichard Ewing Canon (Original Framework)Confidence: 90%
Open Full Specification ↗

The Evergreen Ratio

A financial diagnostic metric representing the ratio of fixed-cost software revenue (traditional SaaS features) to variable-cost AI revenue within a product portfolio. A high Evergreen Ratio indicates a stable, high-margin business with strong structural safety. A declining Evergreen Ratio signals that a company is becoming dangerously dependent on high-COGS AI features, exposing it to AI margin squeeze and severe valuation compression.

Relationship Filter:
Hop Level 1

Direct Relationships (3)

Hop Level 2

Transitive Neighbors (Connected via Hop 1)

Hop Level 3

Extended Causal Ripple Effects

★ Canonical Research Position

Richard Ewing’s Research Thesis

Companies must actively manage their Evergreen Ratio to prevent their SaaS valuation multiples from collapsing.

Genesis & Intellectual Positioning

Why This Specification Exists

1. The Problem

SaaS companies are bolting on AI features and destroying their own gross margins.

2. Existing Approaches

Treating all ARR as equal value.

3. The Structural Gap

No board-level metric identifying the specific risk of high-variable-cost AI revenue dilution.

4. This Specification

A ratio tracking the balance between zero-marginal-cost software and high-variable-cost AI.

Operational Realignment

What Changes If You Believe This?

Engineering

Teams must balance AI integrations with high-margin deterministic features.

Finance & COGS

Segments revenue streams to monitor the structural health of the business.

Product Strategy

Designs AI features specifically to funnel users into evergreen retention loops.

Security & Audit

N/A

Audience-Specific Executive Guidance

Recommended Action by Role

CFO

Include the Evergreen Ratio in all quarterly board decks to contextualize ARR growth.

Recommended Next Step →
Freshness & Research Updates

Latest Publications & Research Activity

BeehiivSeptember 4, 2026

The Bootstrapper's Cloud Credit Playbook

Read Work ↗
CIO.comAugust 31, 2026

Bedrock, Vertex or build it yourself: The AI infrastructure decision most CIOs get backwards

Read Work ↗
LinkedInAugust 17, 2026

When the Cost of Writing Software Approaches Zero, Traditional Product Management Frameworks Break Down

Read Work ↗
Answer Engine FAQ Matrix

Frequently Asked Questions

Q:Why is it called "Evergreen"?

Because traditional SaaS revenue is "evergreen" - once the code is written, it generates revenue repeatedly with near-zero marginal cost.

Q:Should a company aim for a 100% Evergreen Ratio?

No, that would mean ignoring AI entirely, which risks obsolescence. The goal is balance: using AI to drive adoption while relying on evergreen features to drive margin.

01 • Origin & GenesisProvenance Record

Canonical Specification Origin

Companies must actively manage their Evergreen Ratio to prevent their SaaS valuation multiples from collapsing.

First IntroducedAugust 2026
Primary VenueInternal Research
02 • Internal Research Corpusrichardewing.io

Corpus Interconnections

Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.

Articles1
Tools0
Specs1
Chapters1
03A • Verified Human External EvidenceAudit Status: Baseline

External Adoption & Peer Citations

Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.

External Evidence: No independently verified references recorded yet.

This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.

Inspectable Evidence Ledger

Classified evidence items supporting, extending, or refining this canonical research specification.

Evidence ItemPublisherEvidence TypeStrengthRoleAction
Margin Dilution in SaaSInternalObservation★★★★★OriginInspect ↗
Academic & Industry Attribution Standard

Recommended Citation

Canonical Reference String

Ewing, R. (2026). "The Evergreen Ratio." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/evergreen-ratio

BibTeX Citation
@article{ewing_evergreen_ratio,
  author = {Ewing, Richard},
  title = {The Evergreen Ratio},
  journal = {Richard Ewing Research Canon},
  year = {2026},
  url = {https://www.richardewing.io/concepts/evergreen-ratio}
}
First Origin & Provenance:Internal Research (August 2026)
Current Specification Version:Version 1.0 (Q2 2026 Baseline)