churn-signal-identification
Churn Signal Identification
Spot the warning signs before customers leave, not after.
How to use
/churn-signal-identificationApply churn signal constraints to this conversation./churn-signal-identification <product>Build a churn early warning system for the described product.
Constraints
The Churn Timeline
Churn has phases. Interventions MUST happen in the early invisible phase, not the decision phase.
- Invisible phase (weeks/months before): subtle behavior changes, slight usage dips
- Consideration phase (days/weeks before): evaluating alternatives, asking about exports
- Decision phase (days before): customer has decided. Usually too late.
- Action phase: cancel, don't renew, stop paying
Signal Categories
MUST monitor all six categories:
- Usage decay: login frequency drops, core action frequency drops, session duration decreases, feature breadth narrows
- Engagement decay: stopped opening emails, unsubscribed from updates, support tickets drop to zero (gave up, not satisfied)
- Team decay: active users on account decreasing, champion goes inactive, no new users added
- Integration decay: disconnected integrations, reduced API calls, stopped syncing
- Financial signals: downgraded plan, reduced seats, disputed invoice, asked about cancellation terms
- Competitive signals: asked about data export, mentioned competitor in support, viewed comparison pages
Signal Weighting
- MUST assign high/medium/low weight to each signal based on historical correlation with churn
- Champion going inactive = critical. Always investigate.
- Support ticket about export = high. Often means they're evaluating alternatives.
- Email open rate drop = low. Only meaningful as part of a pattern.
- NEVER treat a single low-weight signal as actionable. Look for clusters.
Health Scoring
- Green: active usage, growing engagement. No action needed.
- Yellow: some decay signals. Trigger a check-in.
- Orange: multiple decay signals, clear downward trend. Proactive intervention.
- Red: major signals firing, usage near zero. Escalate to retention or senior contact.
Intervention Matching
- Usage decay → re-engagement (personalized outreach, highlight unused features)
- Champion inactive → relationship (reach out directly, connect with replacement)
- Downgrade → value demonstration (ROI review, plan optimization)
- Export/cancellation inquiry → retention (understand the concern, don't hard-sell)
- Competitive signals → positioning (share differentiation, address specific gaps)
- MUST match intervention to signal. Generic "we miss you" emails make things worse.
Anti-Patterns
- Only measuring churn at cancellation — that's measuring failure, not preventing it
- Treating all churn the same (free user vs. enterprise are different problems)
- Bombarding disengaged users with emails and calls — this accelerates churn
- Ignoring involuntary churn (failed payments) which is fixable with dunning
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1