Rails/Churn threat scan

# Churn threat scan rail

Threat watch list on ClickUp. Cluster reasons from authorized sources. **No send.** Distinct from win-back-week (which parks gated win-back drafts).

## Tool roles (do not blur)

- **ClickUp** = watch list / clusters / owners / dates
- **Notion** = optional cluster write-up — not the board
- **Email / Resend** = **out of scope this rail** (point to win-back-week)

## Done this week looks like

- ClickUp: watch list with threat rows + clusters
- Optional Notion cluster note parked
- Friday: ranked threats + one change
- Zero customer emails from this rail
- Optional companion: win-back-week only if they ask

## Hard rules

- Park by default — **no send**
- Never invent churn %, MRR lost, or competitor moves
- Leave blanks; “no threats found” is a valid Friday line
- One question at a time if a slot is missing
- Soft slots ({{segment}} {{date_window}} {{do_not_touch}}) come from their principal/memory — ask once if missing
- Agent never drafts win-backs on this rail unless they explicitly switch jobs

## Empty watch list (copy into ClickUp)

| Who | Signal snippet | Source | Cluster | Owner | Friday |
| --- | --- | --- | --- | --- | --- |
| | | ticket / chat / CRM | | | |

## Empty cluster table

| Cluster | Count (rows) | Competitor mentioned? | Note |
| --- | --- | --- | --- |
| | | only if in source | |

---

# Part A — Churn threat scan

## Step 1 — Open the watch list (ClickUp)

One list. Free Forever. No send seat.
Sign up: https://clickup.com/signup

## Step 2 — Park threat rows (ClickUp)

Authorized sources only. No invented churn %.

## Step 3 — Cluster reasons (ClickUp)

Tags + short cluster table.

## Step 4 — Optional Notion note

Parked write-up. Not email.

## Step 5 — Friday rank

Top threats. One change. Still no send.

---

# Churn threat scan — Step 1 ClickUp

Open one ClickUp list named for this threat-scan week. Output: empty watch list ready for threat rows.
Do not invent a second Space. Do not invent churn rates or MRR at risk.
Sign up: https://clickup.com/signup
Free Forever. No card required.
This rail does **not** draft or send win-backs. Use win-back-week for gated drafts.

# Churn threat scan — Step 2 Rows

Put threat signals on the list. Only names and quotes/snippets from tickets, chat, or CRM notes they authorized.
Output: rows (who + signal snippet + date if known + owner if named).
Do not invent churn %, competitor switches, or “they will cancel.” Leave blanks. Do not email anyone.

# Churn threat scan — Step 3 Clusters

Cluster the rows by root reason (from the snippets only). Optional: note subscription length or competitor mentions **only if present in the source**.
Output: cluster tags on rows + a short cluster table.
Do not invent percentages. Soft slots ({{do_not_touch}} segments) from principal/memory — ask once if missing.

# Churn threat scan — Step 4 Notion (optional)

If they want a written summary: one Notion page with clusters + open unknowns.
Status: parked — do not email customers, do not publish.
Sign up: https://www.notion.com/signup
Free plan. No card required.

# Churn threat scan — Step 5 Friday

Rank the watch list (their criteria, or recency if none named). Name top threats.
Name one change for next week’s scan.
Output: Friday line. Do **not** draft or send win-backs unless they explicitly switch to win-back-week.

# Churn threat scan — Step 6 Companion (not the scan)

Win-back drafts are a **different job**. Do this only if they ask for win-back-week.
Do not glue Resend/Email send into Mon–Thu threat scan.
Do not invent offers or churn %.

Related tools

Productivity

ClickUp

Threat rows with reason cluster and owner.

Productivity

Notion

Optional cluster write-up. Not the watch list.