brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.
$ npx -y skills add getcrew44/crew44 --skill saas-revenue-growth-metrics --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/saas-revenue-growth-metricsContext preview
The summary Claude sees to decide when to auto-load this skill.
Calculate SaaS revenue, retention, and growth metrics. Use when diagnosing momentum, churn, expansion, or product-market-fit signals.
name: saas-revenue-growth-metrics 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"
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.
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.
**ARPU (Average Revenue Per User)** — Average revenue generated per individual user.
**ARPA (Average Revenue Per Account)** — Average revenue generated per customer account.
**ARPA/ARPU Analysis** — Using both metrics together to understand monetization.
**ACV (Annual Contract Value)** — Annualized recurring revenue per contract (excludes one-time fees).
**MRR/ARR (Monthly/Annual Recurring Revenue)** — Predictable recurring revenue normalized to monthly or annual.
**Gross vs. Net Revenue** — Gross revenue before vs. net revenue after discounts, refunds, credits.
---
Metrics that measure how well you keep and grow existing customers.
**Churn Rate** — Percentage of customers who cancel in a period.
**NRR (Net Revenue Retention)** — Revenue retention from existing customers including expansion and contraction.
**Expansion Revenue** — Additional revenue from existing customers (upsells, cross-sells, usage growth).
**Quick Ratio (SaaS)** — Revenue gains vs. revenue losses.
---
**Revenue Mix Analysis** — Breakdown
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes