Five accounts to call this week, and why each one is on the list
Every Monday a companion reads eight weeks of usage, thirty days of tickets and CRM contact recency for every account above your ARR threshold, then names at most five, ranked by ARR, with four lines of evidence apiece.
Every Monday you get at most five account names, ranked by ARR, four lines of evidence each. Churn announces itself six weeks early in three tools at once: usage sagged, two tickets closed unresolved, the champion stopped replying, each signal below its own alarm threshold.
A companion reads all three for every account, every week, and comes back with names rather than a score of 64. PostHog, Amplitude and Metabase are native integrations on the usage side, Attio and Salesforce on the CRM side, and support queues are readable in the session you are already signed into.
| Job | A Strawberry companion | Health-score dashboard |
|---|---|---|
| Signal correlation | Two-of-three flags, numbers shown | Composite score, reasoning hidden |
| Delivery | Five names in your Monday morning | You remember to open it |
| Unresolved tickets | Read and quoted, per account | One input among many |
| Next action | One suggested move per account | Interpret the score yourself |
What is the exact prompt?
Scheduled weekly, Monday morning:
- "For every customer account above [ARR threshold]: (1) from analytics, weekly active users for the last 8 weeks and the trend; flag any account down 25%+ from its 8-week peak, and any account where a previously active team went to zero. (2) From the support queue, tickets in the last 30 days; flag accounts with a ticket closed unresolved, reopened, or containing the words 'frustrating', 'switch', 'alternative' or 'cancel'. (3) From the CRM, days since our last two-way contact; flag anything over 45."
- "An account that trips two or more of the three flags is a risk. For each risk account, write four lines: the flags with numbers, what changed and when, the last human touchpoint, and the single most useful action this week. Rank by ARR."
- "Give me at most five accounts. If fewer than five tripped two flags, say so. Do not fill the list by lowering the bar. Read-only everywhere; message no customers."
Two-of-three flags beat a health score
When a dashboard says 64, the account manager goes and reads usage, tickets and activity anyway. The prompt delivers those three directly, already correlated, so the reading is done before Monday starts.
The rule is crude on purpose, so everyone can hold it in their head and adjust it. The "at most five" cap does the rest: five accounts is a Monday plan. The autopsy of why accounts leave belongs in churn analysis.
What counts as good evidence?
Dates and deltas.
"Usage down 40% since the week of May 12, which is the week their admin left per ticket #4471; last two-way email April 30" hands the account manager a first sentence for the call. Numbers on every flag also keep a European holiday week from reading as a crisis.
Tickets that close with the customer still unhappy are the strongest churn signal most teams already own and never aggregate, the same blind spot support ticket triage attacks from the other side.
A person makes the call
The prompt ends at "message no customers" deliberately.
The list exists to spend your team's five best conversations of the week on the right accounts, and the account that needs more than a call gets a full renewal account map.
Track one number monthly: of the accounts that churned, how many appeared on a weekly list first? That is the recall of your tripwire, and it tells you whether to loosen the flags or add a source.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents