← All templates Deals at-risk · open pipeline a competitor just entered

A competitor just showed up on a deal you're working.

A named competitor is talking to a buyer on a deal you’re already working. This Always-on play briefs the deal owner before the evaluation hardens: internal first, then multithread.

Start a 30-day pilot with an ROI guarantee.

Where it fits

From a competitor's move to a briefed owner.

Deal Intelligence is the source. Clay routes it to the deal owner before the evaluation hardens.

Deal Intelligence
The data
A buyer at an account with an open opportunity is talking to a named competitor.
→
Clay table
The row
One row matched to the open deal, its owner, and CRM state.
→
In Clay
The brief
Surface · match deal · brief the owner · route.
→
Slack + CRM
The alert
To the deal owner. Internal, not a cold send.
Follow one activityA competitor starts talking to Jordan Reyes at Northwind (open opp, Stage 3) → row matched to owner Sam Carroll → Clay drafts an internal brief → Slack alert to Sam → multithread before the eval narrows.
What's in the table

One row per open deal in play.

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_open_opp_count > 0. Set your default sort to priority_score descending, and the largest, latest-stage deals surface first.

DI · /open_opportunity 18 columns 2 sample rows verified
demoTevent_typesourced_date#recency_days#confidence#priority_scoreTcompetitorTbuyer_nameTbuyer_titleTaccount_nameopen_oppTopp_stageTopp_amountTaccount_owneroverall_qualifiedTqualified_reasonAIinternal_brief→route
1Open OpportunityJun 6, 202620.9688TempoJordan ReyesVP Revenue OperationsNorthwind LogisticsStage 3$84kSam CarrollNew buyer on a live Stage 3 deal.multithread to jordanOWNER: Sam Carroll
2Open OpportunityJun 8, 202610.9791HelixMarcus BellRVP, SalesHelio FreightStage 4$120kLena OrtizCompetitor entered at proposal stage.brief lena · exec alignOWNER: Lena Ortiz

The table as it looks in Clay: the open-opportunity columns plus the play columns (AI brief, owner route). Scroll for the rest; real activities replace the sample rows once you connect your key.

The play

Brief first. Multithread second.

Step 01 · Surface
The table arrives pre-filtered to open-opp accounts and sorted by priority, so the work starts at the top of the list.
Step 02 · Match the deal
The activity already carries the account owner and CRM state, so each row sits next to the deal it affects. No manual lookup.
Step 03 · Brief the owner
An AI column in your table drafts a short internal brief for the AE: who the new buyer is, where they sit, and a suggested multithread move. Written for your rep, not the buyer.
Step 04 · Route
The brief goes to the deal owner by Slack and a CRM task: assigned, not broadcast. The clock on a competitive evaluation is short.
Step 05 · Multithread
An optional buyer-facing touch reaches the new contact peer-to-peer, so the deal isn't single-threaded on one champion. Ships disabled until the owner approves.
Why internal-first
On an open deal, a clumsy cold email can do more harm than the competitor. The owner decides the touch; the template just makes sure they know in time.
Deal alerts

The brief it writes.

Short, factual, and aimed at your rep: what changed, who entered the account, and the next move. It states the activity plainly and never invents detail it doesn't have. A sample, right.

# Sample: internal brief for the deal owner
Deal:  Northwind Logistics · Stage 3 · $84k
Owner: Sam Carroll
New:   Jordan Reyes is talking to a competitor
       in the forecasting category this week.
       Not on the deal yet.

Move:  Multithread to Jordan before the eval
       narrows. Anchor on the migration risk;
       the champion won't carry that thread alone.

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 the open-opportunity context, so the data shows up as columns in any table sourced from your CRM.
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 an open-opp 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.