AI Overview (under 150 words)

Net Promoter Score (NPS) measures customer loyalty using one question on a 0–10 scale. Calculate it by subtracting the percentage of Detractors (0–6) from the percentage of Promoters (9–10). Passives (7–8) do not count toward the score. The result ranges from −100 to +100. A higher NPS suggests stronger loyalty and word-of-mouth potential. Best practices include surveying at key journey moments, keeping the question unbiased, collecting comments for context, segmenting results, and closing the loop with respondents. Use confidence intervals and trend charts to validate changes over time.

Key Takeaways

• NPS = % Promoters − % Detractors; Passives do not affect the score.
• Use the same 0–10 scale and wording to keep data comparable.
• Segment by product, plan, and journey stage for insight.
• Don’t chase the number; act on themes in comments.
• Report NPS with sample size and margin of error.
• Track trends monthly or quarterly, not daily spikes.

Table of Contents

• What is the calculation of NPS?
• Why it Matters
• Benefits
• Step-by-Step Guide
• Real World Examples
• Common Mistakes
• Best Practices
• Expert Tips
• Comparison Table
• Frequently Asked Questions
• Conclusion
• Call To Action
• Internal Link Suggestions
• External References

What is the calculation of NPS?

Net Promoter Score (NPS) is a loyalty metric based on one standard question:

“How likely are you to recommend our company/product/service to a friend or colleague?”

Customers answer on a 0–10 scale. You then group them:

• Detractors: 0–6
• Passives: 7–8
• Promoters: 9–10

The calculation of NPS is:

NPS = (% of Promoters) − (% of Detractors)

• The result is an integer from −100 to +100.
• Passives don’t count in the formula, but they still matter for analysis.

Why it Matters

• Loyalty signal: NPS shows how likely customers are to refer you.
• Growth proxy: Promoters often renew, expand, and refer.
• Simplicity: One number leaders can track across teams.
• Benchmarking: Compare across products, cohorts, and time.
• Actionable: Comments reveal drivers to fix and amplify.

Benefits

• Fast to collect and analyze.
• Standardized scale allows trend tracking.
• Useful for board reporting and OKRs.
• Helps prioritize product and service improvements.
• Links to churn, LTV, and word-of-mouth growth.

Step-by-Step Guide

1. Draft the core question

• Use the standard wording to maintain comparability: “How likely are you to recommend…?”
• Keep the 0–10 scale. Do not change anchors.

2. Add an open-ended follow-up

• Ask “What’s the main reason for your score?” or “How can we improve?”
• This turns a score into actionable insight.

3. Choose timing and audience

• Post-purchase: 7–14 days after delivery.
• Post-onboarding: After users reach activation.
• Recurring relationship: Every 90 days for active customers.
• Avoid over-surveying the same person within 90 days.

4. Collect responses

• Use email, in-app, SMS, or web widgets.
• Aim for a representative sample across segments.
• Note: Randomize email send times to reduce bias.

5. Categorize responses

• Detractors: 0–6
• Passives: 7–8
• Promoters: 9–10

6. Calculate percentages

• % Promoters = (Promoters / Total responses) × 100
• % Detractors = (Detractors / Total responses) × 100
• Round to one decimal place for clarity.

7. Compute NPS

• NPS = % Promoters − % Detractors
• Present as an integer (e.g., 37), plus sample size (n) and date range.

8. Validate statistical confidence

• Report margin of error (MoE) and 95% confidence interval (CI) for the NPS.
• Tip: With n ≥ 200, changes of 5–10 points may be meaningful.

9. Analyze verbatims

• Tag comments by theme (price, speed, UX, support, reliability).
• Tie themes to score bands to see drivers.

10. Segment and report

• Break out by plan tier, region, product line, platform (iOS/Android/Web), or lifecycle stage.
• Track a rolling 3-month average for stable trends.

Real World Examples

Example 1: SaaS onboarding

• Responses: 250
• Promoters: 140
• Passives: 60
• Detractors: 50
• % Promoters = 140/250 = 56.0%
• % Detractors = 50/250 = 20.0%
• NPS = 56.0 − 20.0 = 36

Insight: Detractors cite confusing setup. After adding guided checklists, next quarter NPS rose to 44.

Example 2: E-commerce delivery

• Responses: 400
• Promoters: 180
• Passives: 120
• Detractors: 100
• % Promoters = 45.0%
• % Detractors = 25.0%
• NPS = 20

Action: Partnered with a faster carrier and improved order tracking. Detractors fell to 80/420 next cycle. NPS climbed to 32.

Example 3: Mobile app performance

• Responses: 120
• Promoters: 36
• Passives: 48
• Detractors: 36
• % Promoters = 30.0%
• % Detractors = 30.0%
• NPS = 0

Follow-up: Crash logs showed issues on older Android devices. A hotfix pushed NPS to 12 within six weeks.

Example 4: B2B services renewal

• Responses: 90
• Promoters: 50
• Passives: 28
• Detractors: 12
• % Promoters = 55.6%
• % Detractors = 13.3%
• NPS ≈ 42

Learning: High promoter share linked to proactive quarterly business reviews. Expanded the practice company-wide.

Common Mistakes

