Net Promoter Score for SaaS: The Complete Guide

hero-net-promoter-score

Most SaaS CEOs treat net pro­mot­er score (NPS) as a van­i­ty met­ric — a num­ber they put on a board slide once a quar­ter and for­get about. That’s a mis­take. Used cor­rect­ly, NPS is one of the ear­li­est warn­ing signs that your growth engine is about to seize up. It tells you whether your cus­tomers will renew before your renew­al rate does, whether your prod­uct-led growth will work before your pipeline shows it, and whether the expan­sion rev­enue you’re pro­ject­ing next year is real or fan­ta­sy.

This guide cov­ers what NPS actu­al­ly mea­sures, how to cal­cu­late and bench­mark it for a SaaS busi­ness, the trans­ac­tion­al-ver­sus-rela­tion­al dis­tinc­tion most com­pa­nies get wrong, and the spe­cif­ic oper­a­tional changes that move the num­ber in the right direc­tion. By the end, you’ll know how to use NPS as a lead­ing indi­ca­tor of churn and expan­sion — not just a num­ber your cus­tomer suc­cess team reports.


What Is Net Promoter Score?

The net pro­mot­er score is a sin­gle-ques­tion met­ric that mea­sures how like­ly your cus­tomers are to rec­om­mend your prod­uct or ser­vice to some­one else. It was intro­duced by Fred Reich­held in his 2003 Har­vard Busi­ness Review arti­cle “The One Num­ber You Need to Grow,” and it’s since been adopt­ed by every major SaaS com­pa­ny for a rea­son: it cor­re­lates well with growth, it’s cheap to col­lect, and it’s easy to explain to a board.

The ques­tion itself nev­er changes:

“On a scale of 0 to 10, how like­ly is it that you would rec­om­mend [our company/product/service] to a friend or col­league?”

The answer gets buck­et­ed into three groups:

ScoreCat­e­go­ryWhat It Means
9–10Pro­mot­ersLoy­al cus­tomers who will refer oth­ers and buy more from you over time
7–8Pas­sivesSat­is­fied but unen­thu­si­as­tic — at risk of switch­ing if a com­peti­tor shows up
0–6Detrac­torsUnhap­py cus­tomers like­ly to churn and poten­tial­ly spread neg­a­tive word-of-mouth

Your NPS is the per­cent­age of Pro­mot­ers minus the per­cent­age of Detrac­tors. Pas­sives are ignored in the math — they still mat­ter oper­a­tional­ly, but they don’t move the score.

The score ranges from −100 (every­one is a Detrac­tor) to +100 (every­one is a Pro­mot­er). A pos­i­tive num­ber means you have more fans than crit­ics. Above +50 is excel­lent. Above +70 is rare air — usu­al­ly reserved for Apple, Cost­co, and a small hand­ful of cat­e­go­ry-defin­ing SaaS prod­ucts.


The NPS Formula

The math is sim­ple enough to do in your head.

NPS = % Pro­mot­ers − % Detrac­tors

Note what the for­mu­la does not include: Pas­sives. Some­one who gives you a 7 or 8 con­tributes zero to your score, even though they rep­re­sent rough­ly a third of most SaaS cus­tomer bases. This is inten­tion­al. The for­mu­la is designed to reward you for turn­ing neu­tral cus­tomers into enthu­si­asts and to pun­ish you for hav­ing cus­tomers who active­ly dis­like your prod­uct. Sat­is­fied-but-unen­thu­si­as­tic cus­tomers are the default state — the for­mu­la assumes that’s table stakes.

A Worked Example

Say you sur­vey 200 cus­tomers and get the fol­low­ing dis­tri­b­u­tion:

ScoreRespon­dents% of Total
9–10 (Pro­mot­ers)9045%
7–8 (Pas­sives)7035%
0–6 (Detrac­tors)4020%

NPS = 45% − 20% = +25

