💼 Business
Churn Post-Mortem from CRM Export Notes (No Invented Reasons)
Write a churn post-mortem from pasted CRM notes. No invented reasons, save amounts, or competitor names.
0Reviews
Prompt
Act as a customer-success lead writing a churn post-mortem from CRM export notes. You reconstruct what the CRM actually recorded. You do not invent a churn reason, a save offer, a competitor, or a revenue number. This is not a QBR narrative and not a win/loss interview script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Account and close/churn date: [Account] - Pasted CRM notes and fields (ARR, plan, reason picklist, tickets): [CRM] - People and roles in the notes: [People] - Product areas named in notes: [Product] - Save attempts I can prove: [Saves or NONE] - Competitor named in CRM (or NONE): [Competitor] - What I want decided next: [Decision] - Words I must not use: [Banned] - Word budget: [Budget or 450] - Audience inside the company: [Audience] Generate: 1. Honesty ledger: ARR, dates, picklist reason, tickets, people, competitor from CRM. Forbidden: reasons not in notes, save math not in Saves. 2. Timeline: dated facts only. If a date is missing, write undated note rather than guessing. 3. Stated reason vs evidence: quote the picklist and the free-text. If they conflict, say so. Do not pick a nicer reason. 4. Save attempts: only Saves. If NONE, write no save attempt in this export. 5. Product links: only Product areas named. Do not add a roadmap item. 6. Decision memo: only Decision. If blank, write none requested. 7. Open questions: five gaps the CRM did not answer. 8. Compliance pass: quote Banned words, invented competitor, invented ARR. Cut them. Print word count vs Budget. Constraints: - Churn post-mortem from CRM notes, not a QBR and not a case study. - Never invent a churn reason, competitor, or dollar amount. - Do not write customer quotes that are not in CRM. - Stay under Budget words. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Account: Harbor Bookkeeping LLC, churn effective 2026-08-15 CRM: ARR 588 USD annual, plan Studio. Picklist reason: missing payroll. Free text 2026-07-02 Omar: they asked if payroll was on the 2026 roadmap, I said not this year. Ticket CS-441 2026-07-18: export CSV of invoices failed twice, then succeeded. No NPS. No competitor field filled. People: Omar Singh CS; Priya Shah champion at Harbor (email in CRM) Product: invoicing, WA sales tax. Payroll not in product. Saves: NONE recorded. No discount offer in CRM. Competitor: NONE Decision: should CS flag payroll-gap accounts before renewal at 90 days Banned: they loved us, 12 percent save rate, QuickBooks won Budget: 450 Audience: VP CS and Head of Product
Example Output
1. Ledger. Harbor Bookkeeping LLC. Churn 2026-08-15. ARR 588 USD annual, Studio. Picklist: missing payroll. Note 2026-07-02 Omar: payroll not this year. Ticket CS-441 2026-07-18 invoice CSV failed twice then succeeded. Champion Priya Shah. CS Omar Singh. Competitor NONE. Saves NONE. Product: invoicing, WA sales tax. Forbidden: QuickBooks, 12 percent save, they loved us, invented quote. 2. Timeline. 2026-07-02 payroll roadmap ask, answer not this year. 2026-07-18 CS-441 CSV flake then success. 2026-08-15 churn effective. Undated: NPS (not in CRM). 3. Reason. Picklist missing payroll. Free text agrees. CSV ticket is separate and resolved; do not promote it to the reason. Do not rewrite as price. 4. Saves. NONE recorded. No discount. 5. Product. Invoicing and WA sales tax are in notes. Payroll is absent. No roadmap date beyond not this year. 6. Decision. Should CS flag payroll-gap accounts 90 days before renewal. Audience VP CS and Head of Product. 7. Open questions. 1) Who decided churn on their side. 2) Whether CSV flake mattered. 3) Competitor none in CRM. 4) Whether 588 USD is still accurate. 5) 90-day flag process owner. 8. Compliance. Cut banned words. Word count under 450. Not a QBR. Gaps: usage metrics, contract end vs 2026-08-15, email body. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.