• Changing the scale: Using 1–5 or 1–7 breaks comparability.
• Counting Passives: Passives do not affect NPS directly.
• Small, skewed samples: Only surveying happy users inflates the score.
• Leading questions: Avoid wording that nudges positive scores.
• Inconsistent timing: Mixing post-purchase with renewal waves muddles trends.
• Ignoring comments: The number alone won’t tell you why.
• Overreacting to noise: Daily swings are normal. Use rolling averages.
• Not closing the loop: Failing to contact Detractors wastes chances to save accounts.
• Single-channel bias: Email-only misses active in-app users.
• Hiding n and CI: Leadership needs uncertainty ranges.

Best Practices

• Standardize the question and 0–10 scale.
• Set sample targets by segment to reduce bias.
• Keep surveys short: one score, one follow-up.
• Use neutral design and accessible UX.
• Send reminders, but no more than one per cycle.
• Tag comments with consistent taxonomies.
• Tie NPS to outcomes: retention, expansion, referrals, support tickets.
• Share wins back to respondents to build trust.
• Publish a quarterly NPS narrative with actions taken.
• Automate alerts for extreme scores with owner routing.

Expert Tips

• Confidence intervals: Estimate CI for NPS using bootstrap or standard methods. Report NPS 42 (95% CI: 35–49).
• Segment drift: Compare current segment mix to previous waves to explain movements.
• Trend smoothing: Use a 3- or 6-period rolling average for exec dashboards.
• Driver analysis: Link tagged themes and product events to scores with regression or Shapley values.
• Text analytics: Use topic modeling or keyword clustering on verbatims.
• Close-the-loop SLAs: Respond to Detractors within 48 hours; track save rate.
• Controlled experiments: A/B test onboarding or pricing changes and measure lift in NPS.
• Benchmark carefully: Industry norms vary widely; trend vs. yourself first.
• Combine metrics: Pair NPS with CSAT, CES, and retention for a full view.
• From score to revenue: Estimate LTV lift by moving a user from Passive to Promoter.

Comparison Table

Frequently Asked Questions

1. What is a good NPS?

• Broadly: <0 is weak, 0–30 is okay, 30–50 is strong, >50 is excellent. Context matters by industry and region.

2. What is the exact NPS formula?

• NPS = (% of Promoters) − (% of Detractors). Passives are excluded from the formula.

3. How many responses do I need?

• Aim for at least 200 per key segment or time period to stabilize results. More is better.

4. Should I round NPS?

• Yes. Report as an integer, and show the date range, n, and confidence interval.

5. Can I change the question wording?

• Avoid major changes. Keep the standard question for comparability.

6. Do Passives matter if they don’t affect the score?

• Yes. Passives often churn quietly. Read their comments to convert them into Promoters.

7. How often should I survey?

• Quarterly is common for relationship NPS. Use event-based (e.g., post-purchase) in between.

8. Can I use NPS in B2B?

• Absolutely. Survey multiple contacts per account and roll up to an account-level NPS.

9. How do I calculate a confidence interval for NPS?

• Use bootstrapping or standard error approximations. Many analytics tools can generate a 95% CI.

10. Should I weight responses?

• Usually no. Weighting by revenue or usage can distort loyalty signals. Instead, segment and compare.

11. What if my NPS is negative?

• It’s a signal to diagnose root causes. Focus on high-impact fixes and fast Detractor outreach.

12. What language should I use?

• Localize the question precisely. Keep the 0–10 scale and neutral wording.

13. Email or in-app?

• Use both. Email reaches infrequent users; in-app captures active users. Watch for channel bias.

14. Should I incentivize responses?

• Small, non-contingent incentives can help. Avoid rewards tied to positive scores.

15. Can I compare my NPS to competitors?

• Be cautious. Methods vary. Publish your method, then track your own trend first.

Conclusion

The calculation of NPS is simple: % Promoters minus % Detractors. The hard part is turning that number into action. Standardize your question, collect a fair sample, analyze comments, and close the loop. Report the score with context and confidence. Do this every quarter, and you’ll see clear links between NPS, retention, and growth.

Call To Action

Ready to move from dashboards to decisions? Use ZenixTools to collect NPS, tag comments with AI, estimate confidence intervals, and automate close-the-loop workflows. Start your free trial and ship your next NPS improvement in days, not months.

Internal Link Suggestions

• ZenixTools NPS Calculator and Confidence Interval Estimator
• ZenixTools Survey Builder: NPS, CSAT, and CES Templates
• ZenixTools Text Analytics: Auto-Tag NPS Comments by Theme
• Guide: How to Close the Loop on Detractors in 48 Hours
• Dashboard Tutorial: Build an Executive NPS Trend with Segments

External References

• Google Search Central: Structured data for FAQs and HowTo – https://developers.google.com/search/docs
• Schema.org: HowTo and FAQPage markup – https://schema.org
• W3C WCAG: Accessible survey design principles – https://www.w3.org/WAI/standards-guidelines/wcag/
• Mozilla MDN: Web forms usability and validation – https://developer.mozilla.org/en-US/docs/Learn/Forms
• Google Analytics Help: Event and conversion tracking – https://support.google.com/analytics