How is Net Promoter Score calculated?
The survey asks a single question: "How likely are you to recommend this product to a friend or colleague?" Respondents answer on a scale from 0 (not at all likely) to 10 (extremely likely). Most surveys add an open text follow-up asking why the person chose that number.
Every response lands in one of three groups:
- Promoters (9 or 10): loyal users who are likely to renew, expand and refer others.
- Passives (7 or 8): satisfied but unenthusiastic users who could switch to a competitor.
- Detractors (0 to 6): unhappy users who may churn and discourage others from buying.
The score is the share of promoters minus the share of detractors. Passives count toward the total number of responses but do not move the score. The result is a whole number between minus 100 and plus 100, not a percentage. A worked example with sample responses is in how to calculate Net Promoter Score.
Teams run two kinds of surveys. A relational survey goes to the whole customer base on a fixed schedule, often quarterly. A transactional survey fires right after a specific moment, such as finishing onboarding or contacting support.
Why does NPS matter for SaaS teams?
Subscription businesses live or die on renewals. NPS is one of the few signals that arrives before a customer cancels. A detractor rating today is an early warning that can be acted on months before the renewal date, which makes NPS a practical input for reducing churn rate.
The score also captures word of mouth. Promoters bring in new accounts through referrals, reviews and internal advocacy when their company evaluates renewals. Passives and detractors do not. A rising promoter share therefore points to cheaper growth, not just happier users.
Because the question never changes, NPS is comparable across time, product areas and customer segments. Product managers use it to check whether a redesign or pricing change helped or hurt. Customer success leads use per-account scores to prioritize outreach. Product marketers mine the open text answers for the exact language customers use to describe value.
Finally, the follow-up comments are often more useful than the number. They tell you what to fix, what to keep and what to say in the next announcement.
Examples of NPS in practice
Quarterly relational survey. A project management tool emails every active workspace admin once a quarter. The team tracks the trend line, not the single score, and reads every detractor comment in a weekly review.
Post-onboarding transactional survey. A B2B analytics product shows the survey in-app on day 14 of a trial, after the user has connected a data source. Low scores route to a customer success queue for a call before the trial ends.
Survey after a major release. A team ships a redesigned dashboard, announces it in the changelog, and triggers an NPS prompt two weeks later only for users who opened the new dashboard. The score is compared with the pre-release baseline for the same segment.
Segment comparison. A company splits results by plan tier and finds self-serve users score far higher than enterprise users. The gap exposes gaps in enterprise onboarding rather than a product-wide problem.
NPS best practices for product and customer success teams
- Keep the question exact. Changing the wording or the scale breaks comparability with earlier surveys and with anyone else's scores.
- Always ask why. The open text answer is where the action items live. Make it optional but prominent.
- Survey at a meaningful moment. Ask after a user has had time to experience value, not on first login. See when to send an NPS survey for timing patterns.
- Do not oversurvey. Space relational surveys by at least a quarter and suppress prompts for users who answered recently.
- Segment before you judge. Break results down by plan, tenure, role and region. A blended score hides the story.
- Close the loop. Reply to detractors within days and tell promoters how to refer or review. Then announce the fixes that came from feedback.
- Watch the trend and the response rate. A score built on a handful of replies is noise. Track both numbers together.
A fuller list with B2B specifics is in NPS best practices for B2B SaaS.
NPS vs CSAT vs CES, and common mistakes
NPS measures loyalty and intent to recommend over the whole relationship. Customer Satisfaction Score (CSAT) measures how happy someone is with one interaction, such as a support ticket. Customer Effort Score (CES) measures how easy a task was to complete. The three answer different questions and work best together, not as substitutes.
Mistakes to avoid
- Treating the score as the goal. The number is a thermometer, not the patient. Chasing it leads to leading questions and cherry-picked timing.
- Ignoring passives. They do not move the score, but they are the easiest group to convert into promoters.
- Comparing across industries. Benchmarks vary widely by market, sales motion and survey channel. Compare against your own history first.
- Collecting without responding. Silent surveys train users to stop answering. A working customer feedback loop is what makes NPS worth running.
- Surveying only happy users. If prompts appear only after a successful action, detractors are underrepresented and the score is inflated.
How AnnounceKit handles net Promoter Score (NPS)
AnnounceKit includes built-in NPS surveys that run inside the same in-app widget used for product updates, so the loyalty question reaches users where they already read your changelog. Segmentation lets you target the survey by plan, role or behavior and compare scores across groups. Feedback that arrives as a feature request can be captured with voting and synced to Jira, closing the loop from comment to fix to announcement. Pricing is flat per project from $79/month with a 15-day free trial.