How do you use RevOps to prospect high-value leads?

TL;DR
Target high-value leads with four RevOps moves: score fit and intent together (not separately), enrich records in cost-tiered waterfalls, route qualified leads to the right rep fast, and feed closed-won outcomes back into your ICP so targeting sharpens over time. The win isn't a bigger list — it's spending rep hours only where fit and intent both point the same way.
Fit without intent is a wish; intent without fit is a distraction
Most scoring treats fit (do they match our ICP?) and intent (are they showing buying behavior?) as separate numbers. That's the mistake. A perfect-fit account with zero activity isn't ready. A high-intent visitor who'll never be a fit is a time sink. The accounts worth a rep's hour are the ones where both are high at once.
So score them on two axes and act on the combination.
| High intent | Low intent | |
|---|---|---|
| High fit | Rep now — top priority | Nurture; trigger on first signal |
| Low fit | Self-serve; don't spend a rep | Ignore |
Enrich in tiers, not all at once
You can't score fit on empty records, but you also shouldn't pay for premium data on everyone. Use an enrichment waterfall: cheap, broad enrichment on every new record; premium firmographic and intent data only once a record shows fit or engagement. Spend follows signal, so your data budget goes to the accounts that might actually convert.
Route fast, because speed is the multiplier
Targeting is wasted if the qualified lead sits in a queue. The canonical 2007 MIT/InsideSales Lead Response Management study found that contacting a lead within five minutes versus thirty made teams roughly 21 times more likely to qualify it. The study is old, but the mechanism hasn't changed: attention decays fast. Route high-fit, high-intent leads to the right rep automatically and immediately — by territory, segment, and availability — so the best leads get worked while they're still warm.
Feed outcomes back into the ICP
Your ICP is a hypothesis until closed-won data tests it. Once a quarter, look at which accounts actually closed, expanded, and retained — and which traits they shared. Then update the fit model to weight those traits up and the ones that produced churn or no-shows down. An ICP you never revise slowly drifts away from reality; one fed by revenue gets sharper every quarter.
What to do this week
Take last quarter's closed-won accounts and list the three traits they share that your current lead score doesn't weight. Add those to your fit score, then re-rank your open pipeline. You'll usually find a handful of high-fit accounts that were sitting unworked because the old score missed them.
Frequently asked questions
Should fit and intent be separate scores? Score them on two axes but act on the combination. High fit plus high intent is the only quadrant that earns immediate rep time; the others get nurture, self-serve, or no spend.
How fast should you contact a qualified lead? As fast as you can — minutes, not hours. The classic MIT/InsideSales study found a 5-versus-30-minute response made teams ~21x more likely to qualify. Automated routing is how you hit that consistently.
How often should you update your ICP? Quarterly, using closed-won, expansion, and churn data. Weight up the traits of accounts that actually succeeded; weight down the ones that churned or never engaged.
How RevPack helps
We build the targeting engine: combined fit-and-intent scoring, a cost-tiered enrichment waterfall, automated speed-to-lead routing, and an ICP that updates from closed-won data. If your reps are busy but working the wrong accounts, that's the system we fix.
- MIT / InsideSales — "Lead Response Management Study" (Dr. James Oldroyd, 2007). leadresponsemanagement.org
- Clay — "Go-to-market with unique data" (enrichment). clay.com
Targeted prospecting in RevOps: score fit and intent together and act on the combination, enrich in cost-tiers, route high-fit/high-intent leads to the right rep within minutes, and feed closed-won data back into the ICP each quarter. Precision and speed beat list size.


