Learn · Taxonomy
Value Continuity Signal Taxonomy
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.
This page is a reference taxonomy, five categories of signals, organized by type, source, severity, and lead time. Each entry includes what distinguishes a true signal from a false positive.
Behavioral signals
Actions customers take, or stop taking, inside the product. These signals are observable without any customer communication.
Declining login frequency
Lead time: 90–180 days before churn
What it tells you: Users are finding less reason to return. Unlike a one-time dip, a sustained downward trend in session frequency indicates disengagement from the product's core value loop.
Distinguish from: Seasonal dips or planned breaks, look for sustained trend over 3+ weeks, not a single low-activity period.
Feature adoption below contract scope
Lead time: 60–150 days before churn
What it tells you: The customer is paying for capabilities they are not using. In a budget-scrutiny environment, this creates build-vs-buy pressure: they may conclude a simpler, cheaper solution covers what they actually use.
Distinguish from: Planned phased rollout, check whether low adoption is intentional (onboarding plan) or unplanned.
User avoidance of core workflows
Lead time: 60–120 days before churn
What it tells you: Users have found friction in a workflow and are routing around it, either using alternative processes or abandoning the workflow entirely. Avoidance often precedes a support ticket, or explains why tickets on a feature stopped after the friction wasn't resolved.
Distinguish from: Workflow redesign or deliberate feature deprecation on the customer's side.
Operational signals
Signals that appear in support and service systems, ticket patterns, escalation history, resolution trends. These are the highest-density source of early churn signal.
Repeated tickets on the same issue
Lead time: 60–120 days before churn
What it tells you: The product has an unresolved friction point the customer keeps hitting. Each recurrence erodes the customer's confidence that the issue will be resolved and increases the probability that they stop trying, by switching products.
Distinguish from: Multiple users filing the same issue type (normal) vs. one account filing the same issue repeatedly (distress signal).
Escalation to customer leadership
Lead time: 30–90 days before churn
What it tells you: Normal support channels have failed to resolve the issue to the customer's satisfaction, and someone with authority has been pulled in. Executive involvement in support interactions is a high-confidence churn signal, these accounts rarely renew without direct intervention.
Distinguish from: Proactive executive engagement (a VP joining a QBR), look specifically for escalations triggered by unresolved support issues.
Competitor name mentioned in ticket
Lead time: Immediate, requires same-day response
What it tells you: The customer is actively researching or evaluating alternatives. This is the most time-sensitive Value Continuity signal, it often appears 2–6 weeks before a formal churn notification.
Distinguish from: Generic industry references (a customer asking 'does this integrate with Salesforce') vs. evaluative language ('we are testing Competitor X alongside this').
Increasing ticket volume without usage growth
Lead time: 90–150 days before churn
What it tells you: Rising support volume while product usage stays flat or declines indicates that friction is accumulating, not that adoption is growing. More tickets with no corresponding increase in value delivery is a distress pattern.
Distinguish from: Rising tickets alongside rising usage, which can indicate onboarding growth.
Relational signals
Signals about the customer relationship itself, who is engaged, who has left, and how responsively the customer interacts with CS teams.
Executive sponsor departure
Lead time: Can occur at any time; risk materializes within 90 days
What it tells you: The person who championed the purchase has left. New stakeholders inherit tools they did not choose and often re-evaluate them early in their tenure. Without proactive re-onboarding and value demonstration, churn risk is significantly elevated.
Distinguish from: Lateral moves within the same organization, focus on situations where the champion leaves the company entirely or moves to a non-buyer role.
Reduced CS response rate
Lead time: 60–120 days before churn
What it tells you: A customer who was previously responsive has gone quiet. Silent accounts are not neutral, they are often processing a decision. Outreach that receives no response, especially from an account that was previously engaged, is a distress signal that warrants investigation through product and support data.
Distinguish from: Temporarily busy contacts (confirm via product usage) vs. accounts that are also declining in product engagement.
Financial signals
Signals that appear in billing, procurement, and contract interactions. These tend to appear later in the distress cycle, but carry high confidence when they do.
Billing dispute or pricing question
Lead time: 90–150 days before renewal
What it tells you: The customer is scrutinizing the ROI of the product, often because internal budget pressure has arrived or because they are dissatisfied with value delivery and looking for a reason to reduce spend.
Distinguish from: Administrative billing questions (wrong invoice amount, payment method update) vs. evaluative questions ('can you justify this pricing for what we're using?').
Contract scope reduction request
Lead time: 60–120 days before renewal
What it tells you: The customer has already decided to pay less. This is a high-confidence contraction signal. The goal shifts from preventing reduction to minimizing scope loss and preserving the relationship for future expansion.
Distinguish from: Strategic downsizing (org restructuring) vs. value-driven reduction (dissatisfaction with ROI).
Onboarding and activation signals
Signals specific to the earliest phase of the customer lifecycle. Activation signals have the longest lead time of any Value Continuity signal, but they predict the most consequential churn outcomes.
Missed first value milestone
Lead time: 0–60 days post-contract
What it tells you: The customer has not yet experienced the product's core value. First value milestones, the moment a customer first realizes why they bought the product, are the strongest predictor of long-term retention. Missing this milestone in the first 60 days is the highest-confidence early churn signal.
Distinguish from: Planned delayed activation (phased rollout with documented start date) vs. unplanned activation failure.
Integration or implementation delay
Lead time: 0–90 days post-contract
What it tells you: The customer cannot use the product at full capacity because a technical dependency is incomplete. Time-to-value gaps created by implementation delays directly reduce the probability of renewal, especially if the delay extends past 30–60 days post-contract.
Distinguish from: Delays caused by the customer's internal IT queue (manageable) vs. delays caused by product issues or onboarding failures (high risk).
How MeridianARR uses this taxonomy
MeridianARR monitors all five signal categories continuously. They are the inputs to the Customer Distress Index (CDI), an account-level ARR risk score that weights signals by severity and lead time, and accounts for compounding (two medium-severity signals from different categories score higher than one alone).
For the full scoring model, how CDI bands work and what each score range means, see the Customer Distress and ARR Risk page. For how signals map to the four ARR motions, see the Value Continuity Framework.
Frequently asked questions
- What are Value Continuity signals?
- Value Continuity signals are customer behaviors, interactions, and data points that indicate whether a B2B SaaS customer is realizing value from a product, or at increasing risk of churning, contracting, or failing to renew. They span five categories: behavioral (product usage patterns), operational (support and ticket data), relational (CS engagement and sponsor changes), financial (billing and contract interactions), and onboarding (activation and implementation status).
- Which category of Value Continuity signal has the longest lead time?
- Onboarding and activation signals have the longest lead time, appearing 0–60 days post-contract but predicting churn that occurs at the 12-month renewal. Behavioral signals like declining login frequency appear 90–180 days before churn. Operational signals like competitor mentions in tickets are the most time-sensitive, requiring same-day response.
- How does MeridianARR use this signal taxonomy?
- MeridianARR monitors all five categories of Value Continuity signals continuously and combines them into the Customer Distress Index (CDI), an account-level ARR risk score. Each signal category contributes to the CDI, with severity and lead time factored into the weighting. CROs, CFOs, CS leaders, and Support leaders see the CDI and the underlying signals that compose it.
- What is the difference between a behavioral and an operational signal?
- Behavioral signals are passive, they reflect what customers do inside the product without any direct communication. Operational signals come from the support system: the tickets, escalations, and interactions where customers actively communicate their frustrations. Both are important; operational signals tend to be higher-confidence because they represent explicit customer communication.