Choosing a North Star Metric for a B2B Product

TL;DR. A North Star metric is the single number that best captures the value customers get from your product, and that predicts long-term business results when it grows. In B2B, choose it at the level where value is actually realised — usually the account or team, not the individual login — and make it a measure of a job completed, not of activity. Pair it with three to five input metrics that teams can move week to week. Revenue is an outcome of a good North Star, not a North Star itself.

What is a North Star metric?

A North Star metric is one measurable number that reflects the core value your product delivers to customers, chosen so that when it grows, the business tends to grow with it. It sits between two things teams usually track separately: what customers care about (getting a job done) and what the company cares about (retention, expansion, revenue).

The idea is most closely associated with the North Star Framework published by Amplitude, the product analytics company. In that framework, a team picks one North Star metric plus a handful of inputs — the measurable customer behaviours that drive it — and product teams work on the inputs rather than trying to move the headline number directly.

The value of the exercise is not the number itself. It is the argument you have while choosing it, because that argument forces a team to agree, in writing, on what "customers getting value" actually means.

Why is choosing a North Star harder in B2B?

Consumer products often have one person who signs up, uses the product and pays. B2B products rarely do, and that makes the obvious candidate metrics misleading.

• The buyer and the user are different people. The person who approves the budget judges the product on outcomes they can defend; the person who uses it daily judges it on friction. A metric that only reflects daily use can miss why accounts renew. This is the same split described in Jobs to Be Done for B2B Product Teams.
• Value is realised by a team, not a login. A reporting tool is valuable when the finance team closes the month with it, not when one analyst opens it. Counting individual active users can rise while the account quietly stops relying on you.
• Usage is uneven by design. Many B2B workflows run weekly, monthly or at quarter end. A daily-active-user metric punishes a product that is used exactly as often as the work requires.
• Volumes are small and cycles are long. With tens or hundreds of accounts rather than millions of users, noisy week-to-week swings are normal, and the link between the metric and renewal can take a full contract term to show up.

None of this makes a North Star less useful in B2B. It means the default consumer examples — time spent, daily actives — rarely transfer.

What makes a good North Star metric?

Amplitude's North Star Playbook offers a checklist that works well as a first filter. A good North Star metric:

1. Expresses customer value — you can see why it matters to the customer.
2. Represents your vision and strategy — it reflects where the product is going, not only where it is.
3. Is a leading indicator — it predicts future results rather than reporting past ones.
4. Is actionable — teams can influence it through their work.
5. Is understandable — people outside the product team can explain it in plain language.
6. Is measurable — you can instrument the product to track it.
7. Is not a vanity metric — when it moves, the change is meaningful.

For B2B, add two tests of our own:

• Is it counted at the right unit? Decide explicitly whether the unit is the user, the team, the workspace or the account, and match it to the unit that renews.
• Would the economic buyer recognise it as value? If the person who signs the renewal would shrug at the number, it is probably measuring activity, not value.

Which kind of value does your product deliver?

Amplitude also describes three "games" a digital product can play: the attention game (value is time spent, typical of media), the transaction game (value is confident purchases or bookings), and the productivity game (value is completing a task or workflow efficiently).

Most B2B software plays the productivity game. That has a direct consequence for the North Star: more time in the product is often a sign of friction, not value. A good B2B North Star usually counts jobs completed — reports delivered, invoices reconciled, candidates hired, deployments shipped — rather than minutes or sessions. Marketplaces and procurement tools are the common exception, where the transaction game fits better.

How do you choose a North Star metric, step by step?

1. Write down the job. In one sentence, state the progress the customer is trying to make. If you cannot write it, the metric discussion is premature — do the discovery first.
2. Pick the unit that renews. Decide whether value is realised by an individual, a team or the whole account, and count at that level.
3. Define "value delivered" as an event. Turn the job into something the product can observe: a completed workflow, a shared output, an approved result. Avoid proxies like logins or page views.
4. Add a quality or frequency threshold. "Accounts that completed at least one reconciliation this month" is sharper than "reconciliations". Thresholds stop a few heavy accounts from masking many idle ones.
5. Check it against retention. Look at your own historical data: do accounts that score well on the candidate metric renew and expand more than those that do not? If there is no visible relationship, keep looking. With few accounts, treat this as a sense check, not a statistical proof.
6. Break it into inputs. List the three to five behaviours that drive the metric — for example breadth (how many teams in the account use it), depth (how many workflows they run), frequency, and efficiency (time to complete the job). Each input should have a named owner.
7. Write the definition down and publish it. Name, exact definition, unit, time window and data source. Ambiguous definitions are the most common reason North Stars get quietly abandoned.

What do B2B North Star metrics look like?

The examples below are illustrative, written for hypothetical products to show the pattern. They are not the metrics of any real company.

Hypothetical product	Job the customer hires it for	Illustrative North Star	Why not the obvious alternative
Accounts-payable automation	Pay suppliers accurately with less manual work	Invoices processed end to end without manual correction, per month	"Invoices uploaded" counts effort, not a completed job
Team analytics dashboard	Give managers a trusted weekly view of performance	Accounts where a report was shared and viewed by at least three people in the week	"Dashboards created" rewards setup, not use
Recruiting platform	Fill open roles with suitable hires	Hires made through the platform per active account per quarter	"Job posts published" is activity; the buyer pays for hires
Developer deployment tool	Ship changes to production safely	Successful production deployments per active team per week	"Builds started" includes failures and noise
Contract management tool	Get agreements approved and signed quickly	Contracts executed through the platform per month	"Documents created" includes drafts that never close

Notice the pattern: each North Star counts a finished outcome, at the account or team level, over a time window that matches how often the work actually happens.

What are the common mistakes?

• Using revenue as the North Star. Revenue is a lagging result of delivering value. It is essential to track, but it does not tell a product team what to change this week. The SaaS Metrics Glossary covers the revenue and retention metrics that should sit alongside the North Star.
• Counting signups or seats. Both can grow while value falls. Seats bought is a sales outcome; seats used to complete the job is closer to value.
• Choosing a user-level metric for an account-level product. Daily active users can rise because one team adopted you while the account's main use case churns.
• Picking several North Stars. Two or three "north stars" is a dashboard. Keep one, and let the inputs carry the detail.
• Changing it every quarter. A North Star should be stable for years, not quarters. Revisit it when strategy or the core job changes, not when the number disappoints.
• Skipping the inputs. Without inputs, teams cannot connect their work to the headline number and it becomes a slide rather than a steering tool.

How does a North Star relate to OKRs and KPIs?

The three work at different altitudes. The North Star is the long-lived measure of customer value. KPIs are the standing health gauges — revenue, retention, uptime — that you monitor continuously. OKRs are time-boxed goals to change something specific this quarter. A practical pattern is to set quarterly OKRs against the weakest North Star input, so the team's short-term goals roll up to the long-term metric. OKRs vs KPIs explains how the monitoring and changing layers fit together.

The North Star also gives roadmap conversations a common test. When a team plans its work in broad horizons rather than dated feature lists, as in a now-next-later roadmap, each item in "Now" should name the input it is expected to move.

Related reading

• The SaaS Metrics Glossary — the revenue and retention metrics that sit alongside a North Star.
• OKRs vs KPIs — how standing health metrics and quarterly goals work together.
• Jobs to Be Done for B2B Product Teams — finding the customer job your North Star should measure.
• Now-Next-Later Roadmaps: When They Work and When They Don't — planning work against outcomes instead of dates.
• All SaaS metrics articles — the growing cluster.