Definition
Net Promoter Score (NPS) is a customer loyalty metric calculated by asking users "How likely are you to recommend this product to a friend or colleague?" on a 0-10 scale. Respondents are categorized as Promoters (9-10), Passives (7-8), or Detractors (0-6). NPS equals the percentage of Promoters minus the percentage of Detractors. The result ranges from -100 to +100.
The metric was introduced by Fred Reichheld of Bain & Company in a 2003 Harvard Business Review article and is maintained through the Net Promoter System. PMs use NPS as a lagging indicator of product satisfaction and a leading indicator of organic growth (Promoters refer new users) and churn (Detractors leave at 2-3x the rate of Promoters).
The NPS Calculator automates score computation and segment analysis, and the Product Analytics Handbook covers how to design NPS programs and integrate results into product decisions.
Why It Matters for Product Managers
NPS matters for three specific reasons.
First, NPS creates a common language for product quality. When the PM, the CEO, and the support lead all discuss whether the product is "good," they need a shared metric. NPS provides one. A score of 35 means 35 percentage points more Promoters than Detractors. It is imperfect but universally understood. This shared language enables faster alignment on priorities.
Second, NPS predicts growth and churn. Bain's research shows that Detractors churn at 2-3x the rate of Promoters. Companies with NPS above 50 grow at 2x+ the rate of competitors in their category. A declining NPS score typically precedes rising churn by 1-2 quarters, making it a valuable early warning system.
Third, NPS generates qualitative insight when combined with the follow-up question. The numeric score tells you how many users are unhappy. The open-ended follow-up ("What is the primary reason for your score?") tells you why. PMs who close the loop with Detractors within 48 hours generate more actionable product feedback than any survey tool or feature request board.
How NPS Works
The Score
NPS = % Promoters - % Detractors
| Category | Score | Behavior Pattern |
|---|---|---|
| Promoters | 9-10 | Active advocates. Refer others. Buy more. Tolerate occasional mistakes. |
| Passives | 7-8 | Satisfied but unenthusiastic. Vulnerable to competitive offers. |
| Detractors | 0-6 | Unhappy. At risk of churning. May actively discourage others. |
Example: 200 responses. 100 Promoters (50%), 60 Passives (30%), 40 Detractors (20%). NPS = 50% - 20% = 30.
Passives are excluded from the NPS calculation but are important strategically: they are the easiest group to move. A single positive experience can convert a Passive to a Promoter.
Two NPS Types
Relationship NPS (rNPS): Surveys the overall product experience. Sent quarterly or biannually to all active users. Tracks long-term brand and product health. This is the NPS people typically reference.
Transactional NPS (tNPS): Surveys satisfaction with a specific interaction. Sent immediately after an event (support ticket closed, onboarding completed, purchase made). Identifies specific touchpoint problems. Useful for PM teams responsible for specific product areas.
How It Works in Practice
Step 1: Design the survey
The core NPS question is standardized: "How likely are you to recommend [Product] to a friend or colleague?" followed by a 0-10 scale. Add one open-ended follow-up: "What is the primary reason for your score?" Keep the survey short. Every additional question reduces response rates.
Step 2: Choose timing and frequency
For relationship NPS: quarterly is standard. Stagger the survey so a random subset of users receives it each week, producing a rolling average rather than a single-point measurement. This smooths noise and provides continuous signal.
For transactional NPS: trigger immediately after the interaction. Add a cooldown: do not survey the same user more than once per 90 days regardless of how many interactions they have.
Step 3: Calculate and segment
Use the NPS Calculator to compute the score and segment it by:
- Plan tier: Free users typically score 5-15 points lower than paid users (they have not committed enough to love it).
- Tenure: New users (first 90 days) may score lower due to learning curve, or higher due to novelty effect. Track both.
- Usage level: Power users score differently from casual users. Heavy users who score low are your most actionable segment.
- Role: In B2B, the admin/buyer and the end-user may have very different NPS scores for the same product.
Step 4: Close the loop with Detractors
This is where NPS becomes actionable. Within 48 hours of receiving a Detractor score, reach out personally:
- Thank them for their feedback
- Ask what specific experience drove their score
- If the issue is fixable (billing error, access problem, missing documentation), fix it
- If the issue is a product limitation, acknowledge it honestly and share whether it is on the roadmap
Closing the loop converts 10-15% of Detractors to Passives or Promoters. More importantly, it generates the specific, contextual feedback that makes NPS valuable to the product team.
Step 5: Code qualitative feedback into themes
Categorize open-ended responses into themes: performance, pricing, reliability, missing features, support quality, onboarding confusion, etc. Track theme frequency over time. If "performance" was the top Detractor theme for three quarters, it should be a top priority regardless of what the roadmap says.
NPS Benchmarks
| Category | Below Average | Average | Good | Excellent |
|---|---|---|---|---|
| B2B SaaS | Below 10 | 20-30 | 30-50 | 50+ |
| Consumer tech | Below 0 | 10-30 | 30-50 | 50+ |
| E-commerce | Below 20 | 30-40 | 40-60 | 60+ |
| Enterprise software | Below 0 | 10-20 | 20-40 | 40+ |
The most meaningful comparison is against your own historical trend and direct competitors. A SaaS product moving from 15 to 25 over three quarters is improving, even if the absolute number is below the "good" benchmark.
Implementation Checklist
- ☐ Choose relationship NPS as the starting point (add transactional NPS later for specific touchpoints)
- ☐ Design the survey: 0-10 scale + one open-ended follow-up question
- ☐ Set the cadence: quarterly for relationship NPS, with weekly random sampling for rolling average
- ☐ Define the survey audience: all active users or stratified random sample
- ☐ Set up automated delivery and collection (Delighted, Wootric, or in-app survey tool)
- ☐ Build a dashboard showing NPS trend, segment breakdowns, and response themes
- ☐ Establish a 48-hour Detractor follow-up process with clear ownership
- ☐ Code qualitative responses into themes and track theme frequency quarterly
- ☐ Set NPS improvement targets by segment (e.g., "Improve enterprise NPS from 28 to 35 by Q4")
- ☐ Share NPS results and top themes in monthly all-hands or product review meetings
- ☐ Pair NPS with behavioral metrics (retention, churn, feature adoption) for a complete picture
- ☐ Do not tie NPS directly to individual compensation (it incentivizes gaming the survey)
Common Mistakes
1. Treating the number as a goal instead of a signal
NPS is a signal of product quality, not a goal to optimize directly. Teams that set "increase NPS by 10 points" as a goal often game it: they survey users after positive interactions, exclude inactive users, or add incentives for high scores. This inflates the number while providing zero useful insight. Improve the product experience and let NPS reflect the improvement.
2. Surveying only happy users
Excluding inactive, low-usage, or recently-complained users from the NPS survey inflates the score and eliminates the most valuable feedback. Survey a representative sample of all active users, including those who have had negative experiences. The uncomfortable Detractor feedback is where the product insights live.
3. Ignoring Passives
Passives (7-8) are the forgotten middle. They are not unhappy enough to complain but not enthusiastic enough to recommend. In competitive markets, Passives are the most at-risk segment because any competitor who offers a slightly better experience can convert them. Understand what would move them to 9-10 and invest accordingly.
4. Over-indexing on the score, under-indexing on the "why"
The numeric NPS score is useful for tracking trends. The qualitative follow-up ("What is the primary reason for your score?") is where the actionable insight lives. Teams that report on NPS without reading and categorizing the open-ended responses are using 10% of the tool's value.
5. Measuring too frequently
Surveying users monthly or, worse, weekly creates survey fatigue. Response rates plummet and the remaining respondents are biased toward those who feel strongly (either very happy or very unhappy). Quarterly is the right cadence for relationship NPS. If you need more frequent data, survey a rolling random subset each week.
6. Not closing the loop with Detractors
Collecting Detractor feedback and not responding to it is worse than not surveying at all. Users who take the time to give negative feedback and receive no follow-up become more negative. Close the loop within 48 hours. Even if you cannot fix the issue, acknowledging it builds goodwill and generates deeper insight.
Measuring Success
Track these metrics to evaluate your NPS program:
- NPS trend (quarterly). Is the score improving, flat, or declining over 4+ quarters? The trend matters more than any single number. A score moving from 25 to 40 over a year indicates real product improvement.
- Response rate. Target: 20-30% for email surveys, 10-15% for in-app. Below 15% suggests survey fatigue, poor timing, or email deliverability issues.
- Detractor close-the-loop rate. Percentage of Detractors who received personal follow-up within 48 hours. Target: 100% for B2B products with identifiable accounts, 50%+ for high-volume consumer products.
- Detractor conversion rate. Percentage of Detractors who improved their score on the next survey. Target: 10-15%. Higher indicates effective follow-up and product improvements.
- NPS-to-churn correlation. Validate that Detractors actually churn at higher rates than Promoters in your data. If there is no correlation, NPS may not be a useful leading indicator for your specific product.
- Theme resolution rate. Percentage of top-3 Detractor themes that received product investment within 2 quarters. Target: at least 1 of the top 3 themes per quarter.
The HEART Framework provides a more structured approach to UX metrics that complements NPS, and the metrics guide covers how to integrate NPS into a broader measurement system.
Related Concepts
HEART Framework is a complementary UX metrics framework (Happiness, Engagement, Adoption, Retention, Task Success) that provides structured measurement beyond the single NPS number. Churn Rate is the metric that NPS predicts: Detractors churn at 2-3x the rate of Promoters, making NPS a valuable leading indicator. Customer Journey Map identifies the touchpoints where transactional NPS is most valuable, connecting the score to specific product moments. Product-Market Fit relates to NPS through the Sean Ellis survey: products where 40%+ of users say "very disappointed" if they lost access tend to have NPS above 40. Retention Rate is the behavioral metric that validates what NPS measures attitudinally: if NPS is high but retention is low, users say they love the product but do not actually return.