North Star Metric: North Star Metric for Developer Tools
Finding the right NSM for developer-facing products where adoption patterns, integration depth, and API usage drive growth.
How to Apply
Track from docs visit → signup → first API call → production usage → expansion.
Evaluate API calls, active projects, production deployments, and MADUs.
Production usage predicts retention far better than trial usage.
Break into DX inputs (docs, SDKs), product inputs, and growth inputs.
Segment by individual vs team vs enterprise adoption patterns.
Expected Outcomes
- ✓ Developer adoption aligned with business value
- ✓ Better DX investment decisions
- ✓ Clear upgrade path metrics
Real-World Examples
Common Pitfalls
Ehsan's Insight
Developer tool NSMs have a unique property: the metric that drives adoption is different from the metric that drives retention. GitHub's adoption metric was repos created. Its retention metric was commits per week. Picking either one alone gives a misleading picture. The best developer tool NSM I have seen is "weekly active integration points" — meaning how many other tools or workflows does your product connect to per active team per week. Stripe measures API calls, but the more telling metric is unique endpoints used per merchant. When a customer uses Stripe for payments, subscriptions, AND invoicing, churn drops below 1% annually. The compounding insight: developer tools that become infrastructure (multi-touchpoint) are 10x more valuable than developer tools that remain features (single-touchpoint). Your NSM should measure the transition.
Ehsan Jahandarpour
AI Growth Strategist & Fractional CMO
Forbes Top 20 Growth Hacker · TEDx Speaker · 716 Academic Citations · Ex-Microsoft · CMO at FirstWave (ASX:FCT) · Forbes Communications Council