Software Growth

North Star Metric

A North Star Metric is the single number that best captures the value customers get from your product and that your team agrees to grow above everything else.

A North Star Metric (NSM) is one measure that tells you whether customers are getting the value you promised. It gives a small team a shared answer to "is what we shipped this week working?" Revenue is a result of value, so it makes a poor North Star on its own. A better one sits upstream, in customer behavior that leads to revenue.

What makes a good one

Amplitude's North Star Playbook frames the metric as a bridge between three views: the customer's needs, the product's features, and the business's growth goals. A useful NSM usually passes these checks:

  • It reflects value delivered to the customer, not just value captured by you.
  • It measures behavior, so it moves when users do something.
  • It leads revenue. If it rises, revenue should follow with a lag.
  • Everyone on the team can see how their work moves it.

Airbnb's "nights booked" is the example the Amplitude material mentions. Notice that it counts completed value for guests and hosts, not signups or page views.

Examples for a small SaaS

  • Invoicing tool: invoices paid through the product per week.
  • Form builder: forms that received at least 10 responses this month.
  • Scheduling app: meetings booked per active account.

With 40 customers and $20k MRR, you might pick "invoices paid per week." If it was 600 last month and 750 this month, the product is delivering more value even before the revenue chart moves.

Input metrics

The NSM is a lagging view of many behaviors, so teams break it into a handful of inputs they can influence: breadth (how many users do it), depth (how much each does), frequency, and efficiency. For the invoicing example, inputs might be the activation rate of new accounts, the number of active accounts, and invoices per account. Individual teams own an input, which keeps the star from becoming an abstraction.

Common mistakes

  • Choosing revenue or MRR and calling it done. It tells you what happened, not what to do.
  • Choosing a vanity count such as total signups or page views, which can climb while customers leave.
  • Picking a metric nobody can influence in a quarter.
  • Changing it every month. Revisit it when your product or customer base changes materially, not on a whim.

For bootstrapped teams

You do not need a workshop. Write down the one action that makes a customer renew, see how many customers did it last month, and put that number on the wall. Pair it with a revenue measure so you do not optimize usage that nobody pays for.

Related terms

Sources

Back to the SaaS glossary