Signal-Based Outbound: A Practical B2B SaaS Playbook

Replace static prospect lists with signal-based outbound using account triggers, prioritization, AI research and human follow-up.

Adrien de Malherbe

Adrien de Malherbe

Europe GTM & AI sales advisor · B2B SaaS

Independent consulting · Barcelona / Europe

The idea, at a glance

An event is not buying intent

  1. FitDoes this account match the ICP?
  2. RelevanceDoes the event create a real problem?
  3. FreshnessIs there a reason to act now?
Prioritize the intersection of account fit, event relevance and timing.

Start with five signals with a plausible causal link to buying, score fit and timing separately and create one measurable play per signal. Reply rates are falling or reps spend too much time researching accounts with no reason to buy now. It is an event worth investigating, not proof of budget or urgency. Pair it with an ICP match and evidence of a problem before initiating a play.

What the public evidence shows

Clay describes Amplitude combining product usage with AI research to identify cross-sell candidates.

Practical takeaway: First-party behavior can give a prioritization system context that a public announcement alone cannot.

Evidence limit: This illustrates prioritization for existing customers. It does not establish cold-outbound conversion rates.

Read the source: Clay: public signal use cases ↗

Public third-party example. No claim of personal involvement by Adrien de Malherbe.

Distinguish account fit from a reason to act

Fit explains whether the account belongs in the ICP. Timing explains why the team should act now. Strong outbound requires both.

Use fit × event relevance × freshness below as a working method. Adapt its criteria to your own sales cycle and data; it is not a validated industry benchmark.

Score five signal families separately

Illustrative example: a target account opens a new region. Confirm the announcement and its date, then research whether that expansion creates a problem your product solves. A new office alone is not buying intent. If there is no plausible connection, keep the account out of the play.

Compare triggered accounts with a holdout

Measure qualified meetings per eligible account by signal, event-to-action time and false-positive rate. Compare against similar accounts without the trigger and use the same observation window.

Fit × event relevance × freshness

Decision or stepEvidence or outputReview rule
Leadership changeCheck whether the new role owns your problemOffer a relevant diagnostic
Expansion announcementVerify the operational changeTest a market-entry hypothesis
Product adoptionConfirm usage and account entitlementAsk about the next team or use case
Hiring activityCheck whether the role signals a real constraintExplore that constraint
Technology changeVerify the source and migration stageDiscuss compatibility
Is a funding announcement a buying signal?

It is an event worth investigating, not proof of budget or urgency. Pair it with an ICP match and evidence of a problem before initiating a play.

How should you measure signal-based outbound?

Measure qualified meetings per eligible account by signal, event-to-action time and false-positive rate. Compare against similar accounts without the trigger and use the same observation window.

Is the public example an Adrien de Malherbe client result?

No. It is an attributed public example from the linked publisher. The proposed frameworks and illustrative scenarios on this page are editorial guidance, not claims of personal involvement or guaranteed outcomes.

Public examples are attributed to their publishers. Vendor claims are not independently verified. Frameworks and illustrative examples are proposed methods, not client results.

Last reviewed:

Work with Adrien

Building a more scalable B2B sales motion?

I help SaaS teams design Europe GTM, revenue operating systems and AI-assisted sales workflows that improve execution without automating away commercial judgment.

Privacy and measurement preferences

Optional measurement records page paths, referral categories and resource interactions in hosting logs. Google Analytics also receives these events and device information and uses a browser cookie identifier. Advertising features are disabled. Form text, names and email addresses are not included in measurement events. Your preference is stored on this device. Measurement starts only if you opt in and respects browser privacy signals.

Google privacy information. You can withdraw consent here at any time.

Contact details are used to respond to your enquiry. Successful sends and delivery errors are counted in operational logs; the message itself is not included in those metrics. Hosting providers may maintain their own request logs.

Optional measurement: disabled.