Back to Tools
GUIDEMay 2026

How to Calculate Net Promoter Score β€” Step-by-Step

TC
Trace Cohen
3x founder, 65+ investments, building Value Add VC

NPS is the single most predictive customer metric for long-term retention β€” and most founders measure it wrong. Here's how to calculate it correctly, benchmark it honestly, and actually use it to move the business forward.

My recommended stack: SurveyMonkey for collection + Amplitude for analysis

Why NPS Is the Metric That Matters Most

Net Promoter Score was invented by Bain in 2003 and is now used by over two-thirds of Fortune 500 companies. For early-stage startups, it's the fastest proxy for product-market fit you can get from your own customers. A rising NPS predicts retention. A falling NPS predicts churn β€” often before it shows up in revenue. If you're not measuring it, you're flying blind.

1

Understand the NPS Formula

NPS is deceptively simple. You ask one question: β€œOn a scale of 0–10, how likely are you to recommend us to a friend or colleague?” Then you segment responses into three buckets and run the math.

9–10

Promoters

Loyal enthusiasts who will refer others and keep buying. These are your best growth lever.

7–8

Passives

Satisfied but unenthusiastic. They won't churn immediately, but they'll leave if a competitor makes a better offer. Not counted in the NPS formula.

0–6

Detractors

Unhappy customers who can damage your brand through negative word-of-mouth. Churn risk is high. Address these first.

The Formula

NPS = % Promoters βˆ’ % Detractors

Score ranges from βˆ’100 (everyone is a Detractor) to +100 (everyone is a Promoter)

Example:

You survey 100 customers. 55 score 9–10 (Promoters), 30 score 7–8 (Passives), 15 score 0–6 (Detractors).
NPS = 55% βˆ’ 15% = +40

Key point

Passives are intentionally excluded from the NPS calculation. They improve your absolute percentage numbers but don't reflect true advocacy. This is by design β€” NPS only cares about your extremes.

2

Design Your NPS Survey

How you ask is as important as what you ask. The wrong survey design produces garbage data β€” responses that don't reflect true customer sentiment, collected at the wrong moment, from the wrong segment.

The two-question structure

Q1

The NPS question (required)

β€œOn a scale of 0 to 10, how likely are you to recommend [Company] to a friend or colleague?”

Use exactly this wording. Don't paraphrase it β€” the benchmark data assumes this phrasing.

Q2

The follow-up (required)

β€œWhat's the main reason for your score?”

Open-ended, optional for respondents. This is where the real insight lives β€” don't skip it.

When to send it

Good timing

  • +30 days after signup (onboarding NPS)
  • +After a key milestone (first value moment)
  • +60–90 days after renewal
  • +Quarterly for your active base

Bad timing

  • βˆ’Same day as signup (no experience yet)
  • βˆ’Right after a support ticket
  • βˆ’During a known outage or incident
  • βˆ’More than twice per year to the same user
3

Choose Your Survey Tool

You need a tool that handles NPS templates, automated distribution, response segmentation, and trend tracking over time. Don't use a Google Form β€” you can't segment, automate, or track trends without a lot of manual work.

SurveyMonkey β€” Best for NPS

  • +Built-in NPS question type with proper 0–10 scale
  • +Automated NPS score calculation and dashboards
  • +Email distribution with follow-up reminders
  • +Segment responses by custom fields
  • +Trend tracking across multiple survey waves
  • +Industry NPS benchmarks built in
See our SurveyMonkey review

Amplitude β€” For Product NPS

  • +In-app NPS surveys triggered by behavior
  • +Correlate NPS scores with product usage events
  • +Segment NPS by feature adoption cohorts
  • +Identify which features drive Promoters vs Detractors
  • +Retention analysis by NPS segment
See our Amplitude review

Early-stage shortcut

If you have under 100 customers, SurveyMonkey via email is all you need. Once you have 500+ active users, add Amplitude to get in-product NPS correlated with feature usage β€” that's where the real insight lives.

4

Collect Responses at Scale

Statistical significance matters. An NPS of +40 from 10 responses is meaningless. The same score from 200 responses starts to tell you something. Here's what you need for reliable data.

Minimum response requirements

50+
Minimum
Directional signal only
100+
Actionable
Enough to segment by tier
200+
Reliable
Track trends quarterly
500+
Statistically robust
Segment by cohort safely

Segmentation that actually matters

