Blog · Playbook

Signal-based outbound: which buying signals actually work in B2B

Signal-based outbound B2B buying signals

Cold outbound delivers 1-3% reply rates in 2026. Signal-based outbound — based on the right buying signals — hits 8-15%, and stacked signals 15-25%. Here are the 12 signals that work, their reply-rate impact, and how to detect them.

The difference between cold and signal-based outbound isn't incremental — it's an order of magnitude. ZoomInfo's research documents that buying-signal outreach typically delivers 8-15% reply rates versus 2-3% for cold. Vanderbuild reports signal-based personalization pushes reply rates to 15-25% versus 1-5% for generic cold email.

This article is part of our GTM Engineering series. Read What is GTM Engineering? and the waterfall enrichment stack for context.

What exactly is a buying signal?

A buying signal is an observable indicating that an account, person, or buying committee is actively in market — or about to be. Not all signals are equal. Three categories.

Category A: Intent signals. Direct indicators of buying interest. Someone visits your pricing page, downloads a whitepaper, requests a demo. Or from third-party platforms like Bombora or G2: a company researches your category.

Category B: Context signals. Organizational changes making buying interest more likely. New leaders, funding, growth, leadership changes. Not "they want to buy," but "the situation is now ripe."

Category C: Trigger signals. Specific events requiring action. Customer leaves, contract expires, new regulation takes effect. Time-bound, often with a short response window.

The big win isn't in one category but in stacking them. Reachly documents that stacked signals convert at 5-10x the rate of single signals.

The 12 signals that work in 2026

Here are the 12 buying signals I consistently see work for B2B. For each: reply-rate lift, detection method, and when it's relevant.

1. New VP/C-level hire at target account

Lift: 4-6x cold baseline (even higher if your product matches the role). Overloop's research identifies this as one of the highest-converting combinations.

How to detect: LinkedIn Sales Navigator alerts, Common Room, Trigify, or a script pulling LinkedIn data weekly for your top-200 accounts.

When relevant: Almost always. New leaders change tooling stacks, are open to new solutions, and want early wins.

2. Recent funding round

Lift: 2-3x cold baseline. Stronger in combination with other signals.

How to detect: Crunchbase, Pitchbook, Dealroom (for EU), or Techleap data for NL. Weekly pull into your CRM.

When relevant: Product categories that get used more with growth (HR-tech, dev tools, sales tech). Less for pure cost-savings tools.

3. Champion job change

Lift: 7x baseline per research. Someone who used your product at a previous company moves to a new one. Overloop calls this one of the absolute highest-converting signals.

How to detect: Monthly LinkedIn scan of your old customer contacts. Or: Champify or UserGems for automation.

When relevant: When your product has a "sticky" user experience. An ex-customer saying "we need this at my new job too" is gold.

4. Job posting for a specific role

Lift: 3-5x baseline. A company hiring a "Head of Customer Success" is in market for CS tools. A "Marketing Manager" posting signals marketing stack investment.

How to detect: LinkedIn Jobs API, Indeed API, or scrapers via Apify. Filter on your ICP companies and relevant roles.

When relevant: Product categories directly tied to role functions. Sales tools for sales hires, CS tools for CS hires.

5. Tech stack change

Lift: 3-4x baseline. A company migrating from Shopify to Shopify Plus is in market for enterprise e-commerce tools. A company replacing HubSpot with Salesforce signals need for migration and integration services.

How to detect: BuiltWith, Wappalyzer, or scripts scanning HTTP headers and JS payloads for specific patterns.

When relevant: Especially for complement product categories — integrations, services-on-top, migration tools.

6. Recent product launch or feature announcement

Lift: 2-3x baseline. A company launching a new API needs developer resources. A new consumer feature points to marketing investment.

How to detect: Press release monitoring (Notified, Meltwater), or company blog scrapers.

7. Recent contract with competitor (expiring in 6-12 months)

Lift: 5-8x baseline when timing is precise. The problem: hard to detect.

How to detect: Reverse-engineer from competitor case studies, public contract data, or network research.

