A Practical Filter for B2B Intent Data, Before You Buy More
Intent data vendors sell the promise of knowing who's about to buy before your competitors do. What they usually deliver is a long list of accounts showing some level of research activity, most of which was already going to happen regardless of anything you do.
This is a filter for deciding which intent signals are specific enough to act on, and which ones are noise dressed up as insight.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
How do you tell a real intent signal from routine research?
A company researching your product category once is common and means almost nothing on its own; most companies periodically evaluate tools in categories they already use. A sustained spike, the same account showing repeated research activity across several sessions in a short window, is a much stronger signal that something has changed internally.
Set a threshold before you act on any signal: a single page view doesn't qualify, but a pattern across multiple visits, multiple people at the account, or multiple related topics does. Without that threshold, sales ends up chasing every account that appears on a report, regardless of how thin the actual signal is.
Weigh the signal against what you already know about the account
An intent signal from an account that's a poor fit for your product, wrong size, wrong industry, no budget authority visible, isn't worth much no matter how strong the signal looks. Filter intent data through your existing ideal customer profile before it ever reaches a rep's queue.
The most useful signals are the ones on accounts you'd already want as customers, showing new activity now. Signals on accounts outside your ICP just create busywork for sales, chasing leads that were never going to close regardless of timing.
Check each intent-flagged account against these filters before it reaches a rep:
- Does the account match your ideal customer profile on size, industry and visible budget authority?
- Is the activity a pattern across several sessions instead of a single page view?
- Are multiple people at the account involved, or are several related topics being researched?
- Can you name the topic or competitor the account was researching, so outreach has something concrete to reference?
- Does a named rep or SDR team own first contact, with an expected response time?
Give sales a specific reason to reach out, not just a name
Handing a rep a list of "accounts showing intent" with no context produces a generic, obviously templated outreach that gets ignored. Pass along what topic or competitor the account was researching, so the rep can reference something concrete instead of a vague "noticed you're exploring solutions in this space."
A specific reference point, tied to an actual signal, reads as informed rather than creepy. A generic mention of "intent data" in an email, without anything specific behind it, often has the opposite effect and makes the outreach feel like surveillance.
For example, instead of telling a rep that an account is showing intent, pass along a note such as 'three people at this account read your pricing comparison pages this week, and one looked at a competitor alternative page.' The rep now has a concrete, accurate reason to reach out and can phrase the first message around the buyer's likely question rather than around the data feed. If a vendor can't tell you which topics drove a signal, treat that as a limit on how much weight to give it, and lean more on activity you can inspect directly.
How do you know if intent data is producing pipeline?
Intent data vendors report on volume of signals delivered, not on whether those signals produced anything. Track, on your own side, how many intent-flagged accounts sales actually engaged, and how many of those engagements produced a real opportunity, separate from your normal inbound and outbound pipeline.
If a quarter passes with a lot of flagged accounts and very little resulting pipeline, that's a reason to tighten your threshold or reconsider the vendor, not a reason to keep passing every signal straight to sales on faith that volume alone will eventually pay off.
Decide who owns follow-up before the signals start flowing
Intent signals that land in a shared inbox with no clear owner get ignored within days. Assign specific reps or an SDR team to intent-flagged accounts before you turn the feed on, with a clear expectation for how quickly a flagged account gets a first touch.
Review that response time periodically. A signal that sits untouched for two weeks before anyone reaches out has usually gone stale, since whatever triggered the research activity may no longer be an active priority for the buyer by the time your rep finally calls.
Rotate ownership deliberately if a specific rep is consistently slow to follow up on flagged accounts. A signal program only works as well as the follow-through behind it, and a repeated pattern of slow response from one person is a coaching conversation, not a data problem.
Share the response time metric with the whole team, not just the slow performer, so the standard is visible and consistent rather than something only raised privately after the fact.
What Good Looks Like
A working intent data program filters raw signals through a fixed threshold and your existing ideal customer profile before they reach sales, gives reps a specific reason for outreach rather than a bare account name, and tracks whether acted-on signals actually convert to pipeline.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Frequently Asked Questions
Is a single page visit from a target account worth acting on?
Generally not on its own. A single visit is common and often means nothing more than routine research. Look for a pattern across multiple sessions, multiple people at the account, or multiple related topics before treating it as a real signal worth a rep's time.
Should sales chase every account that shows up in an intent report?
No. Filter signals through your existing ideal customer profile first. A strong intent signal on an account outside your ICP is still a poor use of a rep's time, no matter how active that account looks in the raw report.
How do we know if our intent data subscription is worth the cost?
Track how many flagged accounts sales actually engaged and how many of those turned into real pipeline, separate from your normal channels. If that number stays low quarter over quarter, tighten your threshold before assuming the whole approach doesn't work.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Ranking for High-Intent Queries When an AI Overview Sits Above You
How to structure pages for high-intent, commercial search terms so both traditional rankings and AI answer overviews can actually extract and cite them.
Building a Topic Cluster Map From Real Search Intent
A worksheet-style walkthrough for grouping keywords by what searchers actually want, so your content structure matches real intent instead of guesswork.
Why AI-Referred Visitors Convert Differently (and What to Track)
AI-referred visitors arrive mid-decision, not mid-search. Here's how to compare their conversion rate fairly against organic and paid traffic.
Content Syndication Without Duplicating Your Own Rankings
Compare guest republishing, licensed syndication networks and self-syndication, and learn how to protect your canonical rankings when others repost your work.
Why AI Citations Show Up as 'Direct Traffic' and How to Fix It
Most AI assistants strip referrer data, so traffic from a citation shows up as direct in your analytics. Here are three practical ways to recover the signal.
The Four Numbers Worth Putting on an AI Search Dashboard
Most AI search dashboards bury leadership in vanity metrics. Here are the four numbers worth reporting and a sample layout for a first version.