đ Works best with your payments and survey sheet. Connect Stripe or Whop and Google Sheets and Jeremy AI reads your cancels for you. It only writes drafts.
Find out why members left, what to ship this week, and how to write to the ones worth winning back.
You'll see the cancellations pasted in with the hard rule, the ranked themes, the five reasons, the five things to ship and the win-back drafts. Nothing is sent.
What this use case does and who it's for
You paste six months of cancellation reasons. Jeremy AI groups them into themes and ranks them by count. It writes "five reasons they left, five things to ship this week." Then it drafts a short win-back message for each of your top 3 segments, and saves everything as one Markdown file.
It's for coaches, community owners and info-product owners who have cancellations and no clear picture of why. Most people read cancel reasons one at a time. This shows you the pattern.
Win-back messages here are drafts only. Nothing is sent. The prompt also locks in a hard rule: the fixes and the drafts stay about the product. No discounts, no pause offers, no downgrades, no "we'll work something out."
What you need before you start
A Jeremy AI account. Nothing to connect to try the sample.
Your cancel reasons from the last 6 months. The sample uses 30. Number them.
For each one: how long they were a member, when they left, and what they said. First names are optional. Leave them out if you like.
Your price and any offer details you'd mention to a returning member.
How to set it up
You use the default Jeremy AI worker. There's nothing to build.
Open Jeremy AI and start a new chat.
Check the worker selector says Jeremy AI.
Paste the prompt below, with your cancellations in place of the sample ones.
Click Send message.
Wait. In the walkthrough, Jeremy AI reads all 30 cancellations in about a minute, and the video runs that part at 4x speed. The answer lands as a file card, one Markdown (.md) file.
Open the file card. Scroll the ranked themes, the five reasons, the five things to ship, and the win-back drafts.
Check the counts against your own tally. They should add up to your total.
Read every draft before you use it. Copy it into your own email tool and send it yourself.
The prompt
This is the exact prompt from the walkthrough. The community, the members and the reasons in it are SAMPLE and made up. Replace them with yours.
The prompt ends with a HARD RULE paragraph. Keep it. It's what stops the fixes and drafts from suggesting pauses, discounts, downgrades or "we'll work something out."
Run a churn autopsy on these SAMPLE (made-up) cancellations from a made-up community, "SAMPLE Launchpad Community". Use ONLY the list below. Don't invent reasons or counts.
Give me: 1) the cancel reasons grouped into themes, ranked by count, with the member numbers in each; 2) "Five reasons they left, five things to ship this week"; 3) one short win-back message DRAFT for each of the top 3 segments (drafts only, no discounts offered, nothing sent). Save it as ONE concise Markdown (.md) file.
CANCELLATIONS:
1. Ava (SAMPLE), left Oct 2026, 2 months a member: "Too expensive for my budget right now"
2. Ben (SAMPLE), left Sep 2026, 5 months a member: "I never had time to watch the lessons"
3. Cara (SAMPLE), left Aug 2026, 1 months a member: "Haven't made any sales yet"
4. Dan (SAMPLE), left Jul 2026, 4 months a member: "Couldn't find the lessons in the portal"
5. Eli (SAMPLE), left Jun 2026, 6 months a member: "$197 a month is more than I can justify"
6. Fay (SAMPLE), left May 2026, 2 months a member: "Fell behind and felt guilty"
7. Gus (SAMPLE), left Oct 2026, 3 months a member: "Joined a different program"
8. Hana (SAMPLE), left Sep 2026, 3 months a member: "Didn't see results in 3 months"
9. Ian (SAMPLE), left Aug 2026, 2 months a member: "Cheaper options exist"
10. Jo (SAMPLE), left Jul 2026, 5 months a member: "Closed my business"
11. Kai (SAMPLE), left Jun 2026, 1 months a member: "Too busy with clients"
12. Lia (SAMPLE), left May 2026, 4 months a member: "Portal is confusing"
13. Max (SAMPLE), left Oct 2026, 6 months a member: "Didn't like the call times"
14. Nia (SAMPLE), left Sep 2026, 2 months a member: "Cutting costs this quarter"
15. Oz (SAMPLE), left Aug 2026, 3 months a member: "No new clients after following the steps"
16. Pia (SAMPLE), left Jul 2026, 3 months a member: "Moved to another coach's community"
17. Quin (SAMPLE), left Jun 2026, 2 months a member: "Couldn't keep up with the weekly pace"
18. Rae (SAMPLE), left May 2026, 5 months a member: "Never found the templates"
19. Sol (SAMPLE), left Oct 2026, 1 months a member: "Had a baby, stepping back"
20. Tess (SAMPLE), left Sep 2026, 4 months a member: "Price went up and I can't swing it"
21. Uma (SAMPLE), left Aug 2026, 6 months a member: "Expected faster results"
22. Vik (SAMPLE), left Jul 2026, 2 months a member: "Card expired and forgot to update it"
23. Wes (SAMPLE), left Jun 2026, 3 months a member: "Work got hectic, no time"
24. Xia (SAMPLE), left May 2026, 3 months a member: "Found a similar program with live support"
25. Yan (SAMPLE), left Oct 2026, 2 months a member: "Wanted 1:1 coaching instead"
26. Zed (SAMPLE), left Sep 2026, 5 months a member: "Still at zero leads"
27. Abe (SAMPLE), left Aug 2026, 1 months a member: "Can't afford it after my slow month"
28. Bea (SAMPLE), left Jul 2026, 4 months a member: "Fell behind after vacation"
29. Cy (SAMPLE), left Jun 2026, 6 months a member: "Too many places to look"
30. Dee (SAMPLE), left May 2026, 2 months a member: "Moving countries, pausing everything"
HARD RULE: the "five things to ship this week" fixes and the win-back drafts must NEVER mention or suggest pausing, discounts, downgrades, cheaper tiers, price changes or financial flexibility (no payment plans, no "we'll work something out"). Fixes must be only about product, onboarding, results, support and community. For price-related cancellations, just group them as a theme; do not propose any money-related fix or offer in the drafts.
Prompting tips and how to adapt it
Number every cancellation. Each theme lists the member numbers behind it, so you can spot-check it.
Keep "Use ONLY the list below." It stops invented reasons and counts.
Quote their words. Paste what the member actually said, not your summary of it.
Include tenure and the date they left. It shows you whether people leave early or late.
Keep the HARD RULE paragraph. It limits the fixes to product, onboarding, results, support and community. Price complaints still get grouped as a theme. They just don't turn into a money-related offer.
Keep "drafts only." Nothing leaves the chat.
Save it as ONE Markdown file. The prompt asks for it, so the answer lands in a file card you can open and edit.
Run it every quarter. Paste a fresh batch and compare the rankings. Did the fixes move the numbers?
Change the segments. Want drafts for the top 5, or only for people who stayed 4+ months? Edit item 3. Keep the HARD RULE in place.
The result to expect
One Markdown file (in the walkthrough it's a sample Launchpad churn autopsy) with:
The cancel reasons grouped into themes, ranked by count, with the member numbers in each.
"Five reasons they left, five things to ship this week."
A short win-back draft for each of the top 3 segments.
With the sample data, the 30 cancellations rank like this:
Price: 6.
Time and pace (fell behind): 6.
No results: 5.
Portal: 4.
Competitor: 3.
Life events: 2.
Four more themes with one member each. One of them is an expired card.
That adds up to 30. Ranks 1 and 2 tie at 6, so the order can differ. Wording and grouping change between runs. Check that the counts add up to your total and that each member sits in one theme.
The five reasons they left. In the video they read like this: the value story never landed before the price did, falling behind had no on-ramp back, the first win took too long to arrive, the portal hid the product, and live human support was the difference-maker but lived somewhere else.
The five things to ship this week. All five are product and experience fixes:
A "Start Here" roadmap.
A "Week-One Quick Win."
A "Restart Here" flow for members who fell behind.
Weekly live calls plus accountability pods.
A product-only win-back sequence.
The win-back drafts. There are 3, one each for the price, time/pace and no-results segments. None of them mention a pause, a discount, a downgrade or flexible payment. They talk about what's changed in the product. For example, the price draft opens with "We rebuilt the front door of Launchpad." The time draft says "Fell behind? There's a restart button now." Nothing is sent.
These are sample numbers and sample members. Your own cancellations will give you your own themes.
Common mistakes and fixes
The counts don't add up. Count by hand. If the total's off, send the prompt again.
Themes are merged differently than you expected. Both can be right. Ask Jeremy AI to split or merge them how you like.
A fix or a draft brings up money or flexibility. Delete that line before you use it. Then check the HARD RULE paragraph is still at the end of your prompt. Win-back messages should talk about what's changed in the product.
Price shows up as the top theme and you want a price fix. The prompt only groups it as a theme. Look at why the value didn't land first, such as the roadmap and the first win.
You expected it to send the messages. It doesn't. Copy the drafts and send them yourself.
The answer isn't a file. Keep "Save it as ONE concise Markdown (.md) file" in the prompt.
Real names in the paste. You don't need them. Number the reasons and drop the names.