Your Competitor's Churn Is Your Best Lead List. Here's the System.
Turn competitor adoptions and churns into your warmest lead list: radar setup, signal payloads, webhook and API wiring, and templates for vendors and agencies.
Every time a company adopts your competitor's product, they are telling the market three things: they have the problem you solve, they have budget for it, and they are acting on it right now. Every time a company drops that product, they are saying something better: the solution they picked didn't work, and they are back in the market.
Most vendors never see either event. That is the whole opportunity. This playbook covers competitor churn monitoring end to end: what to watch, how to set it up in Satellyte (UI and API), the exact data each signal carries, six outreach templates for the two moments that matter, and a separate set for implementation and integration agencies working the same signal from the other side.
Why churned accounts answer faster than any cold list
A cold list is a guess, three separate guesses stacked on top of each other:
- They may or may not have the problem you solve. Most of the list will not, because a list built on firmographics alone has no idea what is actually happening inside any of those companies right now.
- They may or may not have budget. Even fewer of the ones with the problem have money allocated to fix it this quarter.
- They may or may not be evaluating solutions right now. Timing is the hardest guess of all. Someone with the problem and the budget who is not actively looking will not reply to a cold email no matter how good it is.
Cold email averages a 3.43% reply rate platform-wide (Instantly's 2026 benchmark). That number is what happens when all three guesses land wrong most of the time.
An adoption or churn signal answers all three questions before you send anything:
- They definitely have the problem. They just installed a tool that solves it, or just dropped one that failed to.
- They definitely have budget. They were paying for the tool, or are actively shopping for one to replace it.
- They are evaluating solutions right now. The signal fires during the window, not before it and not after.
Outreach that references a concrete event like this lands 15-25% reply rates in the benchmarks (Autobound's aggregation of Lemlist, Instantly, and Belkins data). Take the conservative end of that range against the cold email baseline and the gap is still real: roughly 4x fewer leads needed to land the same customer. The longer they used the tool before dropping it, the more serious the buyer too: that was a real deployment, not a trial that fizzled.
Reply rate is only the first multiplier. It compounds with everything downstream of it: reply to call, call to trial, trial to customer. A signal-anchored list survives the first step at roughly 4x the rate, and tends to hold up better at the later steps too, because the person replying already has the problem and the budget instead of just being curious.
| Lead source | Leads needed for one customer | Time investment | Cost |
|---|---|---|---|
| Cold outreach | High | High | High |
| Content marketing | High | Very high, compounds slowly | Low |
| Paid ads | Medium | Ongoing, stops when spend stops | High |
| Signal-anchored outreach | Low | Low, mostly one-time setup | Low |
Paid ads and content both work, and both have real advantages this comparison is not trying to erase. But both need continuous investment to keep producing, and neither one tells you which specific account to talk to today.
One more thing worth internalizing: the 95/5 rule says roughly 95% of your market isn't buying at any moment. Adoption and churn events are how the 5% identify themselves in public.
Which competitors to watch, and which changes
Not every tool deserves a slot in your radar. The way I think about it:
Direct competitors first. Tools that solve your exact problem at a similar price point. Their adoptions tell you who is in-market; their churns hand you a warm displacement opening.
Adjacent tools second. Products your buyers typically run alongside yours. A company adopting a new sequencer probably cares about the data layer feeding it, and the other way around.
Category leaders third. Their churns are the interesting part. A company that dropped the safe default tried the obvious answer and still walked away.
Satellyte tracks adoptions and churns across a catalog that spans CRM, sales engagement, customer support, visitor identification, intent signals, marketing automation, security and compliance, and more. The full list is on the technology list page. One honest caveat from that page: churn tracking covers most, but not all, technologies, so a few tools are subscribe-only.
Timing adds a second axis to prioritization. The usage_started_at field on every signal tells you how long a company ran a tool before dropping it, and that duration changes what the signal means:
| Scenario | Buyer mindset | Your opportunity |
|---|---|---|
| Just adopted a competitor | "Let's give this a shot" | Moderate, they just committed |
| One quarter in | "Still ramping up" | Low, give them room |
| Churned after one quarter | "This isn't working" | High, they need help now |
| Churned after two quarters | "We gave it a real shot" | Very high, they're serious |
| Churned after a year or more | "We're done with this category" | Highest, they're desperate for something that works |
A churn after a year reads as a company that is finally done with the category. A churn after one quarter usually just means the trial fizzled, and the buyer might not be serious yet.
Setting up competitor churn monitoring in Satellyte
The UI path takes a few minutes and follows the tech stack change guide:
- Go to Radar, create a new one, and open Tech Stack Changes.
- Under Subscribed, pick the tools you want to catch companies adopting.
- Under Churned, pick the competitors you want to catch companies dropping.
- Scope the radar to your ICP with titles, industries, locations, and company size, then save.
Tech stack change signals expanded inside a Satellyte radar, tracking tool adoptions and churns
From that point the radar runs continuously. New adoptions and churns surface as leads with the signal attached, so you always know why a company showed up.
A tip from running this ourselves: keep adoptions and churns in separate radars. They deserve different outreach, and separate radars keep the routing clean downstream.
The data you get with every signal
The source of a lot of bad outreach is thin data. Here is what a tech-change signal actually carries in Satellyte. This is the documented signal shape from our API reference:
{
"id": "lead_123:0",
"type": "tech_changes",
"company": "Acme",
"company_domain": "acme.com",
"lead_id": "lead_123",
"lead_name": "Alex Morgan",
"lead_title": "Head of Revenue Operations",
"linkedin_url": "https://www.linkedin.com/in/alex-morgan",
"title": "Tech stack change detected",
"detail": "Detected from lead/company signals",
"source_url": "https://example.com/source",
"detected_at": "2026-07-15T00:00:00.000Z",
"score": 20
}And when you look up a company's stack directly, each technology item includes:
| Field | What it tells you | How to use it |
|---|---|---|
| vendor_name | Which tool was detected | Name it in your opener |
| vendor_category | The granular category (for example, sales engagement) | Position against the right alternative |
| vendor_upper_level_category | The broader grouping | Route to the right playbook |
| usage_started_at | Unix timestamp of first detection | Gauge how long they have run the tool |
| detected_at (signal) | When the change surfaced | Time the outreach to the event |
| lead_name, lead_title, linkedin_url | The person the radar resolved | Skip the org chart hunt |
| score | Fit score for the lead | Prioritize the queue |
The person is the part cold lists never give you. The radar resolves actual decision makers at the company that fired the signal, so the payload arrives ready to contact, with an email from enrichment when one can be found and verified.
Wiring signals into outreach without code
Satellyte has three no-code paths out, all under Settings, then Integrations:
Custom API webhook. Add your endpoint URL and a private auth header, and Satellyte sends a POST with a JSON body: delivery metadata plus a leads array. Each lead carries the full contact record: name, title, company, location, LinkedIn URL, email and phone when enrichment finds them, the fit score, and the radar that produced it. You can adjust the payload fields or add custom ones. Turn on auto-sync and every new radar lead flows out on its own. Point it at n8n, Zapier, or your own service.
Custom API modal: endpoint, auth header, and payload fields
Direct to your sender. The Instantly integration adds leads with an email address straight into a campaign. The HeyReach integration adds them to a lead list with name, LinkedIn profile, company, title, location, and headline. Slack can notify the team whenever a radar produces new leads.
A workflow shape that has worked well for us:
- Churn signals go out immediately. The window is real and it closes.
- Adoption signals wait a day or two before the first touch. Let them meet the product they just bought; your message reads better once they have opinions about it.
- Log everything to a sheet or CRM either way. The record of which competitors leak accounts, and when, becomes competitive intelligence on its own.
Validate the auth header on your receiver before trusting any webhook payload. That is in the webhook guide and it is good advice for every webhook you will ever set up.
The API loop, for developers
If you would rather own the pipeline, the API guide documents the full loop. Auth is a single X-Satellyte-API-Key header, scoped to your workspace.
1. Create a radar -> POST /radar/create (signals_to_track: ["techstack"])
2. Pull captured signals -> GET /radar/{id}/signals
3. Diff vs your last run -> detect new / removed vendors
4. Pull matching leads -> GET /radar/{id}/leads?min_score=70
5. Push leads to outreach -> POST /leads/pushThe one thing to know before you build: the API returns each company's current stack, not a delta. You persist the vendor list per company after each run and compute the change yourself. A vendor that appears is your adoption signal; one that disappears is your churn signal. Poll on a daily or weekly cadence.
Step 5 takes a destination of webhook_url, heyreach, or instantly, so the exit ramp is the same as the no-code path. There is also a feedback endpoint to report which leads converted, which sharpens what the radar surfaces next.
Six templates for the two moments
The psychology differs by direction. Someone who just adopted a competitor made a decision; attack it and you lose them. Someone who churned wants speed and proof that you understand why the last tool failed.
The placeholders use {{variable}} format, so they map straight onto merge fields in Instantly, HeyReach, or whatever sender you run. Keep the personalization light: one or two specifics beat a paragraph of flattery.
When they adopt a competitor
1: The curious question
Subject: quick question about {{tool}}
Hi {{name}},
Noticed {{company}} recently started using {{tool}} for {{problem}}.
Curious whether it handles {{specific_pain}} well for you. We built
{{our_product}} because that part kept coming up, and the difference
is {{specific_benefit}}.
Not pitching. Quick yes or no: are you happy with {{tool}}?
{{your_name}}It opens on curiosity instead of a pitch, and it names a pain specific enough to prove you know the category.
2: The honest comparison
Subject: {{tool}} vs the alternatives
Hi {{name}},
Saw you're solving {{problem}}. Crowded space, so here's the short
honest version:
- {{tool}} is strong at {{their_strength}}
- We're stronger at {{our_strength}}
- The real difference is {{key_differentiator}}
Happy to send the full comparison if useful. No call required.
{{your_name}}Being fair about the competitor's strengths is what makes the differentiator believable.
3: The case study drop
Subject: how {{similar_company}} handled {{problem}}
Hi {{name}},
{{similar_company}} ran {{tool}} for a while before switching to us.
Their sticking point was {{specific_issue}}.
They're in your space, so the comparison might be worth ten
minutes. Happy to intro you to them directly if you want the
unfiltered version.
{{your_name}}Offering a direct reference signals confidence no metric can fake.
When they churn a competitor
1: The empathy open
Subject: still dealing with {{pain_1}}?
Hi {{name}},
Saw {{company}} is in the {{category}} space. Most teams there run
into {{pain_1}} or {{pain_2}} eventually, and it's the exact gap we
built {{our_product}} to close: {{key_differentiator}}.
Worth a ten-minute walkthrough? No commitment, just the approach.
{{your_name}}It never says we saw them drop {{tool}}, just that we know the category's failure modes cold, so it reads as expertise instead of surveillance.
2: The direct alternative
Subject: looking for a {{tool}} alternative?
Hi {{name}},
You just moved off {{tool}}. Before you pick the next one: most
{{category}} tools struggle with {{root_cause}}.
We took a different route: {{our_approach}}. If you're still
looking, I'll make the evaluation painless: {{incentive}}.
Worth a look?
{{your_name}}Churned buyers are in a hurry. Directness reads as respect for their time.
3: The migration offer
Subject: free migration from {{tool}}
Hi {{name}},
Saw {{company}} moved off {{tool}}. If you had data and workflows set
up there, starting over is the worst part.
We'll migrate it for you, free: {{data_1}}, {{data_2}}, and your
settings. You evaluate us with your real setup instead of a
blank slate.
Want us to handle it?
{{your_name}}Switching friction is the biggest silent objection, and this kills it in the subject line.
For implementation and integration agencies
Not everyone reading this is trying to win the competitor's departing or arriving customer directly. Some of you are the {{tool}} onboarding partner, or the team that connects it to everything else the business runs on. Same signal, different pitch.
If you do the implementation
1: The onboarding question
Subject: just implemented {{tool}}, the onboarding question
Hey {{name}},
Companies that just implement {{tool}} usually have the budget but not the internal expertise to get real use out of it right away.
Satellyte catches the signup the week it happens and hands you the decision makers with verified emails.
You can try it out at no cost.
A quick yes and I will send you the link.
{{your_name}}It skips the pitch and leads with the insight, then makes the ask a one-word reply instead of a call.
2: The same-week question
Subject: {{tool}} rollout at {{company}}, the same-week question
Hi {{name}},
Saw {{company}} just brought on {{tool}}. Most teams bring in outside help in the first 90 days, and whoever reaches out that first week usually gets the account. By month two you are competing with three other agencies instead of none.
Satellyte flags the signup before anyone else does, with verified contacts for whoever owns the rollout.
Free to try, no contract. Want the details?
{{your_name}}By month two you are pitching against incumbents. Week one, there are none.
3: The category window
Subject: new {{category}} install at {{company}}
Hi {{name}},
Every {{category}} rollout opens a 90-day window where the buyer needs an implementation partner and has not picked one yet. Most agencies find out after that window closes.
Satellyte catches the install as it happens, so you are the first call instead of the fifth.
Try it free. Want the link?
{{your_name}}This one widens the trigger beyond a single named tool, for agencies that service a category rather than one platform.
If you do the integration
1: The integration question
Subject: {{tool}} plus your stack, the integration question
Hi {{name}},
Saw {{company}} just adopted {{tool}}. Most teams get the tool live long before they get it talking to the rest of the stack: the CRM, billing, the data warehouse, whatever else runs the business.
Satellyte flags the adoption in real time, so you can reach out before someone else builds the integration for them.
Free to try. Want the details?
{{your_name}}It works because the tool is already live and the gap is obvious to anyone who thinks about it, most buyers just have not yet.
2: The sync question
Subject: is {{tool}} talking to {{adjacent_tool}} yet?
Hi {{name}},
Most {{tool}} rollouts run standalone for the first few months because nobody owns the integration work. That gap is where deals slip through.
Satellyte catches the adoption signal the week it fires, so you can be the one who closes it first.
Try it free, no contract. Want the link?
{{your_name}}Naming the specific adjacent tool signals you already know their stack, not just their category.
3: The connected-systems question
Subject: new {{tool}} install, the connected-systems question
Hi {{name}},
A new {{tool}} install almost always needs to sync with something else: the CRM, the support desk, the finance stack. Most companies do not think about that until it breaks.
Satellyte surfaces the install as soon as it happens, with verified contacts for whoever owns the rollout, so you get there before the gap becomes a fire.
Free to try. Want the link?
{{your_name}}This one widens the ask beyond one specific integration, for agencies who plug in whatever the new tool needs to talk to.
Why this compounds
Paid channels stop the day you stop paying. This loop keeps improving instead: each cycle shows you which competitors leak accounts and which messages convert their users, and adding a new competitor to the radar reuses everything you already learned. After a few months you are sitting on a per-competitor briefing that nobody else in your category has.
The cost of staying blind
Every day you are not watching your category, deals are happening without you. A company drops a competitor's tool and starts looking again. A company adopts a tool that solves the exact problem you solve. Neither one hears from you, because nothing told you either event happened.
A rough sense of what that looks like: a radar tracking five or six direct competitors typically turns up a few adoption signals and a couple of churn signals most weeks that would otherwise go completely unseen, each one a lead someone else gets to first. Actual volume varies a lot with category size and how many competitors you track. Stretch a modest pace like that across a year and it adds up to something like 150-400 missed adoption signals and 100-250 missed churn signals: hundreds of accounts that could plausibly have been yours.
That gap does not stay flat. The accounts you miss this month become the case studies a competitor writes next quarter. The next deal in your category can default to someone else before you even know it was in motion. The longer a category goes unwatched, the bigger the head start for whoever is watching it first, because they get first look at every adoption and every churn while everyone else is still working a cold list.
Start this week
Today: list your five direct competitors, create a churn radar for them, and connect one exit ramp (webhook, Instantly, or HeyReach).
This week: add an adoption radar with a day of delay on the first touch, adapt one template per direction, and start logging results. The system runs from there.
Start with 1,000 free credits. That covers the signal checks and enrichment to catch your first competitor churns before you pay anything. Or watch live signals for your industry first and see what your radar would have caught this week.
Jesse
