The Watermelon Effect Playbook
Your dashboards are green. Your customer is leaving. How to rebuild the health model that catches what usage metrics miss — before the renewal conversation you weren't expecting.
High usage ≠ high value. A captive customer who uses your product daily because switching costs are high will look identical to a loyal customer in your health model — until the day a competitor appears. The Watermelon Effect is a model design problem, not a technology problem.
A perfectly designed health model still fails if the processes triggered by it have quietly broken. Regularly audit: Are alert destinations still valid? Do escalation paths still point to the right people? Are playbooks triggering and completing, or stacking up in a stretched CSM's queue?
"If my primary contact left tomorrow, how would this account look to their replacement?" If the honest answer is "exposed" — the account has a Watermelon risk that no usage metric is reflecting.
The Consumption Gap Playbook
How to measure, manage, and close the gap between what your product can do and what customers actually use — before a cheaper competitor does it for you.
- Contextual in-app prompts triggered by usage pattern analysis
- Surface the "here's what this does for you" message when a relevant capability hasn't been used
- Milestone-based guidance tied to the customer's specific use case
- AI Consumption Gap: treat separately — trust and behavioural change are different obstacles
- Automated outreach triggered when high-value capability not used within 60 days of availability
- Make the "so what?" case in the customer's specific terms — not product release language
- For AI features: peer-based evidence outperforms vendor-led communication
- Multiple touchpoints across channels — one email is never enough
A customer using 80% of core functionality but 20% of AI capabilities has a measurable adoption gap in a category where the commercial value of full utilisation is demonstrable. That is a qualified expansion conversation, not a cold upsell — sourced directly from Consumption Gap data.
The Launch Window Playbook
The renewal trajectory is set in the first 90 days. A framework for designing the launch system that makes Time to Value a programme metric — not a hope.
Customers form their judgement about whether they made a good decision significantly earlier than the renewal date. By day 90, the trajectory — toward renewal and expansion, or toward a difficult conversation — is already established. Most CS teams are managing the launch phase as though they have more time than they do.
Every CS leader has inherited accounts that were never going to succeed — poor-fit customers sold a solution that didn't match their use case or resources. Build the launch failure signal back into the Sales qualification process. The characteristics that predict a successful vs unsuccessful launch belong in pipeline review, not just in CS retrospectives.
The True North Moment Playbook
How to find the single early behaviour that predicts long-term retention — and rebuild your onboarding motion around it.
The True North moment is a specific, observable customer behaviour that, when it occurs within a defined early timeframe, reliably predicts long-term retention. It is not a milestone that feels important. It is the behaviour whose presence in the first 30–90 days is statistically correlated with renewal, expansion, and advocacy — and whose absence is correlated with churn.
- vs Usage: Usage can be high without being valuable
- vs NPS: NPS captures a moment, not a trajectory
- vs Health score: Aggregates obscure as much as they reveal
- vs TTV: TTV measures speed; True North is the specific behaviour that creates it
- Feature-level product instrumentation (not just sessions)
- User-level activity data — not just account-level aggregates
- Minimum 12 months of cohort data to validate against
- CS Ops capacity to run and maintain the analysis
The Customer Apathy Playbook
Customer apathy is a churn signal, not a communication problem. How to build the early warning system that detects disengagement weeks before a CSM notices the silence.
The question is not "how do we get this customer to respond?" The question is: "Why do we find out so late — and how do we build the systems that detect disengagement early enough to do something about it?" Sending another email is the wrong answer to the wrong question.
A system where a CSM or digital engagement sequence is triggered by a threshold combination of signals — not by a CSM noticing an email hasn't been returned. That shift, from reactive to proactive detection, is the single biggest lever available for improving re-engagement outcomes.
The Three Pigs Playbook — Building Essentialness
In an era of aggressive SaaS rationalisation, "nice to have" doesn't survive budget season. How to measure where your customers sit — and systematically move them into the brick house.
Gross Revenue Retention and Net Revenue Retention both move materially when you shift even a modest percentage of your base from "nice to have" to "essential." This is a direct driver of the numbers your CFO and CRO present to the board — not a soft CS metric.
The Customer Advocacy Playbook
Advocacy isn't a satisfaction metric — it's a revenue input. A systematic approach to identifying and activating advocates at scale before your competitors do.
Map your advocacy programme to revenue outcomes: pipeline influenced by reference calls, conversion rate improvement from case studies, review score impact on inbound. When CS leaders frame advocacy this way and tie it to pipeline influence metrics, it becomes fundable, measurable, and cross-functionally supported.
- Formal ask with specific request — not "would you be willing to help?"
- Make the exchange of value explicit — what does the advocate get?
- Build the content with them, not for them
- Connect advocates to each other — community compounds advocacy
- Pipeline influenced by advocacy activities
- Reference call completion rate and win rate correlation
- Review score trajectory on key platforms
- Advocate retention rate vs overall base
The Sales-CS Alignment Playbook
When alignment depends on individual relationships, it's fragile. How to redesign it as a revenue architecture problem — with structural systems that make good alignment the default.
A bad-fit account consumes CS resources at a rate disproportionate to its commercial value, rarely reaches a healthy adoption trajectory, and when it churns, often damages reputation with adjacent prospects. Calculate the fully-loaded cost of a churned bad-fit account — CS resource consumed, implementation cost, sales commission paid, GRR impact — and compare it to the bookings value. In most organisations, this reveals a significant offset of apparent revenue growth.
Not enthusiasm for deals in the pipeline. Not willingness to get on calls with late-stage prospects. It is a continuously maintained, data-grounded intelligence product that tells Sales what a customer who will renew, expand, and advocate actually looks like — and what a customer who will churn looks like, before the deal closes.
The CS Platform Evaluation Playbook
What the vendor won't tell you. A pre-purchase framework for CS and CS Ops leaders that focuses on the internal work — not the platform features — that determines whether your investment delivers.
The platforms matter less than most people assume at the point of selection. What determines whether a CS technology investment delivers is almost entirely the internal work — the foundations, the ownership, the design — that happens before and during deployment.
- Feature-level product usage data available and clean
- CRM data quality assessed — your CS platform is only as good as the data feeding it
- Historical renewal and churn outcomes tagged and accessible
- Stakeholder contact data current and structured
- What data is required to make your health model accurate for my business?
- How long until predictive scoring is reliable enough to act on?
- How do you handle configuration drift over time?
- Show me the AI output quality — live, not demo-ware
What you deploy on day one will gradually drift from reality as your business, product, and customer base evolve. The platform will slowly lose the trust of the CSMs who depend on it — unless CS Ops has a defined process for ongoing calibration, configuration review, and health model recalibration. Build this into the resourcing plan before go-live, not after.