← All templates Renewals at-risk · renewal pipeline a competitor just entered

A competitor is in your customer's account.

A buyer at one of your customers is talking to a named competitor. It’s often the quiet start of a renewal review you weren’t told about. This Always-on play routes the account team a save play, never a cold email.

Start a 30-day pilot with an ROI guarantee.

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 is talking to a named 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 starts talking to Priya Anand at Vertex (Customer, renews 47d) → row matched to CSM Dana Whitfield → Clay 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 activity: a named buyer at one of your accounts, talking to a named competitor. It’s refreshed daily and filtered to accounts where account_status reads customer. A renewal review rarely announces itself. This surfaces it the day a customer starts talking to a competitor.

DI · /churn_risk 17 columns 2 sample rows verified
demoTevent_typesourced_date#recency_days#confidence#priority_scoreTcompetitorTbuyer_nameTbuyer_titleTaccount_nameTaccount_status#renews_in_daysTcsmoverall_qualifiedTqualified_reasonAIsave_brief→alert
1Churn RiskJun 6, 202620.9686TempoPriya AnandDirector, EnablementVertex HealthCustomer47Dana WhitfieldCustomer talking to a competitor before renewal.book the renewal review earlyCSM: Dana Whitfield
2Churn RiskJun 9, 202610.9892HelixMarcus BellVP OperationsHelio FreightCustomer21Sofia Reyes21 days to renewal; competitor in the account.helio renewal: get aheadCSM: Sofia Reyes

The table as it looks in Clay: the customer columns plus the play columns (AI save brief, CSM alert, and no campaign tool, 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 in your table drafts an internal brief: which buyer is talking to a competitor, 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 campaign 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 weighing 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 plainly, 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) is talking
         to 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 replace it once you connect your key, with the buyer and the account named.

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 Competitor evaluations. Read the Clay guide →

Turn your competitors’ pipeline into yours.

Runs on your own account list. The guarantee: new pipeline, or a competitor found in one of your open deals.

Start a 30-day pilot with an ROI guarantee.