How to Select a North Star Metric for SaaS

Every SaaS company eventually faces a measurement crisis. Leadership wants growth, product wants to ship features, and customer success wants to reduce churn — but each team is tracking different numbers. The north star metric is the organizational answer to that fragmentation: a single leading indicator that, when it moves in the right direction, predicts that your business is actually delivering value.

The concept sounds deceptively simple. In practice, most companies either pick the wrong metric, pick the right metric for the wrong reasons, or pick it correctly and then fail to connect it to the day-to-day work of their squads. This guide walks through the criteria for a valid north star, the most common mistakes, and examples across different SaaS business models.

The Three Criteria for a Valid North Star

A north star metric must satisfy all three of the following conditions. Meeting two out of three is not sufficient — a metric that fails on even one dimension will eventually mislead the teams relying on it.

It must be a leading indicator of retention. The north star predicts future revenue, not current revenue. The causal chain is: customers experience value → the north star moves → customers stay and expand. Amplitude's 2024 Product Report found that companies with a validated north star metric that predicts 12-month retention grew annual recurring revenue 1.8x faster than companies tracking engagement metrics without a retention link. This predictive relationship is the core requirement. If you cannot demonstrate that accounts hitting your north star retain at a materially higher rate than accounts that do not, you do not have a north star — you have a dashboard metric.

It must be measurable from product data alone. If your north star requires data from Salesforce, your finance system, or a manual customer survey to calculate, your product team cannot own it. The metric must flow from the product instrumentation. This constraint also means the metric must be precise: "customer health" is not a north star, but "accounts with at least three active users who have completed five or more workflows in the past 28 days" could be.

It must be actionable at the squad level. The north star is only useful if it translates into specific experiments and features that individual teams can build. A metric that can only be moved by the entire company acting in concert — or that requires a pricing change to shift — is a leadership metric, not a product north star. Each squad should be able to articulate: "If we ship X, we expect it to move the north star by Y because of mechanism Z."

Why Revenue Fails as a North Star

Revenue is the most commonly chosen and most consistently wrong north star metric in SaaS. It is tempting because it is unambiguous, financially meaningful, and easy to explain to the board. But it fails all three criteria in subtle ways.

Revenue lags value delivery by weeks or months. A customer who stopped getting value from your product in March may not cancel until their annual renewal in November. By the time revenue drops, the product signal you needed was already eight months old. Conversely, a customer who experienced a breakthrough in your product in January may not expand their contract until Q3. Revenue is not just lagging — it is also obscured by contract structure.

Revenue is controlled by sales and finance, not product. Pricing changes, discounting practices, billing timing, and deal structure all affect revenue independently of whether the product delivered value. A product team optimizing for revenue will eventually start optimizing for deal size rather than product depth.

Revenue cannot be decomposed into squad-level actions. No individual squad ships a feature and sees a clear causal line to revenue. The signal is too aggregated, too slow, and too polluted by non-product factors.

Vanity Metrics: What They Have in Common

Vanity metrics are metrics that go up and to the right regardless of whether your business is healthy. Registered users, total page views, and raw feature usage all share the same fatal flaw: they measure activity, not value delivered. As Mixpanel's 2023 product benchmarks report noted, companies that optimize for raw session counts rather than value-delivery events tend to see higher activation but lower 90-day retention, because they are bringing in users who explore without finding value.

The test for a vanity metric is simple: can your metric go up at the same time as churn? If yes, it is a vanity metric. Registered users can grow while your best customers churn. Page views can increase because confused customers are searching your help center. Monthly active users can rise because you sent an aggressive re-engagement email campaign that pulled in dormant accounts.

The north star must be structured so that it cannot increase while customer retention is deteriorating.

North Star Examples by SaaS Category

Different business models produce different valid north stars. The examples below are illustrative — every company must validate its own metric against its own retention data.

Product-led growth (PLG) companies anchor on value-delivery events. Slack's famously documented north star was "messages sent within a team" — specifically, 2,000 messages sent, which correlated with long-term team retention. Figma's north star is often described as collaborative editing sessions involving two or more users. The common pattern is that PLG north stars measure a collaborative or productive action that signals the product is embedded in a workflow. For a detailed look at how PLG companies define activation events that feed into the north star, see the aha moment discovery framework.

