6.2 Net Promoter Score (NPS) Survey

An NPS survey UI with eleven explicit numbered buttons (0 through 10) color-coded — 0–6 in red, 7–8 in yellow, 9–10 in green — labeled Detractors, Passives, Promoters

At a Glance

~1–3 weeks~1–3 weeks Writing the survey and analyzing the responses each take well under an hour: AI categorizes the open-ended answers and surfaces common themes in minutes. The main cost is calendar time, because responses have to accumulate. You need enough qualified replies (aim for 30 or more) to trust the score, which means a 5-7 day window in the field plus a reminder, followed by the follow-up calls to unhappy customers. Sending the survey is quick; gathering the responses is the week or two.
$0–$120$0–$120 The survey runs on free tools (a free form builder or the free tier of an online survey tool), and AI handles distribution, follow-up routing, and theme extraction at no extra cost. Dedicated NPS platforms start around $100 per month, but they are optional; you only pay for them if you want their built-in automation and benchmark comparisons instead of assembling your own.

Other names NPS Survey · Net Promoter Score

In Brief

A Net Promoter Score (NPS) survey is a single-question loyalty measurement that asks customers to rate, on a scale from 0 to 10, how likely they are to recommend your product or company to a friend. Respondents are grouped into Promoters (9-10), Passives (7-8), and Detractors (0-6), and the final NPS is calculated by subtracting the percentage of Detractors from the percentage of Promoters. The output is a trackable score you can repeat over time to measure whether satisfaction is improving, plus optional follow-up answers that explain the reasons behind each rating.

Common Use Case

You launched a new feature three months ago and want to know whether your customers are happy enough to tell their friends about it. You need a simple, repeatable way to measure loyalty over time and figure out which customers are your biggest fans and which ones might leave.

Helps Answer

  • How loyal are our customers to this product?
  • Which customers would recommend us to a friend?
  • How do different customer groups feel about our product?
  • Are customers becoming more or less satisfied over time?

Description

A Net Promoter Score (NPS) survey is a single-question loyalty survey that asks people who have used your product one fixed question — how likely they are to recommend it — on a 0-to-10 scale, then converts the answers into one score you can track over time. It is meant to measure loyalty and identify the customers most likely to recommend you to others.

The question wording does not change: ask “How likely is it that you would recommend [company / product] to a friend or colleague?” on a 0-to-10 scale. Sort the answers into three groups — Promoters (9-10, your most enthusiastic customers), Passives (7-8, satisfied but unexcited), and Detractors (0-6, unhappy). The score is the percentage of Promoters minus the percentage of Detractors, which lands somewhere between -100 and +100. Keeping the wording and the brackets fixed is what lets you compare one round against the next.

The number itself is only an anchor; the value comes from the open-ended “why” question you ask alongside it. Those written answers are where the useful themes live — what promoters praise, and what detractors want fixed.

The score tells you about past satisfaction, not future behavior, so pair it with what customers actually do — how much they use the product, who is at risk of leaving, who refers others — rather than reading it in isolation. Teams also tend to game NPS when they tie bonuses to it, chasing the number instead of acting on the feedback; treat the score as a prompt to do the follow-up work, not a target to hit.

How to

Prep

  1. Write down why you’re sending this NPS. “Track quarterly trend,” “find detractors before they churn,” and “benchmark against competitors” require different cadences and follow-up workflows. If you can’t name the decision the score will inform, you’re not ready to field it.

  2. Decide who to survey. Pull the list from your CRM or product analytics, filtering for users past onboarding and active recently enough to have a real opinion. Gather enough qualified responses for the score to be meaningful — sampling noise stays large until you clear roughly 30 replies (see Analysis) — and if your user base is small, survey everyone who qualifies.

  3. Decide cadence. Pick one and commit. Relationship NPS surveys the same cohort every 90 or 180 days and tracks the trend of overall loyalty. Transactional NPS is triggered by a specific event (purchase, support ticket close, feature first-use) and diagnoses which moments produce promoters and which produce detractors. Running both at once without segmentation muddies the signal.

  4. Write the survey. The core question is standardized — don’t change it:

    • “How likely are you to recommend [product] to a friend or colleague?” (0 = Not at all likely, 10 = Extremely likely)
    • Add one open-ended follow-up: “What is the primary reason for your score?”
    • Optionally: “What could we do to improve your experience?”
    • Keep the NPS question first. If you embed NPS in a longer survey, the score is not comparable to standalone NPS.
  5. Plan the close-the-loop workflow before you send. Decide who will contact every detractor and within what window (Bain’s standard is 24–48 hours). If nobody is on the hook to respond, don’t run the survey — collecting feedback you won’t act on burns goodwill with customers most likely to be saved.

