Mmcp.market

saas-revenue-growth-metrics skill

by deanpeters·deanpeters/Product-Manager-Skills·7.1k stars

Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.

A100/100content scan

Is the saas-revenue-growth-metrics skill safe?

Clean: nothing in its files matched our rules. We read 4 files in the folder on 2026-09-28.

No findings.

Install the saas-revenue-growth-metrics skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git /tmp/Product-Manager-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Product-Manager-Skills/skills/saas-revenue-growth-metrics ~/.claude/skills/saas-revenue-growth-metrics
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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.

Input

Works best with: The question you're answering (is growth healthy? is churn a fire?) or the metrics you want interpreted. Also useful: Your numbers — MRR/ARR, growth rate, GRR/NRR, expansion, cohort data — partial data is workable.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. Use it as a reference: read the metric sections relevant to your diagnosis.

Example invocation: Interpret these: $4M ARR, 8% MoM growth, GRR 88%, NRR 103% — is the growth masking a churn problem?

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.

  • Why PMs care: Measures per-seat monetization effectiveness. Critical for seat-based pricing models.
  • Formula: Total Revenue / Total Users
  • Benchmark: Varies by model; track trend more than absolute value
  • B2C SaaS: $5-50/month typical; B2B: $50-500+/month

ARPA (Average Revenue Per Account) — Average revenue generated per customer account.

  • Why PMs care: Measures account-level deal size. Critical for account-based pricing models.
  • Formula: MRR / Active Accounts
  • Benchmark: SMB SaaS: $100-$1K/month; Mid-market: $1K-$10K; Enterprise: $10K+

ARPA/ARPU Analysis — Using both metrics together to understand monetization.

  • Why PMs care: Prevents packaging mistakes. High ARPA + low ARPU = undermonetized per seat. Low ARPA + high ARPU = small deal sizes.
  • Example: $10K ARPA with 100 seats = $100 ARPU (reasonable). $10K ARPA with 1,000 seats = $10 ARPU (leaving money on table).

