Skill-Details
saas-revenue-growth-metrics
Useful PM SaaS metrics and growth analysis.
Vor Nutzung prüfen
Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.
SKILL.md
Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.
--- 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:** `AnnVollständige Quelle auf GitHub lesen (öffnet externe Seite)