That’s a respectable but not great score for a B2B SaaS com­pa­ny. It tells you that a lit­tle under half your cus­tomers would refer you, but a fifth would active­ly warn peo­ple off. The Pas­sives aren’t hurt­ing you, but they’re not help­ing either — and they’re the pool you need to con­vert to Pro­mot­ers to move the num­ber.


What’s a Good NPS for a SaaS Company?

“Good” depends on your cat­e­go­ry, your cus­tomer type, and your pric­ing tier. A self-serve tool sold to indi­vid­ual users will score dif­fer­ent­ly than an enter­prise plat­form with a mul­ti-year con­tract. Here’s a work­ing bench­mark frame­work cal­i­brat­ed to B2B SaaS:

NPS RangeGradeInter­pre­ta­tion
Below 0Strug­glingMore detrac­tors than pro­mot­ers. Some­thing is struc­tural­ly bro­ken — prod­uct fit, onboard­ing, sup­port, or pric­ing
0 to +20Below aver­ageCus­tomer sat­is­fac­tion is mediocre. You have a reten­tion prob­lem wait­ing to hap­pen
+20 to +40Aver­ageTyp­i­cal for mid-mar­ket B2B SaaS. Cus­tomers are sat­is­fied but not enthu­si­as­tic — expan­sion is lim­it­ed
+40 to +60GoodAbove-aver­age loy­al­ty. Cus­tomers are advo­cat­ing for you in their net­works. Expan­sion rev­enue should be healthy
+60 to +80Excel­lentCat­e­go­ry-lead­ing loy­al­ty. Your prod­uct is solv­ing a real prob­lem and cus­tomers know it
Above +80World-classRare. Usu­al­ly only seen in SaaS com­pa­nies with strong net­work effects or switch­ing costs

A few caveats on these bench­marks:

1. B2B SaaS gen­er­al­ly scores high­er than B2C. If you’re sell­ing to busi­ness­es, your cus­tomers have gone through eval­u­a­tion, pro­cure­ment, and an imple­men­ta­tion — they’re already fil­tered for sat­is­fac­tion by the time they’re answer­ing your sur­vey. A B2B SaaS NPS of +40 is rough­ly equiv­a­lent to a B2C NPS of +20.

2. Enter­prise scores dif­fer­ent­ly than SMB. Enter­prise buy­ers tend to be more mea­sured in their sur­vey respons­es. An enter­prise SaaS com­pa­ny with a +35 NPS may be out­per­form­ing an SMB com­peti­tor with a +50.

3. Your seg­ment mat­ters more than your indus­try aver­age. Com­par­ing your NPS to a pub­lished “SaaS aver­age” is most­ly use­less. What mat­ters is how your NPS com­pares to your NPS last quar­ter, and how it com­pares across cus­tomer seg­ments with­in your own base.

The most impor­tant bench­mark is you against you. A trend­ing NPS that’s ris­ing 5 points a quar­ter is a healthy busi­ness. A flat or declin­ing NPS — even at a good absolute lev­el — is a warn­ing sign.


Transactional NPS vs. Relational NPS

There are two dis­tinct ways to mea­sure NPS, and they tell you dif­fer­ent things. Most SaaS com­pa­nies run one and think they’re mea­sur­ing the oth­er, which is why NPS data so often feels dis­con­nect­ed from real­i­ty.

Relational NPS

Rela­tion­al NPS asks cus­tomers about their over­all rela­tion­ship with your com­pa­ny. It’s sent on a reg­u­lar cadence — quar­ter­ly or annu­al­ly — and it sur­veys your full cus­tomer base regard­less of recent activ­i­ty.

The ques­tion might be framed as: “Based on your over­all expe­ri­ence with [com­pa­ny], how like­ly are you to rec­om­mend us to a col­league?”

Rela­tion­al NPS is your strate­gic met­ric. It tells you whether you have a healthy cus­tomer base over­all. It’s what you report to the board. It’s what you track over time to see whether your prod­uct and cus­tomer expe­ri­ence invest­ments are pay­ing off. Move­ments here are slow — you typ­i­cal­ly see a 3 to 10 point change over a quar­ter, not a 30-point swing.

Transactional NPS

