Signal Library

The b2b intent data signal

B2B intent data outbound is the most over-sold signal in the game. It is directional, not a green light, and it is best used to stack.

A topic surge times the move. It does not justify it on its own.

By Rahul · Updated June 2026 · 7 min read

Book a Fit Check

Signal Snapshot

Soft signal

Indicates

An account is researching your category

Strength

Directional · soft, weak alone

Window

Weeks, surge windows move slowly

Detect with

Bombora, G2 Buyer Intent, 6sense, ZoomInfo Intent

Skip it when

You use it alone, or no ICP fit underneath

Family: research and topic surge Best as a stacking layer

B2B intent data outbound runs off topic-surge research: tools that flag when an account reads about your category across the web. It is the softest signal in outbound, directional, not a trigger.

Two flavors

One signal, two very different flavors

"Intent data" gets sold as one thing. It is really two, and they are not equally useful. Knowing which one you are looking at is most of the job.

1 Broad · soft

Co-op and bidstream topic surge

Bombora and the big platforms watch content consumption across thousands of B2B sites. When an account's research on a topic spikes above its own baseline, you get a "surge." It is broad, account-level, slow, and never tells you the person.

2 Narrower · higher

Review-site activity, like G2

G2 Buyer Intent shows accounts comparing products, reading reviews, and checking pricing in your category. That is closer to a real evaluation than a topic surge. Still account-level, still anonymous, and only useful if your buyers actually use G2.

Both are third-party: they read the open web, not your own data. The opposite is first-party intent, the visits and behavior on your own site, which we cover in the website intent signal. First-party tells you who. Third-party only tells you maybe.

How do you detect an intent surge?

You buy access to a data co-op or a review marketplace and read the surge against an account's own baseline. Here is what each source actually catches.

Source	What it catches	Freshness
Bombora Company Surge	Topic research across roughly 6,000 B2B sites, scored against each account's own baseline. The category standard for broad surge.	Weekly refresh
G2 Buyer Intent	Accounts comparing products, reading reviews, and viewing pricing on G2. Narrower and higher intent than open-web surge.	Near daily
6sense	Blends third-party intent with anonymous web activity into a predictive stage. Reviewers call the model directional, not a crystal ball.	Continuous, modeled
ZoomInfo Intent	Bombora-fed topic intent bundled with contact data, so you can pair a surging account with people to reach.	Weekly, contact-matched

Tool-agnostic

We work across most intent providers and adapt to your stack. For the full breakdown of what each one is worth, see our guide to signal and intent tools. With intent data, the harder question is never the provider, it is what you do once the surge fires.

The compliance line

Topic intent from a co-op like Bombora is aggregated at the account level and gathered under the provider's own consent framework, so the surge itself is low risk to act on. The exposure starts when you pair it with named EU or UK contacts, which becomes personal data under GDPR and usually needs a lawful basis. Keep third-party intent at the account level, add people only where you have one, and take advice you trust, not ours, as the legal word.

Paying for intent data and not sure it is earning its keep?

Book a Fit Check

The window: slow to fire, slow to fade

Intent data is not a perishable alert like a job change. Surge windows move in weeks, which is both the upside and the catch.

The lag

You are already late

Most surge data refreshes weekly. By the time the alert lands, the committee may have started shortlisting. You are joining a conversation in progress.

The plateau

A multi-week read

A surge usually holds for a few weeks while the account researches. You have room to move, but no precise moment that says "now."

The fade

Back to baseline

The surge settles. Either they bought, they paused, or it was never real intent. The signal tells you none of those, so do not over-read the drop.

The slow window is exactly why intent data works better as a timing layer than a trigger. It tells you an account is warm-ish over a stretch of weeks, which is the right shape to combine with a sharper signal that tells you the moment.

The play: stack first, then act on the surge

We almost never start a sequence off intent data alone. The play is to use the surge to time and theme outreach that a stronger signal already justified.

1

Filter the surge to ICP fit first

A surge on an account that will never buy your category is noise with a score on it. Cut the list down to accounts that already match your ICP before anything else.
2

Look for a second, sharper signal

A website visit, a job change, product usage, a hire. The intent surge becomes worth acting on the moment a person-level or first-party signal lands on the same account.
3

Find the person, then theme the message

Since the surge is account-level, enrich to the right contact. Use the surging topic to choose the angle, not to claim you know they are buying. Lead with the problem, never the surveillance.
4

Reach out about the problem, on time

A short, specific note about the thing they are clearly weighing, sent inside the surge window. The data set the timing and the topic. The reason to care comes from the harder signal underneath.

Combining a soft signal with a sharper one is the whole point of the signal stacking play, where intent data earns its place as a layer rather than a lead.

The angle

The angle that works, and the one that doesn't

The fastest way to waste intent data is to tell the prospect you can see them researching. Lead with their problem, not your dashboard.

The generic move

"Hi Sam, I noticed your team has been researching outbound platforms recently. Looks like you're in-market. Want to grab 15 minutes to see a demo?"

✕Claims to know intent it cannot actually see
✕Creepy, the account-level surge was never about Sam
✕Leads with a demo before earning a reason to care

The signal-native move

"Hi Sam, saw your team is scaling the SDR org. Most teams at that stage hit a deliverability wall around now. Here's how two similar teams got past it. Worth a look whether or not we ever talk."

