Saas Revenue Growth MetricsSAFE

Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: saas-revenue-growth-metrics
argument-hint: "[metrics or question]"
description: Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.
intent: >-
  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.
type: component
theme: finance-metrics
best_for:
  - "Understanding your key revenue and retention metrics"
  - "Calculating MRR, ARR, churn, and NRR correctly"
  - "Building a metrics dashboard for your SaaS product"
scenarios:
  - "I need to calculate and interpret our MRR, churn rate, and NRR for a board deck"
  - "Help me understand the difference between gross and net revenue retention and how to improve it"
estimated_time: "10-15 min"
---


## 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,

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.