Your overall NPS is a blended average that hides the real signal. Always break it down by at least three dimensions:

  • Plan tier: Enterprise customers almost always score higher than SMB. If your enterprise NPS is +60 and SMB is +10, you have very different problems to solve.
  • Customer tenure: 0–90 day customers vs 12+ month customers reveal onboarding problems vs long-term value delivery gaps.
  • Feature adoption: Customers who use your core feature daily should score dramatically higher. If they don't, your value prop is broken.
5

Analyze and Benchmark Your Score

A score of +35 could be excellent or terrible depending on your industry. Context is everything. Here are the benchmarks I use when advising portfolio companies.

IndustryPoorAverageGoodExcellent
B2B SaaS< 1010–3030–5050+
E-commerce< 2020–4040–6060+
Financial Services< 00–2525–4545+
Healthcare Tech< 1515–3535–5555+
Consumer Apps< 2525–4545–6565+
Marketplace< 1010–3030–5050+

What drives Detractor scores

Read every Detractor response. Categorize the open-ended answers into themes. The most common root causes I see across startups:

  • Onboarding friction (40% of Detractors): They never got to value. Fix onboarding before anything else.
  • Missing features (30%): They use the product but it doesn't solve their full workflow. Roadmap signal.
  • Bugs or reliability (20%): They've been burned. Follow up fast β€” this group is salvageable if you show urgency.
  • Pricing perception (10%): They don't see the ROI relative to cost. Packaging or communication problem, not product.
6

Close the Loop and Move the Number

Running NPS and doing nothing with the results is worse than not running it at all. It signals to customers that you asked for their feedback and ignored it. Closing the loop is what separates companies that use NPS as a vanity metric from those that use it as a growth tool.

Detractors (0–6)

  • β†’Follow up within 48 hours
  • β†’Founder or CSM call (not a form email)
  • β†’Diagnose the root cause
  • β†’Share a specific fix timeline
  • β†’Re-survey in 60 days

Passives (7–8)

  • β†’Invite to product advisory group
  • β†’Share your roadmap and get input
  • β†’Early access to new features
  • β†’Ask what would make them a 9
  • β†’Track usage β€” are they getting stickier?

Promoters (9–10)

  • β†’Ask for a G2/Capterra review
  • β†’Invite for a case study or testimonial
  • β†’Launch a referral program
  • β†’Ask for warm intros to their network
  • β†’Invite to your customer community

The cadence that works

Run NPS quarterly to your entire active base. Run milestone NPS (30-day, 90-day post-signup) continuously. Review Detractor responses weekly in your product meeting. Track your NPS trend monthly. It should go up every quarter β€” if it's flat, something is wrong.

The Single Most Important Takeaway

NPS only matters if you close the loop. Sending a survey and not following up with Detractors tells your unhappiest customers that you asked for their opinion and don't care about it β€” which guarantees they churn. The founders who get the most out of NPS are the ones who treat every Detractor response as a personal customer support ticket that requires a human response within 48 hours.

5 NPS Mistakes That Kill the Signal

1

Surveying too frequently

Hitting customers with NPS every month creates survey fatigue and artificially suppresses scores. Quarterly is the maximum for your established base. More frequent than that and you're measuring survey annoyance, not product sentiment.

2

Reporting the overall number without segments

An NPS of +32 company-wide might hide an enterprise NPS of +65 and an SMB NPS of +5. The blended score tells you nothing actionable. Always break it down by cohort before presenting to your board or team.

3

Skipping the open-ended follow-up

The number tells you the score. The text tells you the reason. Without the open-ended question, you know you have a problem but not what to fix. Never run NPS without the β€œwhat's the main reason for your score?” follow-up.

4

Surveying only satisfied customers

If you send NPS only to customers who logged in this week, you're sampling your most engaged users. Your NPS looks great but misses the customers who are quietly churning. Include customers who haven't logged in for 30+ days β€” that's where the real signal is.

5

Not tracking it as a trend

A single NPS reading is a snapshot. What matters is whether it's trending up or down quarter over quarter. A +45 that fell from +60 is a red flag. A +25 that climbed from +5 is a strong signal you're making the right changes. Track the trend, not just the current score.

πŸ“Š

Ready to start measuring NPS?

Set up your first NPS survey in 15 minutes with SurveyMonkey, then layer in Amplitude to correlate scores with product behavior.

Some links help support Value Add VC at no extra cost to you.