SaaS Metrics That Reveal the Next Move

A SaaS team can finish a month with more subscription revenue and still have a hard question to answer: did the product become more valuable to its customers, or did new sales temporarily cover the revenue lost from existing accounts? A single growth number cannot settle that question. Neither can a busy dashboard full of signups, invoices, and usage charts. The useful metrics connect the route from a customer’s first experience to a durable subscription, then show what it costs to repeat that route.

The starting set is monthly recurring revenue (MRR), customer acquisition cost (CAC), activation, gross revenue retention (GRR), and net revenue retention (NRR). Read them together. MRR describes the subscription base; CAC describes the spend needed to add customers; activation asks whether newcomers reach a meaningful product outcome; and the two retention measures show what happens to revenue from customers already on the books. Each answers a different operating question, so a good result in one can conceal a problem in another.

Start with recurring revenue, then ask what moved it#

As Stripe’s MRR guide explains, MRR puts eligible subscription amounts on a monthly basis. With 100 accounts each paying 100 currency units per month, the simple starting figure is 10,000 units of MRR before any exclusions or adjustments. That arithmetic is useful because it gives a consistent base for comparing periods, including businesses with different billing intervals. It is only as consistent as the rule for what counts: specify which subscriptions are eligible and how discounts enter the calculation.

Annual recurring revenue (ARR) expresses the recurring base on an annual scale. Neither figure is recognized accounting revenue, as Stripe’s MRR and ARR support article explains. A yearly subscription may contribute a monthly normalized amount to MRR even though its invoice, cash collection, and accounting treatment follow different timelines. Use MRR and ARR to discuss the subscription run rate, and use the company’s accounting policy and financial statements for recognized revenue.

For an operating review, the change in MRR matters more than the ending total alone. Take the opening MRR, add recurring revenue from newly acquired accounts and increases from existing accounts, then subtract reductions and cancellations. Keep those movements separate on the page. If new subscriptions add 2,000 units while existing accounts lose 1,500, the net increase is 500; the ending number looks positive, but most of the new business replaced lost revenue. This is an illustrative calculation, not a claim about a typical SaaS company.

There is a practical cost to this clarity. Someone must settle recurring questions about trial subscriptions, one-time charges, discounts, and the status of accounts that have not paid. The decision is worth making once and applying consistently. A sudden change in the inclusion rule can create apparent growth or decline without a comparable change in customer behavior. When the pricing model changes, publish the rule alongside the trend so a reader knows which part is commercial movement and which part is a changed calculation.

Ask what a new customer costs before buying more growth#

Stripe’s SaaS metrics guide defines CAC as acquisition spending divided by customers acquired over a defined period. For an illustrative month with 60,000 currency units of eligible acquisition spending and 30 acquired customers, CAC is 2,000 units per customer. The numerator should be stated, since an advertising-only figure and a figure that also includes sales costs answer different questions.

The formula is simple; the period can mislead. A sales team may do the work in one month and close the account later. If that is how a product sells, matching this month’s full spending with this month’s new customers can make a campaign look expensive just before its customers arrive, then unusually cheap when they do. Compare cohorts over a period that reflects the sales cycle and keep channel allocations consistent. The point is not to find a flattering denominator. It is to know what another customer is likely to require in spending under the same selling conditions.

CAC by itself does not say whether that spending was worthwhile. A customer who stays and expands is different from one who cancels quickly, even if both cost the same to acquire. Read CAC beside the recurring revenue produced by the acquired cohort and what remains of that cohort after time has passed. The question for a spending decision is concrete: if we add another set of customers through this channel, do their subscriptions have a credible route to covering the acquisition cost? If the cohort is too new to answer, say so and limit the commitment until more of its revenue history is visible.

I would also resist pooling every channel into a single CAC when deciding where to spend the next unit of budget. An average can look stable while one channel becomes more expensive and another produces fewer but more durable accounts. Split the calculation only where the spending and customer attribution are credible. A precise looking channel CAC built from loosely assigned shared costs is less helpful than a clearly labeled blended figure with its limits stated.

Define activation as the first useful outcome#

The handoff from acquisition to product use is where a signup count often loses its meaning. Creating an account shows that someone started; it does not show that the person received value. As Amplitude’s guide to product metrics explains, activation centers on a meaningful product milestone reached by an eligible new user. In a hypothetical shared-workspace product, that event might be a new account completing and sharing its first workspace, rather than merely opening an empty one. The right event would differ for a product whose core task is booking, editing, or analyzing.

Make the rate readable: of the eligible users or accounts entering during a stated period, what share reached the chosen event within a stated time window? For example, if an illustrative cohort has 200 eligible new accounts and 80 complete the first-value event within 14 days, its 14-day activation rate is 40%. The 200-account denominator and the 14-day window are part of the result. Switching from accounts to individual users, changing the event, or allowing more time changes the answer even if the product has not changed.

The activation event should be demanding enough to represent a real outcome, but close enough to the beginning of use to guide onboarding work. An event such as clicking through a tour may be easy to count without showing value. An event that usually happens only after months of use would give the team little early feedback. A useful choice is a specific action that a new customer can reasonably reach during the first experience and that expresses why the customer came. Keep that definition stable while comparing cohorts; change it deliberately when the product’s actual first useful outcome changes.

