GuideBuyer intent

25 B2B buyer intent signals, and how to score them

A ranked list of 25 behavioral and business-event signals that indicate buyer intent, grouped by strength, with a 100-point scoring rubric that combines causal events, engagement and third-party intent while capping the inputs that cannot be trusted alone. The ranking is a judgment framework, not measured data: use it as a starting point and adjust it against your own closed-won accounts.

Updated Oct 21, 2026 · By Pankaj Kumar, CEO & Co-Founder
Direct answer

Buyer intent signals are observable behaviors and business events that suggest an account is moving toward a purchase. This page ranks 25 of them in four groups: causal business events, stacked events, first-party engagement and third-party intent. A 100-point rubric combines them, capping third-party intent so it can lift a borderline account but never put an event-free account on top.

The 25 signals, grouped by strength

Group A: causal business events (strongest)

#SignalStarting pointsNotes (heuristic)
1New leader in the buying function35Often receptive in the first months after the start date; see leadership change signals
2Hiring surge in the buying function (2+ roles in 30 days)30See hiring signals
3Vendor dropped in your category35Time-sensitive; act soon; see technology change signals
4CRM or core-system migration25Adjacent categories reconsidered in the same project
5First adoption of an adjacent category20A motion is being built; the tooling decision is unmade
6Funding round (Seed to Series B)20Broad; relevance often lasts for months after the round closes; see funding signals
7Expansion: new region, office or product line20New motion, new capability needed
8New function created (first RevOps hire, first SDR manager)25Greenfield decision
9Strategic initiative announced publicly15Quote it back
10Acquisition or merger15Longer fuse; consolidation follows

Take the highest single event, not the sum, for the base (maximum 35 points before ICP fit).

Group B: stacking (the bonus, capped at 10)

#SignalPointsNotes
11Second Group A event within 45 days, same function+7In our judgment, the strongest timing evidence
12Third Group A event within 60 days+3 (cap)Diminishing; the case for timing is already made

Group C: first-party engagement (confirming, specific)

#SignalPointsDecay
13Pricing page visit830 days
14Comparison or "vs" page visit830 days
15Integrations or security page visit630 days
16Multiple people from the same account in 14 days+630 days
17Return visit within 7 days+430 days
18High-intent content download (buyer's guide, ROI tool)545 days
19Product signup or trial started15Does not decay while active
20Email reply or link click on a trigger-based email630 days

Cap Group C at 20 points.

Group D: third-party and review activity (confirming, shared)

#SignalPointsNotes
21Topic surge on your category8Every competitor sees it; see buyer intent data
22Topic surge on an adjacent category4Function-level evidence only
23Review-site category activity8Late-stage; competitors see it too
24Competitor comparison activity naming you10Rare and valuable
25Event or webinar registration on the topic5Confirms function; weak alone

Cap Group D at 15 points.

Declared intent (overrides)

A demo request, inbound reply or explicit hand-raise adds 20 points and moves the account straight to a human thread regardless of the rest. It is added after ICP fit is applied.

The rubric

ComponentPointsRule
Highest Group A event0 to 35Highest single event; weight by function relevance to your ICP
Stacking (Group B)0 to 10Second event +7, third +3
First-party engagement (Group C)0 to 20Sum, capped, decaying
Third-party and review (Group D)0 to 15Sum, capped
Declared intent0 or 20Added after ICP fit; routes to a human thread
ICP fit×0.5 to ×1.2Scales the A to D points (not declared intent). The final score is capped at 100. From your weighted ICP; the ICP generator produces one
ScoreStateAction
70 or moreStrong fit, worth a person's timeHuman thread to the economic buyer; outreach to the rest of the committee drafted for your team to review and approve (see buying committee)
50 to 69WatchOutreach to the coach drafted for your team to review and approve; recheck in 30 days
Under 50OutIgnore until a Group A event fires

The weights sum to exactly 100: 35 for the strongest event, 10 for stacking, 20 for first-party engagement, 15 for third-party activity and 20 for declared intent. The cap on Group D is the whole design. A perfect third-party surge score at an account with no business event tops out at 15 points times ICP fit (at most 18), which is never enough to trigger a human. Once a Group A event appears, the same surge becomes confirming evidence that can lift the account over 70. That is how intent stays an input and never becomes the trigger. The thresholds are starting values, not validated cut-offs.

Worked example (illustrative, not a real account). A new head of sales is hired (35). A hiring surge in the same function follows within 45 days (+7 stacking). The account visits the pricing page (8) and two people from it visit within 14 days (+6), so Group C is 14. A topic surge on your category adds 8 in Group D. Subtotal: 35 + 7 + 14 + 8 = 64. With an ICP fit of ×1.1, 64 × 1.1 = 70.4, which rounds to 70, so the account goes to a human thread. Without the hiring surge the subtotal is 57, times 1.1 is 62.7 (63), which stays on watch.

How does PravRaha score intent?

PravRaha's Market Scanner reads hiring, funding, tech-stack and leadership signals against your ICP and shows which accounts appear to be moving and why. It does not publish a score cut-off, a buying date or a validated hit rate. Outreach is drafted for your team to review and approve, then sent from your own connected mailbox. On the Growth plan, the Pipeline Optimizer reads outcomes and adjusts what gets prioritized in the next cycle. The rubric above is a framework you can use by hand, with or without PravRaha. See the platform page.

After you have a score

Next step

Run the numbers on your own outbound.

Free, no signup. The ICP generator and outbound ROI calculator use the same logic PravRaha uses to prioritise accounts.

FAQ

Questions, answered.

In our judgment, stacked business events in the buying function: a new leader followed by hiring, or a tech-stack change followed by a dropped vendor. Among behavioral signals, repeated visits to pricing and comparison pages by multiple people from the same account are strongest. Single anonymous visits and third-party topic surges are weakest alone.

Use a weighted rubric: causal business events (up to 35 points for the strongest single event), stacking (up to 10), first-party engagement (up to 20, decaying over 30 days), capped third-party intent (up to 15) and declared intent (up to 20). Those components sum to exactly 100. ICP fit scales the event and engagement points (0.5 to 1.2), and the final score is capped at 100. 70 or more suits a human thread, 50 to 69 is watch. The weights are a judgment framework; tune them on your closed-won accounts.

No. The ranking and point values are a judgment framework built from how buying decisions are made, not measured data or a study of conversion rates. They give you a consistent starting order. Replace them with weights from your own closed-won and closed-lost accounts as soon as you have enough history.

No. A high score means the account deserves attention first. Signals raise the odds of a useful conversation; they do not promise a purchase or a purchase date.

Next step

See which accounts are moving.

Point PravRaha at your market and work from movement instead of a filtered list. If you would rather walk through it with us first, a Pipeline Review is 45 minutes on your ICP and your current stack.

Built from Ranchi. Built for the world.