Sales-led SaaS companies face a harder instrumentation problem because value delivery often happens in meetings, spreadsheets, and processes that live outside the product. The north star for sales-led companies tends to be an activation milestone count: the number of accounts that have completed onboarding and reached a defined adoption threshold. This metric is harder to game because it requires both successful onboarding and sustained usage, and it predicts renewal because underadopted accounts are the primary source of logo churn.

Marketplace SaaS companies typically have two customer sides, which creates a bifurcated north star problem. Most resolve it by anchoring on a transaction completion event that requires both sides to participate — a successful match, a completed booking, a fulfilled order. The north star must capture the moment of value exchange, not just traffic or listings.

Infrastructure and API companies (Twilio, Stripe, Sendgrid) anchor on consumption metrics because value delivery is identical to consumption: API calls made, events processed, emails sent. The north star is typically weekly active paying accounts above a consumption threshold, which separates growth accounts from trial accounts and filters out one-time integrators.

The North Star Selection Process

Selecting a north star is an empirical exercise, not a workshop exercise. The process has four steps.

First, generate candidate metrics. Ask each functional leader — product, engineering, customer success — to nominate the three metrics they believe best predict whether a customer will stay. You will typically get eight to fifteen candidates covering activation events, engagement patterns, feature adoption rates, and outcome indicators.

Second, run retention correlation analysis. For each candidate metric, segment your existing customer cohorts by whether they hit the metric in their first 30 and 60 days. Calculate 12-month retention for each segment. The metric with the largest retention gap between the "hit" and "did not hit" segments is your strongest north star candidate. According to research from OpenView Partners, the best-performing SaaS companies validate their north star against two to three years of cohort data before anchoring on it.

Third, test actionability. For the top two or three candidates, run a working session with squad leads to answer: "What would we build or change to move this metric?" If squads cannot generate five concrete initiatives in thirty minutes, the metric is too abstract. The activation rate framework describes how to connect activation events to squad-level experiments.

Fourth, add a counter-metric. For every north star, identify one metric that measures the downside risk of optimizing the north star too aggressively. If your north star is weekly active accounts, your counter-metric might be average support ticket rate per account — preventing a scenario where you drive activation through confusion-driven product exploration.

Common Mistakes After Selecting a North Star

Setting it and forgetting it. A north star is valid for a business model and a stage. As you move from SMB to mid-market, or from single-product to multi-product, the metric that predicted retention at $1M ARR may not predict it at $10M ARR. Revisit the retention correlation analysis annually.

Letting the north star drift into a dashboard. When leadership starts reporting twelve metrics in the same breath as the north star, the organizing function of the metric is lost. The north star must remain singular and privileged. Everything else is a contributing metric or a counter-metric.

Failing to connect the north star to compensation or OKRs. A metric that guides product decisions but does not influence how teams are evaluated will be deprioritized when the quarter gets busy. The north star needs to be the organizing principle of the product OKR process, not just a slide in the all-hands. The SaaS input/output metric hierarchy describes how to build that connection structurally.

Measuring it too infrequently. A north star that is calculated monthly is too slow for weekly product decisions. Most companies calculate the north star on a weekly basis, with daily visibility for teams running active experiments. The B2B SaaS KPI dashboard template shows how to structure the reporting cadence.

Frequently Asked Questions

Conclusion

The north star metric is the most important organizational decision a product team makes. It sets the direction for OKRs, determines what gets instrumented, and tells every squad what success looks like. Getting it wrong — by choosing revenue, choosing a vanity metric, or choosing a metric that cannot be disaggregated into squad actions — creates organizational drag that compounds over quarters.

Getting it right requires empirical validation: run the retention correlation, test the actionability, install a counter-metric, and revisit it annually. A north star that has been validated against real cohort data, connected to real squad OKRs, and protected by a real counter-metric is not just a metric — it is a management system.