How to pick a metric that measures delivered value instead of extracted revenue, break it into an input tree teams can actually move, and know when you've earned the right to have one at all.
The theory in one paragraph
Revenue is a lagging trace of value you delivered months ago — steering by it is driving with the rear-view mirror. A north star metric replaces it with the single number that captures the moment customers receive your core value: nights booked for Airbnb, time spent listening for Spotify, messages sent for WhatsApp. Because delivered value predicts retention, and retention predicts revenue, the north star leads where financial metrics lag. Its second job is political: when every team optimizes one shared number instead of departmental KPIs, growth stops being a department and becomes the company's operating system — which is exactly what Sean Ellis and the growth-hacking movement were arguing for.
The mechanics — as Sean Ellis defined them, not the folklore version.
Revenue measures what you took from customers; the north star measures what they got. Airbnb's nights booked only grows when both a guest and a host got what they came for. That's the design bar: find the event where the customer's success and your success are the same event. If your metric can rise while customers get less value — ad impressions, time-in-app for a utility — you've picked a self-portrait, not a north star.
Value delivered this week becomes retention next month and revenue next quarter. That lag is why a company can post record revenue while its north star quietly falls — Blockbuster-style borrowed time. A well-chosen north star gives you the bad news early enough to act on it, which is the entire point of a leading indicator.
No team can walk in Monday and move 'nights booked' directly — it's an output. So you decompose it into input metrics: active listings, search-to-booking conversion, repeat guest rate. Each input is ownable by a specific team and movable within a quarter, and the tree is explicit about the math connecting them. The north star aligns; the inputs operate.
You have to earn a north star
Ellis's own sequencing is the part that gets skipped: before the metric comes the 40% test. Survey users — 'how would you feel if you could no longer use this product?' — and if fewer than 40% say 'very disappointed', you don't have product-market fit yet, and a north star would just measure how efficiently you deliver something people don't want. The metric is a scaling instrument, not a discovery instrument. Pre-PMF, your north star is finding the value; only after do you get to count it.
Coined 'growth hacking' · early growth lead at Dropbox and LogMeIn · author of Hacking Growth
Ellis ran growth at a string of breakouts — LogMeIn, Eventbrite, and Dropbox in its earliest days — and kept noticing that the job he did had no name, so in 2010 he gave it one: growth hacking. Through his GrowthHackers community he popularized two ideas that fit together like lock and key: the north star metric as the number a growth team exists to move, and the 40% survey as the test of whether you've earned the right to move it.
Each step maps to a field in the North Star Metrics tool — finishing the read means finishing the work.
One sentence, one event: 'a founder shares a finished canvas', 'a guest completes a stay'. Not a feature, not a session — the exchange where the promise of the product is kept. Everything else hangs off this sentence.
North Star Metrics · value momentAsk active users how they'd feel if the product disappeared. Under 40% 'very disappointed' means the honest north star is still qualitative — keep iterating on value, and don't build a measurement cathedral on sand.
A real candidate captures the value moment, moves with retention, and is measurable weekly. Strike revenue (lagging), registered users (vanity), and anything that can grow while customers get less value. You should end with two or three candidates and a clear argument for one.
North Star Metrics · candidate metricsBreak the north star into three to five input metrics with explicit math between them — breadth (more users doing it), frequency (doing it more often), depth (doing more of it per session). Assign each input to a team. An unowned input is a wish.
North Star Metrics · input treeWire the tree into your weekly cadence: each experiment names its target input before it runs, and the north star gets reviewed against trend, not point-in-time. When the number moves and no experiment claims credit, that's not a win — that's a mystery to investigate.
North Star Metrics · experiment logThe steps above are the North Star Metrics tool's structure. Open it and work through them with your own startup — your readiness score starts building from the first field.
Free account · no card required
Teardowns from our benchmarks library where this framework is doing real work.
Benchmark teardown
Airbnb
Nights booked counts delivered value for both sides of the marketplace in one number — the design bar for two-sided north stars
Read the teardown
Benchmark teardown
Spotify
Time spent listening beats subscriber count because it predicts churn before churn happens
Read the teardown
Benchmark teardown
Messages sent, not registered users — optimizing the send builds the network effect as a side effect
Read the teardown
A north star metric is the single number that best captures the value customers receive from your product, used to align every team's work. Classic examples: Airbnb tracks nights booked, Spotify tracks time spent listening, WhatsApp tracks messages sent, and Facebook famously tracked daily active users. Each measures a moment of delivered value rather than a financial outcome.
A company has many KPIs — departmental numbers like CAC, ticket response time, or uptime — but only one north star. KPIs measure whether a function is performing; the north star measures whether the customer is winning, and it sits upstream of the KPIs as the number they should all ultimately serve. If a KPI improves while the north star doesn't, the KPI is measuring motion, not progress.
Usually no — revenue measures value you extracted, lags the customer experience by months, and can rise short-term through moves that destroy value, like aggressive pricing or dark patterns. The exceptions are businesses where the transaction is the delivered value, such as marketplaces using GMV as a proxy for successful exchanges. Even then, most teams pair it with a value-side check like repeat purchase rate.
Survey your active users with one question: 'How would you feel if you could no longer use this product?' If at least 40% answer 'very disappointed', Ellis's benchmark says you have product-market fit; below that, you're still searching for it. The threshold came from his pattern across dozens of startups — companies above it could scale growth, companies below it stalled. It's the gate you pass before committing to a north star.
One — the alignment power comes from its singularity, because two north stars reintroduce the departmental tug-of-war the framework exists to end. Teams that feel one number is too narrow usually need guardrail metrics (checks that the north star isn't being gamed, like quality or margin floors) and an input tree, not a second north star.
AARRR Pirate Metrics
Dave McClure · 2007
OKRs
Andy Grove & John Doerr · 1999
The Hook Model
Nir Eyal · 2014
Sources
Independent educational summary written by StartupKit from public sources. North Star Metric is the work of Sean Ellis; this page is not affiliated with or endorsed by the author.