About Incumbently

We built the data we wish we had. Then we used it on ourselves first.

Incumbently started inside a B2B lead generation agency. Daniel, our founder, ran outbound for more than 100 clients and kept hitting the same wall: tech data that was months old and had no proof behind it.

01The agency02The problem03The agents04Customer zero05Launch
Why we started
Every client asked me the same two questions. Who uses my competitor? And who is ready to leave? The tools could answer the first one, badly. None of them could answer the second. So we built agents that watch the signals that change first, and ran our own outbound on them before we let anyone else in.
DDanielFounder, Incumbently
How we got here

From agency to product. In five steps.

  1. 01The agency

    Ran outbound for 100+ B2B clients.

  2. 02The problem

    Tech lists were stale, had no dates and no proof. Good timing was luck.

  3. 03The agents

    Built agents that watch DNS records, job posts, new hires and 75+ other signals, all day.

  4. 04Customer zero

    Used Incumbently for our own outbound before launch.

  5. 05Launch

    Opened it to everyone, MCP first, so it works inside Claude, ChatGPT and Cursor.

Dogfooded

We were customer zero. Every feature ran our own pipeline first.

Before anyone else could sign up, Incumbently found and timed our own prospects. The switch alerts, the lists and the MCP answers you get are the same ones we used.

AI assistant · Incumbently MCP
Which companies using Zendesk look like they're moving to Intercom?
Incumbently · find_switching_accountsincumbent: Zendesk · challenger: Intercom · last 30 days

I found 18 accounts with switch signals in the last 30 days. Here are the strongest five, each with the signals behind it:

CompanySignalsSwitch scoreFirst signal
Corvid LabsJobsHire9223d ago
Juniper PayJobsCertDNS828d ago
Tidewater FreightJobsDNSHire6916d ago
Halcyon HealthCertDNS592d ago
Saltbox RetailJobsCertDNS5125d ago

46 sources · open any row to see the DNS record, certificate or job post

Ask a follow-up…
Illustrative · asked in an AI assistant with the Incumbently MCP server connected
Team chat · #switch-alerts
IncumbentlyApp · 9:41
Switch alert · score 91Saltbox Retail is moving off HubSpot
  • Jobs 3 job posts ask for Salesforce experience
  • Cert New support subdomain issued 9 days ago
  • Hire New Head of Support joined from a Salesforce customer
Suggested buyer · Head of Customer SupportOpen case fileDraft email
Illustrative · alerts post to Slack, email or a webhook
What we believe

Four rules we build by.

Proof over guesses

Every signal is something our agents saw, with the date they saw it. If we didn't see it, we don't show it.

Timing beats lists

Knowing who uses a tool is easy. Knowing who is about to switch is the part that books meetings.

Work where you work

Ask in Claude, ChatGPT or Cursor. Get alerts in Slack or email. No new tab to babysit.

Public data only

We read what companies publish openly. We never log in to a site to collect data.

History matters

Every change keeps its date, so you can see what a company used before and when it moved.

Intent plus proof

Job posts show the plan. Infrastructure shows the change. We use both, together.

100+Agency clients served
1,500+Software products tracked
20+Signal types
Data sourcing

Where our data comes from.

We collect signals that companies publish openly, and we keep a record of where each one came from.

  • DNS records, subdomains and public certificate logs
  • Website code that any visitor's browser loads
  • Public job posts on careers pages and job boards
  • Company news, press releases and team announcements
  • No logins, no paywalls, no getting around bot checks
  • Anyone can ask us to correct or remove their data
Founder

Daniel

Tech veteran. Ran a B2B lead generation agency for 100+ clients before starting Incumbently.

Your turn

Talk to Daniel.

Tell us who you sell against. We'll show you which of their customers are moving this month, live, in about 15 minutes.