Every B2B CS Leader I know is struggling with downgrades.
2023 was the year of cost-cutting.
With CFOs tightening their purses, many decision-makers were asked to reduce operating costs to meet the company's margin goals.
In response, every team went through a tech review exercise.
They bucketed their tech stack between must-haves and nice-to-haves.
The result was three-fold:
We all felt the initial pain of the cancellations.
I even wrote an edition of the newsletter on how to win NRR in 2024, focused on downgrades, upgrades and cancellation strategies in this new world.
After the first shock, most have been able to steady the cancellation ship. However, the downgrade trend seems to be here to stay.
This newsletter is here to help you identify, track, tackle and prevent a downgrade issue.
Measuring Downgrades
"You can't improve what you don't measure" - Peter Drucker
Before you fix a problem, you have to understand it. And too many of us only have a high-level view of our downgrades.
Not all downgrades are made the same.
By looking at this data, you might learn that most of your downgrades happen because of one or two root problems that can be addressed at scale. Jackpot! 🎰
Or you might learn that your downgrade problem is less clear-cut, and you'll have to fix a few things to get this number under control.
To do this analysis, I like bucketing 'Downgrades Reasons' into 3 categories:
You can bake these reasons into your CRM, so each time a downgrade happens, the CSM or the customer can mark the reason for the downgrade, making future analysis easier.
In this macro-climate, consumption downgrades are natural. Customers have let people go and right-sizing the subscription makes sense. There's nothing healthy you can do to convince them to retain those licenses or seats.
Your best bet is to convince them to shift dollars into other products that might add extra value.
For Pricing downgrades, you either have to get more specific about demonstrating value (here is how you can start measuring customer outcomes) or better at communicating value (here is a guide to delivering powerful EBRs).
Below I will focus on helping you identify and fix the usage issue.
Tracking "Usage" Downgrade Risk
A big problem with this type of downgrade is that it's hidden.
From the outside, these customers look healthy...
The problem is that most usage metrics and health scores are pretty dumb.
They are not designed to consider the nuances of the different tiers or add-ons. It's a peanut butter spread approach that tends to tell very little about a customer's likelihood to downgrade.
So from a high-level forecasting perspective, they fall through the cracks for leaders.
There's limited visibility on future risks:
The solution?
Do away with rigid usage metrics that look at log-in frequency and a few top tools utilised, and move to smart and tailored metrics that take into account utilisation based on package and use-case.
These tailored scores will allow you to:
So, once you spot the problem, how do you fix it?
Fixing Usage Related Downgrades
The overall utilisation of SaaS tools is dropping drastically.
In Martech, for example, utilisation has dropped from 58% to 33% in just 2 years. (Gartner)
Our product teams are building more and more functionality, and our customers are adopting less and less of them.
Why is this happening?
Customers are failing to unlock the full value of the tier, add-on or extra products they've purchased.
My hunch is that the problem is two-fold:
1- We are not as intentional when onboarding customers, especially existing ones.
2- As we release new features, we are not doing a great job at getting customers to use them to drive value for their business.
To fix both of these problems, you'll need a cohesive value realisation journey:
If you sell intentionally, tailor onboarding, continuously enable customers to achieve the solution's full- potential, you WILL increase adoption.
And if the tools are being adopted, and driving value for the customer...
The downgrade risk will drop significantly!
TL'DR
If your customer is downgrading, they likely didn't get value from key extra functionality you offer.
Do these 3 things and watch your downgrade problem turn into success stories!