When relevant: Critical in markets with long contracts (enterprise software, ERP, financial tools).

8. LinkedIn engagement on your content

Lift: 4-7x baseline for first-degree connection targets. Someone liking or commenting on your content is a warmer prospect.

How to detect: LinkedIn engagement scrapers (Phantombuster, Trigify), or native if you post on your organization's account.

9. Pricing page visits (own website)

Lift: 6-10x baseline. Someone visiting your pricing multiple times is close to buying intent. Combine with identification of anonymous traffic (RB2B, Vector, Albacross).

How to detect: First-party analytics + visitor identification tool. Requires GDPR-compliant implementation.

10. Product usage spike (PLG signal)

Lift: 5-10x baseline. For product-led growth companies: a free-tier user suddenly using many more features or inviting more colleagues.

How to detect: Sync product data from Amplitude, Mixpanel, or PostHog to your CRM with threshold alerts.

11. Industry-specific regulatory triggers

Lift: 3-6x baseline within target segment. A new SOC 2 requirement, GDPR interpretation change, new NIS2 deadline — companies must respond, often with tools.

How to detect: Industry publication monitoring, RSS feeds from regulators, participation in industry communities.

12. M&A activity

Lift: 3-4x baseline. Acquisitions or mergers lead to stack rationalization and vendor relationship reevaluation.

How to detect: Mergermarket, Dealroom, or industry news monitoring.

The stacking effect: combinations that triple

The highest reply rates don't come from one signal but from combinations. Prospeo's research documents that the combination "new VP + recent funding at the same account" delivers 4-6x baseline reply rates, placing it among the highest-converting combinations in B2B outbound.

Concrete combinations I see work in practice:

  • VP Sales hire + champion job change: 8-10x baseline;
  • Funding + tech stack change: 5-7x baseline;
  • Relevant role posting + pricing page visit: 6-9x baseline;
  • Champion job change + LinkedIn engagement: 7-12x baseline.

The engineering challenge: signal overlay. Build a system combining multiple signal sources per account into a composite score. Not trivial, but the difference between 5% and 15% reply rate.

The signal window: speed is everything

A signal has an expiration. A new VP hire is gold in weeks 1-4, lukewarm at week 8, irrelevant after 12. Funding rounds stay relevant 6-9 months. Job changes 3-6 months.

What this means for your system: detection frequency matters. Weekly scanning for new signals often delivers better results than monthly scanning across more sources. Speed > volume.

What does NOT work as a signal

Three commonly-cited "signals" that don't work in practice:

1. Generic website visits. A prospect landing on your homepage isn't automatically a signal. Only when they go deeper (pricing, demo) does it become usable.

2. LinkedIn profile views. People look for all sorts of reasons. Low signal-to-noise ratio.

3. A whitepaper download. As a sole signal often research behavior, not buying intent. Valuable in combination with other signals.

The implementation: how to start?

Three steps for a first signal-based outbound system.

Step 1: Pick 3 signals that best match your product. Not 12. Three. For most B2B companies that works: champion job change, VP hire at target accounts, pricing page visits. Too many signals at once = nothing done well.

Step 2: Build detection. Tools: Clay for signal-detection workflows, Common Room for cross-channel monitoring, Trigify for LinkedIn signals. Combine in a central data platform.

Step 3: Write signal-specific messaging. Outreach that explicitly names the signal ("I noticed you just became Head of Sales at X — congrats") converts substantially better than generic openers. Vanderbuild's framework highlights this as critical: signal must be explicit in the message.

The core: signals not just detected, also activated

Many companies buy signal tools and see no improvement. Reason: detection is there, but activation isn't. The signal enters the CRM, no one responds within the window, the signal expires.

What works: signal-based workflows. When signal X is detected at an ICP-fit account, automatically: 1) account gets prioritized in CRM, 2) signal-specific sequence starts, 3) AE gets notified. No manual step in between, no forgotten leads.

Read also GTM Engineering in the age of AI for how AI agents orchestrate these workflows. Or see the modern GTM stack for the tools making signal detection viable.