
Step into Cadenspring Cloud, a fictional B2B SaaS vendor serving clinics. Compare public retention definitions before diagnosing one fixed customer cohort; no earlier lecture is needed.
Separate logo churn, lost recurring revenue, contraction, expansion and new business; treat reported loss reasons as questions to verify.
Complete a function diagnosis and a 30/60/90-day repair plan; review an AI draft against its stated inputs.
Tools in this lecture (10): Revenue Leakage Diagnosis HTML file; working parts: Baseline; Loss reasons; Process review; Repair plan; AI draft; slide tools: Cohort entry checklist, Loss interview prompts, Product referral template, AI draft review checklist.
Use the fictional Cadenspring Cloud portfolio to choose coverage from customer ARR, workflow complexity and credible expansion potential; this lecture supplies its own context.
Compare high-touch, tech-touch and pooled CSM service promises, then check workload and cost-to-serve with payroll counted once.
Review public segmentation guidance and record one coverage exception with a customer communication route.
Tools in this lecture (6): Segment Coverage Matrix HTML file; working parts: Customer inventory; Coverage matrix; Service promise; Load and cost; Exceptions.
Use one customer at fictional Cadenspring Cloud to agree the first administrative outcome; all necessary example data are supplied here.
Examine public onboarding guidance; record Sales-to-CS acceptance, mutual stages and usage evidence for first value.
Measure time-to-value with completed and incomplete journeys kept separate; record recovery for a blocked stage.
Tools in this lecture (6): Onboarding Map HTML file; working parts: Outcome; Handoff; Stages; Cohort; Recovery.
Investigate one fictional Cadenspring Cloud account signal with the supplied context; distinguish an observation, a suspected cause and a customer-confirmed cause.
Review public health-score guidance; configure signals, weights and thresholds without treating a color as renewal probability or missing data as zero.
Use customer-specific NPS or CSAT appropriately, then check an AI health summary and record a human decision, action and escalation condition.
Tools in this lecture (6): Health Signal Action Board HTML file; working parts: Signals; Queue; Review; Action; Draft.
Build a renewal forecast for the supplied opening cohort at fictional Cadenspring Cloud; actual retention and forecast versions remain separate.
Review public renewal and retention documents; inspect renewal exposure, category assumptions, recovery ownership and a separate expansion lane.
Reconcile GRR and NRR on the same base, excluding new customers; review assumptions and an AI renewal draft before a commercial decision.
Tools in this lecture (8): Renewal Forecast and Retention Plan HTML file; working parts: Cohort ledger; Exposure calendar; Forecast categories; Recovery record; Expansion lane; Retention bridge; Review note & AI draft.
Prepare or rehearse an executive business review for a fictional Cadenspring Cloud customer, using the context and figures supplied in this lecture.
Examine public business-review guidance; distinguish confirmed outcomes from capacity estimates and use a four-stage QBR/EBR conversation.
Plan post-sale executive sponsorship and contact continuity; check an AI QBR draft and return customer feedback to Product without promising a delivery date.
Tools in this lecture (8): QBR and Executive Relationship Planner HTML file; working parts: Review purpose; Outcome statement; Executive relationship program; Contact continuity; Customer conversation; Product feedback and agreements; AI draft and rehearsal record.
Take the supplied fictional Cadenspring Cloud segment and calculate the CSM work promised against available hours; no other lecture is required.
Review public role and capacity guidance; distinguish CS staff from CSMs, customer accounts from sites, and monthly hours from annual costs.
Record a staffing decision, a role brief and observed hiring criteria, plus a variable-pay principle for legal review.
Tools in this lecture (7): CSM Capacity and Team Planner HTML file; working parts: Portfolio; Capacity; Costs; Roles and hiring; Pay; Review.
Run one joint weekly review at fictional Cadenspring Cloud using the supplied dashboard and four-function operating model.
Examine public CS and Product guidance; agree Sales, CS, Product and Support handoffs and use usage data, customer feedback and NPS in context.
Align with Product on roadmap requests, record the Product response and customer return route, and check an AI dashboard comment; an unconfirmed date stays unconfirmed.
Tools in this lecture (7): CS Weekly Operating Dashboard HTML file; working parts: Model; Handoffs; Dashboard; Product; Weekly review; AI comment.
This course contains the use of artificial intelligence.
Customer retention needs a system before it needs another escalation.
Put 50+ practical tools behind the work to reduce churn and grow NRR in a B2B company.
A renewal can look healthy until the customer stops answering. An onboarding can be marked complete while the first useful outcome remains unconfirmed. A busy CSM team can still leave a whole customer segment without enough capacity. When these problems sit in separate spreadsheets and conversations, the director sees the loss after the opportunity to act has narrowed.
The change is a connected operating picture: one customer cohort, explicit service promises, a visible path to first value, reviewed risk signals and a renewal forecast that shows its assumptions. Customer meetings end with a recorded next step. Staffing discussions start with the work and available hours. Product requests return to customers through a clear communication route.
Mike is the founder and leader of an academy serving individual students and corporate clients, with responsibility for customers in his own company. His perspective draws on 20 years in HR, including building service functions. The course combines that management perspective with documented CS practices and a clearly fictional business scenario.
What the tool count means
These are 58 counted tools across file containers, their working parts and reusable slide tools, rounded down to 50+. They are packaged in 16 downloadable resources: eight lecture presentations and eight HTML files. The internal working parts are contained in the HTML files. Models, definitions, repeated views, export buttons and demonstrations do not add to the count.
One company, eight independent management tasks
Cadenspring Cloud is a fictional vertical B2B SaaS vendor whose customers are clinics. Its people, customers and figures are fictional examples: illustrative numbers, not market benchmarks. There are no patient records. Each lecture supplies its own context and the necessary example data, so it can stand alone.
The path starts with revenue leakage and a 90-day repair plan, then moves into customer segments and coverage models. Onboarding connects signed scope to an agreed first outcome. Health review connects a signal to an investigated risk and a human decision. Renewals connect retention and expansion to the same opening customer cohort. QBR and executive business reviews connect customer priorities to confirmed outcomes and the next conversation. Team planning connects the book of business to hours, hiring and compensation. The final operating rhythm brings Sales, CS, Product and Support into one weekly review.
Each lecture examines one to three real public documents, discussing what their structure or definition contributes and what still needs adapting. The course distinguishes gross revenue retention (GRR), net revenue retention (NRR), customer churn and new business. Published retention definitions can use different cohorts, periods or averaging methods; the fictional scenario keeps its own definition visible.
Customer Success and Product Management collaboration runs through the operating model: usage data provides context, QBR feedback and loss reasons inform product development, and a joint review aligns requests with the product roadmap. Effective communication includes returning the Product response to the customer. Net Promoter Score (NPS) is an input about satisfaction and loyalty, interpreted with its sample and period rather than used as a substitute for customer investigation. Roles, decision rights and a practical joint review record make the collaboration concrete.
Public documentation from Gainsight, ChurnZero, Totango, HubSpot, Salesforce and Zendesk provides context for current CS practices. Selected Gainsight demonstrations are mockups rebuilt from public documentation; the real interface and workflow may differ. The course is independent and is not affiliated with these vendors. The working HTML files require no platform subscription.
AI prepares a draft health summary, churn-signal summary, QBR or dashboard comment; the CSM or director checks its inputs and wording. Decisions about a customer, discount or escalation remain with people. Do not send real customer or user data to public AI services without the required contract and company policy. For contracts, renewal terms and compensation, check with your legal team.
What is included
Every renewal window arrives whether the operating gaps have been reviewed or not. Open the first diagnosis, choose one process gap and put the next review on the calendar. Enroll now and start your first lesson today.