CRMTypical lead time: 60–120 daysFalse-positive risk: Medium
Stalled expansion pipeline
An account approaching renewal with no open expansion or upsell opportunity, after a history of regular pipeline creation. Healthy accounts generate commercial motion; silence here means nobody inside is building a case to stay.
Detection logic
Compare opportunities created per account per quarter against the account's own 4-quarter baseline. Flag accounts in the final 120 days before renewal with zero open opportunities where the baseline is 1+.
When it lies to you
Some enterprise accounts buy on multi-year cycles with genuinely quiet middle years. Check contract structure before flagging.
CRMTypical lead time: 30–90 daysFalse-positive risk: Medium
Renewal close-date slippage
The renewal opportunity's close date is pushed repeatedly. One push is scheduling; three pushes is the customer telling you — politely — that signing is not a priority.
Detection logic
Count close-date changes on the renewal opportunity in the last 90 days via field history. Flag at 2+ pushes, escalate at 3+.
When it lies to you
Procurement calendars, budget freezes, and M&A can push dates without churn intent. Cross-check with champion engagement before acting.
CRMTypical lead time: 45–120 daysFalse-positive risk: Medium
Champion goes quiet
No logged activity (calls, emails, meetings) with the identified champion for 30+ days in an account that previously had weekly or biweekly contact. Relationships cool before contracts do.
Detection logic
For each account, track days since last activity logged against the champion contact role. Flag at 30 days, escalate at 45.
When it lies to you
Champions take leave; activity sometimes gets logged against the account but not the contact. Verify the contact-role mapping first.
CRMTypical lead time: 30–120 daysFalse-positive risk: Medium
Risk language in activity notes
Phrases like “evaluating alternatives”, “budget cut”, “leadership reviewing vendors” appear in call notes, tasks, or emails logged to the account. Reps hear the truth and write it down — then nobody reads it.
Detection logic
Keyword and phrase scan over activity descriptions and email bodies logged in the last 90 days. Keep the phrase list short and review hits manually — context matters.
When it lies to you
Negotiation posturing: “we're looking at competitors” is often a discount play. Distinguish one mention from a pattern across multiple touches.
CRMTypical lead time: 30–90 daysFalse-positive risk: Low
Support cases spike pre-renewal
Cases linked to the account rise sharply in the two quarters before renewal. A rough last mile poisons the renewal conversation no matter how good the year was.
Detection logic
Join case records to the account; compare case count in the last 90 days against the prior 90. Flag at 2x baseline or 3+ P1/P2 cases.
When it lies to you
A platform-wide incident spikes every account at once — check whether the spike is account-specific before flagging.
CRMTypical lead time: 30–60 daysFalse-positive risk: Medium
Contract redlines multiply
Legal and procurement touches on the renewal paperwork run well above the prior term's count. Heavy redlining often means the deal is being re-justified from scratch.
Detection logic
Count contract versions, legal tasks, or procurement activities on the renewal vs the previous term. Flag at 2x prior-term activity.
When it lies to you
New procurement leadership or a first enterprise-grade MSA can inflate redlines without churn intent. Check who is driving the markup.
