SaaS Metrics Guide: MRR, Churn, LTV/CAC, and Analytics Infrastructure [2026]

87% of SaaS companies that fail cite poor unit economics as a contributing factor. Yet most teams spend years measuring vanity metrics — user signups, page views, total revenue — rather than the metrics that actually predict whether the business is viable. The difference between a SaaS company that raises a Series B and one that runs out of runway after Series A is often not product quality; it is which team understood their unit economics first.

This guide covers the essential SaaS metrics: how to calculate each one correctly, what the benchmarks mean for your business, how the metrics relate to each other, and the analytics infrastructure required to measure them reliably at scale.

SaaS Metrics Guide: Why Standard Accounting Fails

SaaS businesses cannot be understood through traditional revenue and profit metrics alone. A SaaS company signing 20 new annual contracts this month might show a worse P&L than last month if those contracts include large onboarding service components — while the actual business health (recurring revenue foundation) improved dramatically.

SaaS-specific metrics exist because they reveal what traditional accounting obscures: the quality of revenue (recurring vs. one-time), the stability of the customer base (retention), and the efficiency of growth spending (unit economics).

Revenue Metrics

Monthly Recurring Revenue (MRR)

MRR is the monthly revenue that is contractually predictable. Include only recurring subscription revenue; exclude one-time payments (setup fees, professional services, usage overages billed separately).

MRR decomposition:

• New MRR: Revenue from customers who activated this month for the first time
• Expansion MRR: Revenue increase from existing customers (plan upgrades, additional seats, usage overages)
• Contraction MRR: Revenue decrease from existing customers (plan downgrades, seat reductions)
• Churned MRR: Revenue from customers who cancelled this month
• Net New MRR = New MRR + Expansion MRR - Contraction MRR - Churned MRR

When Net New MRR is positive, the business is growing. When negative, it is contracting — regardless of how many gross new customers signed up.

Tracking MRR components separately reveals which levers are working. A company with strong New MRR but high Churned MRR is like a leaky bucket — filling as fast as it drains. High Expansion MRR relative to Churned MRR signals a product that customers grow into.

Annual Recurring Revenue (ARR)

ARR = MRR × 12. Used for annual-contract businesses and investor communication. A company with $100K MRR has $1.2M ARR. ARR is used in SaaS valuation multiples (e.g., "trading at 10x ARR").

For businesses with mixed annual and monthly contracts, convert all contracts to monthly recurring value before aggregating.

Retention and Churn Metrics

Logo Churn Rate (Customer Churn)

Logo churn measures how many customers you lose in a period:

Logo Churn Rate = Customers Lost in Period / Customers at Start of Period × 100

A SaaS product with 500 customers at the start of Q1 that loses 15 customers by Q1 end has a 3% quarterly logo churn rate, or approximately 1% monthly.

Benchmark context:

Monthly Churn	Interpretation
<1%	Best-in-class: median SaaS leader
1-3%	Healthy: sustainable with normal growth
3-5%	Concerning: meaningful drag on growth
>5%	Critical: growth cannot outpace losses

A 5% monthly churn rate means the average customer stays 20 months. A 2% monthly churn rate means 50 months. The compounding difference in LTV is enormous.

Revenue Churn vs. Logo Churn

Revenue churn measures the dollar value of lost subscriptions, not the customer count. A company that loses 10 small customers ($50/month each) but retains its 3 enterprise customers ($5,000/month each) has high logo churn but near-zero revenue churn.

Track both, but optimize decisions based on revenue churn — the metric that actually affects your income statement.

Negative revenue churn: If expansion MRR from existing customers exceeds churned MRR, net revenue churn is negative. This means existing customers are paying you more this year than last year, net of all losses. Negative revenue churn is the hallmark of a product with strong product-market fit and expansion motion.

Net Revenue Retention (NRR)

NRR measures what happens to revenue from a fixed group of customers over 12 months:

NRR = (Starting MRR + Expansion MRR - Contraction MRR - Churned MRR) / Starting MRR × 100

An NRR of 110% means a cohort of customers spending $1M/year this year will be spending $1.1M/year next year — without acquiring a single new customer. This is the most powerful indicator of a SaaS product's long-term compounding value.

NRR	Tier
>130%	Elite (Snowflake, Twilio at peak growth)
110-130%	Excellent (top-quartile SaaS)
100-110%	Good (sustainable growth engine)
90-100%	Average (needs improvement)
<90%	Weak (revenue contracting in existing base)

Cohort Retention Analysis

Cohort analysis tracks groups of customers who started in the same period over time. Customers who signed up in January 2026 are one cohort; customers who signed up in February 2026 are another.

Cohort retention curves reveal:

• Time to stabilization: At what month does churn rate fall below 1%? This is when the "successful" customers have separated from those who would have churned.
• Effect of product changes: Did the cohort that signed up after a major onboarding improvement retain better than previous cohorts?
• Segment differences: Do customers from a specific acquisition channel or plan tier retain significantly better or worse than others?

A retention curve that flattens early (customers stabilize quickly) indicates product-market fit in that customer segment. A retention curve that keeps declining 18+ months out indicates a product that customers abandon gradually rather than in the first weeks.

Unit Economics

Customer Acquisition Cost (CAC)

CAC is the fully-loaded cost to acquire one new paying customer:

CAC = (Total Sales + Marketing Spend in Period) / New Customers Acquired in Period

Common CAC calculation errors:

• Including only advertising spend, not salesperson salaries
• Not allocating SDR/BDR time to CAC
• Dividing by total new users rather than paying customers
• Using quarterly CAC for a business with 6-month sales cycles

