If you are running a SaaS product right now, you probably have 12 dashboards open, 47 metrics tracked, and zero clarity about whether things are actually getting better. You know your signup count, your churn rate, your MRR, your NPS, your support ticket volume, your email open rate, and your landing page conversion rate. But when it comes time to make a decision — should we ship this feature? Should we kill this channel? Should we raise prices? — none of those metrics give you a clear answer.
That is because you do not have a North Star metric.
A North Star metric is the single number that best captures the core value your product delivers to customers. It is not the only metric you track. But it is the one that overrides the others when they conflict. It is the metric that tells you whether your SaaS is growing in a healthy direction, or just getting bigger in a way that will eventually collapse.
This guide shows you how to pick the right North Star metric for your developer tool or SaaS product, how to avoid the vanity metric traps most indie founders fall into, and how to use your North Star to actually make better decisions.
Why Indie Developers Drown in Metrics
The analytics tools available today are incredible. PostHog, Mixpanel, Amplitude, Plausible, and dozens of others will track every click, scroll, and event in your product. The problem is not a lack of data. The problem is too much data and too little signal.
When every metric is available, every metric becomes important. The developer who checks MRR daily starts optimizing for short-term revenue. The developer who obsesses over signups starts buying cheap traffic that never converts. The developer who tracks feature usage ships features that drive clicks but not retention.
Without a North Star, you are not running a business. You are playing whack-a-mole with dashboards.
The North Star metric solves this by creating a hierarchy. It says: “This number matters most. Every other number exists to explain why this number is moving.” When your North Star is up, you are probably making good decisions even if secondary metrics wobble. When your North Star is flat or down, something fundamental is broken — and you need to find out why.
For a deeper look at setting up the tracking infrastructure that feeds into your North Star, read Conversion Tracking for Developers.
What Makes a Good North Star Metric
Not every important number qualifies. A North Star metric must satisfy four criteria:
1. It reflects customer value. The metric grows when users get more value from your product, and shrinks when they get less. If users could get maximum value while your North Star tanks, it is the wrong metric.
2. It predicts long-term revenue. There should be a clear correlation between your North Star and your ability to make money. Not necessarily a direct line — but if the North Star grows consistently, revenue should follow within a reasonable timeframe.
3. It is actionable. You should be able to design experiments, features, and campaigns specifically to move this metric. A North Star that moves randomly is useless for decision-making.
4. It is comprehensible. Everyone on your team — including you at 2 AM — should be able to say what it is and why it matters without checking a document.
Here is how this filters out the common wrong answers:
| Metric | Why It Usually Fails |
|---|---|
| Total signups | Vanity metric — ignores activation, retention, and revenue quality |
| Page views | Easy to manipulate, weak connection to product value |
| MRR/Revenue | Lagging indicator, does not tell you if current users are healthy |
| App downloads | No correlation with actual usage or value |
| Social media followers | Completely disconnected from product success |
The North Star Metrics by SaaS Type
Different products deliver value in different ways. Your North Star should match your product’s core value proposition.
SaaS Tools Where Usage = Value
For products where the more someone uses it, the more value they get — project management, note-taking, design tools, documentation:
North Star: Weekly Active Users (WAU) or Monthly Active Users (MAU)
Why: A user who opens your product every week is getting value. A user who signed up once and never returned is not. WAU is a better metric than total users because it measures engagement, not accumulation.
Example: Notion’s North Star is likely “weekly active teams” — because a team that uses Notion weekly is getting collaborative value and is unlikely to churn.
Infrastructure and API Products
For developer tools where value is delivered through API calls, webhooks, or background processing:
North Star: API Requests Processed or Jobs Completed
Why: Your customers are building on top of your infrastructure. The more requests they send, the more embedded your product is in their stack, and the higher the switching costs.
Example: Stripe’s North Star is almost certainly “total payment volume” — the dollar value of transactions they process. It directly correlates with revenue, customer success, and product lock-in.
Collaboration and Team Products
For products that become more valuable as more team members use them:
North Star: Teams with 3+ Active Members
Why: Single-user accounts churn easily. Teams with multiple engaged members have network effects, higher switching costs, and natural expansion revenue.
Example: Figma’s North Star is likely “active teams with shared files” — because the magic of Figma happens when designers, developers, and stakeholders collaborate in real time.
Creator and Content Platforms
For products where users create something that generates value:
North Star: Projects Created or Content Published
Why: A user who creates something in your product has invested time and energy. That investment predicts retention and future upgrades.
Example: Webflow’s North Star might be “sites published” — because a published site represents a committed user who has gone through the entire creation workflow.
High-Touch B2B SaaS
For products with sales-led onboarding and annual contracts:
North Star: Customers Achieving First Value or Time-to-Value
Why: In sales-led SaaS, the biggest risk is not churn — it is failed onboarding. If a customer does not experience value in the first 30-60 days, they will not renew.
Example: A complex analytics platform might track “dashboards created with live data in the first 14 days” as their North Star.
How to Find Your North Star Metric
If you do not know your North Star yet, here is a three-step process to find it:
Step 1: Map the value moment.
What is the single action in your product that, if a user does it, makes them significantly more likely to stick around and pay?
For an email tool, it might be “sent first campaign.” For a hosting platform, it might be “deployed first site.” For a code review tool, it might be “reviewed first pull request.” This is often called the “aha moment” — the instant a user understands why your product is valuable.
Step 2: Check correlation with retention.
Look at your historical data. Do users who perform the value moment in their first week have higher 3-month retention? If yes, you have found a strong candidate. If no, keep looking. The value moment must predict retention, or it is not the right North Star.
Step 3: Test if it is actionable.
Can you design an experiment to move this metric? If your North Star candidate is “teams with 3+ members,” you could run an experiment: invite team members during onboarding vs. after first use. If you cannot think of an experiment, the metric might be too abstract.
For the technical implementation of tracking these moments, see the cohort analysis guide to validate whether your chosen metric actually predicts retention.
The Counter-Metric: What Your North Star Hides
Every North Star metric has a dark side. Optimize for one number blindly and you will eventually break something else. That is why you need counter-metrics — guardrails that prevent your North Star from being gamed.
Example 1: Your North Star is WAU.
- The risk: You spam users with notifications to drive logins. WAU goes up, but users hate you.
- Counter-metric: Session quality score (time spent, actions completed) or support tickets per user.
Example 2: Your North Star is API requests.
- The risk: You encourage inefficient API usage to inflate the number.
- Counter-metric: Error rate or customer-reported latency.
Example 3: Your North Star is projects created.
- The risk: Users create empty projects and never return.
- Counter-metric: Projects with 3+ sessions or published/shipped projects.
Pick 2-3 counter-metrics that represent the health of the user experience. Your goal is to grow the North Star without harming the counter-metrics. If they conflict, the counter-metric wins — because destroying user experience for a short-term metric spike always backfires.
Using Your North Star to Make Real Decisions
A North Star metric is useless if it does not change how you operate. Here is how to actually use it:
Feature Prioritization
When deciding what to build next, score every feature idea by its expected impact on the North Star. Not “will users like this?” Not “is this technically interesting?” Just: “If we ship this, what is our best guess for how the North Star moves in 30 days?”
This kills feature bloat. That cool integration nobody asked for? If it does not move the North Star, it does not ship.
Channel Evaluation
When testing a new marketing channel, do not just measure signups. Measure North Star contribution. A Twitter thread that drives 500 signups but zero activations is worse than a niche blog post that drives 50 signups and 40 activations. The North Star keeps you honest about channel quality.
For evaluating channels through this lens, the customer acquisition cost guide shows you how to connect channel spend to actual product engagement.
Pricing Experiments
When testing a price change, watch the North Star alongside revenue. A price increase that boosts MRR but crashes your active user count is a warning sign. You might be pricing out your most engaged users and replacing them with fewer, wealthier users who do not actually need the product. The North Star tells you if the customer base is getting healthier or just more expensive.
Team Alignment
If you have collaborators, contractors, or eventually employees, the North Star is your shared language. “We need to grow” is vague. “We need to get weekly active teams from 200 to 400 by Q3” is specific. Everyone can orient their work around that number.
The North Star Evolution: How It Changes as You Grow
Your North Star metric should evolve as your business matures. Here is the typical progression:
Pre-launch to 100 users:
- Focus: Activation. Did they experience the value moment?
- Candidate North Star: “Users who completed onboarding” or “Users who performed the aha moment”
100 to 1,000 users:
- Focus: Retention. Are they coming back?
- Candidate North Star: “Weekly active users” or “30-day retention rate”
1,000 to 10,000 users:
- Focus: Engagement depth. Are they using more features over time?
- Candidate North Star: “Power users” (users who use 3+ core features) or “feature adoption rate”
10,000+ users:
- Focus: Business health. Is the product sustainably profitable?
- Candidate North Star: “Net revenue retention” or “expansion MRR”
Do not jump ahead. A 50-user SaaS tracking net revenue retention is optimizing for a stage it has not reached yet. Start with activation, prove retention, then graduate to engagement and revenue expansion.
A Simple North Star Dashboard
You do not need a complex BI tool. A simple dashboard you check weekly is enough:
| Metric | This Week | Last Week | Change | Target |
|---|---|---|---|---|
| North Star (e.g., WAU) | 847 | 812 | +4.3% | 1,000 |
| Counter-metric 1 (e.g., Avg session quality) | 6.2 min | 6.4 min | -3.1% | > 5 min |
| Counter-metric 2 (e.g., Support tickets / 100 users) | 2.1 | 2.3 | -8.7% | < 3.0 |
| Secondary: MRR | $4,240 | $4,100 | +3.4% | $5,000 |
| Secondary: New signups | 45 | 52 | -13.5% | 50 |
Spend 5 minutes every Monday looking at this table. If your North Star is up and counter-metrics are healthy, you are on track. If your North Star is flat for 3+ weeks, something is broken and you need to investigate. If your counter-metrics are flashing red, pause growth experiments and fix the experience.
Start With One Number
Indie developers are drowning in data because the tools make it easy to track everything. The skill that separates successful founders from stressed ones is the ability to ignore most of it and focus on what actually matters.
Pick your North Star metric this week. Write it down. Put it somewhere you will see it daily. Share it with anyone you work with. When a decision feels ambiguous, ask: “Which option moves the North Star more?”
That one question will cut through more noise than any dashboard ever built.
Your North Star is the measurement layer of a larger marketing system. For how it connects to traffic, offers, and conversion, see the DRM 101 guide.
Topics
Related Articles
// frequently asked questions
Common Questions
What is a North Star metric and why does my SaaS need one?
A North Star metric is the single most important number that captures the core value your product delivers to customers. It aligns every team and decision around one clear goal. Without it, you optimize for conflicting metrics — marketing chases signups while product chases activation while support chases ticket closure — and nobody knows if the business is actually getting healthier.
What are good North Star metrics for developer tools and SaaS products?
Common North Star metrics for SaaS include Weekly Active Users (WAU) for products where regular usage drives value, Number of Teams Onboarded for collaboration tools, API Requests Processed for infrastructure products, Projects Created for creative tools, and Revenue for businesses where the transaction itself is the core value. The right metric depends on what your users do in your product that makes them stick around and pay.
Can revenue be a North Star metric?
Revenue can be a North Star metric for businesses where the purchase is the core value moment — e-commerce, marketplaces, or high-ticket B2B SaaS. But for most SaaS products, revenue is a lagging indicator. It tells you what happened last month, not whether users are getting value this month. A better approach is to use a usage metric as your North Star and track revenue as a close secondary metric that validates the usage.
How is a North Star metric different from a vanity metric?
A vanity metric looks good but does not predict future success. Total signups is a vanity metric if 90% of signups never return. A North Star metric must be: directly tied to customer value (users get more value as the metric grows), actionable (you can run experiments to move it), measurable (you can track it accurately), and reflective of long-term business health (not a short-term spike).
How often should I review or change my North Star metric?
Review quarterly, but change only when your business model or product stage shifts. Early-stage products often start with activation metrics ("did they experience value?") and graduate to retention metrics ("are they coming back?") as they mature. If you pivot, acquire a new product line, or discover that your current North Star no longer predicts revenue, then it is time to change. Avoid chasing new metrics monthly — consistency is what creates alignment.
Want More Marketing Tactics?
Subscribe to the CodeToCash newsletter for weekly articles, playbooks, and DRM strategies for developer entrepreneurs.
Trusted by indie developers shipping SaaS, tools, and templates. No spam.
// discussion
Questions? Thoughts?
Join the conversation below. You'll need a free GitHub account to comment.