5 essential metrics for B2B SaaS in the growth stage
January 2026
Growth-stage B2B SaaS is a specific kind of pressure. You've proven the product works. Now you need to prove the business works — that you can acquire customers efficiently, keep them, and expand revenue without burning through your runway.
Most teams respond by building dashboards with 30+ metrics. That's not measurement — it's noise. The goal isn't to track everything. It's to track the five numbers that actually change your decisions.
What most teams get wrong about SaaS metrics
The first mistake is treating metrics as report cards. Metrics aren't there to make you feel good or bad — they're decision-making tools. If a metric doesn't change what you'd do next, it doesn't belong on your leadership dashboard.
The second mistake is measuring inputs instead of outcomes. Page views, email open rates, number of demos booked — these are activity metrics. They tell you people are busy. They don't tell you the business is healthy.
The third mistake is looking at everything monthly. Some metrics need weekly attention. Others are only meaningful over quarters. Cadence matters as much as the metric itself.
Metric 1: CAC (Customer Acquisition Cost)
What it is: Total sales and marketing spend divided by the number of new customers acquired in the same period.
Why it matters for growth-stage SaaS: CAC tells you the real price of growth. Early on, you can tolerate high CAC because you're learning. At growth stage, CAC should be stabilising or declining as you find repeatable channels. If CAC keeps climbing while growth stays flat, you're buying growth instead of earning it.
Healthy range: Varies wildly by ACV (annual contract value). For SMB SaaS (ACV under $10k), CAC should typically be under $5k. For mid-market ($25–100k ACV), CAC of $15–40k is common. The absolute number matters less than the trend and the ratio to LTV.
Decision trigger: If CAC rises more than 20% quarter-over-quarter without a corresponding increase in deal quality or ACV, I'd revisit channel mix first, then positioning. Often the problem isn't spend — it's targeting the wrong segment with the wrong message.
Cadence: Monthly, reviewed quarterly for trends. Marketing owns the inputs; finance validates the calculation.
Metric 2: LTV:CAC Ratio
What it is: Customer Lifetime Value divided by Customer Acquisition Cost. The single most important ratio in SaaS economics.
Why it matters: LTV:CAC tells you whether your growth is sustainable. A ratio below 3:1 means you're spending too much to acquire customers relative to what they're worth. Above 5:1, you're probably under-investing in growth and leaving market share on the table.
Healthy range: 3:1 to 5:1 for most growth-stage SaaS. Below 3:1 is a warning. Above 5:1 means you should be spending more aggressively on acquisition — or your LTV calculation is too optimistic.
Decision trigger: If the ratio drops below 3:1, don't panic — but don't ignore it. First check whether the problem is on the LTV side (churn increasing, expansion revenue stalling) or the CAC side (acquisition getting more expensive). The fix is completely different depending on which side is moving.
Cadence: Quarterly. This is a strategic metric, not an operational one. The CEO and CFO should own the conversation; marketing and CS provide the inputs.
Metric 3: CAC Payback Period
What it is: How many months it takes for a customer to generate enough gross margin to cover the cost of acquiring them.
Why it matters: LTV:CAC tells you the eventual return. Payback tells you the cash flow reality. A great LTV:CAC ratio with 24-month payback means you need serious capital to fund growth. A 6-month payback means growth funds itself.
Healthy range: Under 12 months is strong. 12–18 months is acceptable if retention is excellent. Beyond 18 months at growth stage, you're putting real strain on cash flow and need to either improve onboarding (to accelerate value delivery) or raise prices.
Decision trigger: If payback drifts beyond 18 months, here's what I'd revisit first: onboarding experience (are customers reaching value fast enough?), pricing structure (are you charging enough for the value delivered?), and segment focus (are you acquiring customers who are genuinely a good fit?).
Cadence: Monthly calculation, quarterly strategic review. Product and CS teams are critical here — payback isn't just a sales metric, it's an onboarding and value-delivery metric.
Metric 4: Net Revenue Retention (NRR)
What it is: Revenue from existing customers this period, including expansion and contraction, divided by their revenue from the prior period. Expressed as a percentage.
Why it matters: NRR is arguably the most important metric in SaaS. It tells you what happens after the sale. NRR above 100% means your existing customer base is growing without any new sales. That's compounding revenue — the holy grail.
Healthy range: Above 110% is excellent for mid-market and enterprise SaaS. 100–110% is healthy. Below 100% means you're leaking revenue faster than you're expanding it, and no amount of new customer acquisition will fix that long-term.
Decision trigger: If NRR drops below 100%, stop all "growth initiatives" and focus on retention and expansion. Seriously. Acquiring new customers into a leaky bucket is the most expensive mistake in SaaS. I'd look at: churn reasons (product gaps? pricing? poor support?), expansion opportunities (are CSMs equipped to identify upsell moments?), and onboarding quality.
Cadence: Monthly tracking, but the real insight comes from cohort analysis — looking at NRR by customer segment, cohort vintage, and product tier. CS and revenue ops own this; the CEO should review it monthly.
Metric 5: Churn Rate
What it is: Percentage of customers (logo churn) or revenue (revenue churn) lost in a given period.
Why it matters: Churn is the silent killer. You can mask it with aggressive acquisition for a while, but eventually it catches up. At growth stage, every point of churn reduction has a massive compounding effect on long-term revenue.
Healthy range: Annual logo churn under 10% is good for SMB SaaS, under 5% for mid-market and enterprise. Revenue churn should be net negative (meaning expansion exceeds contraction + churn) — that's what NRR above 100% means.
Decision trigger: If monthly churn exceeds 2% (roughly 22% annualised), treat it as a fire. Conduct exit interviews, analyse the last 20 churned accounts for patterns, and check whether churn concentrates in a specific segment or cohort. Often, churn isn't a product problem — it's a fit problem. You're acquiring the wrong customers.
Cadence: Weekly monitoring of leading indicators (usage drops, support ticket spikes, missed QBRs). Monthly churn calculation. Quarterly deep-dive on churn patterns. CS owns the metric; product and marketing need to act on the insights.
How often I want to see these 5 metrics in leadership dashboards
Weekly: Churn leading indicators (usage trends, NPS/CSAT dips, support volume). Not the full metric, but the early signals.
Monthly: CAC, Churn Rate, NRR. These are your operational pulse. The leadership team should review them together, not in functional silos.
Quarterly: LTV:CAC, CAC Payback Period. These are strategic metrics that need enough data to be meaningful. They belong in board conversations and annual planning.
Who owns what:
CEO/CFO — owns the LTV:CAC conversation and overall unit economics narrative.
VP Marketing — owns CAC, contributes to payback analysis (top-of-funnel quality).
VP Sales — owns deal velocity and average ACV, which directly affect CAC and payback.
VP CS/CRO — owns NRR and churn, with product support for usage-based leading indicators.
The point isn't that each function tracks "their" metric in isolation. It's that someone is accountable for each number, and the leadership team connects them into one story every month.
---
*This article is part of the [Metrics Hub](/metrics) — a practical library of metrics for founders, CMOs and growth leaders. See also: [Which metrics matter for B2C e-commerce at CMO level](/article/metrics-b2c-ecommerce-cmo-level) and [Metrics for B2B2C](/article/metrics-b2b2c-partners-end-users).*