Learn / Operational Playbook
The Value Continuity Framework
Four motions. Specific owners. Clear intervention triggers. The Value Continuity Framework is not a description of how post-sale revenue protection works, it is a playbook for how to run it, organized around the signals that determine what happens next.
MeridianARR is a Value Continuity platform for B2B SaaS companies that connects support, onboarding, product friction, customer distress, and renewal risk into post-sale revenue intelligence.
Value Continuity is the discipline of detecting, explaining, and acting on customer signals that threaten recurring revenue before they become churn, contraction, or failed renewals. The framework below is how that discipline becomes an operational system. Each motion has a purpose, a trigger, signal inputs, intervention actions, and a success criterion. Skip to a motion:
Detect
Surface distress signals before they compound
The first motion is signal detection, continuously reading support ticket patterns, product usage trends, onboarding progress, and engagement signals to identify distress before it compounds into churn risk. Detection is not a quarterly review; it is a continuous process run against live account data.
Primary owner
Platform (MeridianARR CDI) + Support leadership monitoring
Trigger
CDI score moves into Watch band (26+) on any account
Signal inputs
- Ticket volume increasing month over month without corresponding usage growth
- Repeated tickets on the same issue within a 60-day window
- Executive escalation filed
- Login frequency declining for 2+ consecutive weeks
- Onboarding milestone missed beyond scheduled date
Intervention actions
| Action | Owner | Timing |
|---|---|---|
| Flag account in CDI dashboard | Automated (MeridianARR) | Immediate on signal threshold |
| Alert assigned CSM of CDI band change | MeridianARR → CS platform | Real-time |
| Route competitor-mention signals to CRO | MeridianARR → CRO | Same-day |
Success criteria for this motion
All Watch-band and above accounts flagged within 24 hours of threshold crossing. No critical-band accounts reaching renewal conversation without prior CDI alert.
Explain
Translate signals into a shared account narrative
Detection produces a CDI score. Explanation turns that score into a story the entire revenue organization can act on. The Explain motion is where MeridianARR connects the underlying signals, specific ticket patterns, specific adoption gaps, specific escalation history, to the account narrative that CS, Support, CRO, and CFO all see the same way.
Primary owner
CS leadership + Support leadership + MeridianARR account view
Trigger
CDI score in Watch band (26+) or account approaching renewal within 180 days
Signal inputs
- CDI score band and 30-day trend (improving, stable, deteriorating)
- Top 3 contributing signals with source (help desk, product analytics, CRM)
- Account ARR value and contract scope vs. usage delta
- Escalation history summary (count, severity, recency)
- Time in current CDI band (how long has this account been at risk?)
Intervention actions
| Action | Owner | Timing |
|---|---|---|
| Generate account distress brief from CDI signals | MeridianARR account view | On-demand or weekly automated |
| Present CDI signals in CS team account review | CS leader | Weekly account review cadence |
| Share CDI risk summary with CFO for ARR forecasting | CRO or CS leader | Monthly or at board prep |
Success criteria for this motion
Cross-functional alignment on which accounts are at risk and why, before the renewal conversation. CFO and CRO operating from the same signal data as CS and Support.
Act
Intervene with the right motion at the right CDI band
The Act motion is the intervention playbook, specific responses tied to specific CDI bands and specific signal types. Not every at-risk account needs the same response. A Watch-band account with a single escalation needs a targeted CS check-in. A Critical-band account with four compounding signals needs executive involvement and a concrete remediation offer.
Primary owner
CS leadership (Watch, At-Risk); CRO + CS (Critical); Product (friction-driven risk)
Trigger
CDI band determines intervention type; signal type determines intervention content
Signal inputs
- CDI band and primary contributing signal (determines who owns response)
- Signal type: product friction vs. engagement gap vs. escalation vs. competitor evaluation
- Account ARR size (determines escalation threshold for executive involvement)
- Days to renewal (determines urgency, same intervention, compressed timeline)
- Prior intervention history (has this account been in At-Risk before? what worked?)
Intervention actions
| Action | Owner | Timing |
|---|---|---|
| Watch band: Targeted CS check-in with specific agenda tied to triggering signal | Assigned CSM | Within 5 business days of band change |
| At-Risk band: CS leadership outreach + product friction report if applicable | CS leader + Product team | Within 48 hours of At-Risk threshold |
| Critical band: Executive escalation, CRO or CEO involvement, concrete remediation offer | CRO | Within 24 hours of Critical threshold |
| Competitor-mention signal (any band): CS + CRO briefed, competitive response initiated | CRO + CS | Same day as signal detection |
Success criteria for this motion
Every At-Risk account has a documented intervention within 5 days of band threshold. Critical-band accounts have a named executive owner and a remediation plan with measurable milestones.
Protect
Turn the renewal from a conversation into a confirmation
The Protect motion begins 180 days before renewal, not 30 days. If Value Continuity signals have been detected, explained, and acted on across the prior motions, the renewal conversation is a confirmation, not a negotiation. Protect is the motion that measures whether the prior three motions worked.
Primary owner
CS leadership + CRO + CFO (for ARR forecast alignment)
Trigger
180-day pre-renewal window opens for every account
Signal inputs
- CDI score at 180 days out vs. 90 days out vs. 30 days out (trajectory matters)
- Intervention history: were Watch/At-Risk signals addressed and resolved?
- Adoption vs. contract scope: is the customer using what they're paying for?
- Executive sponsor stability: same buyer, or new decision-maker?
- Usage trend in the 60 days before renewal conversation (leading indicator of outcome)
Intervention actions
| Action | Owner | Timing |
|---|---|---|
| 180-day mark: CDI review and renewal risk classification (low/medium/high) | CS leader | At 180-day mark |
| 90-day mark: Renewal success plan, what needs to be true for a clean renewal? | CS leader + assigned CSM | At 90-day mark |
| 60-day mark: Executive alignment if CDI is in At-Risk or Critical band | CRO | At 60-day mark if CDI ≥ 51 |
| 30-day mark: Final CDI review; escalate to board if material ARR at risk | CFO + CRO | At 30-day mark |
Success criteria for this motion
Net revenue retention rate improves. Surprise churn (accounts that churned without prior CDI signal) approaches zero. Renewal forecast accuracy improves because signal-based risk replaced CS subjective assessment.
How MeridianARR runs the framework
MeridianARR is a Value Continuity platform for B2B SaaS companies. It automates the Detect motion by continuously reading support, product, onboarding, and engagement signals. It powers the Explain motion through CDI account views that give every revenue-adjacent leader the same signal picture. It enables the Act motion by routing signals to the right owner based on CDI band and signal type. And it makes the Protect motion proactive, starting 180 days before renewal, not 30.
The framework does not work without a platform running it. And the platform is not useful without a framework giving each signal a place in the operational model. MeridianARR and the Value Continuity Framework are designed together.
Frequently asked questions
- What is the Value Continuity Framework?
- The Value Continuity Framework is MeridianARR's operational model for post-sale ARR risk management. It organizes intervention into four motions, Detect, Explain, Act, Protect, each with specific signal triggers, ownership assignments, intervention types, and success criteria. Unlike a lifecycle model organized around CS activities, the Value Continuity Framework is organized around signal data and intervention timing.
- Who owns each motion in the Value Continuity Framework?
- Detect is primarily platform-driven, with Support leadership monitoring CDI thresholds. Explain is owned jointly by CS and Support leadership, producing a shared account narrative. Act is tiered by CDI band: CSMs own Watch-band interventions, CS leadership owns At-Risk, and the CRO owns Critical. Protect is a cross-functional motion owned by CS, CRO, and CFO together in the renewal window.
- How does the Value Continuity Framework differ from a standard CS lifecycle?
- A standard CS lifecycle (Onboard → Adopt → Expand → Renew) is organized around what CS teams do. The Value Continuity Framework is organized around what the signals say. The same four lifecycle phases exist, but each phase has specific signal thresholds, intervention triggers, and ownership rules, making it an operational playbook rather than a stage description.
- When should the Protect motion begin?
- The Protect motion begins 180 days before renewal, not 30 or 60 days. Accounts with high CDI scores approaching renewal with only 30 days of intervention time have far lower recovery rates than accounts where distress signals were caught and addressed at the 180-day mark. Value Continuity is specifically designed to extend the intervention window.
- What is the relationship between the Value Continuity Framework and the Customer Distress Index?
- The Customer Distress Index (CDI) is the measurement instrument that powers all four motions. CDI scores trigger the Detect motion, are explained in the Explain motion, determine the intervention tier in the Act motion, and are the primary risk metric tracked in the Protect motion. The CDI does not exist independently of the framework, it is the measurement system the framework operates on.