Execution

  1. Pick your distribution channel.

    • Email (most common): Short message, 2–3 sentences, subject line like “Quick question about [product].”
    • In-app (higher response rate): Trigger after the user completes a key action. In-app survey tools make this easy.
    • Post-interaction: Send immediately after a support ticket is resolved or a key milestone is reached.
  2. Send and wait. Give respondents 5-7 days to reply. Send one reminder after 3 days. Expect 10-30% of emailed customers to respond (the response rate), and higher for in-app or post-interaction triggers.

  3. Close the loop on detractors within 24–48 hours. A real human contacts every detractor (0–6) to understand their specific issues. AI-powered platforms can automate the routing (detractors to support, passives to re-engagement, promoters to referral programs), but the human conversation with the detractor is non-negotiable.

  4. Don’t argue with the score. When a detractor explains their reason, listen and capture; don’t defend the product. The verbatim is the data — debating it teaches the customer to stop responding.

Analysis

The original NPS calculation, per Reichheld and Bain, subtracts the percentage of Detractors from the percentage of Promoters and ignores Passives:

NPS = % of Promoters – % of Detractors

Before you read too much into the number, remember it is an estimate from a sample, not a census, so it carries a margin of error that shrinks as responses grow. At around 30 responses, sampling noise alone can swing the score by 10 points or more, so treat early readings as directional. A wave-over-wave change is only statistically meaningful when it is larger than that margin — with the small samples typical of early-stage startups, that usually means a move of several points on a few hundred responses, not a one- or two-point wobble on thirty.

A single score doesn’t mean much on its own. Anchor it three ways:

  • Against your prior wave. A 5-point movement across consecutive quarterly waves with the same cohort and same instrument is real signal. Smaller moves sit inside the noise floor.
  • Against industry benchmarks. Published SaaS benchmarks put the median NPS around +36, with the strongest performers well above. Treat these vendor-published numbers as rough reference points, not targets — they are self-reported and inconsistently measured.
  • Against behavior. Compare each NPS bracket against retention, account expansion, and referral activity in your own data. If your promoters do not actually retain or refer at higher rates than your passives, the score is not telling you much about loyalty.

The open-ended “why” is where the useful insight lives. Group the written answers by score bracket and look for repeated language: what promoters praise tells you what is working; what detractors complain about repeatedly tells you what to fix first.

Segment before you act on the headline. A single company-wide number blurs distinct cohorts. If you have meaningful groups — plan tier, acquisition channel, tenure, or region (kept within consistent geographic groupings, per the cultural-scoring bias below) — recompute the score within each. A +20 overall can hide a +50 enterprise cohort and a -10 free-tier cohort, and those two readings point at opposite actions. Only cut where you have enough responses per group (aim for 30 or more) to trust it.

Mine the Passives, not just the Detractors. Closing the loop on detractors is the canonical NPS move, but Passives (7-8) are usually the cheapest points to gain: they already like the product and sit one or two notches below recommending it. Their open-ended answers tell you the specific gap between satisfied and enthusiastic — often a single missing capability or unresolved friction. Investigating why a 7-8 isn’t a 9-10 gives you a clearer, lower-effort path to lifting the score than winning back detractors who may never have been a fit.

