Who this is for
CS, founders, and PMs who want to learn from every cancellation, so churn reasons become a pattern to fix, not a dozen forgotten anecdotes.
The moment this saves you
Customers tell me exactly why they're leaving on the cancellation call, the most valuable feedback there is, and I never write it down, so we keep losing people for reasons we could have fixed.
See it work
Messy spoken thought in. A clean, structured artifact out.
Churn note from a cancellation call. The customer is leaving, mid-size team. The stated reason was price, but digging in the real reason is they never got their team to adopt it, only two of their eight seats were active, so they couldn't justify the cost. The root cause is an onboarding and adoption problem, not actually price. They said they loved the product itself, the people who used it were happy. They're switching to a cheaper competitor mostly to cut losses. The thing that would have saved them is better team onboarding, this is like the fourth churn for this exact reason. They might come back if we nailed adoption.
Churn note, June 5, 2026
- Customer: Mid-size team
- Stated reason: Price
- Real reason: Low team adoption, only 2 of 8 seats active, so they couldn't justify the cost
- Root cause: Onboarding / adoption problem, not actually price
- Notable: They loved the product; active users were happy
- Where they're going: A cheaper competitor (cutting losses)
- Pattern: ~4th churn for this exact reason
- Win-back potential: Possible if we fix team adoption
The workflow
Record a voice note
Hit the hotkey and talk, no formatting, no typing.
Tag it with this context
Contextli shapes your words into the structured output above.
Find it later
Everything's searchable and organised by context.
Pull it into Claude or ChatGPT
Bring your contexts straight into your AI tools with the Contextli MCP.
Your raw recording and transcription stay on your device, so you can always go back to the original.
The prompt behind this context
I'm going to debrief why a customer churned. Turn it into a churn note: a bold "Churn note, [today's date]" heading, then labeled lines: Customer (brief descriptor), Stated reason (what they said first), Real reason (the underlying cause if it differs), Root cause (the category, e.g. adoption, price, missing feature), Notable (anything positive or surprising), Where they're going, Pattern (if this is recurring), and Win-back potential. Separate the stated reason from the real one clearly. Don't invent reasons or patterns I didn't state. Output only the note.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Use this context
One tap adds it to your clipboard. Open Contextli and paste to add it.
Next, open Contextli, Contexts, Import, paste.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Your raw recording and transcription stay on your device, so you can always go back to the original.
Related contexts
Post-Call Debrief
You hang up and the next call's already ringing. Take twenty seconds to debrief out loud while it's fresh, the real objection, the budget hint, who actually decides, and it lands as a CRM note with next steps, not a vague one-liner.
Support Issue Note
A customer describes a problem in a rambling, emotional mess and you have to turn it into something engineering can act on. Talk through what they reported. You get a clean ticket with the issue, steps, and impact, so the fix happens instead of getting lost in translation.
Feature Request
A customer asks for something and it lands in your head as a vague 'they want X.' Say what they actually asked and the problem underneath. You get a brief with the real user problem, not just the feature, so the backlog reflects needs instead of demands.