Client Success Loop
Module 5 is the revenue retention and expansion layer of the operating system. It converts client data into a health scoring system that feeds 6 other modules and transforms customer success from a cost center into a revenue engine.
Module 5 operates at the intersection of four upstream inputs. Module 4 (Integrated Tech Stack) provides the clean, unified data that the health scoring model requires. Module 3 (KPI Precision Grid) supplies the client-facing metrics that form part of the health score's outcome dimension. Module 2 (SOP Codex) documents the escalation procedures that activate when a client's score drops. Module 1's AI Readiness Index determines whether the AI-driven churn predictor can operate at full capacity or must run with human-in-the-loop oversight.
Downstream, Module 5's outputs flow into six modules. Client health data feeds Module 6 (Sales Velocity Engine), where it identifies which customer profiles are most likely to expand. Customer concentration data feeds Module 9 (Exit and Acquisition Layer), where it becomes a valuation input. And the AI churn predictor itself is governed by Module 7 (AI Deployment Canvas), registered in the AI Register with bias and drift audit requirements.
A standalone customer success program monitors clients and intervenes when problems surface. Module 5 monitors clients and routes the data into sales strategy, exit readiness, and AI governance simultaneously.
Why Customer Success Programs Fail
The industry statistics are consistent: acquiring a new customer costs five to seven times more than retaining an existing one. Yet most mid-market companies invest disproportionately in acquisition and treat retention as a reactive function.
Pattern 1: Reactive intervention. The customer success team learns of problems through complaints, renewal conversations, or non-renewal. By then, relationship damage is done. The team scrambles to save accounts with discounts or attention that belonged months earlier.
Pattern 2: Single-dimensional health tracking. Companies tracking client health typically use one metric: NPS, CSAT, or usage. Each captures one dimension and misses others. High NPS with declining usage appears green but signals risk. Low NPS with expanding invoices appears red but indicates health.
Pattern 3: Success data stays in the success team. Client health data lives in the customer success platform. Sales does not see it. Finance does not see it. The executive team gets a quarterly summary. Nobody connects client health to pipeline strategy, capital allocation, or exit valuation because the data is siloed in one department.
Module 5 addresses all three patterns through a composite health score (multi-dimensional), an AI churn predictor (proactive), and data routing to Modules 6, 9, and the leadership dashboard (systemic).
The Customer Journey Map
What it does
The Customer Journey Map outlines the entire client lifecycle from kickoff through expansion. It identifies five phases with clear owners, due dates, and success metrics.
Five phases
Kickoff and Provisioning. Initial setup and activation. The clock starts here, and the first measurement point is time-to-provision. This metric feeds into Module 3's Baseline Snapshot.
First-Value Delivered. When the customer experiences initial benefit. This milestone predicts long-term retention. Companies reaching first-value within the defined window retain at 85%+. Those missing it retain at 40% or lower.
Adoption Deepening. Continued engagement and deeper feature use. The health score tracks usage depth, not just frequency.
Value Validation at Renewal. Demonstrating ongoing worth with hard ROI data. This phase connects directly to the QBR Engine.
Expansion and Advocacy. Identifying opportunities for growth and encouraging customer advocacy. Expansion data feeds Module 6's lead scoring model (existing customer expansion is the highest-probability pipeline).
Why the map must be actionable
A journey map that sits on a wall is decorative. Module 5 requires that every milestone has a named owner in the CRM, a due date that triggers a task if missed, and a success metric that feeds the health score. This connects to Module 2 (SOP Codex), where the onboarding process, the first-value delivery process, and the renewal process are each documented as searchable, version-controlled SOPs.
The Client Health Score Model
What it does
The Client Health Score combines four dimensions into a composite score that predicts retention, expansion likelihood, and risk.
Four dimensions
Usage. Logins, feature depth, session duration, and trend direction. A declining usage trend is the earliest churn signal, often appearing 60 to 90 days before any other indicator.
Outcome. Quantifiable improvements in the client's KPIs attributable to the product or service. This dimension uses data from Module 3 (KPI Precision Grid). If the client's metrics are improving, the outcome score is green. If they are flat or declining, the relationship is at risk regardless of what the NPS says.
Relationship. NPS, CSAT, and qualitative feedback from account managers. This is the dimension most companies track. In Module 5, it is one of four, not the only signal.
Financial. Invoice age, upsell status, contract value trend, and payment consistency. Late payments are a churn predictor. Expanding invoices are a retention signal. This dimension connects to Module 8 (Agile Capital Allocation), where client financial health data informs revenue-side gate KPIs.
Scoring and visualization
Different weights are assigned based on what truly predicts retention for the specific business. The defaults are Usage (30%), Outcome (30%), Relationship (20%), Financial (20%), but these are calibrated during implementation based on historical churn data. The score runs 0 to 100: red below 40, amber 40 to 70, green above 70, the AERI convention (starting value).
Results are visualized with a traffic-light system consistent with every other VWCG OS module (Green, Amber, Red). The consistency matters. A leadership team reviewing Module 3's KPI dashboard, Module 5's client health dashboard, and Module 8's capital tracker sees the same color language across all three. Red means the same thing everywhere: intervention required.
Automation
A weekly script pulls the latest data from all sources, recalculates scores, and pushes results to a dashboard. Alerts fire when any account drops to amber or red. The alerts route to the account owner and their manager through Slack, consistent with Module 3's Variance Alert Engine.
The AI-Driven Churn Predictor
What it does
The churn predictor uses machine learning to forecast client defection before it happens. It combines health score trends, support ticket sentiment, login frequency patterns, and contract renewal proximity into a probability score.
Trigger threshold
When churn probability reaches 0.6 or higher, the escalation SOP activates. The SOP is time-bound: customer success manager and executive sponsor assigned within 4 hours, root-cause analysis call within 24 hours, mitigation plan agreed within 72 hours and tracked in the project management tool.
Human override
Customer success managers can override AI flags when they have context the model lacks. Overrides must be documented with a reason. Override frequency is tracked. If a CSM overrides more than 20% of flags, either the model needs retraining or the CSM needs coaching. The data determines which.
Connection to Module 7
The churn predictor is an AI deployment. In the VWCG OS, this means it falls under Module 7's full governance framework. The model appears in the AI Register with a Model Owner (data/ML team) and a Business Owner (VP of Customer Success). Quarterly bias and drift audits verify that the model performs consistently across customer segments, company sizes, and industries.
If Module 1's AI Readiness Index scores the organization below 40%, the churn predictor runs in human-in-the-loop mode. Every flag requires manual review before the escalation SOP activates. Above 70%, the predictor can trigger the SOP automatically. Between 40% and 70%, it operates in supervised mode with monthly accuracy reviews.
This tiered activation is unique to the VWCG OS. Standalone churn predictors deploy based on technical readiness. Module 5's churn predictor deploys based on organizational readiness as measured by Module 1.
The QBR Engine
What it does
The Quarterly Business Review Engine is a structured process that converts successful client relationships into expansion opportunities.
QBR flow
The review follows a fixed sequence. Open with outcomes delivered (hard ROI data, not anecdotes). Present relevant product roadmap items. Review the ROI math with the client. Identify expansion opportunities based on usage data and emerging use cases. Set new goals for the next quarter that feed back into the health score model.
AI enhancement
AI can auto-draft QBR decks from CRM and usage data, reducing prep time from hours to minutes. This AI component is, like the churn predictor, governed by Module 7 and subject to human review before client delivery.
Expansion triggers
Three signals indicate expansion readiness: the client is exceeding initial goals (outcome dimension green), new use cases are emerging from usage data (usage dimension trending upward), and NPS/CSAT signals are positive (relationship dimension green). The QBR Engine flags the account for expansion when outcome and relationship are green and usage trends up for two consecutive weekly reads. A client at or above 15% of trailing-12-month revenue is never flagged. This signal feeds into Module 6's pipeline as the highest-probability lead source.
Downstream Connections Summary
Module 5 feeds six downstream modules:
- Module 6 (Sales Velocity Engine): Client health data identifies which customer profiles drive expansion. The highest-probability pipeline is existing customers with green health scores and emerging use cases. Module 6's lead scoring model weights expansion leads higher because the conversion rate is 3 to 5 times higher than new-logo acquisition.
- Module 9 (Exit and Acquisition Layer): Customer concentration data from the health score model feeds directly into Module 9's Customer Concentration Analysis. If any single client reaches 15% of trailing-12-month revenue, Module 9 flags a valuation discount risk. This data is always current because the health score model updates weekly.
- Module 7 (AI Deployment Canvas): Both the churn predictor and the QBR deck generator are registered AI deployments subject to Module 7's governance framework, including quarterly bias and drift audits.
What makes this different from standard customer success
Standard customer success programs (Gainsight methodology, SaaS best practices, customer success playbooks) produce a health score and an escalation process. The deliverable is retained and expanded accounts.
Module 5 produces a health score that feeds sales strategy (Module 6), exit valuation (Module 9), and AI governance requirements (Module 7). The customer success function does not operate in isolation. It operates as a data source for the operating system. Every health score update ripples into pipeline prioritization, concentration risk assessment, and model accuracy monitoring. A standalone program retains clients. Module 5 retains clients and routes the data into 6 other modules simultaneously.
Routing in practice
A SaaS company's Module 5 health score flagged that its largest client represented 22% of recurring revenue. Module 9 immediately tagged the concentration as a valuation risk. Module 6 received the signal and increased new-logo acquisition weighting in the pipeline prioritization. Three months later, the churn predictor flagged a second client at 0.7 probability. The escalation SOP activated within 4 hours. The retention team resolved the issue, but the flag also routed to Module 8. Because the revenue base was at risk, Module 8 opened a hold review of a planned expansion project at the next Forum. One health score update moved through four modules in parallel, each responding with its own playbook. Each route arrived as a proposal, and leadership confirmed them at the next review.
Who This Module Is For
Module 5 was designed for mid-market companies where client retention is acknowledged as important but managed as a departmental function rather than a system input.
These companies have customer success teams. They may have health scores. What they lack is the connection between client health data and sales strategy, capital allocation, exit readiness, and AI governance. The data exists but it stays in the customer success platform. Module 5 breaks it out and routes it into the modules that need it.
The Working Specification
The instrument scores five dimensions: Journey Map Operability, Health Score Integrity, First-Value Discipline, Churn Predictor Governance, and Expansion and Concentration Routing. Weights are version 1.0 calibration defaults from 2026-08-20, tuned to each client during calibration.
The Instrument
The Client Success Loop Diagnostic scores 5 dimensions on a 0 to 5 scale against written anchors. The composite score is a weighted sum with equal weights of 0.20 per dimension. Four standing page metrics carry the published thresholds. Clients reaching first-value inside the window retain at 85% or better, and outside it at 40% or lower. A churn probability of 0.6 triggers the escalation SOP: CSM plus executive sponsor in 4 hours, root-cause call in 24 hours, mitigation plan in 72 hours. CSM overrides above 20% of flags mean retrain the model or coach the CSM. Any single client at or above 15% of trailing-12-month revenue flags M09 valuation discount risk.
| Dimension | Weight | What it measures | Score 1 | Score 3 | Score 5 |
|---|---|---|---|---|---|
| Journey Map Operability | 0.20 | All five phases (kickoff, first-value, adoption deepening, value validation, expansion) mapped with named CRM owner, due date that triggers a task, and success metric feeding the health score | Journey undocumented or wall-decoration. No owners, no dates, no metrics | Map exists with owners. Task triggers and metric feeds partial | Every milestone owned, dated, task-triggering, and metric-feeding. Onboarding, first-value, and renewal SOPs coded in M02 |
| Health Score Integrity | 0.20 | Composite uses all four dimensions (usage, outcome, relationship, financial). Weights calibrated from historical churn data. Weekly automated recalculation. Traffic-light consistent with M03 and M08 | Single-metric tracking (NPS only) or none. Silent churn arrives as surprise | Four-dimension composite exists but manual, stale, or uncalibrated | Four-dimension composite auto-recalculated weekly. Weights calibrated. Amber and red alerts route to account owner and manager |
| First-Value Discipline | 0.20 | First-value window defined per offer. Time-to-first-value measured per client. Retention tracked against the 85% and 40% split. Time-to-provision feeds the M03 baseline snapshot | First-value undefined. Onboarding drifts. Early churn unexplained | Window defined and measured. Breaches common and unrouted | Window defined, measured, and improving. Breaches trigger intervention. Split validated against own cohort data |
| Churn Predictor Governance | 0.20 | Predictor registered in the M07 AI Register with model and business owners. Activation mode matches M01 AERI tier (below 40 human-in-the-loop, 40 to 70 supervised, above 70 automatic). Overrides documented with the 20% rule tracked. Quarterly bias and drift audits run | No predictor, or one deployed on technical readiness alone ignoring AERI state | Predictor live and registered. Override tracking or audit cadence lapses | Tiered activation matches AERI. Overrides documented with 20% rule enforced. Quarterly audits clean. Escalation SOP fires on 0.6 within time bounds |
| Expansion and Concentration Routing | 0.20 | QBR cadence held with ROI-first flow. Three-green expansion signals route to M06 pipeline. Concentration data feeds M09 weekly. Health data visible to M08 revenue-side gates | Success data siloed in the success team. Expansion opportunistic. Concentration unmeasured | QBRs happen. Routing to M06 and M09 manual or partial | Three-green expansion flags auto-route to M06 as highest-probability leads. Concentration feeds M09 current weekly. Health informs M08 gates |
Scoring and Bands
| Band | Range | What it routes to |
|---|---|---|
| Red | 0.0 up to but not including 2.0 | Proposes the owning remediation playbook. Safety routes act on the first reading (Routing table below) |
| Amber | 2.0 to 3.5 inclusive | PB-M05-04 monitoring with 30-day pulse checks |
| Green | above 3.5 up to and including 5.0 | Hold and monitor through M13 (weekly for the concentration signal) |
Routing
Red bands fire the routes below. Every amber dimension routes to PB-M05-04. Green dimensions hold and are monitored through M13. Conditions read the module 0 to 5 bands unless a row names another scale. A color changes only when a score clears the band edge by a margin, or holds for two consecutive scorings. The margin is 0.25 points on 0 to 5 scales and 5 points on the AERI 0 to 100 scale. Safety routes are the routes that set AI mode in any module, the Privacy Impact Assessment rule, or Module 12 classification and response windows. They tighten on the first reading and loosen only after an independent re-score clears the edge. When two routes set the same parameter differently, the most restrictive value wins for safety routes, and the owning module's value wins for every other parameter. A route that fires from a scored dimension is a proposal until leadership confirms it in the M13 Phase 3 review. Routes that fire from measured values and events (PV2, KPI variance, revenue concentration, dates, and logged events) act on the reading. Scorer agreement has not yet passed the reliability test. A proposal is confirmed at the next monthly governance review or the M13 Phase 3 review, whichever comes first, and a playbook's stated duration starts at confirmation. Routes that restore the M13 cadence itself act on the reading. A route that carries evidence feeds the next scoring of the receiving dimension and never sets a score directly. Module instruments are scored quarterly in weeks 11 to 12 of the M13 cycle, Module 1 in Phase 1, and measured signals at their own review cadence. An RT code names the destination action, so several source rows can share one.
Outbound routes
| Signal | Condition | Destination | What fires |
|---|---|---|---|
| Journey Map Operability | red | M05 PB-M05-02 | First-Value Acceleration (RT-M05-FIRST-VALUE-RED) |
| Journey Map Operability | red | M02 PB-M02-01 | Onboarding, first-value, and renewal processes must be coded SOPs |
| Health Score Integrity | red | M05 PB-M05-01 | Health Score Build (RT-M05-HEALTH-SCORE-RED) |
| Health Score Integrity | red | M04 PB-M04-02 | M04 runs a parity and duplicate check on the CRM, support and usage sources feeding health scores |
| First-Value Discipline | red | M05 PB-M05-02 | First-Value Acceleration |
| Churn Predictor Governance | red | M05 PB-M05-03 | Escalation and Churn Response Activation (RT-M05-CHURN-ESCALATION-RED) |
| Churn Predictor Governance | red | M07 PB-M07-01 | M07 registers or re-registers the churn predictor and QBR generator with both owners |
| Expansion and Concentration Routing | red | M05 PB-M05-01 | Health Score Build |
| Expansion and Concentration Routing | red | M06 PB-M06-02 | M06 stops taking expansion leads from M05 until routing is amber |
| Expansion and Concentration Routing | red | M09 PB-M09-01 | M09 marks concentration evidence unverified until M05 routing is amber |
| Concentration signal | >= 15% of trailing-12-month revenue | M09 PB-M09-01 | Single client at or above 15% of trailing-12-month revenue becomes an M09 valuation input |
| Churn probability | >= 0.6 on a client tied to a funded project (model probability) | M08 PB-M08-03 | Opens a hold review of that project's next tranche at the next Forum. Release still follows the two-checkpoint evidence rule |
| Client expansion signal | on event | M06 PB-M06-02 | Client becomes a priority lead unless M05 routing is red or its revenue share reaches the concentration threshold |
Dependencies, documented and not routed: M05 time-to-provision is an input to the M03 baseline snapshot. M05 predictor mode follows the M01 AERI band (now an M01 route).
Inbound routes
| Signal | Condition | Source module | What fires in M05 |
|---|---|---|---|
| AERI overall subscore | < 40 (AERI 0 to 100) in M01 | M01 | Churn predictor and QBR generator run advisory only. The model never starts the escalation SOP, a person decides (PB-M05-03) |
| AERI overall subscore | 40-70 (AERI 0 to 100) in M01 | M01 | Each churn flag starts the escalation SOP once a person confirms it. Monthly accuracy review (PB-M05-04) |
| AERI overall subscore | > 70 (AERI 0 to 100) in M01 | M01 | Churn predictor fires the escalation SOP automatically (PB-M05-04) |
Playbooks
Every playbook follows one lifecycle: open, running, met or missed, escalated, closed. A trigger that arrives while a playbook is open is logged against the open run. An outcome met, with an independent re-score at amber or better, closes the run, and the owner's next queued red opens. An outcome missed at the end of its stated duration escalates to the owner's manager and the next M13 quarter planning agenda. Someone other than the owner re-scores the dimension. Each owner runs at most three red playbooks at once. Further reds queue, ranked by how many modules the red dimension routes into. Safety playbooks (PB-M07-02, PB-M12-02, PB-M12-03) never queue. A red route opens a red playbook. A route that changes a mode, a cadence, or a data feed runs under the module's standing playbook. When a red playbook's outcome is met, any standing duty it set up continues under the standing playbook, which does not count toward the cap. Escalation for a CEO-owned playbook goes to the board.
PB-M05-01: Health Score Build (Score Integrity)
Trigger: Health Score Integrity red, single-metric tracking discovered, or stale or manual scoring. Confirms M04 data quality is green first, then stands up the four-dimension composite (usage, outcome, relationship, financial) starting from the page default weights 30/30/20/20. Weights are calibrated against 12 months of churn history where available, weekly recalculation is automated, and alerts wire to account owner plus manager consistent with the M03 Variance Alert Engine. Outcome: composite auto-recalculating weekly, weights calibrated and logged, alerts firing, health visible outside the success team. Owner: VP of Customer Success with data/ML support, 4 weeks.
PB-M05-02: First-Value Acceleration (Journey / First-Value)
Trigger: Journey Map Operability or First-Value Discipline red, first-value window undefined or breached as the norm. Defines first-value per offer in the published style, and maps all five journey phases with named owner, task-triggering due date, and success metric. Current time-to-first-value is measured per client. The 85/40 retention split is validated on own cohort data. Onboarding and renewal become coded M02 SOPs. Breach alerts fire before the window closes. Outcome: window defined and measured, journey map actionable in the CRM, in-window retention tracked against the page split, breach alerts live. Owner: VP of Customer Success with onboarding lead, 5 weeks.
PB-M05-03: Escalation and Churn Response Activation (Predictor Governance)
Trigger: Churn Predictor Governance red, escalation SOP missing or unmet, predictor outside the M07 register, or override rate above 20%. Also opened by routes from M01 AERI overall subscore. Registers the churn predictor in the M07 AI Register with Model Owner and Business Owner, and sets the activation mode from the current AERI score. The escalation SOP is codified in M02 with the published 4, 24, and 72-hour bounds. The override log runs weekly. The escalation path is test-fired on a live or simulated flag. Outcome: predictor registered with both owners, activation mode matches AERI tier, test-fired escalation met every time bound, override log running with the 20% rule, audits scheduled. Owner: VP of Customer Success as Business Owner with data/ML Model Owner, 4 weeks.
PB-M05-04: Retention Loop Monitoring (Amber Path)
Trigger: any M05 dimension amber, or green-state standing maintenance. Also opened by routes from M01 AERI overall subscore. Reviews the weekly recalculation output for new amber and red accounts, tracks the override rate, and confirms expansion flags reached M06 and the concentration feed reached M09. The QBR cadence holds per account with the ROI-first sequence, and quarterly M07 audit results go on file. Outcome: weekly and quarterly cycles running without gaps, routing verified to M06 and M09, trends feeding M13. Owner: VP of Customer Success, standing, with a 30-day pulse check for each amber dimension and green maintenance at the next M13 cycle.
Working templates ship with the module: the client health score config, the churn escalation SOP, and the QBR deck outline. Template artifacts and full playbook bodies are delivered during an engagement.