AI analysis tools sort hundreds of written answers into themes and surface the most common reason behind each bracket in minutes. Spend your own attention on the outliers and the ambiguous answers the AI flags rather than reading every response one by one. Then have AI line the scores up against behavior — how often customers use the product, who is at risk of leaving, who refers others — to check that your promoters are actually driving growth.

Biases & Tips
  • Selection-timing bias Sending the NPS survey shortly after a positive event (a successful onboarding, a closed support ticket, a new release) inflates the score; sending after a negative event deflates it. Pick a consistent trigger (e.g., 30 days after first paid month) and stick to it so scores are comparable over time.
  • Sample composition bias The customers who do not respond are not represented in the score. The ones most likely to answer are usually your strongest promoters and your most frustrated detractors; passives tend to skip surveys, so the headline score over-represents the two extremes. Track the response rate alongside the score, and check for systematic gaps (for example, 50% response from your enterprise tier but 5% from your free tier).
  • Cultural-scoring bias Cultures vary in their willingness to use the high end of the 0–10 scale. Western European and Japanese respondents systematically rate lower than US respondents on identical experiences; some Asian markets cluster around the middle. Compare segments only within consistent geographic groupings, and use change-over-time within a region rather than absolute scores across regions.
  • Detractor self-selection A vocal minority of detractors will respond, write extensively, and dominate the verbatim analysis even when they represent a small share of the customer base. Weight detractor commentary by their actual proportion of the response set, and contrast against silent-majority behavior (usage, retention) before reorganizing the roadmap around their complaints.
  • Survey-position fatigue bias Placing the NPS item after a long battery of questions lowers scores by 5–10 points because tired respondents rate less generously — making results incomparable to standalone NPS.

Next Steps

  • Run Customer Discovery Interviews with detractors to understand the specific issues behind their low scores.
  • Interview your Passives (7-8) as well — they are the group most easily tipped into promoters. A few Customer Discovery Interviews usually surface the one gap keeping them from a 9 or 10.
  • If distinct cohorts show up, recompute the score per segment and track each on a Dashboard; a healthy segment can hide inside a mediocre average.
  • Use a Product-Market Fit Survey alongside NPS to learn whether detractors lack product-market fit or just have fixable complaints.
  • Track NPS on a regular cadence and watch the trend on a Dashboard to measure how product changes move the score over time.
  • Use the three brackets (promoters, passives, detractors) to tailor how you communicate with each group, and run Customer Discovery Interviews with each to learn what drives their rating.
Learn more

Case Studies

Apple Retail: Closing the loop on detractors

Reichheld and Markey’s The Ultimate Question 2.0 (Harvard Business Review Press, 2011) cite Apple store managers calling detractors within 24 hours, with the closed-loop program credited for an estimated $25M in additional annual sales.

Read more

Charles Schwab: 24-hour detractor follow-up

Bain cites Schwab alongside Apple Retail as leading NPS organizations that contact every customer who submits a negative rating within 24 hours, with frontline staff briefed to resolve issues.

Read more

Taylor & Hart: NPS as the one metric

The London bespoke jeweler tracked separate service and product NPS scores above 80, used the gap to overhaul manufacturing and logistics, and grew to roughly €4.5M annual revenue with a 70% revenue lift.

Read more

Manheim: Operationalized closed loop

The auto-auction operator collected over 10,000 transactional and relationship survey responses in 18 months, identified 110 improvement initiatives, and contacted detractors within 24 hours.

Read more

Groove: SaaS NPS primer

Groove’s customer-support team published a general NPS playbook, a useful small-team reference for setting up a first survey; the survey tool the playbook describes (Delighted) is being discontinued, and the post itself is preserved on the Internet Archive.

Read more

CustomerGauge: SaaS NPS benchmarks

Self-published benchmark sets the SaaS median at +36, with Nutanix (92), Zoom (72), and Google (58) as top performers — a directional anchor for interpreting a first reading.

Read more

Got something to add? Share with the community.