saas-revenue-growth-metrics
Calculate and interpret core SaaS revenue, retention, and growth metrics to diagnose business momentum and product-market fit.
- Covers 10+ essential metrics: MRR/ARR, ARPU/ARPA, churn rate, NRR, expansion revenue, and Quick Ratio, with formulas and quality checks for each
- Includes cohort analysis and revenue mix frameworks to reveal hidden trends that blended metrics obscure (e.g., cohort degradation, concentration risk)
- Provides benchmarks for each metric (e.g., <2% monthly churn is great; NRR >120% is excellent) and decision rules for when to scale vs. fix retention
- Highlights 10 common pitfalls: confusing revenue with profit, ignoring cohort degradation, treating all churn equally, and misinterpreting blended metrics
Purpose
Master revenue and retention metrics to understand SaaS business momentum, evaluate product-market fit, and make data-driven decisions about growth investments. Use this to calculate key metrics, interpret trends, identify problems early, and communicate business health to stakeholders.
This is not a business intelligence tool—it's a framework for PMs to understand which metrics matter, how to calculate them correctly, and what actions to take based on the numbers.
Key Concepts
Revenue Metrics Family
The "top-line" metrics that measure how much money the business generates.
Revenue — Total money earned from selling products/services before expenses. The "top line" of the income statement.
- Why PMs care: Every feature should connect to revenue (direct or indirect). If you can't articulate revenue impact, prioritization becomes impossible.
- Formula: Sum of all customer payments in a period
- Benchmark: Growth rate matters more than absolute number (context-dependent by stage)
ARPU (Average Revenue Per User) — Average revenue generated per individual user.
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K