A lot of teams buy an intent data subscription, get a weekly list of "surging accounts", forward it to sales, and six months later can't point to a single deal it produced. The data usually isn't the problem. What's missing is a plan for which signals deserve a rep's attention, how fast to act, who to contact and what to say.
This guide covers how intent data works, where each kind is strong and weak, and a workflow for turning it into meetings, starting with the data you already own.
What intent data is
Intent data is behavioral evidence that a company, or a person at a company, is researching a problem or a product category. It comes in three kinds, based on who collects it.
Type | Where it comes from | Examples | Strength | Weakness |
|---|---|---|---|---|
First-party | Your own website, emails, product and events | Pricing page visits, demo requests, trial signups, webinar attendance, feature usage | Directly about you, fresh, already paid for | Only covers people who already found you; most visitors are anonymous |
Second-party | Another company's first-party data, shared or sold | A review site telling you which companies viewed your category or your profile | Specific to buying research | Limited to that one platform's audience |
Third-party | Aggregated across many sites by a data provider | An account reading far more content than usual about "sales engagement" or a competitor | Finds accounts before they visit you | Account-level, indirect and noisy |
It helps to know how third-party "surge" data is made. Providers like Bombora collect content consumption from a network of B2B publishers, map the reader to a company (usually by IP address or domain), assign the content to topics, and flag a surge when a company reads about a topic much more than its own normal baseline. So a surge tells you "someone at this company, maybe several people, is reading more about this subject than usual." It doesn't tell you who, why, or whether they're buying or writing a report.
That's why intent data works best as a timing layer on top of a good account list, not as a way to build the list. If you want a broader framework that also scores funding, hiring, leadership and technology changes, see our guide to signal-based prospecting. This post stays with intent data itself.
Match the response to the signal
Different signals deserve different speeds. A reasonable starting point:
Signal | Type | Confidence | Response |
|---|---|---|---|
Demo request or contact sales form | First-party | Very high | Minutes, not hours |
Trial signup from an ICP-fit company | First-party | Very high | Same day |
Repeat pricing or comparison page visits from a known account | First-party | High | Within 24 hours |
Viewed your profile or category on a review site | Second-party | Medium to high | Within a few days |
Surge on your category topics | Third-party | Medium | Outbound within a week if the account fits your ICP |
Single blog read or newsletter click | First-party | Low | Nurture only |
The research on inbound speed is old but clear. In The Short Life of Online Sales Leads (Harvard Business Review, March 2011), Oldroyd, McElheran and Elkington found that firms contacting a lead within an hour were nearly seven times as likely to qualify it as firms that waited longer than an hour, and over 60 times as likely as those that waited a day or more. In their audit of 2,241 US companies, the average response time was 42 hours. The details of buying have changed since then, but a hand-raiser who hears back tomorrow has had a full day to talk to someone else.
Layer 1: Get first-party intent working
Start with what you own. It costs little, it's the most reliable data you'll get, and until it works, third-party data just gives you more signals you can't act on.
Identify website visitors. Company-level identification (Leadfeeder, now part of Dealfront, or HubSpot's Breeze Intelligence, which absorbed Clearbit) matches visits to companies. Person-level tools like RB2B try to name the individual, mostly for US traffic. Check privacy rules for your region before turning on person-level identification.
Define which pages count. Pricing, comparison pages, integration docs and case studies for your core segment are high-intent. The careers page and blog homepage are not. Exclude existing customers and your own team.
Score engagement over a window. One pricing visit is interesting. Three people from the same company on pricing and a competitor comparison page in the same week is a buying committee.
Use product data if you have a free tier or trial. Teammates invited, usage approaching a plan limit and a key feature activated are usually stronger signals than anything on the website.
For the enrichment side of website traffic in more depth, see our guide on how to enrich website visitors.
Layer 2: Add third-party intent carefully
Once first-party signals reliably reach reps, third-party data can find accounts earlier in their research. Common sources are Bombora (topic surge data, also resold inside many other platforms), ABM platforms like 6sense and Demandbase that build their own intent models, TechTarget for technology buyers, and review sites like G2 and TrustRadius for second-party category and competitor research.
A few rules that save a lot of wasted outreach:
Pick narrow topics. "Sales" or "marketing automation" surges at almost every company. Choose topics close to the specific problem you solve, plus competitor names.
Require ICP fit first. Only look at surges from accounts that already match your target firmographics. Intent should never pull an off-profile company into a rep's queue.
Look for persistence. An account surging on related topics for two or three weeks in a row is more meaningful than a one-week spike.
Test it before trusting it. Split surging ICP accounts into two groups, work one and not the other for a quarter, and compare meetings and pipeline. Also check your recent closed-won deals: did the provider show those accounts surging before the opportunity opened?
Layer 3: Turn the signal into a contact and a conversation
This is where most intent programs break. A surge or an identified visit gives you a company. A rep needs a person, a verified way to reach them and a reason to write. The workflow:
Signal arrives. Your visitor identification tool, intent platform or CRM sends the company domain and the signal details.
Check fit. Enrich the company (size, industry, location, tech stack) and drop anything outside your ICP.
Find the buying committee. Look up the two or three roles that usually buy from you at that company.
Get contact details. Run a waterfall for verified work emails and, for high-confidence signals, mobile numbers.
Route. Create or update the account and contacts in HubSpot or Salesforce with the signal and its date attached, then alert the account owner.
Reach out within the response window for that signal tier.
In Databar you can receive signals by webhook or API into a table, run company enrichment and contact waterfalls across 160+ data providers, and sync results to your CRM, so steps 2 to 5 run without anyone copying domains between tools. Flows let you lay out that sequence as one pipeline.
What to say (and what not to)
Use intent data to decide who and when. Be careful about using it to decide what the first line says.
"I saw you were on our pricing page yesterday" tells the reader they're being tracked, and most people don't like that. "Your company has been researching sales engagement tools" is worse, because it's often wrong and always strange. Instead, write about the problem the signal points to:
Category surge: "Teams comparing sales engagement tools right now usually get stuck on the same question: how to keep contact data fresh once it's in the sequencer. Here's how a few teams your size handle it."
Competitor research: "If you're weighing [category] options, these are the three questions I'd ask any vendor, including us."
Pricing page visits: A short, useful note from the account owner offering a quick walkthrough of plans or a relevant case study. Don't mention the visit.
The exception is when the person gave you the signal on purpose: a demo request, a webinar question, a trial signup. Referring to those directly is just good service.
Mistakes that waste intent budgets
A dashboard with no owner. If a signal doesn't trigger a specific action (an alert, an enrichment run, a sequence enrollment), nobody will act on it.
Leading with third-party data. Buying surge data before first-party signals reach reps means more noise flowing into a process that doesn't work yet.
Treating every signal the same. Push only high-confidence, ICP-fit signals to reps in real time. Send the rest to a weekly review or nurture, or reps will start ignoring alerts altogether.
Stopping at the account. Intent data names a company. Without contact enrichment, a rep has to research each account manually, and speed disappears.
Never checking results. Track meetings and pipeline by signal type every month and cut what doesn't convert.
A 30-day rollout
Week 1: Audit first-party signals
List every signal you already capture (forms, visitor identification, email engagement, product events) and where it lands today. Turn on company-level visitor identification if you don't have it. Agree with sales on which pages and actions count as high intent.
Week 2: Build the workflow
Define three tiers (act now, this week, nurture). Connect the signal source to enrichment so each qualifying company gets matched contacts with verified emails. Set up routing to account owners and alerts where reps actually work.
Week 3: Go live and measure
Route the first accounts to reps. Track time from signal to first touch, reply rate, meetings booked and whether reps agree the accounts were worth their time.
Week 4: Tune, then decide on third-party
Adjust tier thresholds, remove pages or signals that only produced noise, and look at which signals led to meetings. Only then decide whether third-party intent is worth piloting, and design the pilot with a control group from the start.
Common questions
What is the best source of intent data?
Your own first-party data: demo requests, trial activity, and identified visits to high-intent pages. It's about your product specifically and it's current. Third-party data is useful for finding accounts earlier, but it's less precise.
How much does intent data cost?
It varies a lot by type. Website visitor identification tools are typically monthly subscriptions, often priced by identified companies or contacts, and several offer free or entry tiers. Third-party intent from ABM platforms and data providers is usually sold on annual contracts through a sales process, priced by topics, accounts or seats. Get current quotes, and pilot with a clear success metric before signing a long contract.
Is intent data accurate?
First-party signals are accurate about what happened on your site, but matching a visit to a company or person is probabilistic, especially with remote workers and VPNs. Third-party surge data is directionally useful at the account level and unreliable as proof that a specific company is buying. Treat it as a reason to look, not a reason to assume.
Does intent data comply with privacy law?
That depends on the provider, how the data is collected and where your prospects are. Company-level data is generally lower risk than person-level identification, which faces stricter rules in places like the EU. Ask vendors how they source and consent their data, and check with your legal team. For more on reading and acting on specific buyer signals, see our guide to buyer intent signals.
Connect intent to action
Intent data tells you which accounts to look at. Enrichment tells you who to talk to there and how to reach them. If you want to wire those together, Databar paid plans start at $99/month, you're only charged for results, and there's a 14-day trial with the full product.
Recent articles
See all








