Is an NPS Target a Fair KPI for a CSM?

It measures the balance between advocates and critics among the people who answered a single question about likelihood to recommend. Passives are excluded from the arithmetic entirely, which is why the number moves further than sentiment does.

In the first half of 2026, a benchmark set built from 3,248 in-app responses across 13 SaaS products broke down as 56% promoters, 13% passives and 31% detractors, which produces the +30 median discussed below. Note the shape: nearly a third of respondents sit in the detractor band, and the band includes every 6.

Median in-app NPS was +30 in the first half of 2026, with a wide spread either side. Use the percentile column rather than the median when someone proposes a target, because the distance between typical and top quartile is fourteen points.

The sample skews to small and mid-sized SaaS and to in-app surveys rather than emailed relationship surveys, which usually score differently. Full range across the products measured was minus 12 to plus 64, so a target of +50 is asking for the top of the market rather than a healthy account base.

Because of the response count, not the customers. NPS is a difference of percentages, so with a small denominator each response is worth a large number of points, and account-level surveys almost always have small denominators.

At a 4.3% median response rate, getting 25 responses from one account means surveying roughly 580 users of that account. Most B2B accounts do not have 580 users, which is the arithmetic reason account-level NPS targets misbehave.

When it is used for the thing it measures, on a sample large enough to be stable, and where the CSM can influence the answer. Three of those conditions fail more often than they hold.

Raise the response rate first, then work the comments. Anything that changes who gets asked changes the score without changing the customer, and everyone senior to you has seen that trick.

1. 1

   Widen who is asked

   Survey the users, not only the admin contact. A score built on one champion per account measures your relationship with one person, which is the thing most likely to change without warning.

2. 2

   Ask in the product, at a moment of completion

   In-app surveys after a task finishes get answered more often than emails, and the answer is about something specific rather than about a vague feeling.

3. 3

   Read every comment, because there are few of them

   About 11% of responses carry a comment at the median company. That is the entire qualitative dataset, and it is small enough to read in an hour.

4. 4

   Call every detractor within 48 hours

   Not to change the score. To find out what the survey was too small to tell you, which is often an unresolved issue or an unmet expectation from the sale.

5. 5

   Report the response count beside the score

   Every time. It is the honest presentation and it stops the team over-reacting to a ten-point move that came from one person.

One behavioural measure and one commercial measure, so the scorecard covers what customers do and what they pay as well as what they say.

• Usage change against the account's own baseline, which moves earlier than sentiment and needs no responses. See why change beats level.
• Gross retention on the book, the number the business is protecting. See how to hit a gross retention target.
• NPS itself, reported with response counts, as the advocacy and reference signal it is good at.

One legitimate use worth defending: NPS finds your references. Promoters with comments are the shortlist for case studies, reviews and reference calls, and that is a real contribution a CSM can be credited for.

GainTrace scores accounts on behaviour rather than on survey responses: usage depth and trend, support history, billing movement and stakeholder change, on one record per account. Churn prediction surfaces the quiet accounts that never answer a survey, which is the population a net promoter score structurally cannot see.