 Picture the scene. Your company's annual conference is coming up and your CEO asks you to nominate a customer to present on the value they have achieved from your solution. Your mind fixes immediately on one name. Mature account, long relationship, usage data that looks exceptional, a primary contact you have worked with for years and consider a genuine ally. You tell the CEO they are a certainty and pick up the phone with complete confidence.
The response stops you cold. "I was going to call you. I'm not sure how to tell you this, but we won't be renewing when the contract is up." Every objective indicator pointed the same direction. Usage was high. Surveys were positive. The relationship felt strong. However, the customer was already gone in everything but paperwork. You didn't miss a warning sign. You had the wrong warning signs. This is the “Watermelon Effect” in action: green on the surface, red underneath. Despite the significant investment the CS industry has made in health scoring infrastructure over the past decade, it is more dangerous in 2026 than it has ever been, not because the problem has gotten harder, but because the false confidence that a well-configured dashboard produces has gotten higher.
0 Comments
 There is a question that sits at the heart of every CS programme, and most organisations are not answering it with enough precision.
At what point does a new customer stop evaluating your solution and start depending on it? The moment this transition happens is what practitioners call the “True North” moment. It is the point at which a customer moves from "nice to have" to "can't live without." It is one of the most commercially valuable pieces of intelligence a CS organisation can hold, because almost everything downstream (i.e. how onboarding is designed, when health alerts trigger, what digital engagement sequences try to achieve, when a renewal can be forecast with confidence) should be calibrated around it. The challenge is that most CS organisations either do not know what their True North moment is, or believe they know but have not validated it against actual retention data. That distinction matters enormously. A True North moment that is defined by intuition rather than analysis is just as likely to reflect what the CS team finds most satisfying to deliver as what actually predicts whether a customer stays.  Most CS leaders know the story. Three little pigs, three houses made out of straw, sticks, and bricks. The wolf has no trouble with the first two. Only the house built from the right material survives when the pressure comes.
I've used this story for years when working with CS organisations because it maps so cleanly onto one of the most revealing questions you can ask about any subscription business: What proportion of your customers would say that your solution is: no longer needed, nice to have, or essential? In 2026, this question has moved from a CS programme health check to a board-level commercial metric. The economic environment of the past several years - sustained budget scrutiny, aggressive SaaS rationalisation, procurement teams instructed to cut anything that isn't demonstrably business-critical - means the wolf is at the door for a significant proportion of most SaaS customer bases. The houses made of straw and sticks are not holding.  There is an old CS concept that describes Sales as the “matchmaker”, in other words the function that brings the customer and the CS team together, and whose quality of judgement determines whether the relationship has a chance of thriving or is heading for an early exit. The concept is still accurate. The problem is that most organisations have treated it as an interpersonal challenge rather than a structural one.
When Sales-CS alignment depends primarily on whether the Sales Executive and the CSM have a good relationship, whether the handoff conversation was thorough, or whether the post-sale team happens to raise concerns about a deal early enough for anyone to act on them, that alignment is fragile. It works when individuals make it work and breaks down when they don't, when workloads increase, when teams turn over, or when a deal close date creates pressure to move faster than the process allows.  In subscription businesses, there is a common assumption that CS leaders need to manage through: that the renewal is far enough away to allow time for the relationship to develop, the product to prove itself, and any early missteps to be corrected. In practice, this assumption is one of the most expensive beliefs a CS organisation can hold.
Customers form their judgement about whether they made a good decision significantly earlier than the renewal date. For most SaaS businesses, the trajectory of the relationship - whether it is heading toward renewal and expansion or toward a difficult conversation at contract end - is established within the first ninety days. Not because customers are impatient, but because the signals available to them are strongest at the beginning: does the product do what they were told it would? Are the people supporting them as capable as the people who sold to them? Is achieving their goals going to be as straightforward as the sales process suggested?  There is a familiar moment in every CS organisation. A CSM flags an account as at-risk. The reason? The customer hasn't responded in weeks. Emails have gone unanswered. A meeting request has been ignored. The CSM asks what to do, and someone suggests sending another email.
This is the wrong diagnosis and the wrong response and it is costing CS teams retention they cannot afford to lose. Customer apathy is not primarily a communication problem. It is a leading indicator of churn, and by the time a CSM is wondering which channel to try next, the risk has usually been building for weeks or months. The customer who has stopped responding has almost always been telling you something through their behaviour long before they stopped answering their email.  Customer advocacy has always been a signal that your CS motion is working. When a customer is willing to put their name and reputation behind your solution, you've done something right. However in 2026, treating advocacy as a nice-to-have metric is leaving serious revenue on the table.
Peer influence now drives the majority of B2B buying decisions. Buyers arrive at vendor conversations already shaped by what they've read, heard, and been told by people they trust. Your advocates are operating in that space whether you're managing them or not. The question isn't whether advocacy matters; it's whether you have a systematic programme for identifying and activating advocates before your competitors do.  The CS technology market has never been more capable or more confusing. Platforms that were primarily workflow tools five years ago have been rebuilt around AI. New entrants are making claims about predictive churn modeling, generative account summaries, and autonomous engagement that would have sounded speculative not long ago. Established vendors are racing to match them. Somewhere in the middle of all this, CS leaders are being asked to make significant technology investments, justify them to CFOs who are scrutinising every line of the tech budget, and actually get value from whatever they buy.
 There is a term that deserves to be at the centre of every CS leader's operating vocabulary: the Consumption Gap. It describes the distance between what your product is capable of and what your customers are actually using. And in 2026, as SaaS products ship new functionality (AI capabilities in particular) at a pace that outstrips any customer's ability to absorb it, the gap has never been wider or more commercially consequential.
The definition is deceptively simple. The implications are not. |