Learn / Scoring Model
The Customer Distress Index
The Customer Distress Index (CDI) is MeridianARR's account-level ARR risk score, a number from 0 to 100 that summarizes how many distress signals an account is showing, how severe they are, and how they compound. This page explains the score bands, the compounding model, and what each band means for intervention priority.
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.
CDI score bands and what they mean
The CDI does not produce a binary at-risk / not-at-risk classification. It produces a continuous score across four bands, each with a distinct interpretation and prescribed intervention response. Understanding the bands is essential to using CDI for triage.
- What this score means
- No material distress signals. The account is logging in, engaging with CS, resolving support tickets without escalation, and progressing through onboarding milestones on schedule.
- What it does not mean
- A CDI of 0–25 does not mean the account will definitely renew. It means no leading indicators of risk are currently visible. Maintain standard CS motion.
- Prescribed intervention
- Standard renewal cadence. No intervention required. Monitor for signal emergence 90+ days before renewal.
- What this score means
- One or more distress signals are present but have not yet compounded. Common triggers: moderate ticket volume increase, a single escalation, an onboarding milestone slipping, or declining login frequency in a subset of users.
- What it does not mean
- A CDI of 26–50 does not mean churn is likely, it means the account needs a closer look. A single signal may resolve without intervention. But left unmonitored, watch-band accounts account for a disproportionate share of surprise churn.
- Prescribed intervention
- CS check-in with specific agenda tied to the triggering signal. Do not run a generic QBR, address the specific friction. Increase monitoring frequency.
- What this score means
- Multiple distress signals are present and have begun compounding. Common combinations: recurring support tickets on the same issue + declining engagement, or an escalation + reduced feature adoption. The account is in the distress-to-churn pathway.
- What it does not mean
- A CDI of 51–75 does not mean the account will churn, it means the window to prevent churn is open but closing. At-risk accounts that receive targeted intervention in this band show materially higher retention rates than those flagged at renewal time.
- Prescribed intervention
- Executive-level CS engagement. Direct outreach from CS leadership or CRO. Specific product or support resolution plan with committed timeline. Involve product team if friction is a product issue. Set CDI re-evaluation checkpoint in 30 days.
- What this score means
- Severe compound distress. Typical patterns: executive escalation + competitor mention + declining logins, or prolonged unresolved friction (8+ tickets on same issue) + CS disengagement + billing query. At this score, the customer has likely already begun evaluating alternatives.
- What it does not mean
- A CDI of 76–100 does not mean churn is certain, some critical-band accounts are recoverable, particularly if the distress has a discrete cause (a product bug, an implementation gap) that can be resolved with urgency. But recovery at this band requires more than a check-in call.
- Prescribed intervention
- Emergency escalation protocol. CRO or CEO involvement if account size warrants. Concrete remediation offer, not a meeting, an action. Recovery plan with measurable milestones. Reassess ARR risk in financial forecast.
How signals compound in the CDI model
Individual distress signals carry limited predictive weight in isolation. Customer distress is a pattern, signals accumulate and reinforce each other. The CDI model weights signals in combination, not just individually. The table below shows how compounding works for a common signal sequence.
| Signal combination present | CDI impact | Why it compounds |
|---|---|---|
| Low (+8–12 points) | One escalation resolved promptly has limited predictive weight. Context matters, executive or operational? |
| Moderate (+22–28 points) | Escalation driven by a pattern of unresolved issues signals systemic product friction, not a one-time incident. |
| High (+38–45 points) | Product friction + executive dissatisfaction + disengagement is a three-signal compound pattern with strong churn predictive power. |
| Critical (+58–70 points) | All prior signals plus active competitor evaluation. This four-signal compound puts virtually any account in the critical band regardless of starting state. |
CDI impact ranges are illustrative. Actual scores depend on signal severity, account context, and recency weighting.
What the CDI reads, and what it does not
The CDI is built from five categories of Value Continuity signals. It is important to understand both what it includes and its deliberate scope boundaries.
CDI reads
- Support ticket volume, escalation history, repeated issues, content signals
- Product adoption gaps, feature friction, activation milestone completion
- Onboarding progress, implementation status, time-to-value trajectory
- Login frequency trends, CS response rate, executive sponsor changes
- Contract scope vs. usage, billing interaction patterns
CDI does not replace
- CS judgment about relationship quality and strategic fit
- Sales pipeline data or expansion opportunity forecasting
- Product roadmap alignment or NPS/CSAT benchmarking
- Help desk SLA management or agent performance tracking
MeridianARR replaces the CS platform for B2B SaaS teams that need native support intelligence. The CDI is the account risk signal, built from the distress signals that live in support and product data, which CS health score models are not designed to read.
Using CDI scores in practice
CROs use CDI to pressure-test net revenue retention forecasts: which accounts in the "expected to renew" bucket have CDI scores above 50? CFOs use CDI to quantify the ARR at risk from distress-band accounts. CS leaders use CDI to prioritize their team's attention by signal severity rather than renewal date. Support leaders use CDI to demonstrate that their team's data is a revenue intelligence input, not just an operational cost metric.
MeridianARR is a Value Continuity platform for B2B SaaS companies that makes this cross-functional visibility possible, giving every revenue-adjacent leader access to the same account-level risk picture, built from the same underlying signal data.
Frequently asked questions
- What is the Customer Distress Index?
- The Customer Distress Index (CDI) is MeridianARR's account-level ARR risk score, calculated from support interaction patterns, product usage signals, onboarding status, engagement trends, and financial risk indicators. It ranges from 0 (no detected distress) to 100 (severe compound distress). CDI is designed to give CROs, CFOs, CS leaders, and Support leaders a shared, signal-based view of which accounts are at risk and why.
- What does a high CDI score mean?
- A high CDI score means an account is exhibiting multiple distress signals across multiple signal categories, and is therefore at elevated risk of churning, contracting, or failing to renew. Scores above 50 indicate the account has entered the distress-to-churn pathway. Scores above 75 indicate severe compound distress requiring immediate intervention.
- Why do signals compound in the CDI model?
- Customer distress rarely follows a single signal. It follows a pattern: one signal emerges, it goes unresolved or unnoticed, which leads to additional signals, escalations, disengagement, competitor evaluation. In the CDI model, signals are weighted not just individually but in combination, because compound signals have materially higher churn predictive power than any individual signal alone.
- How is the CDI different from CS health scores?
- CS health scores are typically built from CRM engagement data, product login frequency, and CS team assessments. The CDI is built from support-signal data instead: ticket patterns, escalation history, issue repetition, and content signals like competitor mentions that CS health score models are not designed to read. Because MeridianARR owns the support data natively, the CDI detects churn risk earlier and more accurately than CS health scores. For B2B SaaS teams using MeridianARR, the CDI replaces the CS health score as the primary account risk signal.
- Which accounts should be prioritized based on CDI?
- Prioritize critical-band accounts (76–100) for immediate intervention, with at-risk accounts (51–75) as the second tier. Watch-band accounts (26–50) should have increased monitoring frequency and a specific CS check-in focused on the triggering signal. Healthy accounts (0–25) maintain standard cadence, but watch for signal emergence as they approach renewal windows.