Framework · 6 min read

Net Promoter Score (NPS) & Feedback Loop Framework

A closed feedback loop with owners and actions.

Fred Reichheld and Bain & Company · View sources ↓

At a glance

Use this when
You need a repeatable way to connect customer sentiment to follow-up action.
What you will work towards
A closed feedback loop with owners and actions.
Bring to the reading
A specific decision from your work and the customer evidence you have so far.

What it is

A framework for using customer feedback, especially NPS, CSAT, and open-ended interviews, to inform product marketing strategy. PMM uses NPS to identify brand advocates (Promoters) and detractors (Detractors), gathers the reasons behind their sentiment, and closes the loop by addressing root causes in product, support, messaging, or pricing. NPS on its own is just a number; the framework's value comes from pairing the score with qualitative follow-up and a defined action for every segment of respondent.

When to use it

  • Quarterly, or after major product releases, to capture sentiment shifts
  • To identify which customer segments have the highest and lowest NPS, and why
  • When NPS is declining, to diagnose whether the cause is a product issue, a support issue, or a messaging or expectation-setting issue
  • To recruit advocates for case studies, testimonials, and referral programmes
  • To identify at-risk accounts (Detractors) before they churn
  • When building the business case for an investment in product or support, since NPS trends give a leading indicator that predates churn and revenue impact

Ownership

At a scaled company with a specialised PMM team, the Head of Product Marketing owns the segmentation, theme analysis, and the resulting messaging or roadmap recommendations, while the Head of Customer Success owns the Detractor and Passive outreach itself, since that requires an existing account relationship PMM doesn't hold. Survey design and cadence decisions typically sit with whichever of the two functions administers the survey tool; in most scaled organisations that's Customer Success. At a solo or founding-PMM stage, the founding PMM owns the entire loop, from sending the survey through to following up with individual Detractors, because there is no separate CS team yet.

How to apply it

  1. Send the NPS survey: Ask one question: "How likely are you to recommend us to a peer, on a scale of 0 to 10?" with an optional follow-up: "Why?" Keep the survey to just these two questions; response rates drop sharply once a survey asks for more than a minute of a customer's time.
  2. Segment the responses: Categorise respondents into Promoters (9 to 10), Passives (7 to 8), and Detractors (0 to 6). Calculate NPS as the percentage of Promoters minus the percentage of Detractors, ignoring Passives in the calculation itself while still reading their comments.
  3. Analyse by segment: Is NPS different across customer segments, industries, company sizes, or use cases? If NPS for Enterprise is 60 but SMB is 20, these segments need fundamentally different strategies, not a single blended response.
  4. Identify themes: Read every piece of open-ended feedback rather than skimming a sample. Are Detractors unhappy about product gaps, pricing, support speed, or unmet expectations set during the sales process? Are Promoters citing specific features, customer success relationships, or ease of use? Tag each comment by theme so the volume of each issue is countable.
  5. Close the loop:
    • Detractors: Have support or customer success reach out individually, understand the issue, and resolve it where possible. If it's a product gap, escalate to the product team with the customer's specific comment attached, not a paraphrase.
    • Passives: Identify what would move them into the Promoter category. Often it's a single missing feature or a single unresolved support ticket, so a targeted outreach can convert a meaningful share of this group.
    • Promoters: Ask for a case study, a testimonial, or a referral. Invite them to a customer advisory board or an early-access beta programme, since Promoters are also your best source of product feedback for what to build next.
  6. Track and trend: Monitor NPS monthly or quarterly, not just as an annual snapshot. Which initiatives, whether product, support, or marketing, correlate with NPS improvements? Keep a simple change log alongside the NPS trend line so cause and effect stay visible over time.
  7. Report NPS alongside a leading business metric: Pair the NPS trend with a metric like renewal rate or expansion revenue when reporting to leadership, since a rising NPS score alone can be a hard sell without a link to commercial outcomes.

Example

