Subscribe to your competition

Know what your competitors are doing inside your accounts with verified competitor activity events available in Clay, Claude, your CRM, and Slack.

Request Access → See the docs

claude_code · deal_intelligence_mcp

Trusted by revenue teams at

The gap

Most competitor activity in your accounts happens in channels you don't have access to.

You can see almost everything your buyers do in public. You can't readily see what they do with the vendors competing against you.

What you can see

Website visits
Content downloads
Webinar attendance
Form fills and demo requests
LinkedIn posts and engagement
Job changes and funding rounds
Email opens, clicks, replies
Account owner meeting notes in your CRM

What you can't

A buyer at your account accepts a connection request from a seller at a competitor.

Three buyers at the same account accept connection requests from competitors in the same week.

One buyer accepts connection requests from sellers at three competitors in five days.

The data

Verified competitor activity data without guesswork or noise.

Every event is a real connection acceptance, observed at one of your named accounts, between a named buyer and a named executive at one of your competitors. Updated daily. Structured. 0.95+ confidence.

Named on both sides Every event identifies the buyer (name, title, company) and the executive at your competitor (name, title, company).

Confidence ≥ 0.95 Identity, role, and company are confirmed against authoritative sources before the event publishes.

Daily refresh Events update each day, routed by territory, segment, owner, or any field in your CRM.

Scenarios Every event is tagged by the deal scenario it sits in: new_business, open_opportunity, closed_lost_revival, churn_risk.

// Sample event payload from /competitive_activity
{
  "event_id": "evt_8H3K9PqR2nL",
  "event_type": "closed_lost_revival",
  "timestamp": "2026-05-18T14:22:08Z",
  "confidence": 0.99,
  "buyer": {
    "name": "Marc Eisenberg",
    "title": "Director, RevOps",
    "company": "Workday"
  },
  "competitor": {
    "company": "CaptivateIQ",
    "seller": {
      "name": "[redacted]",
      "title": "Account Executive"
    }
  },
  "account_context": {
    "stage": "closed_lost",
    "lost_date": "2025-09-04",
    "owner": "@sasha"
  },
  "routing": {
    "territory": "NAMER-ENT",
    "slack_channel": "#deal-revivals"
  }
}

/competitive_activity Verified connection events at every account in your book GET · STREAM

/closed_lost_revival Buyers re-engaging with competitors at closed-lost accounts GET · STREAM

/churn_risk Buyers at customer accounts engaging with competitors GET · STREAM

/account_activity All competitive events at a single named account, last 90 days GET

/buyer_activity All competitive events tied to a single named buyer GET

View full API reference →

Solutions

Source pipeline, revive closed-lost, and navigate open opportunities.

Knowing what your competitors are doing inside your accounts changes what you do next: surface new pipeline already in evaluation, reopen a stalled deal, reframe the talking points in your next meeting, and reach the champions and directors on the buying committee.

01 · New Business

Find accounts already in evaluation before your account owner has reached out.

Connection events at accounts you haven't worked yet tell you the buying committee is in motion. Your agent can put the right account owner in front of the right buyer before the competitive evaluation is fully framed.

→ /competitive_activity · stream

02 · Closed-Lost Revival

Catch the moment a lost account re-enters market.

When a buyer at a closed-lost account starts engaging a competitor again, the deal is re-opening. Save plays go out before the new vendor has run discovery.

→ /closed_lost_revival · stream

03 · Open Opportunity

Know which deals turned competitive while you were following up.

Connection events at active opportunities mean the buyer just opened a second evaluation. The account owner adapts the next call from "follow-up" to "competitive close" — same day.

→ /account_activity · query

04 · Renewal Risk

See the renewal review 60 to 90 days early.

Customer accounts engaging with competitor sellers signal procurement is evaluating alternatives. Your CSM gets weeks of runway to run a save before the formal renewal cycle begins.

→ /churn_risk · stream

Integrations

Available everywhere your workflows already live.

Events flow into the surfaces your team is already operating in. No new dashboard. No new tool to learn. The same event reaches Clay tables, Claude agents, your CRM, and Slack.

