How to choose a north star metric: a practical framework
Max Musing
Max MusingFounder and CEO of Basedash
· July 14, 2026

Max Musing
Max MusingFounder and CEO of Basedash
· July 14, 2026

A north star metric is the single number that best captures the value your product delivers to customers. It sits above your dashboard as the one measure the whole company works to move, and it works best when growth in the number means customers are getting more value. For a messaging app it might be messages sent between people who know each other. For a marketplace it might be transactions completed. For a subscription analytics tool it might be weekly active teams running queries.
Choosing one well is harder than it looks, because the wrong north star pushes teams to optimize a number that goes up while the business stalls. This guide covers a practical framework for choosing a north star metric, examples by business model, common anti-patterns, and when a single north star is the wrong idea.
A north star metric (sometimes called a north star KPI) is a single, high-level measure that a company chooses as its primary indicator of success. The idea is that if you pick the right one, then focusing the whole organization on moving it will pull revenue, retention, and growth along with it.
The concept was popularized by growth advisor Sean Ellis and later formalized in Amplitude’s North Star Playbook, which frames the north star as the metric that “best captures the core value your product delivers to customers.” The emphasis on value matters. Your north star should be the measure that sits closest to the moment a customer gets what they came for, even if it is not your biggest number or your most impressive chart.
Two things a north star metric is not:
If you want the broader distinction between plain measures and the ones worth managing, see our guide on KPI vs metric. A north star is a specific, company-level KPI with an unusually heavy job.
Before you pick one, it helps to know what you are selecting for. A strong north star metric passes five tests.
Use these as a scoring rubric. Write down two or three candidate metrics and rate each one against the five tests. The candidate that scores well across all five, rather than perfectly on one, is usually the right choice.
The right north star depends heavily on how your product creates value. The table below maps common business models to the kind of value moment they hinge on and a candidate metric that sits close to it. Treat these as starting points.
| Business model | What “getting value” looks like | Candidate north star metric |
|---|---|---|
| Product-led SaaS | A team does real work in the product every week | Weekly active teams performing a core action |
| Content or media | People spend time with content they find worth returning to | Weekly time spent by returning users |
| Marketplace | A buyer and seller complete an exchange | Transactions completed per period |
| Messaging or collaboration | People communicate with others who matter to them | Messages sent between connected users |
| E-commerce | Customers buy and come back to buy again | Repeat purchase rate or orders per active customer |
| Usage-based infrastructure | Customers run more real workloads on your platform | Consumption of the core resource (queries, API calls, compute) |
Publicly, growth teams often cite examples like nights booked for a lodging marketplace, or time spent listening for a music service. These illustrate the pattern and are not confirmed internal metrics, so borrow the logic rather than the exact number.
Each of these is an action a customer takes that signals value, and each can be counted consistently. None of them is “revenue” or “total signups.”
Revenue is the outcome you want, so it is tempting to make it the north star. But revenue is a lagging indicator: by the time it moves, the behavior that caused it happened weeks or months earlier.
Revenue also invites shortcuts that damage the business. A team told to move revenue this quarter can raise prices, push aggressive upsells, or chase low-fit customers who churn later. All three lift revenue briefly and hurt the company. A well-chosen north star sits upstream of revenue, so moving it tends to grow revenue durably rather than borrowing it from the future.
The healthiest setup is to treat the north star as the primary operating metric and revenue as the business result it should predict. If your north star climbs for two quarters and revenue does not follow, you probably picked the wrong north star, but that is no reason to abandon the approach.
Work through these steps in order.
You will rarely find a perfect metric. Aim for the one that is directionally right and hard to game, then refine the definition as you learn.
On its own, a north star is too high-level to tell anyone what to do on Monday. Break it into input metrics: the two to four levers that, when pulled, move the north star.
If your north star is weekly active teams running a core action, the inputs might be new team activation rate, the percentage of teams that reach the core action in their first session, and week-four retention. Each input is something a specific team can own and affect directly.
This is a shallow metric tree: the north star at the top, its direct drivers below, and the tactical metrics teams manage beneath those. The tree keeps everyone aimed at the same goal while giving each function a lever it controls. When the north star stalls, you look down the tree to find which input broke.
Watch for these predictable mistakes.
A north star is a focusing tool, and focus is only useful when you know what to focus on. Skip it, or hold it loosely, in these cases.
In these situations a short list of the three or four numbers that matter beats a single metric chosen for the sake of having one. Our take on data-driven decision making goes deeper on when metrics help and when they get in the way.
Once you have chosen a north star and its inputs, the metric needs a home the whole team trusts. That usually means computing it from your production database or warehouse rather than a spreadsheet someone updates by hand, so the definition stays consistent and the number is current.
A lightweight BI tool like Basedash works well here: you connect it to the database that already holds the underlying events, write the query that defines the metric once, and put the north star and its input metrics on a dashboard the team sees on a regular cadence. Computing it live keeps the definition in one place, so “active teams” means the same thing to everyone looking at it. Heavier enterprise platforms can do this too. The tool matters less than defining the metric once, measuring it consistently, and keeping it visible.
Whatever you use, keep the north star review on a fixed rhythm, weekly or monthly, and always look at it alongside its input metrics so a stall points you to a cause.
A north star metric is a specific, company-wide KPI. It is the single most important measure of the value your product delivers, chosen to align the whole organization. A KPI is any metric tied to a goal, and a company can have many. The north star is the one at the top that the others should ladder up to.
Usually no. The purpose of a north star is focus, and multiple north stars defeat that. The exception is a company with separate product lines, which may need one per line. Individual teams should have their own input metrics, but the company should share a single north star.
Generally no. Revenue is a lagging result of delivering value, and optimizing it directly tends to encourage short-term tactics like aggressive upsells or price hikes that hurt long-term retention. A better north star sits upstream of revenue so that moving it grows revenue durably. Watch revenue as the outcome your north star should predict.
Rarely. A north star only compounds if it holds long enough to shape many decisions. You may refine how it is calculated as your understanding improves, but swapping the metric itself every quarter signals that it was not the right choice. Change it only when the business model or the value you deliver shifts.
An input metric is one of the two to four levers that move your north star. If the north star is weekly active teams, inputs might be activation rate, first-session success rate, and week-four retention. Inputs are owned by specific teams and are directly influenceable, which makes them the day-to-day levers for moving the north star.
It can, but it usually should not. A weighted score of several signals can be more accurate, yet it fails the simplicity test: people cannot explain it or reason about what moved it. A single countable action that closely tracks value is almost always a better north star, with the richer analysis kept in the supporting metrics beneath it.
Written by

Founder and CEO of Basedash
Max Musing is the founder and CEO of Basedash, an AI-native business intelligence platform designed to help teams explore analytics and build dashboards without writing SQL. His work focuses on applying large language models to structured data systems, improving query reliability, and building governed analytics workflows for production environments.
Basedash lets you build charts, dashboards, and reports in seconds using all your data.