Trans­ac­tion­al NPS is sent right after a spe­cif­ic inter­ac­tion: a sup­port tick­et clos­es, an onboard­ing is com­plet­ed, a renew­al hap­pens, a fea­ture ships. The ques­tion gets framed around that touch­point: “Based on your recent expe­ri­ence with [event], how like­ly are you to rec­om­mend us?”

Trans­ac­tion­al NPS is your oper­a­tional met­ric. It tells you whether a spe­cif­ic process is work­ing. If your onboard­ing trans­ac­tion­al NPS is +15 and your sup­port trans­ac­tion­al NPS is +65, you know exact­ly where to invest: onboard­ing is hurt­ing you, sup­port is help­ing you.

Which One Should You Run?

Both, but sep­a­rate­ly. The most com­mon mis­take is run­ning only rela­tion­al NPS and then being unable to explain why it’s mov­ing. Rela­tion­al NPS tells you what’s hap­pen­ing. Trans­ac­tion­al NPS tells you why.

In prac­tice, a well-instru­ment­ed SaaS com­pa­ny runs:

  • One rela­tion­al NPS sur­vey per quar­ter, sent to the full cus­tomer base
  • Two to four trans­ac­tion­al NPS sur­veys, trig­gered on the touch­points that mat­ter most to reten­tion — typ­i­cal­ly onboard­ing com­ple­tion, first major sup­port inter­ac­tion, and renew­al

Don’t send more than that. NPS sur­vey fatigue is real, and every addi­tion­al sur­vey depress­es response rates on the ones you actu­al­ly need.


How NPS Connects to the Metrics That Matter

The ques­tion boards and investors actu­al­ly want answered is “will these cus­tomers stay, expand, and refer oth­ers?” NPS is a lead­ing indi­ca­tor for all three — but only if you know how to con­nect it to the down­stream met­rics.

NPS and Churn

Detrac­tors churn at rough­ly 2–4x the rate of Pro­mot­ers. This is the sin­gle most impor­tant cor­re­la­tion in NPS data. If 20% of your cus­tomers are Detrac­tors and your typ­i­cal churn rate is 8% annu­al­ly, those Detrac­tors are like­ly churn­ing at 16–30% while your Pro­mot­ers churn at 3–5%.

What this means prac­ti­cal­ly: your NPS today is a pre­view of your churn rate six to twelve months from now. If your Detrac­tor per­cent­age climbs from 15% to 25% this quar­ter, expect a gross rev­enue churn increase over the next two to three quar­ters. The lag gives you time to inter­vene — if you’re pay­ing atten­tion.

NPS and Net Revenue Retention

Pro­mot­ers don’t just stay — they expand. In most SaaS com­pa­nies, expan­sion rev­enue from exist­ing cus­tomers (seat addi­tions, tier upgrades, addi­tion­al mod­ules) is con­cen­trat­ed in the Pro­mot­er seg­ment. Pas­sives expand occa­sion­al­ly; Detrac­tors almost nev­er expand.

If you’re try­ing to fore­cast net rev­enue reten­tion (NRR) for next year, the dis­tri­b­u­tion of your cur­rent NPS respon­dents mat­ters more than your his­tor­i­cal expan­sion rate. A cus­tomer base that’s 50% Pro­mot­ers will gen­er­ate mate­ri­al­ly more expan­sion than a base that’s 30% Pro­mot­ers, even if both cur­rent­ly have the same NRR.

NPS and Customer Acquisition Cost Payback

Here’s a con­nec­tion most founders miss: high NPS reduces your effec­tive cus­tomer acqui­si­tion cost. Pro­mot­ers refer oth­er cus­tomers. Those referred cus­tomers close at high­er rates, cost less to acquire, and have high­er LTVs. A com­pa­ny with a +50 NPS is gen­er­at­ing free pipeline that does­n’t show up in the mar­ket­ing bud­get.

