North Star Metric and OKRs for SaaS Teams That Ship
A team without a shared measure of success optimises for whatever its function can see. A north star metric gives everyone the same target, and OKRs turn it into quarterly work. This guide shows how to choose a metric that means something and how to write objectives that change behaviour.
TL;DR
- A north star metric measures the value customers receive and predicts long-term revenue. It is not revenue itself.
- Good candidates are leading indicators you can influence, such as nights booked or weekly active teams.
- Break it into input metrics so each team can see how its work moves it.
- OKRs are quarterly: a few ambitious objectives, each with measurable key results about outcomes, not activity.
- Review weekly, grade honestly, and keep the number of goals small.
Why one number helps
Product, marketing and sales each have natural metrics: features shipped, leads generated, deals closed. Each can improve while the customer gets nothing new. A north star metric points them all at the same thing: the value customers actually receive.
Choosing a north star
A useful north star meets five tests.
| Test | Question |
|---|---|
| Value | Does it capture a customer getting real value? |
| Leading | Does it move before revenue and retention do? |
| Influenceable | Can teams change it through their work? |
| Measurable | Can you compute it weekly from data you trust? |
| Understandable | Can anyone in the company explain it in one sentence? |
Examples often quoted: Airbnb’s nights booked, which combines guests and hosts getting value, and Spotify’s time spent listening, which reflects engagement. For a B2B tool, candidates could be weekly active teams completing the core workflow or invoices processed per month.
Avoid vanity measures like sign-ups or page views, and avoid metrics you can inflate by annoying customers, such as notifications sent.
Break it into inputs
A north star alone is too coarse for a team to act on. Decompose it into inputs.
For a tool whose north star is weekly active teams completing a core workflow:
| Input | Owner | Example lever |
|---|---|---|
| New teams reaching activation | Product, growth | Onboarding |
| Teams still active after four weeks | Product, success | Retention work |
| Reactivated teams | Marketing, success | Win-back sequences |
| Workflows completed per team | Product | Depth features, integrations |
Now each team can see which input it moves and how that rolls into the whole.
From metric to OKRs
OKRs (objectives and key results) connect that target to a quarter’s work. Google’s re:Work guide is a clear introduction. The structure:
- Objective: a short, qualitative, ambitious statement. “Make the first week with us unmistakably useful.”
- Key results: two to four measurable outcomes that show whether you got there. “Raise activation within 7 days from 22% to 35%.” “Cut median time to first report from 3 days to 1 day.”
Key results should measure outcomes, not tasks. “Launch the new onboarding flow” is a task, while “raise activation to 35%” is an outcome.
A worked example
A 25-person SaaS company picks weekly active teams as its north star. The quarter’s company objective: “Make new teams successful faster.” Key results: activation within 7 days up from 22% to 35%, week-4 retention up from 31% to 38%, and median time to first value down from three days to one. Product takes the first and third, success the second, and marketing supports with onboarding emails. Each team writes one or two OKRs that feed those numbers.
Run them with rhythm
- Weekly: a 20-minute check-in on the key results and blockers.
- Mid-quarter: adjust if something is clearly off track or obsolete.
- End of quarter: grade each key result honestly, write what you learned, and set the next set.
Grade on a 0 to 1 scale. Ambitious goals often land around 0.6 to 0.7. If you hit 1.0 every time, your targets are too safe.
Common mistakes
- Too many OKRs. More than a handful dilutes focus.
- Output key results, such as “ship five features”, which reward activity, not results.
- A metric no one controls, which leads to excuses.
- Cascading rigidly, forcing every team to link every goal.
- Tying OKRs to pay, which encourages sandbagging.
- Changing the north star every quarter, so no trend builds.
Where it fits as you grow
At small scale, one company-level set and a weekly review is enough. As you add managers, teams will need their own goals, which connects with scaling from 10 to 20 and org design at 20 to 50. Pair the north star with commercial measures from SaaS metrics so you are watching value and economics together, and use product-market fit signals to check you are measuring the right thing.
Questions to test your north star
Before you commit, ask:
- If this number doubled, would customers clearly be better off?
- Could we raise it in a way that hurts customers, for example with more notifications?
- Does it usually move several weeks before revenue and retention?
- Can every team name at least one action that changes it?
- Can a new hire understand it in one minute?
If any answer is no, refine the definition. Then check it against reality: plot the metric against retention for your last six cohorts. If cohorts with a higher value do not retain better, you have measured activity rather than value.
Your next step
Plot your candidate north star against retention for the last six cohorts. If higher values do not predict better retention, change the candidate. Do this before you announce anything to the company.
Bottom line
Choose a north star that reflects customer value and leads revenue, decompose it into inputs teams can move, and write a few OKRs with outcome-based key results. Review weekly, grade honestly and keep the metric stable long enough to see a trend.
Frequently Asked Questions
What makes a good north star metric?
It reflects customer value, correlates with retention and revenue, is measurable frequently, and teams can influence it. Airbnb's nights booked and Spotify's time spent listening are commonly cited examples.
Should revenue be the north star?
Usually not. Revenue lags and can rise through short-term tactics that hurt customers. A value metric that leads revenue is more useful, with revenue tracked alongside it.
How many OKRs should a team have?
Fewer than feels comfortable: typically one to three objectives with two to four key results each. Too many goals dilute focus.
Do OKRs work for small startups?
Yes, in a light form. At ten people, a single company-level set of objectives and a weekly check-in may be enough. Add team-level OKRs when coordination gets harder.
