PromptSharpPrompt LibrarySales › Churn post-mortem: what was knowable, and when

Account GrowthFREE

Churn post-mortem: what was knowable, and when

An account left and the account team has a story. Reconstruct what the record actually shows and find the point where it was still saveable.

The prompt — copy and run it

You are a retention analyst running a blameless churn post-mortem. I will paste the account history. Be direct — a comfortable post-mortem teaches nothing.

Produce:

A) THE TIMELINE: the account's history as evidenced in my material, marking each point where a signal appeared, what was done about it, and how long the gap was between the signal and any response. Separate what the record shows from what the team believes.

B) THE DECISION POINTS: the two or three moments where a different action plausibly changes the outcome, what the available information supported doing at that moment, and the honest entry "not visible at the time" for anything only obvious in hindsight.

C) THE PATTERN CHECK: which of these signals would be detectable in other accounts today from data we already collect, the specific check that would surface them, and the stated churn reason compared against what the timeline actually supports — these often disagree.

Inputs: [ACCOUNT HISTORY: USAGE OVER TIME, SUPPORT CONTACTS, STAKEHOLDER CHANGES, QBR NOTES, INVOICES OR CONTRACT CHANGES] · [STATED CHURN REASON] · [WHAT THE TEAM BELIEVES HAPPENED] · [WHAT WE MONITOR ACROSS OTHER ACCOUNTS TODAY]

Rules: Do not invent events, sentiment, or motives the record does not support — write "not in the record" and never assign blame to a named individual. Use roles and internal account IDs, never customer names or personal data. Keep confidential CRM, deal, and customer data out of consumer AI tools and follow your employer's AI-use policy. This reads the record; the account team's context still matters and should be added, not overwritten. Verify the timeline against the support, billing, and usage record before this post-mortem circulates.

How to use this prompt

  1. Copy the full prompt above with the Copy button.
  2. Fill in your inputs. Replace each bracketed placeholder with your specifics: [STATED CHURN REASON][WHAT THE TEAM BELIEVES HAPPENED][WHAT WE MONITOR ACROSS OTHER ACCOUNTS TODAY]
  3. Paste into ChatGPT, Claude, or Gemini and run. Read the reality guardrail below before you act on the output.

Why this prompt works

Churn post-mortems converge on the exit-interview reason, which is usually the most polite answer rather than the true one, and the same failure repeats. Separating the evidenced timeline from the team's narrative surfaces the disagreement, and demanding the honest "not visible at the time" label prevents hindsight from producing a lesson nobody could actually have acted on.

Get a prompt like this every day

The PromptSharp Sales Brief ships one desk-ready prompt every weekday — free on the web today. Free forever. Today's Sales issue is live on the web right now — subscribe and we email you the sample issue immediately, then the Sales daily every weekday as its email edition ships. Unsubscribe anytime.

Subscribe free → Read a sample issue
Reality guardrail: this prompt makes the model reason from data you paste — it does not source or verify facts for you. Check every claim, keep confidential data out of consumer AI tools, and follow your employer's AI-use policy.

Frequently asked

When should I use this prompt?

An account left and the account team has a story. Reconstruct what the record actually shows and find the point where it was still saveable.

Why does this prompt work?

Churn post-mortems converge on the exit-interview reason, which is usually the most polite answer rather than the true one, and the same failure repeats. Separating the evidenced timeline from the team's narrative surfaces the disagreement, and demanding the honest "not visible at the time" label prevents hindsight from producing a lesson nobody could actually have acted on.

What mistake does this prompt help you avoid?

Post-mortems that adopt the stated churn reason and blame an individual — the evidenced timeline is separated from the team narrative and hindsight-only findings are labelled as such.

Related Sales prompts

Sales

Account expansion map: whitespace, warm paths, and the renewal story

QBR season. Turn usage data and org knowledge into an expansion plan the account team can actually execute.…

Sales

Renewal risk read: a QBR prep that surfaces churn before it's a surprise

Renewal is 90 days out and you're not sure where you stand. Build a QBR that reads the account honestly and catches churn signals …

Sales

Slipped-deal autopsy: find the pattern that keeps pushing the quarter

The same deals slip every quarter and the post-mortem always blames the customer's timeline.…

Sales

Account research brief: from raw filings to a first-touch angle

You have 30 target accounts and one hour. Turn one account's public footprint into a brief you can actually open a conversation wi…

Sales

Build the fit scorecard from your own closed-won and closed-lost

Everyone has an ICP slide and nobody built it from data. Derive the account-fit scorecard from the deals you actually won and lost…

Sales

Win-loss read: what actually correlates with winning here

Everyone has a theory about why deals close. Test the theories against your own closed deals and find which ones the data can supp…

Sales

Stage hygiene audit: which deals are sitting where they do not belong

The forecast is only as honest as the stage definitions. Audit the pipeline against the exit criteria and find the deals that were…

All Sales free prompts

The PromptSharp Sales Brief page — five full free prompts plus today's issue.

PromptSharp Daily — free

The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. Two things in one brief: you get better at AI and prompting, and you see the sharpest prompts from across the network.

Double-opt-in. Unsubscribe anytime. No spam, ever.

Better together
Make prompts remember you: Brainfile

Even a sharp prompt starts from zero unless your AI knows you. Brainfile is persistent context — your work, voice, and priorities loaded into every session. Brainfile is the memory; PromptSharp is the playbook. Together they compound — the same prompt gets sharper because it runs on YOUR context.

Set up your brainfile →

Want both? The All-Access + Brainfile annual bundle covers the pair.

PromptSharp — sharp prompts for professionals.
Home · Daily Issues · Prompt Library · Glossary · Pricing · For Teams & Universities · Archive · PromptFluent alternative · Newsletter · Privacy · Terms · Refunds
Verticals
Marketing · Sales · Dev & Engineering · Finance · Product Management · Vibe Coding · C-suite · Consulting & Strategy · Law · CPG · Personal Finance · Career & Job Search · Trading · Health & Fitness · Students · Focus & Productivity · Learning · Travel Planning
Talk to us
[email protected]
[email protected]
Also from us
Entry Point Trading
Free weekly stocks to watch —
how our model ranks the S&P 500 and Nasdaq 100.
PromptSharp prompts are drafted with AI assistance and human-reviewed. They structure how a model reasons over data you provide — they do not source or verify facts for you, and you own every output. Nothing here is financial, legal, tax, or investment advice. Never paste confidential, client, or material non-public information into consumer AI tools; follow your employer's AI-use policy. © 2026 PromptSharp.