Clay Native

Add Deal Intelligence as a column in any Clay table. Enrich accounts with competitor activity history. Trigger Clay workflows on new events.

enrich · deal_intelligence · /competitive_activity

Claude Native MCP

Native MCP server. Your agent calls /competitive_activity directly, runs reasoning over the events, and writes back to your CRM.

mcp · deal_intelligence · stdio

REST API OpenAPI

Standard JSON API with OpenAPI 3.0 spec. Authenticate with an API key. Call any endpoint from any agent, framework, or backend.

GET · api.dealintelligence.io · /v1

Webhooks Push

Events delivered to any HTTPS endpoint with each daily refresh. Retries, signatures, dead-letter queues, replay support.

POST · your-endpoint.com/events

Slack Routed

Routed to the right channel by territory, segment, or account owner. Threaded by account so the full activity history travels with the event.

slack · #competitive-events · routed

CRM Salesforce · HubSpot

Events written directly to the opportunity or account record. Custom fields, activity timeline entries, and trigger-ready signals for routing.

write · Opportunity · custom_field

FAQ

Common questions, answered.

What do I do with the data?

We help you with these use cases, however, some customer get creative beyond these:

Get into new deals. A buyer at an account your team hasn't worked yet connects with a competitor. The account owner opens the account before the evaluation closes.

Adapt the open opp. A buyer at an active opportunity connects with a competitor. The account owner walks into the next call calibrated to that competitor, not running a generic follow-up.

Reopen closed-lost. A buyer at a closed-lost account starts engaging a competitor again. Save plays go out before the new vendor has run discovery.

Catch the renewal review early. A buyer at a customer account engages a competitor. The account owner has runway before the formal renewal cycle.

Every event is tagged with which of the four scenarios it sits in, so your routing decides what your team does next.

How do you verify the events?

Identity, role, and company on both sides are confirmed against authoritative sources before the event publishes. If we can't verify the pair at 0.95 or higher confidence, the event doesn't fire. Confidence and verification metadata travel with every event.

How fresh is the data?

Refreshed daily. Events update each day, delivered through whichever surface your team is already using e.g. Clay, Claude, your CRM, Slack, webhooks.

What scenarios do you cover?

Four. New business — accounts you haven't worked yet, buying committee is in motion. Open opportunity — deals you're working that just turned competitive. Closed-lost revival — lost accounts re-entering market. Renewal risk — customer accounts engaging competitors before the renewal review. Every event is tagged with the scenario it sits in.

What exactly is a Deal Intelligence event?

A real connection acceptance, observed at one of your named accounts, between a named buyer and a named executive at one of your competitors. Structured, refreshed daily, shipped above 0.95 confidence. A single named data point — not a score, not an inference.

What conversion should I expect?

Across customers, about 5 percent of events convert to influenced opportunities, but conversion depends on account owner response time, ICP fit, and how you route them. Volume depends on competitor activity at your account list. Events are observed, not manufactured.

How does this work with our CRM?

Events write directly to the opportunity or account record as a custom fields. Your CRM keeps its source-of-truth role; the events become part of the timeline. Salesforce and HubSpot are supported natively; other CRMs via webhook to any HTTPS endpoint.

How does it connect to Clay and Claude?

Clay connects via HTTP table — new events arrive as rows on your refresh cadence. Claude connects via the MCP server — one config block gives any Claude agent access to the full event API.

What do I need to get started?

A CRM connection (Salesforce or HubSpot) and the competitors you want to monitor. We sync your accounts directly from your CRM. On the setup call we connect the CRM, calibrate routing, and start your 30-day pilot.

Is there a free trial?

Yes. We run a 30-day pilot against your account list so you see real events before the annual commitment.

How do you handle data privacy and compliance?

SOC 2 audited. GDPR compliant and privacy-first by design. No do not retain customer data in any of our storage systems. Full detail on the trust portal.

Deal Intelligence

Subscribe to your competition.

Know what your competitors are doing inside your accounts.

Request Access → See the docs