When customers churn, that’s a problem.
Even if their churn was “unavoidable” it still hurts.
Churn hurts on several levels: from lowering revenue to hurting employee morale.
And churn means something happened to the customer (out of business, acquired, etc.) or – and MUCH more likely – they didn’t achieve their Desired Outcome through their interactions with your company.
In order to avoid churn in the future, we need to learn from the churn that has occurred in the past.
Which means every former customer must have a reason associated with them.
By focusing on Customer Success, you should get to a point where customer churn isn’t a big deal anymore. But until you get to that point, you may lose customers -maybe a significant number – so you have to figure out how to get our customers on the right path toward their Desired Outcome.
One of the ways we can do this is by looking at the reasons our customers are churning today.
Ideally, every former customer will have two churn reasons associated with their customer record: an internal reason – one derived from our understanding of why they churned (finance data, support tickets, pre-cancel usage data, etc.) – and where possible, a reason from them directly. This can be from a conversation, survey, third-party interview, etc. They could have told you directly as they were canceling, but you may not have that in one place yet.
That said, it is totally realistic that you’ll not always get a response from a churned customer – though you should always try – but you can at the very least posit a theory of your own based on their behavior – in-app and beyond – as well as customer satisfaction surveys, financial data, support tickets, training consumption, etc.
When your internally-inferred reasons do not align with the reasons given by the customer, you know your ability to predict churn is low. If they are aligned, you know you’re relying on the appropriate Success Vector inputs.
But you can’t do that sort of comparative analysis unless you’re capturing and recording both internal and customer-sourced reasons for churn.
So add two fields to your customer record and from now on, when a customer cancels make sure you have 100% coverage on internal reasons and as many customer-derived reasons as possible. I like to see at least 50% coverage for customer-shared reasons.
And if you can, go back, at least, 30-days for self-service, month-to-month “contracts” or a quarter or two for annual contracts to get customer-derived reasons for churn. Asking customers that churned further back than those time frames may not yield enough to warrant wasting cycles, but you could – and should – go back as far as you can (don’t worry about your early adopters) to fill in the internal reason.
By the way, this is a great place for the Customer Success bot method. “Hey, I just saw that you canceled. Sorry to see you go; can you tell me about your experience, though?” You want to ask the question in a way that’s not about, “Tell me what we can do better so we can” … because you don’t want it to be about you.
When you ask your customers why they canceled (or didn’t renew), ensure you ask about their experience and not “so you can help other customers better” or help yourself. Keep it about them.