← All templates Catch the renewal review early · /churn_risk

A competitor is in your customer's account.

A buyer at one of your customers accepted a reachout from a competitor — often the quiet start of a renewal review you weren't told about. This template routes the account team a save play, never a cold email.

Request Access → See the docs

Where it fits

From a competitor's move to a saved renewal.

Deal Intelligence is the source; Clay routes the CSM the save play — never a cold email.

Deal Intelligence

The data

A buyer at a customer account accepted a reachout from a competitor, near renewal.

→

Clay table

The row

One row matched to the customer, the renewal date, and the CSM.

→

In Clay

The brief

Surface · match account · write the save brief · alert.

→

Slack + CRM

The CSM

An internal alert to the account team — no cold send.

Follow one activityA competitor reaches Priya Anand at Vertex (Customer, renews 47d) → row matched to CSM Dana Whitfield → AI drafts a save brief → Slack alert to Dana → renewal review booked early.

What's in the table

One row per renewal at risk.

Each row is one verified reachout — a buyer at one of your accounts accepted a reachout from a named competitor executive, daily, at 0.95+ confidence — filtered to accounts where account_status reads customer. A renewal review rarely announces itself; this surfaces it the day a customer takes a competitor's call.

DI · /churn_risk 17 columns 2 sample rows 0.95+ confidence

	demo	Tevent_type	sourced_date	#recency_days	#confidence	#priority_score	Tcompetitor	Tbuyer_name	Tbuyer_title	Taccount_name	Taccount_status	#renews_in_days	Tcsm	overall_qualified	Tqualified_reason	AIsave_brief	→alert
1		Churn Risk	Jun 6, 2026	2	0.96	86	Gong	Priya Anand	Director, Enablement	Vertex Health	Customer	47	Dana Whitfield		Customer engaging a competitor pre-renewal.	book the renewal review early	CSM: Dana Whitfield
2		Churn Risk	Jun 9, 2026	1	0.98	92	Clari	Marcus Bell	VP Operations	Helio Freight	Customer	21	Sofia Reyes		21 days to renewal; competitor in the account.	helio renewal — get ahead	CSM: Sofia Reyes

The table as it looks in Clay — the customer columns plus the play-spine (AI save brief, CSM alert — no sequencer, by design). Scroll for the rest; real activities replace the sample rows once you connect your key.

The play

Route the team. Don't email the customer.

Step 01 · Surface

Filter to activities on customer accounts. Sort by renewal proximity and priority so the closest, largest renewals rise first.

Step 02 · Match the account

Each row already carries the account owner and CSM from your CRM, so the alert lands with the people who hold the relationship.

Step 03 · Write the save brief

An AI column drafts an internal brief: which buyer engaged, where the renewal stands, and a suggested save move. Written for the CSM, never for the customer.

Step 04 · Alert

The brief posts to the account team in Slack and as a CRM task on the renewal. Assigned to a name, with the renewal date attached.

Step 05 · No cold send

There's no sequencer step here by design. The next touch is a human one from the account owner — a check-in call, not a campaign.

Why internal-only

An automated email to a customer evaluating alternatives reads as exactly what it is. A timely, informed call from their CSM reads as attention. The template protects the difference.

CSM routing

The alert it sends.

Plain and internal — what happened, when the renewal is, and the suggested move. It states the activity without naming the competitor executive, and it goes to the account team, not the customer. A sample, right.

# Sample — internal Slack alert to the account team
Account: Vertex Health · Customer · renews in 47d
CSM:     Dana Whitfield
Activity:  Priya Anand (Dir. Enablement) accepted
         a reachout from a competitor in the category this week.

Save:    Book the renewal review now, ahead of
         schedule. Lead with the enablement rollout
         they flagged in Q2 — that's the seam a
         competitor would pry at.

Sample row. Real activities arrive aggregate until you connect your key — named buyers, named accounts, never a named competitor executive.

How the data arrives

Two ways into your table.

Via your CRM · recommended

CRM sync writes competitive-activity fields onto your Salesforce or HubSpot records — including customer status, renewal date, and the assigned CSM — so the alert routes itself.

Via webhook · event-driven

Point a Clay table's Webhook source at the per-table URL, add it in your Deal Intelligence settings, and each new competitive activity on a customer account posts a row.

Shares the same data backbone as Get into new deals. Read the Clay guide →

Deal Intelligence

Subscribe to your competition.

Know what your competitors are doing inside your accounts.

Request Access → See the docs