Help me diagnose which of my customers are most likely to churn — and what to do about it — before they cancel.
BUSINESS MODEL: {SaaS_subscription / usage-based / B2C / B2B}
CUSTOMER SEGMENT we're focused on: {SMB / mid-market / enterprise}
DATA AVAILABLE per customer: {tenure / monthly_usage / number_of_users / feature_adoption / support_tickets / contract_length / NPS}
KNOWN CHURN PATTERNS in our history: {what_we've_seen_predict_churn_in_past}
TYPICAL TIME from 'risk signal' to 'cancellation email': {days_weeks}
WHO ACTS on the diagnosis: {CSM / Sales / Founder / nobody_yet}
WHAT WE'RE WILLING TO DO to save an account: {discount / change_csm / executive_call / new_feature_commit}
DESIGN:
1. **A churn risk score** (0-100) composed of 4-6 weighted signals. Be specific about what each signal looks like in our data.
2. **The signals** broken into:
- *Lagging* (already in trouble — usage dropped, tickets up)
- *Leading* (early warning — login frequency, key feature adoption)
- *Behavioral* (champion left, expansion plans canceled, multi-week silence)
3. **3 tiers of risk** with action playbooks:
- *Critical (80-100):* exec save, 7 days
- *Watch (50-79):* CSM intervention, 30 days
- *Healthy (<50):* normal cadence
4. **A 'save email' template** for the Watch tier — sent by CSM, calm, no panic.
5. **An 'exec save call' agenda** for Critical tier — 30 min, structured.
6. **What NOT to do** — common moves that ACCELERATE churn when you can sense it.
7. **Measurement** — how to know whether your save efforts are actually working (vs sampling bias).0 copies·0 saves·4 views
248 words·1,587 chars
Sample output
Model: B2B SaaS subscription. Segment: mid-market ($30K-$200K ARR). Data: tenure (months), MAU vs licensed seats, # admin actions/month, # support tickets, key feature usage flags, NPS quarterly, contract renewal date. Known patterns: decline in admin actions is the strongest predictor — months before users go silent.
1. The churn risk score (0-100):
Weighted sum of 5 signals, each scored 0-100, then weighted:
risk_score =
0.30 × admin_engagement_drop +
0.20 × user_activation_drop +
0.20 × support_signal +
0.15 × champion_signal +
0.15 × contract_signal
This is a starting point — refine weights from your post-mortem churn analysis.
2. The signals:
Admin engagement drop (lagging-but-strong):
Parameters
Text generation parameters
FAQ
The single highest-fidelity churn signal isn't usage — it's the champion changing. Build that into your score before the rest. If a customer's champion takes a job at another company, treat it as Critical until proven otherwise. The prompt targets ChatGPT (GPT-4) and lives in the Analysis & Research category on mycopyprompt.
This prompt is written for ChatGPT (GPT-4). It's a text/chat prompt — paste it into ChatGPT (GPT-4) (or compatible LLMs like Claude or GPT-4) to get the expected output.
1. Click the Copy button on this page to copy the full prompt. 2. Open ChatGPT (GPT-4). 3. Paste the prompt into a new conversation. 4. Replace any {placeholders} with your specifics, then send. Most prompts produce the right output on the first try; complex ones may need 1-2 iterations.
Yes — every prompt on mycopyprompt is free forever. No paywall, no signup wall for browsing or copying. You can use it for personal or commercial work, just don't redistribute the entire mycopyprompt library.
Absolutely — most prompts are templates. Look for {placeholders} (curly braces) and swap them with your own values. You can also reword sections, add constraints, or chain it with other prompts.
See the "Sample output" panel above — that's a real example of what ChatGPT (GPT-4) returns when this prompt runs. Your output will vary in wording but should follow the same structure and depth.
Similar prompts
Matched against every prompt in the catalog by title.
User activation drop (leading):
Support signal (behavioral):
Champion signal (behavioral, highest-fidelity):
Contract signal (lagging):
3. Risk tiers + playbooks:
Critical (80-100) — exec save, 7 days:
Watch (50-79) — CSM intervention, 30 days:
Healthy (<50) — normal cadence:
4. The 'save email' for Watch tier (sent by CSM):
Subject: Quick check on [Customer Org Name] + [Product Name]
Hi [Champion Name],
Wanted to reach out directly. Looking at the data on our end, [specific signal — admin actions dropped, MAU is at X%, etc.] I want to make sure we're not missing something important on your side.
Three ways I'd love to dig in:
1. Are there gaps in how the team is using [product] that we could close together? Sometimes the right onboarding session resets things. 2. Is there a change in your team or your priorities I should know about? No judgment — just want to align. 3. Is there a feature or workflow that's been stuck on 'I wish this worked' for too long? I'd like to surface it to product.
Would you have 30 min in the next 2 weeks for a working session? Not a check-in — I want to come prepared with specific things, and I'd love your honest read.
If we're not the right tool anymore, I'd rather know that too — we'll handle it gracefully. Let me know.
Thanks, [CSM Name]
5. Exec save call agenda (30 min for Critical):
0-5 min: gratitude + framing. ('I asked for this conversation because I noticed [signal] and I wanted to come to you directly.') 5-15 min: listen. Ask: 'What's the honest answer about where we stand? What's worked, what hasn't, what's changed for you?' 15-25 min: my offer. Be specific: 'Here's what I'm willing to do — A, B, or C. Which one would actually help?' 25-30 min: one decision + a date. ('We'll do X by Y. I'll personally check in on Z. Is that a yes?')
Document it in writing within 24 hours. Send to them.
6. What NOT to do:
7. Measurement (so you know if saves are working):
Don't just count 'saves'. Compare:
Report monthly: 'Of the 12 Critical accounts in the last quarter, 7 renewed, 2 churned, 3 are still pending — vs a baseline of 50% renewal for Critical without intervention.' That's the only way to know your save program is real.