Net Promoter Score (NPS)

NPS (Net Promoter Score) is a single-question loyalty metric: “How likely are you to recommend us to a friend or colleague?” answered on a 0-10 scale. You bucket respondents into promoters (9-10), passives (7-8), and detractors (0-6), then subtract the percentage of detractors from the percentage of promoters. The result is a number from -100 to +100. It was introduced by Fred Reichheld in a 2003 Harvard Business Review article and is now the most widely tracked loyalty metric in B2B SaaS.

What NPS is not

NPS is not a satisfaction score. CSAT asks “how satisfied were you with this specific interaction?”; NPS asks about willingness to advocate, which is a higher bar and a forward-looking signal. NPS is also not a revenue metric — it does not predict renewal on its own the way NRR or GRR do. And it is not a per-respondent score: an individual answer of 9 is a “promoter,” but a single person does not have “an NPS.” NPS is always a property of a population.

The calculation

NPS = %Promoters − %Detractors

Passives count toward the total respondent base but are excluded from the subtraction — they drag the score down by diluting the promoter percentage without adding to it. Worked example: 100 responses, 50 promoters (9-10), 30 passives (7-8), 20 detractors (0-6).

%Promoters = 50 / 100 = 50%
%Detractors = 20 / 100 = 20%
NPS = 50 − 20 = +30

The 30 passives never appear in the arithmetic but they are why the score is +30 and not +71 (50 promoters out of 70 non-passive responses). This is the single most misread part of NPS.

Relational vs transactional NPS

The same question runs in two distinct programs, and conflating them is a common error.

• Relational NPS (rNPS) is surveyed on a fixed cadence — usually quarterly or twice a year — independent of any specific event. It measures the overall health of the relationship and is the number you put on a board slide or benchmark against peers. Sample the whole base; watch the trend, not the absolute.
• Transactional NPS (tNPS) fires right after a defined event: a support ticket closes, onboarding completes, a feature ships. It measures the quality of that touchpoint. tNPS is operationally actionable — a low tNPS on closed tickets points your support lead at a specific process — where rNPS is strategic.

Do not compare an rNPS number to a tNPS number, and never blend them into one figure. They sample different populations at different moments and answer different questions.

How NPS shows up in real CS work

A CSM treats a detractor response on a relational survey as a renewal-risk signal and opens a save play; a promoter is a candidate for a case study, reference, or expansion conversation. The highest-value part of an NPS program is not the number — it is the verbatim follow-up question (“What’s the primary reason for your score?”) and the closed-loop follow-up, where someone actually contacts detractors within a few days. A program that collects scores and never closes the loop is theater.

Healthy benchmarks are context-dependent, but as rough B2B SaaS bands: above +40 is strong, +20 to +40 is solid, 0 to +20 is mediocre, and negative means more detractors than promoters. Compare yourself to your own trend and to direct competitors, not to a cross-industry headline number — consumer and B2B distributions are nothing alike.

Common pitfalls

• Reading the absolute number instead of the trend. A single +30 means little; +30 trending down from +45 over three quarters is a fire. Always chart the time series.
• Tiny samples treated as signal. With under 100 responses the score swings wildly on a handful of answers. Report the response count alongside every NPS figure and suppress the number below a minimum n (commonly 30-50).
• Survey-timing bias. Surveying only after a win, or only the accounts your CSMs hand-pick, inflates the score. Sample the whole eligible base on a fixed schedule.
• Gaming via incentives. Tying CSM comp directly to NPS produces coached responses (“if you can’t give us a 10, tell us why first”). Measure it; don’t bonus on it.
• No closed loop. Collecting detractor scores without contacting detractors wastes the most actionable data you have. Route every detractor to an owner with an SLA.

Related

• NRR vs GRR — the revenue-retention metrics NPS is often (wrongly) expected to predict
• Delighted and AskNicely — NPS-native survey tools
• Gainsight — folds NPS into a broader customer health score