Net Promoter Score

What is Net Promoter Score?

Net Promoter Score (NPS) is a survey metric that asks customers how likely they are to recommend a company to a friend or colleague on a 0 to 10 scale, then nets the percentage of detractors against the percentage of promoters to produce a single number. It's one of the oldest and most widely adopted instruments for gathering user feedback at scale.

The method is commonly attributed to Fred Reichheld, who introduced it in the Harvard Business Review article "The One Number You Need to Grow" (December 2003). Reichheld's argument, drawn from Enterprise Rent-A-Car's practice of tracking a single recommend question across its branches, was blunt: "If growth is what you're after, you won't learn much from complex measurements of customer satisfaction or retention. You simply need to know what your customers tell their friends about you."

The scoring mechanics come straight from that article. Respondents rate the recommend question from 0 to 10. Reichheld grouped 9-10 raters as "promoters," 7-8 as "passively satisfied," and 0-6 as "detractors," then defined the net-promoter score as the percentage of promoters minus the percentage of detractors. Bain & Company later built a consulting practice, the Net Promoter System, around the same scale and categories, and Net Promoter, NPS, and Net Promoter Score are now registered trademarks jointly held by Bain, NICE Systems, and Reichheld himself, so using the name commercially requires a license even though the underlying question is free to ask.

Why it matters for product-market fit

NPS is a Listen-stage instrument. It's cheap to run and gives a whole company one simple trend line to watch. Inside Produck's Listen, Diagnose, Decide, Ship loop, that's exactly its job: a lightweight signal that tells you something changed, not a substitute for the diagnosis that comes next.

The trap most teams fall into is treating the score as the finish line. A dropping NPS tells you sentiment is moving in the wrong direction. It doesn't tell you why. That's a Diagnose problem, and it's the gap we wrote about in the PMF stack being broken: most teams have plenty of Listen tools and little that turns a number into a shipped fix.

At Produck, we treat an NPS dip or spike as a trigger to go read the actual comments behind it and tie the response to a customer's retention and usage data. From there it routes into a Decide-stage prioritization call. Used that way, NPS earns its place next to sharper instruments like the Sean Ellis test instead of standing in for them.

When it works, and when it doesn't

It works when:

1. You already have a baseline and are watching the trend over time rather than a single snapshot.
2. You pair every score with the free-text comment box and actually read the comments.

It falls short when:

1. You treat the number as a KPI to defend instead of a prompt to investigate.
2. You survey once a year and expect it to catch a fast-moving problem.
3. You have no process downstream to turn a falling score into a shipped change.
4. You benchmark against other industries instead of your own history.

How to apply it

1. Send the single recommend question ("How likely are you to recommend us to a friend or colleague?") on a 0-10 scale, with an open text field right below it.
2. Trigger it after a real moment of value, like a renewal or a completed onboarding, rather than on a fixed calendar schedule alone.
3. Score every response into promoter, passive, or detractor and calculate the net score, but store the raw comments alongside it.
4. Route detractor comments to whoever owns the affected feature within the same week, while the context is fresh.
5. Track the score by cohort, such as plan tier or signup month, instead of one company-wide average, since a blended number hides where the pain actually is.
6. Revisit the trend monthly and treat any sharp move as a cue to open a Diagnose session, not just a slide in a board deck.

Net Promoter Score vs Sean Ellis test

NPS asks whether a customer would recommend you and produces a score from -100 to 100. The Sean Ellis test asks how disappointed a customer would be if they could no longer use your product, with responses bucketed into very disappointed, somewhat disappointed, and not disappointed. See the Sean Ellis test entry for the specific "very disappointed" threshold it uses as a product-market-fit signal.

The two measure different things. NPS is a loyalty and advocacy gauge that works well once you have an established customer base and want to track sentiment over time. The Sean Ellis test is aimed squarely at answering whether you have PMF at all, which makes it the sharper tool earlier in a product's life, while NPS becomes more useful as a longitudinal health check once fit is established.