SaaS Analytics: The Essential Metrics Every SaaS Team Needs
SaaS analytics measures the health and growth trajectory of subscription software businesses. Because revenue is recurring (not one-time), SaaS metrics focus on retention, expansion, and efficiency rather than just acquisition. The right metrics tell you whether your business is healthy, growing sustainably, and building enterprise value.
The Core SaaS Metrics
Revenue Metrics
| Metric | Formula | Why It Matters |
|---|---|---|
| MRR (Monthly Recurring Revenue) | Sum of all monthly subscription fees | The heartbeat of a SaaS business |
| ARR (Annual Recurring Revenue) | MRR x 12 | For annual planning and valuation |
| New MRR | MRR from new customers this month | Measures acquisition effectiveness |
| Expansion MRR | MRR gained from upgrades/add-ons | Existing customer growth |
| Contraction MRR | MRR lost from downgrades | Indicates value delivery problems |
| Churned MRR | MRR lost from cancellations | Customer loss |
| Net New MRR | New + Expansion - Contraction - Churn | Overall growth rate |
MRR Waterfall Example:
| Component | Amount |
|---|---|
| Starting MRR | $500,000 |
| + New MRR | +$45,000 |
| + Expansion MRR | +$28,000 |
| - Contraction MRR | -$8,000 |
| - Churned MRR | -$22,000 |
| = Ending MRR | $543,000 |
| Net New MRR | +$43,000 |
Retention Metrics
| Metric | Formula | Excellent | Good | Concerning |
|---|---|---|---|---|
| Gross Revenue Retention (GRR) | (Starting MRR - Contraction - Churn) / Starting MRR | > 95% | 90-95% | < 85% |
| Net Revenue Retention (NRR) | (Starting MRR + Expansion - Contraction - Churn) / Starting MRR | > 120% | 100-120% | < 100% |
| Logo Retention | (Customers End - New) / Customers Start | > 95% | 90-95% | < 85% |
NRR > 100% means you grow revenue from existing customers even without adding new ones. Top SaaS companies achieve 120-140% NRR.
Efficiency Metrics
| Metric | Formula | Target |
|---|---|---|
| CAC (Customer Acquisition Cost) | (Sales + Marketing Cost) / New Customers | Lower is better |
| CAC Payback Period | CAC / (Monthly Revenue per Customer x Gross Margin) | < 18 months |
| LTV:CAC Ratio | Customer Lifetime Value / CAC | > 3:1 |
| Magic Number | Net New ARR / Prior Quarter Sales & Marketing Spend | > 0.75 |
| Rule of 40 | Revenue Growth Rate % + EBITDA Margin % | > 40% |
| Burn Multiple | Net Burn / Net New ARR | < 2x |
Engagement Metrics
| Metric | What It Indicates |
|---|---|
| DAU/MAU ratio | Product stickiness (> 20% good, > 50% excellent) |
| Feature adoption rate | Are users getting value from the product? |
| Activation rate | Do new users reach their "aha moment"? |
| Time to value | How quickly do users see first value? |
| Session frequency | How often users return |
| NPS (Net Promoter Score) | Would users recommend you? |
SaaS Analytics by Stage
Pre-Product Market Fit (Pre-$1M ARR)
Focus on:
- Activation rate (are users getting value?)
- Retention (are they staying?)
- Qualitative feedback (why or why not?)
- Time to value (how fast is the "aha moment"?)
Do not obsess over: CAC, LTV:CAC, Magic Number (too early, not enough data)
Growth Stage ($1M-$10M ARR)
Focus on:
- MRR growth rate (> 100% YoY for top quartile)
- Net revenue retention (are you expanding within accounts?)
- CAC payback period (is growth efficient?)
- Churn rate by segment (where is the leaky bucket?)
- Sales cycle length and win rate
Scale Stage ($10M-$100M ARR)
Focus on:
- Rule of 40 (balance growth and profitability)
- Magic Number (sales efficiency at scale)
- Net revenue retention by cohort (is it sustainable?)
- Revenue per employee (operational efficiency)
- Free cash flow margin (path to profitability)
Enterprise Stage ($100M+ ARR)
Focus on:
- Gross margin expansion
- Free cash flow generation
- Market share within ICP
- Platform expansion revenue
- International growth rates
Building a SaaS Analytics Practice
Data Sources
| Source | Metrics It Provides |
|---|---|
| Billing system (Stripe, Chargebee, Zuora) | MRR, churn, expansion, contraction |
| CRM (Salesforce, HubSpot) | Pipeline, win rate, sales cycle, CAC |
| Product database | Usage, activation, feature adoption, engagement |
| Marketing tools | Lead generation, channel performance, attribution |
| Support system | Ticket volume, satisfaction, resolution time |
| Finance system | Expenses, margin, cash flow |
Analytics Stack
- Data warehouse: Snowflake or BigQuery (central truth)
- ETL: Fivetran (connect all SaaS tools automatically)
- Transformation: dbt (define metrics precisely)
- Analytics: Skopx (ask any metric question in natural language), ChartMogul (SaaS-specific dashboards)
- Product analytics: Amplitude or Mixpanel (user behavior)
Key Reports to Automate
| Report | Audience | Cadence |
|---|---|---|
| MRR Waterfall | Executive team | Monthly |
| Cohort retention | Product + CS | Monthly |
| Pipeline and forecast | Sales leadership | Weekly |
| Feature adoption | Product team | Weekly |
| Customer health scores | CS team | Daily |
| Unit economics (CAC, LTV) | Finance + leadership | Monthly |
| Board deck metrics | Board | Quarterly |
Common SaaS Analytics Mistakes
- Conflating bookings with revenue. A signed annual contract is bookings, not recognized revenue. These are different numbers.
- Ignoring cohort effects. Overall NRR can look healthy while recent cohorts retain worse (masked by older, stickier cohorts).
- Not segmenting metrics. Enterprise NRR of 130% and SMB NRR of 85% look fine as a blended 110%, but the SMB problem needs attention.
- Measuring only acquisition. Companies often track CAC religiously but ignore expansion revenue and retention, which drive more enterprise value.
- Vanity metrics. Total registered users, total revenue (cumulative), and page views without conversion context tell you nothing actionable.
Summary
SaaS analytics revolves around the subscription revenue engine: acquire customers efficiently (CAC), retain them (GRR), expand them (NRR), and do it all profitably (Rule of 40). The right metrics depend on your stage, but MRR, NRR, and CAC payback are universal. Connect your billing, product, and sales data, define your metrics precisely, and make them accessible to every team that can influence them.
Saad Selim
The Skopx engineering and product team