# Churn reasons read as strategy

> Use when cancellation reasons are piling up and you need to know which part of the strategy they indict.

## À remplir avant de lancer

- `{{CHURN_REASONS}}`
- `{{CHURNED_ACCOUNT_DATA}}`
- `{{RETAINED_ACCOUNT_DATA}}`
- `{{ACQUISITION_SOURCE}}`

## Prompt

```
You are a retention analyst. Your job is to say which function owns each churn cause, and to resist the assumption that all of it is product.

Cancellation reasons and verbatim comments: {{CHURN_REASONS}}
Attributes of the churned accounts: {{CHURNED_ACCOUNT_DATA}}
Attributes of accounts that stayed: {{RETAINED_ACCOUNT_DATA}}
How each churned account was acquired: {{ACQUISITION_SOURCE}}

Produce:
1. Group everything in {{CHURN_REASONS}} into causes: wrong fit at sale, expectation set in marketing, onboarding, missing capability, price, sponsor left, or company change. Give counts, and put anything ambiguous into an eighth group called unclear.
2. A table with columns: Cause | Count | Share | Owner (marketing, sales, product, success, nobody) | Evidence quote | Preventable before signup.
3. Compare {{CHURNED_ACCOUNT_DATA}} against {{RETAINED_ACCOUNT_DATA}} and name the attributes that actually differ. Report counts, not impressions.
4. Break the preventable causes down by {{ACQUISITION_SOURCE}} to show whether one route brings accounts that leave.
5. What this says about the ICP and about the promises being made before the sale.
6. The single cause to work on first, with the reason it beats the larger group.

Constraints: stated reasons are what people say, not always why they left. Where the account data contradicts the stated reason, say so. If unclear is the largest group, say the exit survey is the problem. No em dashes.
```

## Obtenir un meilleur résultat

- Export the free text field, not just the dropdown; the dropdown was built to be quick, not accurate.
- When one channel dominates the preventable causes, the fix belongs in acquisition rather than success.
- Always include retained accounts, since churn data alone makes every attribute look like a cause.

---

Extrait de la bibliothèque de prompts QuQi - https://www.quqi.io/fr/prompts/churn-reason-strategy-read