Used by the teams building modern revenue.

Vendr's RevOps team runs every outbound play out of Clay. Their existing waterfall enrichments told them who the buyers at target accounts were and what tech they ran. What they couldn't see was which of those accounts had already started talking to a competitor.

R. Martinez added Deal Intelligence as a column in the team's master outbound table — input company_domain, output the latest competitive events at that account. The column populated immediately during the 30-day pilot, and the daily refresh started landing new events into the table the following morning.

"We added Deal Intelligence as a column in Clay and rebuilt our outbound waterfall around it. The events route into territories and the AE has the context before they pick up the phone."

The team rebuilt the outbound sequencing around the new column. Accounts with a recent competitive event move into a "warm competitive" track that takes priority over generic ICP outbound. AEs see the buyer, the competitor, and the event timestamp in their daily pull, before any call is scheduled.

Three quarters in, accounts that showed competitive-touch events generated 3.2× the pipeline of comparable accounts without them. Median lead time between event observation and competitor close is 12 days — long enough to run a credible counter-pitch.

Gainsight's GTM Engineering team operates the company's agentic GTM stack — Claude Code agents that draft AE call prep, generate save plays, and write enriched context back to Salesforce. The team's principle: every new data source must arrive in the agent stack via MCP, not via a vendor dashboard.

J. Kim wired Deal Intelligence into Claude Code in one morning. The MCP server config dropped into the team's shared mcp.json and exposed all six endpoints as tool calls the agents could reason over.

"We wired Deal Intelligence into our Claude Code workflows via MCP in a morning. Every event lands as structured context for the agent drafting the AE's next move. No dashboard. No human triage."

The pattern that emerged: when an AE opens an account in Salesforce, an internal agent pulls /account_activity for the 90-day window, drafts a call-prep brief that includes any competitive events, and writes it as a Salesforce note. The AE reads the brief; no human ever opens a Deal Intelligence interface.

"We don't think of it as a vendor we log into. It's an MCP tool the agents call. The product is the data shape, not the UI."

Navattic's Customer Success team learned about renewal risk the way most CS teams learn: too late. Procurement at a customer account would quietly open evaluation, run discovery calls with two or three competitors, and reach Navattic's CSM only in the final two weeks of the renewal cycle — by which point the decision was usually already made.

T. Andersson wired /churn_risk into the team's Slack channel via webhook. Every time a buyer at a customer account engages a competitor seller, the event lands in #cs-saves — threaded by account, with the buyer name, the competitor, and the event timestamp.

"/churn_risk events at our customer accounts give us 60 to 90 days of runway we didn't have. Our save plays go out earlier and our renewals are healthier."

The save plays now go out the same week the event fires, not the same week the renewal opens. The CSM has 60 to 90 days to run a proactive review, schedule executive alignment, and ship the next-quarter product roadmap before procurement formally opens the cycle.

Save-play conversion at accounts with churn-risk events is 18 percentage points higher than the team's baseline save rate. The team attributes the difference to the runway, not to any change in the save play itself.