Facebook tracking pixel Skip to main content

Retention and proof

Find out who might cancel.

Looks through your active accounts for the early signs of churn: activity falling against its own baseline, a long silence, goals missed or gone stale, a complaint still open, and weak numbers going into a renewal. Each account gets a risk level of high, medium or low, the evidence behind it, and a recommended save play. Accounts at high risk are flagged to your escalation contact. The customer never hears from the skill.

Request access Have us build it
  • Each signal cites its evidence
  • Save plays are advice
  • Customers are never contacted

At a glance

Group
Retention and proof
Command
/churn-watch
Uses
Accounts, goals and meeting notes
Writes
A ranked risk list, ledger rows
Sends
Nothing. Drafts only.

01When to use it

Run it on a rhythm, and before renewals.

  • Every week or month, to catch accounts drifting away before they cancel without a word.
  • Ahead of a renewal cycle, a quarterly business review or a retention push, to learn which relationships need a save play first.
  • After a rough delivery period, a missed goal, or an escalation nobody resolved.

Not for

02What it needs

Accounts, goals, and the last conversations.

  • On a solo or team setup, every file in your accounts folder, with its status, value, renewal date, last touch and owner.
  • On an agency setup, the active client's context, goals and meeting notes, and nothing from any other client.
  • Your numbers log, or that client's goals log, for targets missed, figures gone stale and the gap between current and target.
  • Recent meeting notes, for the last real contact with each account and any escalation still open.
  • The previous watch for the same scope, if one exists, and the escalation contact named in your config file.

03What it writes

A ranked report, two rows and the callouts.

Operations/reviews/{date}-churn-watch.md
The report on a solo or team setup. A re-run opens with what changed: accounts newly at risk, recovered or worse. Then the risk list, one row per account with its level, its signals and their evidence, and its save play, followed by a callout for each high-risk account.
Clients/{slug}/reports/{date}-churn-watch.md
Where the report goes on an agency setup. It sits in the active client's own reports folder, marked confidential, so it stays behind that client's firewall.
Ledger rows
Two appended rows: how many accounts sit at medium or high risk, and what those accounts are worth together, each with a source and a confidence. They land in your numbers log, or in the client goals log on an agency setup.
Escalation callouts
One per high-risk account, carrying its signals and save play, for the contact in your config file. None of them is customer-facing.
Daily/YYYY-MM-DD.md
One line with the count and value at risk and the names of the high-risk accounts.

04Limits

What it never does.

  • Reach out to a customer, send or post anything, or touch a renewal or an account. It recommends, and a person acts.
  • Read a sibling client on an agency setup, even to see what normal looks like. Each account is judged against its own history.
  • Assign a risk level on a hunch. Every level names its signals, and thin evidence is marked inferred.
  • Call a metric behind when the ledger never tracked it.
  • Edit, reorder or tidy an earlier ledger row.

What stays with you.

  • Running each save play, whether that is a check-in, a value recap, a goal reset, a fix for the escalation or a renewal conversation.
  • Deciding what happens to each high-risk account once its callout reaches your escalation contact.

05Sample output

The risk list, worst first.

Taken from the report of a made-up office coffee supplier with three business accounts. A real list cites a file and a date for every signal.

Operations/reviews/2026-09-30-churn-watch.md Illustrative, not a client result.
Example Law Office High
Signals and evidenceNo meeting since 2026-08-21. Renews 2026-11-08 with orders behind target
Save playRenewal conversation, led by the account owner
Example Gym Medium
Signals and evidenceComplaint about late deliveries, open since 2026-09-10
Save playFix the delivery problem, then a check-in
Example Clinic Low
Signals and evidenceWeekly orders below its own baseline, numbers log row of 2026-09-28
Save playA value recap for the owner to send

Also from the run

  • Since the last watch: Example Gym is newly at risk.
  • Callout: Example Law Office, flagged to the escalation contact in the config file.
  • In the numbers log: at-risk-count, 2 accounts at medium or high risk.

06Related skills

Often run beside it.

07Questions

Before you run it.

Will it email customers who look at risk?

No. Every save play is a recommendation. High-risk accounts go to the escalation contact in your config file as flagged callouts, and the skill never contacts the customer.

Does an agency run look at other clients?

No. It works inside the active client's folder alone and never reads a sibling, not even to compare. The report is filed in that client's folder and marked confidential.

What pushes an account to high risk?

How many signals it shows and how serious they are. A renewal close at hand with weak numbers, or an escalation still open, moves it toward high. By default, silence means no contact in 30 days, and a renewal counts as close within 60 days.

Have us build it

We can build it for you.

Start with the free plan. A person names the first fix.

Get your free plan Or run it yourself with the toolkit.