ACV (Annual Contract Value) — Annualized recurring revenue per contract (excludes one-time fees).

  • Why PMs care: Compares economics across different contract structures. Enables sales compensation design and segment analysis.
  • Formula: Annual Recurring Revenue per Contract (don't include setup fees, professional services)
  • Benchmark: SMB: $5K-$25K; Mid-market: $25K-$100K; Enterprise: $100K+

MRR/ARR (Monthly/Annual Recurring Revenue) — Predictable recurring revenue normalized to monthly or annual.

  • Why PMs care: The heartbeat of subscription businesses. Valued at 5-10x+ multiples. Track components (new, expansion, churn).
  • Formula: MRR = Sum of all recurring subscription revenue per month; ARR = MRR × 12
  • Benchmark: Growth rate and quality matter; track new MRR, expansion MRR, churned MRR, contracted MRR

Gross vs. Net Revenue — Gross revenue before vs. net revenue after discounts, refunds, credits.

  • Why PMs care: Discounts and refunds can hide bad acquisition quality or product problems.
  • Formula: Net Revenue = Gross Revenue - Discounts - Refunds - Credits
  • Benchmark: Refunds >10% is a red flag; track by acquisition channel

Retention & Expansion Metrics Family

Metrics that measure how well you keep and grow existing customers.

Churn Rate — Percentage of customers who cancel in a period.

  • Why PMs care: Silent killer of SaaS. Undermines all acquisition efforts. 5% monthly churn = 46% annual churn (compounding).
  • Formula: Customers Lost in Period / Starting Customers
  • Benchmark (Monthly): <2% great, 2-5% acceptable, >5% crisis
  • Benchmark (Annual): <10% great, 10-30% acceptable, >30% crisis
  • Note: Logo churn (customer count) differs from revenue churn (dollar amount)

NRR (Net Revenue Retention) — Revenue retention from existing customers including expansion and contraction.

  • Why PMs care: The holy grail metric. NRR >100% means you grow without new logos. Highly valued by investors.
  • Formula: (Starting ARR + Expansion - Churn - Contraction) / Starting ARR × 100
  • Benchmark: >120% excellent, 100-120% good, 90-100% acceptable, <90% problem
  • Example: Start with $1M ARR, add $300K expansion, lose $100K to churn = $1.2M / $1M = 120% NRR

Expansion Revenue — Additional revenue from existing customers (upsells, cross-sells, usage growth).

  • Why PMs care: Most capital-efficient revenue (no CAC). Should drive NRR >100%.
  • Formula: Sum of upsells + cross-sells + usage increases from existing customers
  • Benchmark: Should represent 20-30% of total revenue; drives NRR >100%

Quick Ratio (SaaS) — Revenue gains vs. revenue losses.

  • Why PMs care: Shows if you're building on solid ground or running on a treadmill.
  • Formula: (New MRR + Expansion MRR) / (Churned MRR + Contraction MRR)
  • Benchmark: >4 excellent, 2-4 healthy, <2 leaky bucket

Analysis Frameworks

Revenue Mix Analysis — Breakdown of revenue by product, segment, or channel.

  • Why PMs care: Identifies which products fund the business and where to invest. Reveals concentration risk.
  • Formula: Product/Segment Revenue / Total Revenue × 100
  • Benchmark: No single product >60% ideal; diversification reduces risk

Cohort Analysis — Group customers by join date and track behavior over time.

  • Why PMs care: Blended metrics hide critical trends. Shows whether business is improving or degrading.
  • Method: Track retention, expansion, and LTV by cohort (e.g., "Jan 2024 cohort")
  • Benchmark: Recent cohorts should perform same or better than old cohorts

Anti-Patterns (What This Is NOT)

  • Not profit metrics: Revenue is top-line, not bottom-line. High revenue with negative margins is a disaster.
  • Not vanity metrics: Total revenue growth means nothing if driven by unsustainable discounting or margin-destroying deals.
  • Not blended averages: ARPU that averages $10 SMB and $1,000 enterprise customers hides segment economics.
  • Not isolated numbers: Churn rate alone doesn't tell the story—need to see cohort trends and NRR.

When to Use These Metrics

Use these when:

  • Evaluating overall business health and product-market fit
  • Comparing performance across time periods or cohorts
  • Prioritizing features with direct monetization paths (ARPU impact, expansion enablers)
  • Communicating with leadership, board, or investors
  • Assessing retention problems (churn analysis, cohort degradation)
  • Measuring pricing or packaging changes (ARPU/ARPA shifts)

Don't use these when:

  • Evaluating profitability (use margin metrics instead)
  • Assessing capital efficiency (use LTV:CAC, payback period)
  • Making product investment decisions without cost context (revenue alone isn't ROI)
  • Comparing across wildly different business models without normalization

Application

Step 1: Calculate Revenue Metrics

Use the templates in template.md to calculate your core revenue metrics.

Revenue

Revenue = Sum of all customer payments in period

Example:

  • Month 1 payments: $100,000
  • Revenue = $100,000

Quality checks:

  • Is this gross or net revenue? (Clarify if discounts/refunds are included)
  • Is revenue growing cohort-over-cohort, or just from new customer adds?
  • What's the revenue growth rate vs. headcount/cost growth rate?

ARPU (Average Revenue Per User)

ARPU = Total Revenue / Total Users

Example:

  • Total Revenue: $100,000/month
  • Total Users: 2,000
  • ARPU = $100,000 / 2,000 = $50/user/month

More skills from deanpeters/Product-Manager-Skills

  • Aacquisition-channel-advisorEvaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
  • Aagent-orchestration-advisorDesign multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
  • Aai-shaped-readiness-advisorAssess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
  • Aaltitude-horizon-frameworkUnderstand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
  • Aansoff-matrixMap evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.
  • Aautonomous-investigationThe protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.
  • Abattle-card-builderResearch and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
  • Abusiness-health-diagnosticDiagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
  • Acompany-intelResearch a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
  • Acompany-researchCreate a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
  • Acompetitive-analysis-processOrchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.
  • Acompetitive-intel-watchScheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.

All agent skills → · MCP servers