Spray and pray is dying
A lot of people would agree that “spray and pray” approach to outbound is falling into obsolescence1. Platforms like Instantly are trying to pivot to AI, but their legacy tech is just too rigid to support that kind of change.
In the past, the sheer cost of human labor made per-prospect personalization at scale unsustainable, forcing teams to rely on ‘spray and pray’ to maintain their ROI2.
Signal-based, agentic outbound is the future3. In this article, I’ll break down three architectures driving this shift.
Approach A: Signal-triggered
Everything starts with a signal. Whether a prospect leaves a negative review about a competitor on G2, closes a new funding round, or visits your pricing page, they are instantly identified and routed into an outbound platform. That signal then becomes the foundation of your outreach. It serves as the ultimate icebreaker because it immediately answers critical question: Why now?
To setup, you choose a signal to monitor and a native language instruction for Agent to know what to do when the signal fires for a prospect.
Under the hood
Behind the webhook, signal engines all work the same way in simple terms: they are watchers.
Because most of the internet (LinkedIn, job boards, the SEC) does not offer native push notifications (webhooks) for state changes, these engines have to manufacture them. Each one picks a source of truth (LinkedIn profiles, public ATS boards like Greenhouse and Lever, SEC filings, your customer’s own website, competitor G2 pages, community feeds) and takes a snapshot of it on a schedule. By acting as state-polling watchers, they pull the current state (Snapshot A), wait a few minutes or hours, pull the new state (Snapshot B), and compute the delta (diff). Anything that changed gets transformed into a synthesized webhook event and pushed to us.
The differences between engines come down to what they watch and how often:
| Engine Type | Examples | How It Works |
|---|---|---|
| Job-Change | CoreSignal, UserGems, Champify | Scrape millions of LinkedIn profiles and diff the current-role field. |
| Website-Intent | RB2B, Warmly | Sit as a snippet on your site, catch every visitor, and resolve the IP to a company or person against a pool of cookies and ISP data they have built up. |
| Funding | Crunchbase | Watch SEC EDGAR filings and press feeds, then run entity recognition on the text to figure out who raised how much. |
| Technographic | TheirStack, BuiltWith | Crawl websites and job posts to fingerprint the tools each company uses, then diff week over week. |
| CRM-Signal | Native integrations | Skip the crawling entirely because your CRM is already a live event stream, so they subscribe to record changes directly through Salesforce or HubSpot APIs. |
What do they actually crawl?
Nobody watches the whole internet. Every engine maintains an internal watchlist, and the shape of that list is what makes each engine expensive or cheap, deep or narrow. Three patterns cover most of the market.
The first pattern is crawl-the-world. Engines like CoreSignal, BuiltWith, Bombora, and Crunchbase build one giant internal database of tens or hundreds of millions of profiles, sites, or companies, and refresh it continuously on their own dime. When you subscribe, you tell them which companies you care about, and they filter their firehose down to your list before pushing the webhook. You are paying for the fact that they already crawled everyone else.
The second pattern is crawl-what-you-care-about. Engines like UserGems and Champify do not crawl the world. They crawl exactly the contacts you have in your CRM and nothing else. You sync your closed-won opps and buyer contacts, they add those profiles to their crawl queue, and you get alerts only on people already in your book. This is much cheaper to run, which is why entry pricing is lower, but the coverage is exactly the size of your database and never bigger.
The third pattern is wait-to-be-triggered. Website intent tools like RB2B and Warmly do not crawl at all in the traditional sense. They sit as a snippet on your site and only react when someone visits. The heavy lifting is a pre-built identity graph of cookies and IP-to-company mappings that they built once and keep refreshing. The signal is the visit. The lookup happens in real time against a graph they already have.
CRM and product-analytics signals are the simplest of all because your CRM and your CDP are already emitting events natively. There is no crawling, no watchlist, no diffing. The engine just subscribes to a stream that already exists and forwards the events.
Autopilot vs human approval
Once a signal fires and the Agent drafts a sequence, someone has to hit send. That someone can be you or it can be the Agent itself.
By default, we run human-in-the-loop. The Agent drops the drafted sequence into your queue with the signal context and the reasoning, you scan it, edit anything that feels off, and approve. This is the mode that actually works in the wild. The customers we studied who attribute real pipeline to signal-triggered outreach (Vanta at 9x ROI on signals, Sendoso at 78% open and 3.2x more replies, Ideals at 452 meetings) all run the approval loop. The pattern that failed publicly and drove the 2025 AI SDR churn wave (11x, Artisan) is the one where AI drafts and AI sends with no one in the middle. Signals were not the failure mode there. The fatal flaw was removing human judgment from early, hallucination-prone tech, resulting in a volume play that simply burned domains at scale.
That said, not every signal needs the same level of scrutiny. A funding round with a clean ICP match and a fresh timestamp is a very different confidence level than a “prospect commented on a competitor post” signal. So we let you turn on Autopilot per signal type. Signals you trust, you let the Agent send directly. Signals you want to see first, stay in the approval queue.
Types
Tier S: documented 5x+ lift
| # | Signal | Approach | Weight | Who benefits | Impl |
|---|---|---|---|---|---|
| 1 | Trial signup + 3 team invites in 7 days (PQL composite) | PLG event ingest via webhook. Customer’s product fires trial_started + invite_sent events with team member count | 20x conversion vs solo trials (Nutshell case study) | Any PLG SaaS with self-serve trial | Complexity 2/5. 2-3 eng weeks. Build webhook endpoint + rule engine. Zero data cost. Customer’s Segment/PostHog/Mixpanel POSTs to Kanesh. Alternatives: Correlated (custom pricing), MadKudu ($24K-81K/yr), Pocus (bundled into Apollo $49/mo since March 2026), Common Room ($30K/yr). Ship your own webhook first; ML PQL scoring is 5/5 and needs training data across customers. |
| 2 | Past champion moved to new company | CRM contact linked to closed-won opp × LinkedIn job change diff | 3-5x cold reply, 39% win rate vs 19% baseline, 12% activity→opp (UserGems). New execs 3-5x more likely to initiate tech eval in first year (Gartner). Champion left = 51% churn probability within 12mo, 65% for exec-level (ChurnZero). | Anyone with a CRM history | Complexity 3/5 (data cheap, scoring hard). Buy paths: LeadMagic pay-as-you-go ~$0.021/lookup (10K contacts = $210/mo); CoreSignal Premium $1,500/mo with Employee webhooks; UserGems $2,750/mo (30K records); Champify $1,250-$3,000/mo. Do not build LinkedIn scraper. hiQ v. LinkedIn breach ruling = $500K judgment. Hard eng work is the champion classifier (opp-role join, deal-size weighting, recency decay). Champify’s stack is the reference. |
| 3 | New CFO/CRO/CMO/CISO hired at target account | SEC 8-K Item 5.02 filings (public co) + CoreSignal Employee API webhook filtered by experience_title on target-company list | 14% reply vs 1.2% cold for new CRO outreach; 5-10x eval likelihood in 90-day window; 46% of new-to-role sales execs underperform first 100 days, defensive tool decisions. 70% budget allocated first 100 days (vendor claim, treat as directional). | Finance tools (new CFO), sales tech (new CRO), martech (new CMO), security (new CISO, 18-26mo tenure = recurring cycle) | Complexity 2/5. SEC EDGAR RSS free, ~2hr latency. sec-api.io webhook tier $50-200/mo. CoreSignal Premium $1,500/mo covers private co. Amplemarket has NO discrete signal for this. Whitespace. |
| 4 | Signal stacking (3+ signals fire on same account) | Score composite = signal_A × freshness × ICP_fit + signal_B … trigger when threshold breached | 2.4-10x conversion lift vs single signal (Unify GTM). GTM composite (funding + RevOps hires + site changes) = 47% conversion lift, +43% larger deals (MarketBetter). | Anyone with 3+ signal sources wired | Complexity 2/5 once individual signals are wired. Rule engine in Kanesh. Zero external data cost. Pure math on already-ingested signals. |
| 5 | Multithreading (5+ engaged buyers on same account) | OpportunityContactRole diff in SF + LinkedIn enrichment for new stakeholders | 30% close vs 5% single-threaded (Gong). 2-3x win rate, 130% lift on deals >$50K, 78 days faster close (Gong 1.8M-deal analysis). Gartner: 3+ engaged stakeholders = 2.5x close, +30% deal size. | Any B2B enterprise motion | Complexity 2/5. Pure CRM diffing. Salesforce Pub/Sub API for OpportunityContactRole changes. Free. |
Footnotes
-
According to Instantly’s 2026 Cold Email Benchmark Report, average reply rates have plummeted to 3.43% (down from 8.5% in recent years) as AI spam filters and buyer fatigue actively penalize generic volume. (Source) ↩
-
Research from firms like Bridge Group and platforms like Autobound confirm the “research-to-outreach” cycle used to be entirely manual. Because human Sales Development Representatives (SDRs) had to spend hours researching prospects to write tailored emails, the cost-per-acquisition (CAC) was simply too high to execute personalization at scale. ↩
-
2026 market data shows that signal-triggered outbound campaigns achieve 15–25% reply rates while lowering the cost per qualified meeting by 30–40% compared to traditional cold outbound. (Source) ↩