Most early teams track too many numbers. Signups, page views, downloads, followers, revenue, churn, and a dozen others compete for attention in every meeting. The result is that nobody knows what truly matters, and every metric can be argued up or down to tell a different story.
A north star metric cuts through the noise. It is one number that tells you whether customers are getting real value from your product. This guide explains how to choose one, how to break it into inputs that teams can act on, and how to avoid the common mistakes that turn it into another vanity number.
A north star metric measures the core value your customers receive. It sits between your product and your revenue. If customers receive more value, the number rises, and healthy revenue typically follows. It is not a goal in itself and not a financial target. It is a compass.
It is also not a vanity metric. Total signups only goes up. App downloads say nothing about whether anyone uses the app. Page views can be inflated by a single campaign. A good north star reflects value that users experienced, which means it needs an action behind it, not just a visit.
If a metric fails these tests, keep looking. A common warning sign is a number that goes up even when customers are unhappy.
The right metric depends on how your product creates value. These are illustrative examples, not universal rules.
Notice the pattern. Each one counts a completed, valuable action over a time period, rather than a raw count of people or visits.
Consider an illustrative scenario with a small invoicing SaaS for freelancers. The founders track signups and see them climb. Revenue is flat. In a team meeting, nobody can explain why.
After reflection, they realise the value is not in creating an account but in getting paid. A customer who sends an invoice and receives payment through the tool has received the core benefit. They pick a north star of "invoices paid through the platform each week". Now the conversation changes. Signup growth matters only if those people send invoices. Product work focuses on making the first invoice fast. Marketing targets freelancers who invoice regularly rather than anyone curious.
For example, such a team might discover that many signups never send an invoice, which points to a problem with onboarding rather than with acquisition. That insight would be invisible if they only watched signups.
The north star is too big for any single team to move directly. Break it into inputs that map to team responsibilities. A typical decomposition is: number of active customers, times the share who reach first value, times how often they repeat the action.
Each factor suggests a team and a set of experiments. Growth works on the number of new qualified users. Product and design work on the share reaching first value. Lifecycle and customer success work on repeat usage. If you are working on that second factor, our guide on mobile app onboarding and first-win activation shows concrete tactics for moving it.
A north star is only useful if the data is trustworthy. Before you set targets, check that the underlying events are tracked accurately, named consistently, and documented. Many teams discover that the number they thought they had is wrong because events fire twice or miss certain platforms.
Build a tracking plan first, then add dashboards. We explain how in our guide to an analytics tracking plan and event naming. Review your data quality on a schedule, not only when numbers look odd.
A rising total can hide a leaking bucket. If new users keep joining while older users quietly leave, the headline number looks healthy until growth slows. Look at your north star by cohort, grouped by signup week or month, and see whether newer cohorts perform as well as older ones.
Cohort views also show the effect of product changes. If a redesigned onboarding raises the share of new users reaching first value, the cohort after the change should look better. Our article on cohort retention analysis walks through how to read these charts.
Return to the invoicing example. The north star is invoices paid through the platform each week. A simple decomposition could be: active freelancers, times the share who send at least one invoice, times the share of those invoices that get paid online, times the average number of invoices per active freelancer.
Each factor now has an owner and a clear experiment list. Growth can target freelancers who invoice often. Product can shorten the path to the first invoice. Payments can improve the online payment experience for the end client. Customer success can nudge occasional users toward a regular habit. Nobody is guessing which number to move, and the team can see which factor is the current bottleneck.
Even a good north star can drift out of date. If you launch a new product line, enter a different customer segment, or change your pricing model, revisit it. Signs of trouble include the metric rising while retention falls, teams finding easy ways to inflate it, or a new customer group that gets value in a different way. When you change it, announce why, keep the old series for comparison, and avoid changing it again for a good while.
Put the north star and its inputs on one dashboard that opens every weekly meeting. Review what moved, why, and what experiment is next. Keep notes on decisions so you can learn from them later. Share the number with the whole company, since people make better daily choices when they see how their work connects to the result.
Be careful with targets. A rigid target can encourage shortcuts. Prefer a direction and a growth range, and discuss trade-offs openly. If you are building a product with an analytics layer or dashboards for your customers, our SaaS development services can help you design the data model so these metrics are reliable from the start.
A north star metric will not fix a weak product, but it makes problems visible and focuses effort. Start by defining the value your customers receive, find the action that proves it, and measure it over a sensible period. Break it into inputs, add guardrails, and review it every week.
Mavani Solution has delivered 37+ products for startups and SMEs, and the teams that grow steadily are usually the ones that know exactly which number tells them they are helping customers. Choose yours, write it down, and let it guide your next sprint.