Net Promoter Score (NPS)

What is Net Promoter Score (NPS)?

NPS stands for Net Promoter Score. It measures customer loyalty with a single question: "How likely are you to recommend [product] to a friend or colleague?" Respondents pick a number from 0 to 10, and that number sorts them into one of three groups: promoters, passives or detractors.

The metric was introduced by Fred Reichheld in a 2003 Harvard Business Review article, and it spread quickly for a simple reason: it is one question, anyone can answer it in seconds, and the result is one number a whole company can follow. The "net" in the name is the subtraction that produces the score: the share of people who would recommend you, minus the share who would not.

What NPS measures is intent to recommend, which is used as a stand-in for loyalty. It does not measure satisfaction with a single interaction, and it does not measure usage. That distinction matters when you decide what to do with the number.

The NPS Scale: Promoters, Passives and Detractors

The NPS scale runs from 0 to 10, and the three groups are not evenly sized. Seven of the eleven possible answers make someone a detractor, and only the top two make a promoter.

• Promoters (9 to 10): loyal enthusiasts who are likely to keep using the product and recommend it to others.
• Passives (7 to 8): satisfied but not enthusiastic. They are not unhappy, yet they would switch without much regret.
• Detractors (0 to 6): unhappy or indifferent customers who are unlikely to recommend you and may actively warn others off.

The uneven split is deliberate. A 6 feels like a fairly positive answer to the person giving it, but people who answer 6 rarely recommend anything. The scale is strict so that the promoter group contains only people who would genuinely put their name behind your product.

How NPS Is Calculated

NPS = % Promoters − % Detractors

1. Count all the responses to the survey.
2. Work out the percentage that are promoters (9 or 10) and the percentage that are detractors (0 to 6).
3. Subtract the detractor percentage from the promoter percentage.

With 200 responses, of which 100 are promoters, 60 are passives and 40 are detractors, promoters are 50% and detractors are 20%. The NPS is 50 minus 20, so +30.

Three details trip people up:

• NPS is not a percentage. It is built from two percentages, but the result is written as a whole number, +30 rather than 30%.
• The range is -100 to +100. A score of -100 means every respondent is a detractor, +100 means every respondent is a promoter.
• Passives still count. They do not appear in the formula, but they are part of the total, so a large passive group pulls both percentages down and keeps the score close to zero.

NPS is also not an average of the 0 to 10 answers. Two products with the same average rating can have very different scores, because NPS only looks at which of the three groups each answer falls into.

How to Read an NPS Score

As a rough reading guide for SaaS, a score below 0 is a warning, a score between 0 and 30 leaves clear room to improve, a score between 30 and 50 is healthy, and anything above 50 points to real advocacy. Treat those bands as orientation, not as a target: scores vary by industry, by audience and by how and when the survey is sent, so a comparison with another company is rarely like for like.

The most reliable benchmark is your own score over time, collected the same way each round. For current SaaS ranges and how to compare fairly, see the benchmark section of the full NPS guide.

Always read the score next to the number of responses. An NPS based on 25 answers can swing by many points when two people change their mind, so small samples need caution before anyone celebrates or panics.

Relational vs. Transactional NPS

There are two ways to run an NPS survey, and they answer different questions.

Relational NPS is the number most companies report and track as a trend. Transactional NPS is narrower and more diagnostic: it points at one step of the customer journey. Keep the two apart when you report them, because a transactional score collected just after a good support call will usually run higher than the relational score from the same customers.

NPS in Product Management

For a product team, the single company-wide score is the least interesting part of NPS. The value comes from cutting it into pieces and reading the reasons.

• Segment the score. Compare NPS by plan, by role, by account size and by how long the user has been a customer. A healthy overall number can hide one segment that is deeply unhappy.
• Read it next to usage. Compare what promoters do in the product with what detractors do. Features that promoters use and detractors have never opened are strong candidates for better onboarding and feature discovery.
• Count the reasons. The open follow-up answer is where the product insight lives. Group the comments into themes and count them, so the roadmap reflects what many users said and not the loudest single comment. The customer feedback analysis guide covers the method.
• Ask inside the product. An in-app survey reaches people while they are using the product, so the answer reflects the experience they are having right now and not a memory of it.
• Pick the moment. Ask after the user has had time to get value, not in the first session and not in the middle of a task.

How to Actually Use NPS Data

Collecting NPS is worthless without acting on it. The actions that pay off most:

Close the loop with detractors. Reach out personally to low scorers within a couple of days. A customer who tells you they are unhappy is giving you a chance to fix it before they churn. The ones who do not tell you just leave.

Always ask the follow-up question. "What is the main reason for your score?" is where the real insight lives. Look across the answers for systemic issues, not only individual complaints.

Do not ignore passives. They are the easiest group to move. Ask what is missing for them, and you often get a short, concrete list.

Turn promoters into referrals. Promoters are already willing to recommend you. Make it easy with a timely prompt to leave a review, refer a colleague or take part in a case study.

Tell users what changed. When feedback leads to an improvement, announce it in the product. Users who see their feedback acted on are far more willing to answer the next survey.

NPS vs. CSAT vs. CES

NPS is one of three common customer survey metrics, and each one answers a different question.

They are complements, not rivals. Many SaaS teams run NPS on a schedule for the big picture and use CSAT or CES at specific moments to find out where the experience breaks.

NPS Limitations in SaaS

NPS is a useful proxy, not a complete picture. The main limitations to keep in mind:

• It is a lagging signal. NPS reflects past experience. By the time a user gives you a poor score, they may already be on their way out. Pair it with leading indicators such as activation and feature usage.
• Response bias. Very happy and very unhappy users are more likely to answer. Passives, who may be the bulk of your risk, often skip the survey.
• No causality. NPS tells you how people feel, not precisely why. That is what the follow-up question and behavioural data are for.
• It says what people intend, not what they do. Someone can say they would recommend you and never do it. Treat NPS as one input to a customer health score, not as the whole of it.
• Over-asking wears it out. Too many surveys lower response rates and skew the result towards the few who still answer. See the guide to survey fatigue.