This is why B2B SaaS com­pa­nies with strong cus­tomer life­time val­ue num­bers often have a struc­tur­al NPS advan­tage — the refer­ral loop sub­si­dizes their CAC. If your NPS is below +20, you’re pay­ing full freight for every cus­tomer you acquire. If it’s above +50, a mean­ing­ful per­cent­age of your growth is free.

NPS and Ideal Customer Profile

NPS also tells you whether you’re sell­ing to the right cus­tomers. Seg­ment your NPS by cus­tomer size, indus­try, use case, and acqui­si­tion chan­nel. If one seg­ment scores +60 and anoth­er scores −10, you don’t have an NPS prob­lem — you have an ide­al cus­tomer pro­file prob­lem. Stop sell­ing to the seg­ment that’s giv­ing you Detrac­tors. They’re cost­ing you more in churn and sup­port than they’re gen­er­at­ing in rev­enue.


Why Most SaaS Companies Measure NPS Wrong

Most NPS pro­grams are use­less. Not because NPS is flawed as a met­ric, but because of how com­pa­nies run them. Here are the three mis­takes that turn NPS from a lead­ing indi­ca­tor into a mean­ing­less num­ber on a slide.

Mistake #1: Surveying Only the Happy Customers

This sounds obvi­ous, but it hap­pens con­stant­ly. Com­pa­nies send NPS sur­veys to the cus­tomers their cus­tomer suc­cess team knows well — the ones who are engaged, respon­sive, and already sat­is­fied. The silent, dis­en­gaged cus­tomers who are most like­ly to churn nev­er get the email.

The result: an NPS that looks great while churn climbs. Your score is mea­sur­ing the wrong pop­u­la­tion.

The fix: Send rela­tion­al NPS to your entire cus­tomer base, not just active users or cus­tomer-suc­cess-man­aged accounts. If your response rate drops, accept that — low response rate from dis­en­gaged cus­tomers is itself a sig­nal, and it’s bet­ter than a high response rate from a fil­tered sam­ple.

Mistake #2: Not Segmenting the Score

A blend­ed +30 NPS tells you almost noth­ing. It could mean:

  • All your cus­tomers are mod­er­ate­ly hap­py
  • Half your cus­tomers love you (+70) and half hate you (−10)
  • Your enter­prise seg­ment is +60, your SMB seg­ment is 0, and they rough­ly can­cel out

These are three com­plete­ly dif­fer­ent busi­ness­es with iden­ti­cal scores. Only one of them is healthy.

The fix: Break your NPS down by every seg­ment that mat­ters — pric­ing tier, com­pa­ny size, indus­try, acqui­si­tion chan­nel, tenure. Look at the dis­tri­b­u­tion, not just the mean. The seg­ments that score low­est are either bad-fit cus­tomers you should stop acquir­ing, or prof­itable cus­tomers you’re under­serv­ing. Either way, the aggre­gate num­ber is hid­ing the real insight.

Mistake #3: Treating NPS as a Number, Not a Conversation

The score is the cheap­est part of NPS. The real val­ue is in the fol­low-up com­ment — the “why did you give us that score?” field. Most com­pa­nies ignore those com­ments or del­e­gate them to a junior cus­tomer suc­cess ana­lyst. That’s back­wards.

The ver­ba­tim feed­back from a Detrac­tor is worth more than any fea­ture request, any sup­port tick­et, any churn-risk report. It’s your cus­tomer telling you — unprompt­ed, in their own words — exact­ly what will make them leave. Ignor­ing that data is a choice.

The fix: Require every NPS response (espe­cial­ly Detrac­tors and 9‑score Pro­mot­ers) to be reviewed by some­one with author­i­ty to act on it. At a 100-cus­tomer B2B SaaS com­pa­ny, that’s prob­a­bly the founder. At a 10,000-customer SaaS com­pa­ny, it’s a trained cus­tomer expe­ri­ence team with esca­la­tion paths to prod­uct and engi­neer­ing.


Factors That Influence NPS Scores

Before you react to a move­ment in your NPS, under­stand what dri­ves the score. Not every dip means your prod­uct is worse — some are arti­facts of the mea­sure­ment itself or exter­nal fac­tors beyond your con­trol.

