How to Identify In-Market B2B Buyers in Real Time

How to Identify In-Market B2B Buyers in Real Time

Identifying in-market B2B buyers in real time requires combining three signal sources into one queue: first-party behavioral signals on your site, third-party intent from networks like Bombora and G2 Buyer Intent, and identity resolution that names anonymous activity. The output is one ranked queue a rep works today.

FL0 is an AI revenue intelligence platform that detects in-market B2B buying signals across the web, consolidating first-party and third-party intent data to surface accounts actively evaluating solutions. The rest of this guide walks through the seven steps revenue teams use to stand up a real-time in-market identification motion, from defining the signal set to routing the resulting queue into rep workflows.

Last updated: 2026-04-28

What does in-market actually mean for a B2B buyer?

In-market means an account is currently evaluating solutions in your category, not that it merely fits your ICP. The Forrester B2B Buyer Insights research and Gartner B2B buying journey study both report that B2B buyers complete most of their evaluation before contacting a vendor, which means in-market accounts often look identical to fit accounts on a firmographic basis but show clear behavioral differences when intent data is added.

A practical operational threshold: an account is in-market when one or more of its stakeholders is actively researching the category, the team is comparing two or more vendors, and the activity has occurred in the last 14 days. The exact threshold depends on sales cycle length and signal density in the category. The LinkedIn B2B Institute research on demand suggests roughly 5% of any given category's TAM is actively in-market at any moment, which sets a useful denominator for the queue.

Step 1: Define the signal set you will track

Start with a small, defensible signal set rather than wiring every available source on day one. The most common starting set covers four signal types: pricing-page visits on your own site (captured via HockeyStack or Dreamdata), demo-request abandonment, third-party category research from a feed like Bombora Company Surge, and review-site visits via G2 Buyer Intent or TrustRadius intent.

For each signal, define the threshold that escalates an account into the in-market queue: a single pricing visit from a fit account, three or more category research events in 14 days, a competitor comparison view on G2. Document the thresholds; otherwise the queue drifts as different reps work different definitions in their head. The TOPO research on intent activation covers the threshold patterns most often used.

Step 2: Stand up identity resolution on your site

First-party signals are useless without identity resolution. Deploy a reverse-IP and identity-graph tool such as Clearbit Reveal (Breeze Intelligence), Leadfeeder (now part of Dealfront), Snitcher, or Albacross so anonymous traffic resolves to a named account. For US-focused product-led growth motions, RB2B and Warmly add person-level resolution on top of account-level identification.

Match rate varies by region, ICP, and traffic source. Test the chosen tool against your last 90 days of inbound and confirm the match rate on the segments you care about before standardizing. The IPinfo company-data documentation covers the underlying data sources most reverse-IP tools rely on.

Step 3: Add third-party intent coverage

First-party signals only see buyers who land on your site. The bulk of evaluation happens off-site, which is why Bombora, G2 Buyer Intent, TrustRadius, TechTarget Priority Engine, Foundry intent solutions, and Madison Logic exist. Pick coverage based on category fit: enterprise IT and security categories favor TechTarget and Foundry; horizontal SaaS favors G2 and Bombora; categories with strong TrustRadius reviewer density add TrustRadius.

For teams running an enterprise ABM platform like 6sense or Demandbase, several of these sources are typically included in the platform license. Audit the included sources before buying anything direct. ZoomInfo Intent is also bundled into many existing ZoomInfo contracts.

Step 4: Consolidate signals into one queue

The most common failure mode is a team buying three intent sources, each producing its own dashboard, and ending up with three queues that no rep works consistently. The fix is consolidation: every signal flows into one priority list per rep, with the same ICP filters and recency rules applied to every source.

Without consolidation, the same account appears as three separate "hot" entries when it triggers signals in three sources, and reps spend time deduplicating instead of selling.

Step 5: Set thresholds and ICP filters once, not per source

Every source has its own scoring scheme. Bombora has surge scores; G2 has buyer-intent levels; 6sense has stage classifications. If you accept the source-native thresholds, you inherit five different definitions of "in-market" inside the same team.

The better pattern is one set of thresholds applied at the consolidation layer: a fit-and-intent score that combines firmographic fit (industry, employee count, revenue band, tech stack), recency of signal, signal depth (a competitor comparison is heavier than a category browse), and stakeholder density (multiple contacts from the same account is heavier than one). Score once, route once, work the queue.

Step 6: Route signals to the right motion within five minutes

Response time is one of the most-replicated findings in inbound research. The InsideSales lead response time research, Salesforce State of Sales reporting, and the original Harvard Business Review study on lead response time all show that contact within minutes correlates with materially higher connection rates than contact within an hour or more. The mechanism is competitive: an in-market buyer is simultaneously evaluating multiple vendors, and the first relevant outreach wins disproportionate share of the meeting.

The routing decision is binary: every high-intent signal that clears your threshold either becomes a same-day rep task or it does not. Drift is what kills the motion. Dashboards full of high-intent accounts that no one called are the operational signature of broken routing. Tools like Outreach and Salesloft Rhythm are commonly used to convert routed signals into rep tasks.

Step 7: Measure the queue, not the source

Track queue-level outcomes: percent of queued accounts contacted, percent contacted that converted to meeting, percent of meetings that converted to opportunity, and downstream win rate. Source-level dashboards are diagnostic; queue-level metrics are operational. If queue conversion is low, the diagnostic step is to inspect which sources contributed the under-performing signals and either tighten the threshold for that source or remove it.

Gong revenue research and TOPO research on intent activation both highlight the same pattern: teams that measure source-level intent volume rather than activated outcomes inflate vanity metrics and miss the conversion gap. The metric that drives the program is meetings booked from the queue, not signals captured at the source.

How does FL0 approach real-time in-market identification?

FL0 is the consolidation layer described in Step 4. First-party signals from your site, third-party signals from Bombora, G2, TrustRadius, TechTarget, or any combination route into FL0, get deduplicated against the same account appearing across sources, and produce one priority queue per rep. The thresholds and ICP filters from Step 5 are configured once at the FL0 layer rather than per source.

For teams without an existing intent stack, FL0 includes baseline first-party and third-party coverage so the queue can exist on day one without buying every source platform first.

Does FL0 require an existing intent platform like 6sense or Bombora?

No. FL0 works either way. Teams running an enterprise stack (6sense, Demandbase, Bombora direct, ZoomInfo Intent) feed those sources into FL0 to consolidate the activation layer above tools they already pay for. Teams without that stack use FL0's baseline coverage to stand up an in-market queue as a single platform purchase. The architecture is designed so the source layer is interchangeable and the activation layer (the queue, the thresholds, the routing) is consistent regardless of which sources sit underneath.