A SaaS accounting tool measures Q1 NPS across its base of 12,000 active customers:

  • Overall NPS: 45, which is reasonable but not exceptional for the category.
  • By segment:
    • Mid-market (100 to 500 employees): NPS 60, firmly in Promoter territory.
    • SMB (10 to 99 employees): NPS 15, a clear Detractor-leaning segment.
    • Enterprise (500-plus employees): NPS 50, largely Passive.
  • SMB Detractor feedback: "Too complex, too expensive, support is slow, doesn't work well for freelancers."
  • Mid-market Promoter feedback: "Seamless QuickBooks integration, fast support, perfect for our size."
  • Enterprise Passive feedback: "Does what we need but integrations are limited, and pricing is high for the value at our scale."

Actions taken:

  • SMB strategy: Launch a "Lite" tier that is simplified and lower-priced, partner with a freelancer community for distribution, and add live chat support to address response-time complaints.
  • Enterprise strategy: Develop a public integration roadmap and offer consulting support for custom implementations to move Passives toward Promoter status.
  • Support: Address SMB support speed through additional hiring, better ticket routing, and chatbot automation for common first-response questions.
  • Measurement: Recheck NPS in Q2 specifically for the SMB segment to see whether the Lite tier and support changes move the needle.

By Q2, SMB NPS rose from 15 to 31 following the Lite tier launch and the chat support rollout, while mid-market and Enterprise NPS held steady, confirming the interventions were correctly targeted rather than a general market shift.

Benchmarks: These bands are commonly cited in NPS benchmark reports from Bain & Company (originators of the Net Promoter System) and survey platforms such as Delighted and Retently, though exact cut-offs vary by publisher; treat them as a directional reference, not a fixed standard. For context, typical SaaS NPS bands cited in this literature are roughly: world-class (NPS above 50), good (40 to 50), acceptable (30 to 40), and at-risk (below 30). A mid-market NPS of 60 is world-class by that reading; an SMB score of 15 and an Enterprise score of 50 suggest the two segments need very different strategies rather than a single company-wide initiative. By segment, commonly cited averages are roughly: enterprise software 25 to 35, mid-market SaaS 40 to 50, and SMB or self-service products 30 to 45, so compare your own segment scores against the right band rather than a single blended industry average.

Pitfalls

  • Obsessing over the number. A 45 NPS is useful context, but the insights behind it matter more than the score itself, and teams that fixate on moving the number by a point or two often miss the underlying issue. Recovery: Report NPS alongside its top three qualitative themes every time, so the conversation stays on root causes rather than the number in isolation.
  • No follow-up. If Detractors report that support is slow and the issue isn't fixed, NPS won't improve no matter how many surveys are sent. Recovery: Assign an owner to every major Detractor theme within one week of the survey closing, with a target date for a visible fix.
  • Assuming all Detractors will churn. Some Detractors are highly engaged but critical precisely because they care about the product succeeding. Recovery: Segment Detractors by usage and tenure before writing them off; a heavy, long-tenured user who scores low is often your best source of specific, fixable feedback and can become a Promoter once heard.

How the ideas connect

Choose where to go next

Use alongside

STP Framework →

segment NPS by customer segment to identify which segments need different strategies

Use alongside

Customer Onboarding Maturity Framework →

correlate onboarding experience to NPS outcomes

Use alongside

Feature Adoption Framework →

tie feature adoption rates to NPS improvements

Use alongside

RFM Model →

a behavioural complement to NPS's sentiment signal; cross-reference the two to catch a Champion account with declining sentiment or an At-risk account still scoring well on NPS

Make it useful

Bring it back to your work.

Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.

Check your understanding

Practise applying Net Promoter Score (NPS) & Feedback Loop Framework in five short scenarios.

5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.

Sources

  • Fred Reichheld, "The One Number You Need to Grow", Harvard Business Review (2003). The original article introducing the Net Promoter Score.
  • Bain & Company, Net Promoter System (ongoing resource hub). Bain, Reichheld's firm, co-owns and maintains the Net Promoter System methodology and its implementation guidance.

← All entries in Product Experience & Adoption · Try the category quiz