✓Uses the surge topic to pick the angle, silently
✓Anchors on a real, visible signal, not the surge itself
✓Gives value first, asks for nothing up front

Where it is strong, and where it is weak

An honest read, because the people selling you a six-figure intent contract will only show you the strong column.

Strengths

✓Surfaces accounts you would never have known were curious
✓Good for prioritizing a big TAM by who to look at first
✓A useful timing and theming layer on top of a real signal
✓Review-site intent is genuinely close to a live evaluation

Watch-outs

!Account-level, you never learn who is actually researching
!Slow, weekly refresh means you often arrive late
!Directional, a surge is curiosity, not a buying decision
!Expensive, and easy to over-trust because it has a score

When intent data is just noise

This is the signal most likely to send you sequencing the wrong accounts with false confidence. The whole-account attribution is the root of it: you cannot tell who, or whether they matter. Skip it when:

✕You are using it as a standalone trigger. A surge alone is not a reason to start a sequence. With no fit and no second signal underneath, it is a guess with a number attached.
✕There is no ICP fit under the surge. A great topic spike at a company that will never buy your category is a research footnote, not a pipeline play.
✕You cannot find a credible person. Account-level interest with no plausible buyer to reach is a dead end. The surge does not hand you a contact.
✕The surge could be anyone. A student, a competitor, or a curious analyst can move a topic score. Without corroboration, treat it as directional and nothing more.

Worth keeping in perspective: Gartner finds B2B buyers complete roughly 65 to 70 percent of their purchasing journey before they engage a sales rep. Intent data is one imperfect window into that hidden stretch, not a clear view of it.

Want intent data stacked into a motion that actually books meetings?

Book a Fit Check

Stack it with

Intent data is weak alone and useful in a stack. Its whole job is to add timing and a theme to an account a sharper signal already flagged.

+ Website intent

First-party visits on a surging account turn maybe into yes. Now you know they came to you, not just the category.

+ Job change

A new decision-maker at a surging account is researching with a fresh mandate. The two together name the person and the why.

+ Hiring

A surge plus open roles for the exact gap you fill makes the need concrete and public, not just inferred.

Scoring and combining these on one account is its own motion. We map and weight the combinations through signal mapping, so the soft signals support the strong ones instead of standing in for them.

How we would run it

An example, start to finish

An illustrative walkthrough of the method, not a specific client result. We report real numbers only when they are real.

1

Week 0 · Surge fires

A topic spike lands

Bombora flags a surge on "outbound sales software" at a Series A account. On its own, we treat it as a watch item, not a lead.
2

Week 1 · Qualify and stack

Check fit and a second signal

The account fits the ICP, and a new VP of Sales started six weeks ago. Now the surge has a person and a why behind it.
3

Week 1 · Theme the note

Lead with the problem

A short note to the VP about scaling outbound at their stage, themed by the surging topic. No mention of the dashboard.
4

Weeks 2 to 3 · The ask

Offer a useful conversation

Inside the surge window, a light follow-up and an offer to compare notes. The intent data set the timing, the stack earned the reply.

Signals like this fed pipeline we've built inside these companies

Palm.ai

Alcméon

Mindflow

CEF.AI

Boolee

CoachHub

Inrō

Buster.AI

Palm.ai

Alcméon

Mindflow

CEF.AI

Boolee

CoachHub

Inrō

Buster.AI

FAQ

Questions founders ask

What is b2b intent data outbound?

It is outbound timed off third-party intent data: research-surge signals showing an account is reading about your category across the web. Tools like Bombora, G2 Buyer Intent, 6sense, and ZoomInfo Intent watch content consumption and review-site activity, then flag accounts whose topic interest spikes above their own baseline. It tells you a company is curious. It does not tell you who, or that they are ready to buy.

Is third-party intent data accurate enough to trigger outreach?

On its own, no. It is account-level and directional, not person-level and confirmed. Reviewers describe predictive intent as directional rather than a crystal ball, and most third-party surge data refreshes weekly, so the buying committee may have shortlisted vendors before your alert lands. Treat a surge as a reason to look closer at an account that already fits, not as a green light to start a sequence.

How is review-site intent like G2 different from topic-surge data?

Review-site intent is narrower and higher intent. G2 Buyer Intent shows accounts actively comparing products, reading reviews, and viewing pricing in your category, which is closer to a real evaluation than a broad topic surge across the open web. It is still account-level, matched to a company rather than a named person, and it only helps if your buyers actually research on G2. We fold review-site activity in here because it is a flavor of intent data, not a separate event.

Why is intent data the most over-sold signal?

Because vendors sell the surge as a buying signal when it is really a curiosity signal. Whole-account attribution means you cannot tell who is researching, the data is slow, and a topic spike can come from a student, a competitor, or someone two floors away from the budget. It is genuinely useful as a timing layer on top of a stronger first-party signal, and genuinely weak as a standalone trigger. The honesty gap is what burns teams.

What is the best way to use intent data without wasting it?

Stack it. Use a first-party or person-level signal to justify the outreach, then let the intent surge tell you when to move and which angle to lead with. A surge on an account that already shows website visits, a job change, or product usage is worth acting on. A surge on an account with none of those is a watch item, not a sequence. The signal times outreach you can already defend.

Keep going