Activation is an early signal, not a replacement for retention. A team can improve the share of new users who reach a milestone while those users still fail to stay. After an onboarding change, compare later recurring revenue from the activated cohort with earlier cohorts before calling the change a business win. Conversely, weak activation can explain why paying for more signups is a poor next move: more people will encounter the same obstacle before reaching the product’s value.

Separate revenue saved from revenue expanded#

Retention begins with a fixed group of customers at the start of a period. GRR asks how much of that group’s starting recurring revenue remains after cancellations and reductions, excluding any expansion. NRR takes the same starting group and includes expansion as well. ChartMogul defines GRR and NRR in terms of starting MRR, churn, contraction, and expansion. New customers acquired during the period belong in the growth calculation, not in either starting-cohort retention calculation.

An illustrative 12-month cohort makes the difference visible. Suppose existing customers start with 10,000 units of MRR. Over the period, their cancellations remove 1,000, their downgrades remove 500, and upgrades within that same cohort add 2,000. GRR is (10,000 − 1,000 − 500) ÷ 10,000, or 85%. NRR is (10,000 − 1,000 − 500 + 2,000) ÷ 10,000, or 105%. Both numbers are true under those assumptions. The higher NRR says expansion outweighed losses in money terms; the 85% GRR says the starting revenue suffered material losses before expansion was counted.

If I had to choose one retention figure to inspect first, I would start with GRR, then read NRR. A strong NRR can come from a small set of expanding accounts while other accounts cancel or reduce their plans. That may be acceptable when a product is deliberately sold with small initial contracts that expand as customers use more of it. It is a weaker story when expansion depends on a few exceptional customers and ordinary accounts do not stay. GRR exposes the losses; NRR shows whether the remaining customers more than compensate for them. Neither figure explains the pattern without account-level context.

Account retention adds another useful view because revenue and customer counts can move differently. In a separate illustrative cohort of 100 starting accounts, if 10 cancel and none return during the period, 90 remain: customer retention is 90%. That percentage says nothing about whether the canceled accounts were the smallest or largest. Compare the account count with GRR when deciding whether the problem is broad attrition or a few high-value losses. It is especially important when a product has a wide range of contract sizes.

For both revenue retention measures, state the same time window and opening cohort every time. Monthly and annual retention are different questions; a newly signed customer should not inflate the performance of customers who were already present at the opening date. Data providers can vary in their calculation choices, so the name of the metric alone is not enough to make two figures comparable. ChartMogul’s definitions show how one provider calculates the measures.

Use the combination to decide the next move#

When MRR rises and GRR falls, I would first inspect the lost starting-cohort revenue before increasing acquisition spend. The new customers are adding money, but they may be replacing revenue that should have persisted. Check which opening accounts canceled or downgraded, then whether those accounts had reached the product’s first useful outcome. If the loss is concentrated in accounts that never activated, onboarding and the initial product experience deserve attention. If activated accounts leave after use, the problem lies later in the customer experience or in the fit between the product and those accounts. These are questions the metrics point toward, not conclusions the ratios can establish alone.

When activation and retention improve but MRR barely grows, I would look at the volume and cost of newly acquired customers. The product may be keeping the people it reaches, while the acquisition route is too small or too costly to scale. That pattern can justify testing a larger channel commitment, provided the CAC calculation includes the relevant costs and enough of the acquired cohort’s revenue is visible. The price of waiting for retention information is slower spending. The price of skipping it is committing budget before knowing whether the subscriptions last.

When NRR rises while GRR stays weak, I would avoid a blanket claim that retention is healthy. Identify the accounts responsible for expansion and compare them with the accounts that contracted or canceled. A repeatable path from first value to higher use supports investment in expansion. A small number of large upgrades alongside persistent losses calls for more care. The same NRR can therefore support different decisions depending on which customers created it.

These choices also keep growth beside efficiency. Bessemer Venture Partners’ cloud scaling framework considers revenue growth alongside the resources consumed to produce it. That is a useful principle for a SaaS operating review, though an investor framework should not become a universal target for every product or stage. If a new sales push raises MRR while CAC climbs and retained revenue weakens, the combination deserves scrutiny even when the top line looks attractive.

External benchmarks can sharpen a question, but they cannot settle it without a comparable population and calculation. ChartMogul’s SaaS benchmarks report is based on businesses in its observed data; its methodology and mix shape the resulting comparison. Company size, customer mix, and the exact definition of a metric all matter. Use a benchmark to ask why your GRR or growth differs from a relevant peer group, then decide from your own cohorts and economics. A number from another company’s dashboard cannot tell you whether your next decision should be an onboarding change, a sales investment, or a retention fix.

The monthly review can stay compact. Put opening and closing MRR beside the additions, expansions, reductions, and cancellations that connect them. For the customers acquired in the period, show CAC with its spending boundary and activation with its event, entry population, and window. For customers present at the start, show GRR and NRR over the chosen period and look at the accounts behind a material change. That small set does more work than a larger list of unconnected percentages: it shows where recurring revenue came from, what it cost to create, and how much of the existing base remained.