Intent data is only useful when the right person at the right account gets the right signal at the right time, with enough context to act. Per Forrester research, the gap between an intent surge and rep action is the single largest leak in B2B revenue funnels: most teams in the under-100M-ARR band lose between 60 and 80 percent of high-intent signals because the scoring is undefined or the handoff is unstructured. This guide walks the seven steps that score intent data for clean sales handoff, including the source-weight matrix, the freshness model, the threshold rules, and the SLA structure.
Full disclosure: Abmatic AI ships an intent-data orchestration layer that scores and routes signals to reps, so we have a financial interest in teams running structured intent programmes. The framework here is platform-agnostic. It works whether the source is Bombora, G2, 6sense, Demandbase, your own first-party data, or a stack of all four.
Score intent data for sales handoff in seven steps: classify every source by reliability and recency, build a weighted score (typical band: 0 to 100), define handoff thresholds (warm at 40, hot at 70, urgent at 90), enrich the signal with account context before it reaches the rep, route by territory ownership, attach a 24-hour acknowledgement SLA, and instrument a feedback loop where reps mark each signal good, neutral, or noise. Without the scoring, reps drown in alerts. Without the threshold, marketing forwards everything. Without the feedback loop, the score never improves.
See a scored intent-data pipeline routing live signals to reps with context packets, book a demo.
The recurring failure modes, per public customer reports across the under-100M-ARR band:
The seven steps below address each of these directly.
| Step | Output | Owner | Time |
|---|---|---|---|
| 1. Classify sources by reliability and recency | Source-weight matrix | RevOps plus marketing | 2 to 3 days |
| 2. Build a weighted score | 0 to 100 score per account per topic | RevOps | 3 to 5 days |
| 3. Define handoff thresholds | Warm, hot, urgent breakpoints | Marketing plus sales leadership | 1 day |
| 4. Enrich signals with account context | Context packet template | Marketing operations | 1 week |
| 5. Route by territory ownership | Owner mapping in CRM | RevOps | 2 to 3 days |
| 6. Attach a 24-hour acknowledgement SLA | SLA rule plus breach dashboard | Sales leadership plus RevOps | 2 days |
| 7. Wire the feedback loop | Rep-side good or noise tagging | RevOps plus sales | 1 week |
Every intent source has different signal quality. A typical defensible weighting hierarchy, per public customer reports:
For the deeper distinction, see first-party intent data and predictive intent data.
Translate the source weights into a 0 to 100 score per account per topic. A defensible default formula: signal strength times source weight times freshness factor (where freshness decays linearly to zero over 14 days for most sources, three days for highest-velocity sources like demo requests). Different topics get separate scores so a single account can be hot on one topic and cold on another. For the merge logic across signal types, see signal merge and how to merge first- and third-party intent.
Three tiers, all required:
The thresholds are not magic numbers. They reflect the volume of signals each rep can actually handle. If your warm-and-up volume exceeds 20 per rep per week, the thresholds need to move up.
The context packet is what turns a signal into a workable lead. Required fields: tier, ICP fit score, primary contact (named person plus title), recent firmographic events (funding, hiring, executive change), tech-stack indicators, primary topic of intent, and a one-line suggested opener. Without this packet, the rep spends 15 minutes researching before the first touch, and most do not bother.
The signal goes to the named rep, not a shared queue. Build a CRM rule that assigns based on territory, account ownership, and deal stage. For accounts with no current owner, route to the SDR pool with a tier-aware priority order.
SLA is acknowledgement, not action. The rep marks the signal seen, decides whether to act, and closes the loop in 24 hours. Breach dashboard fires to sales leadership at the 24-hour mark. Without this rule, signals sit in queues for days and the source weight collapses.
Every signal a rep touches gets a one-click feedback tag: good (this signal led somewhere), neutral (worked but not yet), or noise (wrong account, wrong contact, wrong moment). The feedback flows back into source weights and account scoring. Without this loop, the system never learns and the source weights never improve.
This produces a system where reps see fewer signals, with more context, and acted upon faster, rather than the alternative of more signals, less context, and longer time to first touch.
Three metrics, in order of importance. First, signal-to-action time: median hours from signal hitting the queue to rep action. Target band: under 24 hours for hot signals, under 4 hours for urgent. Second, signal quality rate: percentage of acted-on signals tagged good or neutral by the rep. Target: 60 percent or higher within 90 days of programme launch, per public customer reports. Third, signal-to-meeting conversion rate: of signals at the hot or urgent threshold, what percentage produces a meeting in 30 days.
A demo request and a Bombora topic surge are not the same thing. Source weighting is non-negotiable.
A 30-day-old signal is noise. Linear decay over 14 days is the defensible default; tighter for high-velocity sources.
Marketing dumping every alert into a sales channel kills the channel within weeks. Threshold rules matter; warm signals stay in nurture, hot and urgent reach reps.
The signal arrives without contact, fit, or topic. The rep does nothing. Without enrichment, the queue dies.
Reps see signals and never tag them. Source weights cannot improve. Within two quarters, the score is meaningless.
Scoring sits between the data layer and the action layer. Inputs come from your intent-data programme and predictive intent models. Outputs flow into your intent routing pipeline, the mixed-signal prioritisation framework, and ultimately your buying-committee orchestration.
For the broader scoring lens, see lead scoring and account fit score.
First-party direct intent (demo, pricing) typically weights two to three times higher than third-party broad intent (Bombora, vendor topic surges), per public customer reports. The exact ratio should calibrate to your closed-won correlation; if first-party signals correlate more strongly with wins, increase the ratio.
Linear decay over 14 days is the defensible default for most sources. Demo requests and pricing-page visits decay faster (3 to 7 days). Bombora-style topic surges decay over 21 to 30 days because the underlying buying journey is longer.
Calibrate to volume. Start with 70 on a 0-100 scale; if rep volume exceeds 20 hot signals per week, raise it. If volume is below five, lower it. The threshold is a tuning knob, not a fixed value.
Per-topic scores are stronger. An account hot on a competitor-comparison topic and cold on your category needs different handling. Aggregate to an account-level score for dashboards; route on per-topic.
Three controls: threshold tuning, frequency caps (no more than three signals per account per week routed to the same rep), and the feedback loop. The feedback loop is what kills noisy sources before they exhaust the team.
Track signal-to-meeting conversion at each threshold tier. If hot-tier signals convert to meetings at two to three times the rate of warm-tier signals, the score is doing real work. If they do not, recalibrate weights.
Scoring intent data for sales handoff is the difference between intent data being a marketing report and intent data being a revenue input. The system is not magic. It is seven steps, written down, instrumented, and tuned. The teams that build it cleanly see signal-to-action collapse from days to hours; the teams that do not stay stuck on the report.
See a scored intent pipeline running live with thresholds, context packets, and SLAs, book a demo.