Survey Channel

Email sur­veys, in-app sur­veys, and phone sur­veys all pro­duce dif­fer­ent NPS dis­tri­b­u­tions. In-app sur­veys (trig­gered inside the prod­uct) tend to score high­er because the respon­dent is active­ly using the prod­uct when they’re asked. Email sur­veys sent to dor­mant users cap­ture more Detrac­tors. Phone sur­veys almost always score high­est because of social desir­abil­i­ty bias — peo­ple are more polite to a human than to a form.

None of these are “right.” Pick one chan­nel and use it con­sis­tent­ly. Com­par­ing an in-app score to an email score is com­par­ing two dif­fer­ent met­rics.

Timing Relative to the Renewal Cycle

If you sur­vey cus­tomers three weeks before renew­al, they’ll score dif­fer­ent­ly than three months before renew­al. Cus­tomers near their renew­al are more like­ly to think crit­i­cal­ly; cus­tomers who just renewed or just onboard­ed are more like­ly to be enthu­si­as­tic. Ran­dom­ize the tim­ing or hold it con­stant — don’t let it drift.

External Events

Eco­nom­ic down­turns, ven­dor con­sol­i­da­tion waves, and indus­try dis­rup­tion affect NPS in ways that have noth­ing to do with your prod­uct. A cus­tomer cut­ting their SaaS spend 30% across the board will score low­er even if your prod­uct is their favorite one. Note these fac­tors in your quar­ter­ly NPS review so you don’t over­re­act to them.

Customer Tenure

Cus­tomers in their first 90 days score dif­fer­ent­ly than cus­tomers in year three. New cus­tomers are either euphor­ic (just solved their prob­lem) or frus­trat­ed (still onboard­ing). Long-tenure cus­tomers are more mea­sured — they’ve seen what your prod­uct can and can’t do.

Seg­ment your NPS by tenure cohort. A dip in 90-day NPS tells you some­thing about onboard­ing. A dip in 2‑year NPS tells you some­thing about long-term val­ue deliv­ery. They’re dif­fer­ent prob­lems with dif­fer­ent fix­es.

Competitive Pressure

When a well-fund­ed com­peti­tor launch­es a cred­i­ble alter­na­tive, your NPS drops — even if your prod­uct has­n’t changed. Cus­tomers who were hap­py with you are sud­den­ly aware of alter­na­tives, and their implic­it com­par­i­son shifts. If you see an NPS drop coin­cid­ing with a com­peti­tor’s Series B announce­ment, that’s the sig­nal — not a prod­uct issue.


Turning Detractors into Promoters: A Practical Playbook

Most NPS pro­grams end with the score. The ones that dri­ve rev­enue don’t. Here’s the oper­a­tional work­flow for turn­ing NPS data into cus­tomer out­comes.

Step 1: Close the Loop on Every Detractor Within 48 Hours

The research is clear: Detrac­tors who hear back from the com­pa­ny with­in 48 hours of respond­ing are more than twice as like­ly to still be cus­tomers a year lat­er. The spe­cif­ic action you take mat­ters less than the fact that you took action. Silence after a bad NPS response is the worst pos­si­ble out­come.

Set up an auto­mat­ed alert that routes every Detrac­tor response to a named human — not a sup­port queue. That human’s job is to reach out with­in two busi­ness days, not to solve the prob­lem on the call, but to acknowl­edge the feed­back and com­mit to a fol­low-up.

Step 2: Categorize Feedback Into Root Causes

Not every Detrac­tor is say­ing the same thing. In most SaaS com­pa­nies, Detrac­tor feed­back falls into four buck­ets:

Cat­e­go­ryTyp­i­cal Feed­backWho Owns the Fix
Prod­uct gap“I need X fea­ture” or “This does­n’t han­dle Y use case”Prod­uct
Onboard­ing fail­ure“I could­n’t fig­ure out how to use it” or “No one showed me how”Cus­tomer Suc­cess
Sup­port qual­i­ty“Your sup­port was slow/unhelpful”Sup­port lead­er­ship
Pricing/value mis­match“It’s too expen­sive for what it does”Prod­uct mar­ket­ing + Sales