For SaaS businesses with distinct segments (self-serve vs. enterprise), calculate CAC separately. Enterprise CAC includes field sales, legal, and security review costs that self-serve CAC does not.

Customer Lifetime Value (LTV)

LTV is the present value of revenue a customer will generate over their relationship with your product:

LTV = ARPA × Gross Margin / Monthly Churn Rate

Where ARPA = Average Revenue Per Account.

Example: ARPA $200/month, gross margin 75%, monthly churn 2% → LTV = $200 × 0.75 / 0.02 = $7,500

This formula assumes constant churn rate and constant ARPA — neither is exactly true in practice, but it provides a useful approximation. For businesses with significant expansion revenue, use NRR instead of churn rate in the denominator.

LTV/CAC Ratio

The ratio that determines whether your growth investment makes sense:

LTV/CAC	Decision
<1x	Stop spending: you are losing money on each customer
1-3x	Caution: marginal unit economics
3-5x	Healthy: sustainable growth model
>5x	Potentially underinvesting in growth

The 3x rule of thumb comes from the idea that 1x goes to recover CAC, 1x covers ongoing service costs, and 1x is profit contribution. Below 3x, the customer relationship does not generate enough surplus to fund growth.

CAC Payback Period

CAC Payback = CAC / (ARPA × Gross Margin)

The number of months needed to recover CAC through gross margin. Under 12 months is the benchmark for healthy SaaS; 18 months is acceptable; above 24 months creates cash flow challenges even in a growing company.

Usage and Engagement Metrics

DAU/MAU Ratio (Product Stickiness)

Daily Active Users divided by Monthly Active Users measures how often users return to the product. A ratio of 50% means users engage with the product roughly half of all days in the month.

DAU/MAU	Interpretation
>50%	Highly sticky (Slack-tier engagement)
20-50%	Strong daily habit formation
10-20%	Periodic use product
<10%	Low engagement, churn risk signal

Context matters: a quarterly reporting tool should not be expected to have daily engagement. Define "meaningful engagement" per product — for some SaaS products, weekly engagement is excellent.

Feature Adoption Rate

Track which features are activated and actively used by what percentage of accounts. Features with low adoption either need better discoverability, clearer onboarding, or are candidates for removal.

Features with high adoption in churning customers but low adoption in retained customers are an interesting anomaly — they may be indicating feature satisfaction not correlated with retention. Features adopted exclusively in retained customers are your retention drivers worth highlighting in sales conversations.

Time to First Value (TTFV)

How long does it take a newly activated user to reach the first moment of real product value? Define TTFV precisely: completing the first task that represents the product's core promise.

Cohorts with short TTFV retain significantly better than cohorts with long TTFV. If TTFV is consistently above 48 hours, the onboarding experience has a structural problem. Optimizing TTFV has among the highest return on investment of any product improvement in early-stage SaaS.

Analytics Infrastructure

Event Tracking Architecture

A SaaS metrics stack begins with reliable event capture. Define a taxonomy of critical business events:

• User activation events: account created, email verified, payment method added, first feature activated
• Engagement events: login, feature used, record created/updated/deleted, report exported
• Billing events: plan upgraded, plan downgraded, payment succeeded, payment failed, subscription cancelled

Use a consistent naming convention: object.action (e.g., appointment.created, subscription.upgraded, user.invited). Attribute each event with user_id, tenant_id, timestamp, and relevant context properties.

Segment, RudderStack, or direct event streaming to a data warehouse provides the event pipeline. The specific tool matters less than having a consistent, documented event taxonomy.

The SaaS Analytics Data Model

The core data model for SaaS analytics:

Subscriptions table: One row per subscription, tracking plan, price, start date, end date, status. This is the source of truth for all MRR calculations.

Subscription events table: One row per billing event — payment succeeded, payment failed, upgrade, downgrade, cancellation. Enables MRR cohort analysis and event-driven churn attribution.

Usage events table: One row per product event, with user, tenant, event type, and timestamp. Enables feature adoption and DAU/MAU analysis.

Dashboard Design by Stakeholder

Executive dashboard: MRR and ARR with 12-month trend, Net New MRR waterfall (new/expansion/contraction/churn components), NRR, logo churn rate, cash runway. Updated daily.

Product dashboard: DAU/MAU ratio, feature adoption heatmap, TTFV by cohort, onboarding completion funnel. Updated daily.

Finance dashboard: MRR by plan tier, CAC by channel, LTV/CAC by segment, CAC payback trend, deferred revenue. Updated weekly.

Customer success dashboard: Health score distribution, churn risk alerts, accounts approaching plan limits, expansion opportunity signals. Updated in near real-time.

Tools and Implementation

Purpose	Tools
Subscription analytics	ChartMogul, ProfitWell, Stripe Revenue Recovery
Product analytics	Mixpanel, Amplitude, PostHog
Data warehouse	Snowflake, BigQuery, Redshift
BI and dashboards	Metabase, Looker, Tableau, Mode
Event collection	Segment, RudderStack

For early-stage SaaS (pre-Series A), ChartMogul or ProfitWell connected to Stripe provides MRR, churn, NRR, and cohort analysis with minimal engineering effort. Product analytics requires Mixpanel or Amplitude instrumentation in the application code.

For growth-stage SaaS, a centralized data warehouse pulling from all operational systems — subscription platform, application events, support tickets, CRM — enables cross-functional analysis that individual tools cannot provide.

The goal of SaaS analytics infrastructure is not to have the most sophisticated stack — it is to have the right metrics available to the right stakeholders fast enough to inform decisions before the window for action closes. A simple Metabase dashboard on a well-modeled data warehouse serves most teams better than an overengineered analytics platform that no one uses.