B2B Enterprise ABM & Demand Generation EnginePlaybook3 min readUpdated September 2026

Using Third-Party Intent Data Without Guessing at It

An intent signal means that accounts across a vendor's publisher network are researching topics related to your category, aggregated at the company level. It's a real signal, but teams routinely buy an intent feed, get a daily list of surging accounts, and never change anything concrete about outreach based on it.

The fix isn't a better feed, it's treating intent data as a prioritization signal layered onto accounts you already target, rather than as a lead source or a source of specific talking points.

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.

What intent signals can and can't tell you

A surge shows that someone at a company researched adjacent topics across a publisher network, not who specifically searched or what conclusion they reached. That's a meaningfully weaker signal than a form fill or a pricing-page visit on your own site, and treating it as equivalent to either overstates what you actually know about the account's readiness.

Where intent data earns its keep: prioritization, not personalization

Use a surge to decide which accounts already in your target list get the most personalized outreach this week, rather than trying to reference the specific topic in your copy. Referencing a topic you technically shouldn't know a specific person researched tends to read as unsettling rather than perceptive, since you don't actually know who at the account was searching or why. Keep the copy itself focused on the account's likely situation in general terms, and let the timing of the outreach, not its wording, be the part that reflects the surge.

Combining intent with your own first-party signals

Intent data is far more useful stacked with something you already know directly, a target account visiting your pricing page, or a decision-maker at the account changing roles recently. The combination of a third-party surge and a first-party signal is a meaningfully stronger prioritization case than either one alone, and it's worth building your scoring around that combination rather than the intent feed by itself. A surge with no supporting first-party signal at all is worth a lighter, lower-cost touch, not the same priority as one backed by an actual visit to your own site.

A simple scoring rule you can run without new software

Give an account a couple of points for an intent surge on a genuinely relevant topic, a few more for a first-party pricing-page visit, and a point for a recent decision-maker role change. Route anything that crosses a set threshold to a same-week outbound touch through a sequencing tool like lemlist, rather than leaving it in the standard cadence where it might not get a personalized touch for weeks.

What to skip

Skip buying intent coverage on broad, generic topics your entire ICP already researches constantly, since a signal everyone triggers doesn't discriminate between accounts and won't improve your prioritization. Skip treating a single day's surge as durable too, and instead check for a sustained pattern over a couple of weeks before treating it as a real signal worth acting on.

Common mistakes to avoid with intent data:

  • Buying coverage on broad, generic topics your whole ICP already researches, since a signal everyone triggers can't separate one account from another.
  • Treating a single day's surge as durable instead of checking for a sustained pattern over a couple of weeks.
  • Using a surge as a lead source or quoting the researched topic in outreach copy, which tends to read as unsettling.
  • Handing reps a raw surging-accounts list with no context about which signals raised each account.

How to judge whether the feed is even worth renewing

Before a renewal decision, pull every account your intent vendor flagged as surging over the last full quarter and check how many of those accounts actually turned into a sales conversation, regardless of whether the surge itself gets credit for it. If the overlap between surging accounts and accounts that were already active in your pipeline is high, the feed may be telling you what you already knew rather than adding anything new, which is a fair reason to negotiate the price down or drop it.

Getting sales to actually trust the signal

Reps often ignore a surging-accounts list handed to them with no context, since a raw list looks like one more thing to check rather than a reason to change behavior. Show a rep the specific combination behind each flagged account, the topic surge plus the first-party signal that raised it, rather than a single unexplained score, so they can judge for themselves whether the account is worth a same-week touch instead of trusting a number they can't see into.

Executive Capability Standard

What Good Looks Like

A useful intent-data program treats a topic surge as a prioritization signal for accounts already in the ICP, combines it with a first-party signal before acting, and checks for a sustained pattern rather than reacting to a single day's spike.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Review a week of your intent vendor's surging-account list against accounts you already know are in your ICP, to see how much genuine overlap exists before trusting the feed broadly.
2. Do Manually:Build a simple points-based prioritization sheet by hand, combining intent surges with first-party signals you already track, and route the top accounts to outreach yourself.
3. Delegate:Hand the weekly review of surging accounts to an SDR or ops person once the scoring rule is proven, so it becomes a standing routine instead of a one-off exercise.
4. Automate:Connect your intent feed and first-party signals into a shared scoring rule that automatically flags accounts crossing the threshold for same-week outreach in lemlist.
5. Buy:Add a dedicated intent-data vendor with better account-level topic coverage once your current feed's ICP overlap and refresh cadence prove too thin for the accounts you actually target.

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.

Apollo

Useful for pulling the current decision-maker and role-change data that makes an intent surge a stronger prioritization signal.

Visit Apollo→
lemlist

Useful for getting a same-week, personalized outreach sequence to accounts that cross your prioritization threshold.

Visit lemlist→

Frequently Asked Questions

Does intent data tell us who at the account is researching?

Almost never by name. Most vendors source it from co-op publisher networks and report at the company level, not the individual level. That's an important distinction from a form fill, which does tell you exactly who engaged.

How fresh does intent data need to be to matter?

Check the vendor's actual refresh cadence rather than assuming real-time. A surge labeled as this week's activity may reflect data collected several days earlier, and the value of the signal drops quickly the more stale it is by the time you act.

Should intent data change what we say in outreach?

Usually not directly. Referencing a topic surge in your copy tends to feel unsettling rather than perceptive, since you don't actually know who searched or why. Use intent data to decide who gets outreach and how soon, not what the message itself says.

Is intent data worth it for a small target account list?

Less so. Intent data adds the most value when you have more in-ICP accounts than you can personalize evenly and need a prioritization signal. With a small list, you likely have time to research each account directly instead.

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