Calculate and interpret core SaaS revenue, retention, and growth metrics to diagnose business momentum and product-market fit.
Works with
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 chur
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsaas-revenue-growth-metricsExecute the skills CLI command in your project's root directory to begin installation:
Fetches saas-revenue-growth-metrics from deanpeters/product-manager-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate saas-revenue-growth-metrics. Access via /saas-revenue-growth-metrics in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.1K
stars
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.
Total Revenue / Total UsersARPA (Average Revenue Per Account) — Average revenue generated per customer account.
MRR / Active AccountsARPA/ARPU Analysis — Using both metrics together to understand monetization.
ACV (Annual Contract Value) — Annualized recurring revenue per contract (excludes one-time fees).
Annual Recurring Revenue per Contract (don't include setup fees, professional services)MRR/ARR (Monthly/Annual Recurring Revenue) — Predictable recurring revenue normalized to monthly or annual.
MRR = Sum of all recurring subscription revenue per month; ARR = MRR × 12Gross vs. Net Revenue — Gross revenue before vs. net revenue after discounts, refunds, credits.
Net Revenue = Gross Revenue - Discounts - Refunds - CreditsMetrics that measure how well you keep and grow existing customers.
Churn Rate — Percentage of customers who cancel in a period.
Customers Lost in Period / Starting CustomersNRR (Net Revenue Retention) — Revenue retention from existing customers including expansion and contraction.
(Starting ARR + Expansion - Churn - Contraction) / Starting ARR × 100Expansion Revenue — Additional revenue from existing customers (upsells, cross-sells, usage growth).
Sum of upsells + cross-sells + usage increases from existing customersQuick Ratio (SaaS) — Revenue gains vs. revenue losses.
(New MRR + Expansion MRR) / (Churned MRR + Contraction MRR)Revenue Mix Analysis — Breakdown of revenue by product, segment, or channel.
Product/Segment Revenue / Total Revenue × 100Cohort Analysis — Group customers by join date and track behavior over time.
Use these when:
Don't use these when:
Use the templates in template.md to calculate your core revenue metrics.
Revenue = Sum of all customer payments in period
Example:
Quality checks:
ARPU = Total Revenue / Total Users
Example:
Quality checks:
ARPA = MRR / Active Accounts
Example:
Quality checks:
ARPA = MRR / Active Accounts
ARPU = MRR / Total Users
Average Seats per Account = ARPA / ARPU
Example:
Quality checks:
ACV = Annual Recurring Revenue per Contract
(Exclude one-time fees like setup, professional services)
Example:
Quality checks:
MRR = Sum of all recurring monthly subscriptions
ARR = MRR × 12
Track components:
- New MRR (from new customers)
- Expansion MRR (from upsells/cross-sells)
- Churned MRR (from lost customers)
- Contraction MRR (from downgrades)
Example:
Quality checks:
Net Revenue = Gross Revenue - Discounts - Refunds - Credits
Example:
Quality checks:
Logo Churn Rate = Customers Lost / Starting Customers × 100
Revenue Churn Rate = MRR Lost / Starting MRR × 100
Example (Logo Churn):
Example (Revenue Churn):
Quality checks:
Convert monthly to annual:
Annual Churn = 1 - (1 - Monthly Churn)^12NRR = (Starting ARR + Expansion - Churn - Contraction) / Starting ARR × 100
Example:
Quality checks:
Expansion Revenue = Upsells + Cross-sells + Usage Growth (from existing customers)
Example:
Quality checks:
Quick Ratio = (New MRR + Expansion MRR) / (Churned MRR + Contraction MRR)
Example:
Quality checks:
Product/Segment % = Product/Segment Revenue / Total Revenue × 100
Example:
Quality checks:
Group customers by when they joined and track metrics over time.
Example:
| Cohort | Month 0 | Month 1 | Month 2 | Month 3 | Month 6 |
|---|---|---|---|---|---|
| Jan 2024 | 100% | 95% | 92% | 90% | 85% |
| Feb 2024 | 100% | 94% | 90% | 87% | 80% |
| Mar 2024 | 100% | 92% | 86% | 82% | - |
Quality checks:
Before reporting metrics, validate:
Revenue metrics:
Retention metrics:
Analysis:
See examples/ folder for detailed scenarios. Mini examples below:
Company: Mid-market project management SaaS
Revenue Metrics:
Retention Metrics:
Analysis:
Action: Scale acquisition. Unit economics are strong.
Company: SMB marketing automation SaaS
Revenue Metrics:
Retention Metrics:
Cohort Analysis:
| Cohort | Month 6 Retention |
|---|---|
| 6 months ago | 75% |
| 3 months ago | 65% |
| Current | 58% |
Analysis:
Action: STOP scaling acquisition. Fix retention first. Investigate:
Company: Multi-product SaaS platform
Blended Metrics Look Great:
But Revenue Mix Analysis Shows:
| Product | Revenue | % of Total | Growth | Churn | NRR |
|---|---|---|---|---|---|
| Legacy Product | $2M | 67% | -5% MoM | 8% | 75% |
| New Product | $1M | 33% | +80% MoM | 1% | 150% |
Analysis:
Action: Accelerate migration from legacy to new product. Plan for legacy product sunset.
Symptom: "We grew revenue 50% this year, we're crushing it!"
Consequence: Revenue is the top line, not bottom line. You might be growing at a loss, destroying margins, or scaling unprofitable products.
Fix: Always pair revenue metrics with margin metrics (see saas-economics-efficiency-metrics). $1M revenue at 80% margin >> $2M revenue at 20% margin.
Symptom: "ARPU increased 30%!" (but customer count dropped 40%)
Consequence: ARPU rose because you lost all your small customers, not because you improved monetization.
Fix: Analyze ARPU by cohort and segment. True ARPU improvement = same customers paying more, not losing cheap customers.
Symptom: "Blended churn is stable at 3%"
Consequence: Blended metrics can hide that new cohorts churn
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added saas-revenue-growth-metrics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for saas-revenue-growth-metrics matched our evaluation — installs cleanly and behaves as described in the markdown.
saas-revenue-growth-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: saas-revenue-growth-metrics is focused, and the summary matches what you get after install.
saas-revenue-growth-metrics has been reliable in day-to-day use. Documentation quality is above average for community skills.
saas-revenue-growth-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
saas-revenue-growth-metrics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: saas-revenue-growth-metrics is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend saas-revenue-growth-metrics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
saas-revenue-growth-metrics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 50