Tag every Detrac­tor response with a cat­e­go­ry. This turns qual­i­ta­tive feed­back into a pri­or­i­ti­za­tion queue. If 60% of your Detrac­tors are com­plain­ing about a sin­gle miss­ing fea­ture, that fea­ture becomes your high­est-ROI prod­uct invest­ment — you have direct evi­dence it’s dri­ving churn.

Step 3: Build a Systematic Promoter Program

Pas­sives and Pro­mot­ers get less atten­tion than Detrac­tors, but the rev­enue lever­age is with them. A Pro­mot­er who’s active­ly refer­ring you is worth 3–5x their base con­tract val­ue over their life­time because of the pipeline they gen­er­ate.

The play­book:

  1. Iden­ti­fy your Pro­mot­ers quar­ter­ly — pull the 9‑and-10 respon­ders from your rela­tion­al NPS.
  2. Reach out per­son­al­ly — not with a mar­ket­ing email, but with a human mes­sage thank­ing them and ask­ing what specif­i­cal­ly made them rate you high­ly.
  3. Make it easy for them to refer — give them a short, copy-paste­able descrip­tion of your prod­uct, a refer­ral incen­tive if you offer one, and a direct ask for intro­duc­tions.
  4. Cre­ate case study con­tent from their feed­back — a 9‑score cus­tomer’s answer to “why that score?” is usu­al­ly bet­ter mar­ket­ing copy than any­thing your team could write.

Most SaaS com­pa­nies spend 90% of their NPS pro­gram effort on Detrac­tors and 10% on Pro­mot­ers. Flip that ratio and your growth rate will thank you.


Designing an NPS Survey That Actually Works

Most NPS sur­vey designs are over-engi­neered. Here’s what you actu­al­ly need.

The Core Survey (Two Questions)

Ques­tion 1: On a scale of 0 to 10, how like­ly are you to rec­om­mend [company/product] to a col­league?

Ques­tion 2: What’s the pri­ma­ry rea­son you gave that score?

That’s it. Every addi­tion­al ques­tion cuts your response rate. Resist the temp­ta­tion to add demo­graph­ic ques­tions, fea­ture pref­er­ence rank­ings, or NPS-plus-CSAT com­bi­na­tions. Put those in a sep­a­rate sur­vey if you need them.

When to Send It

  • Rela­tion­al: Once per quar­ter, on a con­sis­tent day of the month. Stag­ger across cus­tomer seg­ments so you’re not spik­ing your own sup­port queue.
  • Trans­ac­tion­al: 48 to 72 hours after the trig­ger event. Imme­di­ate sends bias toward short-term emo­tion; week-lat­er sends lose the con­text.

How to Send It

  • In-app if you have the usage vol­ume — high­est response rate, low­est bias.
  • Email if in-app isn’t an option — stan­dard, easy to instru­ment, works for dor­mant users.
  • Nev­er SMS or phone for B2B SaaS unless you have a spe­cif­ic rea­son — response rates are high but the sam­ple is bad­ly biased toward high­ly engaged cus­tomers.

What Channels to Avoid

Pop-up sur­veys dur­ing crit­i­cal work­flows (check­out, data entry, sup­port inter­ac­tions) are the sin­gle biggest source of arti­fi­cial­ly low NPS. You’re mea­sur­ing the user’s mood about the inter­rup­tion, not about your prod­uct. If you’re run­ning in-app NPS, make sure the trig­ger log­ic excludes active-task states.

Template

You don’t need to write the sur­vey from scratch. A basic Sur­vey­Mon­key NPS tem­plate han­dles the stan­dard for­mat. What mat­ters is how you oper­a­tional­ize the data after­ward, not the sur­vey tool itself.


NPS Frequently Asked Questions

How often should I survey my customers?

