North Star Metric Examples for SaaS

A north star metric is the single metric that best captures the value your product delivers to customers. It gives every team in the company a shared answer to the question of what success looks like, and it keeps attention on long-term growth rather than short-term outputs like the number of features shipped or campaigns launched.

For a SaaS company, a good north star metric connects customer value to business success. Revenue matters enormously, but it is usually a result of value rather than the best measure of it. Revenue lags behind what customers experience. By the time a drop in value shows up in revenue, customers have often already decided to leave. A metric that measures value directly gives teams an earlier, more actionable signal. This article explains what makes a good north star metric, offers examples for different kinds of SaaS products, and covers how to choose, use and revisit one.

What makes a good north star metric

A good north star metric has several characteristics. It reflects customer value, meaning it rises when customers get more of what they came for. It predicts long-term growth, so that improving it tends to lead to better retention, expansion and revenue over time. It can be influenced by teams, so product, marketing, sales and customer success can each see how their work moves it. It is easy to understand, so anyone in the company can explain it in a sentence. And it is measured regularly, typically weekly, so teams can see the effect of their work without waiting months.

Metrics that fail these tests make poor north stars. Total registered users is easy to understand but does not reflect value, since many registered users never do anything. Revenue predicts growth by definition but lags customer experience and is hard for most teams to influence directly. Page views reflect activity rather than value.

Examples by type of SaaS product

The right north star metric depends on what the product does and how customers get value from it. The examples below illustrate how different types of products might approach the choice. They are starting points to adapt, not prescriptions.

For collaboration tools, value often comes from people working together. A metric like weekly active teams collaborating captures that. A team where several people are actively working together in the product is getting far more value than a single user occasionally logging in, and teams that collaborate are more likely to stay and expand.

For project management tools, value comes from getting work done. A metric like projects with completed tasks per week captures successful use. It goes beyond counting projects created, which could include abandoned ones, and focuses on whether work is actually moving forward.

For analytics tools, value comes from customers gaining insight. A metric like weekly active accounts viewing reports shows that customers are actually looking at the information the product provides, which is the point of an analytics product. Accounts that connect data but never view reports are not getting value.

For marketing automation tools, value comes from running campaigns. A metric like campaigns sent by active accounts indicates that customers are using the product's core functionality to reach their audience.

For CRMs, value comes from sales teams managing their work in the product. A metric like active sales teams logging deals weekly reflects real usage in sales workflows. A CRM that holds data nobody updates is not delivering value, however many seats are paid for.

For developer tools, value comes from developers successfully building and shipping. A metric like successful deployments or successful API calls from active projects represents value delivered to developers in a way that a count of signups or projects created does not.

For customer support software, value comes from resolving customers' problems. A metric like tickets resolved by active teams captures support outcomes, which is what support teams and their managers care about.

For scheduling software, value comes from meetings getting booked. A metric like meetings booked through the product ties directly to the outcome customers want.

Notice the patterns across these examples. Most of them combine a measure of activity that represents value, such as tasks completed, reports viewed or meetings booked, with a qualifier that focuses on active accounts or teams and a time period, usually weekly. This combination keeps the metric focused on ongoing value rather than one-off actions.

How to choose your north star metric

Start by asking what moment represents real value for your customers. When does the product actually do the thing customers bought it for? For a scheduling tool, it is a meeting booked. For an analytics tool, it is a customer looking at a report and learning something. That moment is the core of your north star metric.

Next, test candidate metrics against your data. Does the metric correlate with retention? Do accounts that score higher on it tend to stay longer, expand more and generate more revenue? If a candidate metric does not predict retention, it may be measuring activity that customers do not actually value.

Consider whether teams can influence it. Product teams can affect how easy it is to reach the value moment. Marketing can bring in customers more likely to reach it. Customer success can help struggling accounts get there. If no team can see how its work connects to the metric, it will not guide decisions.

Keep it simple enough to explain. A metric that requires a paragraph of definitions will not be remembered or used. Aim for something anyone in the company can state in a sentence.

Support it with input metrics

A north star metric is a high-level outcome. Teams also need input metrics, the specific drivers that move the north star, to guide their day-to-day work. For a project management tool whose north star is projects with completed tasks per week, input metrics might include the share of new accounts that create a first project, the number of active users per account, the share of accounts that invite collaborators and the rate at which tasks are completed.

Different teams can own different input metrics. The onboarding team might focus on first project creation, the growth team on collaborator invitations, and the product team on task completion. Together, these inputs drive the north star.

Use it to guide decisions

A north star metric is only useful if it shapes what the company does. Use it to prioritize work by asking how each project would affect the metric or its inputs. Use it in planning to set goals for the quarter or year. Review it regularly, typically weekly, alongside the input metrics that drive it. When the north star moves, investigate why, so the company learns what works. Acquisition channels can be evaluated this way too: a channel that brings in customers who reach the value moment, such as high-intent organic search built through an SEO growth program, is worth more than one that brings in signups who never do.

Be careful not to let the north star become a target that teams optimize at the expense of everything else. A collaboration tool that pushes users to invite colleagues aggressively might raise its weekly active teams metric in the short term while annoying customers. Pair the north star with guardrails, such as retention, customer satisfaction and revenue, to make sure improvements are real.

A worked example

Consider a company that sells a customer feedback tool to product teams. Its first instinct is to use the number of feedback submissions collected as its north star, since collecting feedback is what the product does. When the team checks this against retention, the correlation is weak. Some accounts collect thousands of submissions and still cancel, because nobody on the product team ever reads them.

The team looks more closely at accounts that renew and expand. What they have in common is that product managers regularly review feedback and link it to items on their roadmap. That action, feedback turning into a product decision, is where customers get value. The company changes its north star to weekly active accounts linking feedback to roadmap items. The new metric is slightly harder to move, but it predicts retention far better, and it changes priorities across the company. Product starts improving the linking workflow, customer success starts coaching accounts that collect feedback but never act on it, and marketing starts targeting product managers rather than support teams.

That shift, from measuring what the product does to measuring what customers achieve with it, is the essence of choosing a good north star.

Revisit it as the business changes

A north star metric is not permanent. As the product evolves, the market changes or the company's strategy shifts, the metric that best captures value may change too. A company that expands from serving individual users to serving large teams may need a metric that reflects team-level value. A company that adds a major new product line may need to rethink what value means. Review the north star every year or so, and change it when it no longer reflects how customers get value. Changing it too often, though, undermines its purpose, which is to provide a stable focus.

Avoid the common mistakes

The mistakes with north star metrics are predictable. Companies choose vanity metrics like total signups that do not reflect value. They choose revenue, which lags and is hard for most teams to influence. They choose metrics so complex that nobody understands them. They pick a north star but never connect it to input metrics, so teams cannot see how to move it. They optimize the metric without guardrails. And they choose a metric and then ignore it, so it never guides decisions.

Bringing it together

A north star metric captures the value your product delivers to customers in a single, regularly measured number. A good one reflects customer value, predicts long-term growth, can be influenced by teams, is easy to understand and is tracked frequently. The right choice depends on your product: weekly active teams collaborating for a collaboration tool, projects with completed tasks for project management, accounts viewing reports for analytics, meetings booked for scheduling. Support it with input metrics, use it to guide decisions with guardrails in place, and revisit it as the business changes. Chosen well, it gives the whole company a shared understanding of what success means and a clear signal of whether customers are getting what they came for.