Net Promoter Score (NPS) is a customer feedback metric that measures how likely people are to recommend a product, service, or company to others. SaaS businesses use it to understand customer sentiment, spot possible loyalty issues, and guide follow-up research. NPS is a useful signal, but it does not explain on its own why customers feel the way they do or whether they will renew.
NPS is usually collected by asking a question such as, “How likely are you to recommend our product to a friend or colleague?” Respondents choose a score from 0 to 10. The score groups are then used to calculate the overall result.
How to Calculate NPS
Responses are grouped into three categories based on the score they give.
| Score | Category | What it suggests |
|---|---|---|
| 9–10 | Promoters | Respondents who are more likely to recommend the product. |
| 7–8 | Passives | Respondents who are generally satisfied or neutral but may be less enthusiastic. |
| 0–6 | Detractors | Respondents who may be dissatisfied or unlikely to recommend the product. |
NPS = % of Promoters − % of Detractors
Example: A survey receives 200 responses: 110 promoters, 50 passives, and 40 detractors. Promoters are 55% and detractors are 20%, so NPS = 55 − 20 = 35.
NPS ranges from −100 to +100. Passives count toward the total number of responses but are not directly added or subtracted in the formula. A score of 35 means the promoter percentage is 35 percentage points higher than the detractor percentage. It does not mean 35% of customers will renew or recommend the product.
Why NPS Matters for SaaS
- Tracks customer sentiment. Repeated surveys can show whether reported willingness to recommend is improving or declining.
- Highlights possible friction. Low scores can help teams identify issues with onboarding, usability, support, reliability, or perceived value.
- Guides customer conversations. Feedback gives customer success and product teams a starting point for follow-up questions.
- Supports trend analysis. Consistent surveys can help compare sentiment across periods, plans, or customer groups.
- Creates a shared signal. Teams can use NPS alongside other measures to discuss customer experience and prioritize investigation.
NPS vs. CSAT and Customer Effort Score
| Metric | Main focus | Typical question |
|---|---|---|
| Net Promoter Score (NPS) | Willingness to recommend | How likely are you to recommend this product? |
| Customer Satisfaction (CSAT) | Satisfaction with a product, interaction, or experience | How satisfied were you with this support interaction? |
| Customer Effort Score (CES) | How easy or difficult it was to complete a task | How easy was it to resolve your issue? |
These metrics measure different aspects of the customer experience. NPS is broad and relationship-oriented, while CSAT often focuses on a specific interaction and CES focuses on effort. Using them together can give a more complete picture than relying on one score.
Relationship NPS vs. Transactional NPS
Relationship NPS asks about the customer’s overall relationship with the company or product. It is often measured periodically to track broader sentiment.
Transactional NPS asks about willingness to recommend after a specific event, such as onboarding or a support interaction. The context can help teams identify experience-specific problems, but results should not be treated as interchangeable with relationship NPS.
How to Collect Useful NPS Feedback
- Use clear wording. Keep the recommendation question simple and consistent so results can be compared over time.
- Choose a sensible timing. Survey customers after they have enough experience to judge the product, or after a clearly defined interaction for transactional surveys.
- Ask for context. Include an optional follow-up such as “What is the main reason for your score?” to learn what influenced the response.
- Avoid over-surveying. Coordinate surveys across teams and channels so customers are not repeatedly asked for feedback.
- Keep the audience clear. Record which customer segment, plan, or interaction the survey represents.
- Report response rates. A score from a small or biased group may not represent the full customer base. Show response counts and response rates alongside results.
- Protect privacy. Explain how feedback will be used and limit access to identifiable responses to people who need it.
How to Improve NPS Responsibly
- Review the reasons behind scores. Read comments and group recurring themes instead of focusing only on the headline number.
- Close the feedback loop. Follow up with customers when appropriate, acknowledge their concerns, and explain what can realistically be done.
- Fix recurring product problems. Prioritize issues that create repeated friction, such as confusing workflows, missing capabilities, or reliability problems.
- Improve onboarding and support. Help customers reach value faster and make it easier to get assistance when needed.
- Share insights with the right teams. Product, support, customer success, and leadership should understand the themes relevant to their work.
- Track changes after action. Compare later feedback with earlier results while accounting for differences in audience, timing, and response rates.
- Use multiple measures. Review NPS alongside retention, churn, product adoption, support outcomes, and customer interviews.
Do not pressure customers to give a high score or coach employees to solicit only positive responses. That can distort the data and weaken trust. The goal is to understand and improve the experience, not to optimize the number at any cost.
Common NPS Mistakes
- Treating NPS as a direct measure of retention, revenue, or product-market fit.
- Comparing scores from different question wording, audiences, or survey methods without noting the differences.
- Ignoring response rates and possible response bias.
- Collecting scores without reading or categorizing the written feedback.
- Combining transactional and relationship NPS into one trend without explaining the difference.
- Making large decisions based on a small sample or a short-term change.
- Using generic benchmarks without considering industry, customer type, and survey method.
- Failing to tell customers what happened after they shared feedback.
Frequently Asked Questions
What is a good NPS for a SaaS company?
There is no universal score that guarantees success. Results vary by market, customer segment, product type, survey timing, and method. Compare your score with your own historical results and carefully selected peer benchmarks, and investigate the reasons behind the number.
Can NPS be negative?
Yes. NPS is negative when the percentage of detractors is greater than the percentage of promoters. The score can range from −100 to +100.
Do passives count in NPS?
Passives are included in the total number of responses used to calculate each group’s percentage, but the passive percentage is not directly added or subtracted from the final NPS.
Does a high NPS mean customers will renew?
Not necessarily. Recommendation intent is one signal of sentiment, not a guarantee of renewal. Customers may still leave because of budget, changing needs, product gaps, or other circumstances.
How often should SaaS teams measure NPS?
The right frequency depends on the customer relationship, contract cycle, and survey purpose. Use a consistent schedule for trend tracking, avoid excessive survey requests, and separate relationship surveys from feedback about specific events.