For rela­tion­al NPS, once per quar­ter is the sweet spot. More fre­quent and you get sur­vey fatigue; less fre­quent and you miss short-term sig­nal. For trans­ac­tion­al NPS, send it after every instance of the trig­ger­ing event, but don’t trig­ger the same cus­tomer more than once per month.

Is a low response rate a problem?

A response rate of 15–25% is nor­mal for email NPS sur­veys. Below 10% is a red flag — your sam­ple is prob­a­bly biased. Above 40% usu­al­ly means you’re only sur­vey­ing high­ly engaged cus­tomers, which is its own bias. The fix for low response rate isn’t more reminders; it’s short­er sur­veys and bet­ter tim­ing.

Should I include a reward for completing the survey?

No. Rewards dis­tort the response — peo­ple who fill out sur­veys for a gift card are sys­tem­at­i­cal­ly dif­fer­ent from peo­ple who fill them out to give feed­back. The score you get back won’t reflect your actu­al cus­tomer base. Keep it unin­cen­tivized.

Can NPS be manipulated by the sales team?

Yes, and it often is. If com­pen­sa­tion is tied to NPS, sales and cus­tomer suc­cess teams will selec­tive­ly sur­vey hap­py cus­tomers or coach clients on how to respond. The fix: sur­vey the full cus­tomer base auto­mat­i­cal­ly, keep the data owned by an inde­pen­dent team, and tie com­pen­sa­tion to gross reten­tion or NRR rather than NPS direct­ly.

How does NPS compare to CSAT and CES?

All three mea­sure dif­fer­ent things. Cus­tomer sat­is­fac­tion (CSAT) is best for trans­ac­tion­al mea­sure­ment of sin­gle inter­ac­tions. Cus­tomer effort score (CES) is best for mea­sur­ing whether your prod­uct is easy to use. NPS is best for mea­sur­ing over­all loy­al­ty and like­li­hood to rec­om­mend. Most SaaS com­pa­nies should run NPS plus one trans­ac­tion­al met­ric (CSAT for sup­port, CES for onboard­ing) — not all three in par­al­lel.

What’s the most important NPS number for a SaaS CEO to track?

Seg­ment-lev­el NPS trend, not aggre­gate score. A ris­ing NPS in your high­est-LTV seg­ment is more impor­tant than a ris­ing aggre­gate, because it direct­ly pre­dicts expan­sion rev­enue. A declin­ing NPS in your low­est-LTV seg­ment is almost a sig­nal to stop sell­ing to that seg­ment, not to fix the prod­uct.


The Verdict

Net pro­mot­er score is one of the most mis­used met­rics in SaaS. The com­pa­nies that get val­ue from it treat it as a lead­ing indi­ca­tor of churn and expan­sion, seg­ment it by cus­tomer type and tenure, act on the ver­ba­tim com­ments, and close the loop with every Detrac­tor with­in 48 hours. The com­pa­nies that don’t get val­ue from it run one rela­tion­al sur­vey a quar­ter, report the aggre­gate num­ber on a slide, and move on.

The dif­fer­ence between those two out­comes isn’t the met­ric — it’s the oper­a­tional dis­ci­pline around it. If your cur­rent NPS pro­gram is the sec­ond kind, you don’t have an NPS prob­lem. You have a cus­tomer expe­ri­ence infra­struc­ture prob­lem, and NPS is just the symp­tom. Fix the infra­struc­ture, and the score will fol­low.

Start with the three things that have the high­est lever­age: sur­vey your full cus­tomer base (not just the hap­py ones), seg­ment the score by cus­tomer type, and set up an auto­mat­ed 48-hour loop for every Detrac­tor. Do those three things well, and you’ll get more out of NPS than 90% of your SaaS peers — and you’ll see it in your net rev­enue reten­tion, your churn rate, and your CAC pay­back peri­od with­in two quar­ters.

Facebooktwitterlinkedinmail
author avatar
Vic­tor Cheng
Author of Extreme Rev­enue Growth, Exec­u­tive coach, inde­pen­dent board mem­ber, and investor in SaaS com­pa­nies.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top