The Problem with Traditional Lead Scoring
Your rep opens a new lead in the CRM. Score: 82. She clicks into it and finds a company name, an email, and a note that says "downloaded whitepaper." That's the entire context. She picks up the phone with nothing to say beyond the generic pitch.
Most B2B lead scoring works this way. Points get assigned for demographic fit (job title matches ICP, company size is right) and digital engagement (visited the pricing page, opened three emails, attended a webinar). Add them up and you get a number. The number tells your rep to call, but it doesn't tell them what to say.
SiriusDecisions research found that 67% of B2B leads that score as "qualified" never convert. The scoring model said they were ready. The conversation proved otherwise. The gap between a scored lead and a real buyer is where pipeline goes to die.
What TruSQL Scores Differently
TruSQL™ is Rover Insights' proprietary scoring system. It rates individual leads 0-100, but the inputs are different from anything else on the market: real phone conversations with HR and finance professionals, not web clicks or form fills.
Three components make up every score. Match Quality (40%) measures how closely the prospect's profile matches your configured Ideal Customer Profile: job title, company size, industry, geography, and product needs. Buyer Intent (35%) captures stated buying signals from the conversation: timeline, budget, demo interest, and in-market status. Call Sentiment (25%) reflects the AI analysis of the conversation tone and engagement level.
Each component is visible. Your rep doesn't see a single number and wonder what it means. They see exactly which factors pushed the score up or down, plus a written explanation of the reasoning.
How the Three Components Work
Match Quality (40%)
Before any scoring happens, you configure your ICP in the platform. Target job titles, management levels, company size ranges, industries, and product needs (Payroll, HRMS, LMS, ATS, PEO, EXP). When a new lead enters the system, TruSQL compares their profile against your ICP criteria. More matches, higher score on this component.
This is the foundation. A VP of HR at a 500-person manufacturing company looking for payroll software scores differently than an HR coordinator at a 10-person startup. The Match Quality component ensures your highest scores go to leads that fit your buyer profile.
Buyer Intent (35%)
This is where TruSQL diverges from every other scoring system. Buyer Intent isn't inferred from page visits or content downloads. It's captured directly from the conversation.
During each 6-12 minute call, CDR representatives capture structured buying signals: Is the prospect in-market, lifecycle, or not currently buying? What's their timeline: immediately, within 6 months, 6-12 months, or 12-24 months? Do they have budget approved? Have they expressed interest in a demo? What's their current solution, and how would they rate their satisfaction?
A prospect who says "We're evaluating payroll vendors with a Q2 deadline and budget approved" scores very differently from someone who says "We signed a 3-year contract last month and we're happy with it." Both are valuable data points. The score reflects the reality.
Call Sentiment (25%)
AI analysis evaluates the tone and engagement level of each conversation on a 5-point scale: Strong Positive, Positive, Neutral, Negative, Strong Negative. Sentiment isn't just about politeness. It captures how engaged the prospect was, how openly they shared information, and whether the conversation indicated genuine interest or passive participation.
A prospect who spent 11 minutes explaining their compliance challenges and asking about integration options scores higher on sentiment than someone who gave one-word answers and ended the call at 4 minutes. The length and depth of engagement are real signals.
What Makes the Score Explainable
Black-box scoring is the norm in B2B. Your lead scored 85. Why? "The model determined high intent." That's not useful when your rep needs to prepare for a call in 10 minutes.
Every TruSQL score includes two things other systems don't: a Lead Score Description (a written explanation of why this lead scored the way it did) and AI-generated Recommended Next Steps (a prioritized action list based on the score and conversation context).
A rep looking at a TruSQL score of 84 might see: "Strong ICP match (VP HR, 800-employee financial services company). Stated Q3 buying timeline with budget approved. Currently using [Competitor] with satisfaction rating of 2/5. Expressed interest in a demo. Call sentiment: Strong Positive (10-minute call with detailed feature discussion). Recommended: Schedule demo within 48 hours focusing on compliance automation and multi-state payroll."
Compare that to: "Lead score: 84. Engagement: High." The explainability isn't a nice-to-have. It's the difference between a rep who walks into a call prepared and one who's guessing.
Score Ranges and What They Mean
TruSQL uses three score bands with color coding in the platform.
- 75-100 (Green, Strong Fit): High ICP match, clear buying signals, positive call sentiment. These leads carry the strongest combination of fit, intent, and engagement. Prioritize immediate follow-up.
- 50-74 (Gray, Moderate Fit): Partial ICP match or mixed buying signals. The prospect may be in a lifecycle stage (approaching contract renewal) or early in the research process. Nurture with targeted content.
- 0-49 (Red, Weak Fit): Low ICP match, no immediate buying signals, or negative call sentiment. These leads may become relevant later. The score explanation tells you why the fit is weak today.
The thresholds aren't arbitrary. They're calibrated against actual conversion data. Leads scoring 75+ don't just feel more qualified. They close at measurably higher rates.
How TruSQL Differs from Predictive Lead Scoring
Predictive scoring platforms (6sense, Lattice, EverString) use machine learning to identify patterns in historical data. They answer: "Which accounts look like your past customers?" The models are trained on closed deals, web behavior, and third-party data.
TruSQL answers a different question: "What did this specific person tell us about their needs, timeline, and buying process?" It's not predictive. It's verified. The data comes from a conversation that already happened, not from a model predicting what might happen.
Both approaches have value. Predictive scoring covers more accounts with less effort. TruSQL provides deeper context on fewer leads. The right choice depends on whether your team needs volume (many accounts with probability scores) or depth (fewer leads with conversation-level intelligence).
The 50+ Data Points Behind Each Score
Every TruSQL-scored lead arrives with the full conversation record. Pain points extracted and prioritized (High/Medium/Low). Feature needs ranked by importance. Current solution details: vendor name, satisfaction rating, contract start and end dates. Decision-maker identity: name, title, email, and their role in the buying process. Buying committee members. Budget availability. Demo interest level.
All captured in a single 6-12 minute phone conversation by a trained CDR representative. Not scraped from the web. Not inferred from content downloads. Stated by the prospect in their own words, then structured and scored by the platform.
Rover Insights delivers these scored leads to your CRM within 48 hours. Your rep opens the lead and sees everything: the score, the breakdown, the rationale, the next steps, and the full conversation context. That's what conversation-based scoring makes possible.