Net Promoter Score (NPS) is a widely used metric for measuring client happiness in SaaS businesses, but it has some serious shortcomings.
The Net Promoters Score(NPS) was created by Fred Reichheld and a Bain & Co. and has become very popular with Software as a Service companies. NPS is a very simple survey question:
“On a scale of 0 to 10, how likely are you to recommend us to a friend or colleague?”
Many companies love NPS for its sheer simplicity and lack of effort required by the responder. It's also highly regarded because of the belief that if someone would go as far as to recommend your product to a significant other then they must be a loyal user themselves.
In terms of Customer Success, NPS looks to be a very useful score. After all, one of the main reasons for the role of Customer Success is to develop happy customers and happy customers result in growth.
The calculation of NPS might not be the simple average you were thinking of. Many that are new to NPS tend to think the score would be the mean average of all of the results. In reality, the scale of 0-10 is broken down into 3 groups:
From these groups, the calculation is derived as:
% of Promoters − % of Detractors = NPS
The range is from -100 to 100 and anything over 0 is considered ‘good’.
“Thanks for taking the time to respond to our survey recently. I noticed you scored us a 7 out of 10, can I ask for some context behind that”?
If you are going to use NPS, it’s vital that your CSMs are following up with respondents to find out the ‘why’, especially for your detractors as well as promoters. NPS also needs to feed into a wider Customer Health Score. As we’ve seen, NPS leaves too many unanswered questions and is too simplistic to derive whether a client is truly loyal or not. It is possible that you can set up an automated email to go out to Promoters and heavy detractors. We're also seeing more implementations of NPS have a second follow up question, which might be something like "Would you care to tell us why?". This is great, and just what you need to start to gather a certain level of context behind the initial score.
"Adobe phrase the question slightly different "What would make you more likely to recommend this product to others?"
It’s my belief that a system like NPS should be a constant measure. The best users of NPS will send out a survey at numerous points in the year, just after a platform update, or at a certain time periods, but I think It should be open to being updated at any given point, whenever the client feels like it. It’s far more useful to you as a company to know how the client is feeling after each interaction with your product and staff. It could easily be baked into the system perhaps as a menu item or in Profile settings. A slightly more controversial idea would be to have this score as mutual, so both the CSM and client can update it as they see fit. I’d love to see the comparisons of how happy the CSM thinks the client is versus the client's view. That gap in itself could lead to some useful training and education sessions.
The only real way to measure customer satisfaction is by blending a number of metrics. Usage data, public sentiment, QBRs, and yes NPS/CSAT etc, and this all rolls up to the Customer Health Score, which vitally MUST contain a CSM ‘Gut Score’.
Simon has over 10 years helping clients achieve their goals through the use of software. Having previously lead Customer Success teams in London, Europe and New York City, Simon now owns Kupr Consulting working with B2B SaaS companies to improve their Customer Success teams and processes.
Receive regular emails and help yourself become a Customer Success expert. You can unsubscribe in one click, and your email will never be used for anything else.