Lead scoring best practices for B2B (2026)

Why most lead scoring models are wrong

Every scoring model we audit that was built from scratch is wrong in the same ways:

• Weights are guessed, not calibrated. Someone decided a demo request should be worth 50 points and an eBook download should be worth 5. They're not wrong directionally, but the 5x:50x ratio probably isn't right — and you can't know without data.
• No decay on behavioral signals. A whitepaper download 18 months ago is worth the same as one yesterday. It isn't.
• No negative scoring. Competitor domains, unsubscribes, and explicit non-buying signals don't reduce score, they just fail to add to it.
• MQL threshold set arbitrarily. “100 points equals MQL” — but at 100 points, what's the actual SQL conversion rate? If you don't know, the threshold is wrong.
• No periodic recalibration. The model was built once and hasn't been touched in 3 years. Buying behavior changed; the model didn't.

The 5-step framework

Step 1: Get historical data

Pull 12–24 months of lead-to-SQL conversion data with all behavioral, demographic, and firmographic dimensions you'll consider scoring on. This data lives across your MAP, CRM, and (often) a data warehouse — pull it once, properly.

Minimum data needed:

• Lead created date
• Lead → SQL conversion date (if applicable)
• Behavioral history (page visits, downloads, email engagement, form fills)
• Demographic data at conversion time (title, function, seniority)
• Firmographic data (company size, industry, tech stack)
• Source / channel

Step 2: Identify predictive signals

Run conversion-rate analysis across each signal candidate. The question to answer for each: “What's the SQL conversion rate of leads with this signal vs. without it?”

Keep signals where the high-value group's conversion rate is at least 2x the average. Drop signals where the lift is below 1.5x — they're not worth the modeling complexity.

Step 3: Set weights based on actual lift

Weight each signal proportionally to its conversion lift, not based on intuition. If “Director+ title” has 4x the conversion of average, and “visited pricing page” has 8x the conversion, the pricing-page signal should be weighted ~2x the title signal.

Sample weighting structure for a typical B2B SaaS:

These are illustrative — your specific weights depend on your historical data.

Step 4: Calibrate the MQL threshold

Run scored leads through the model retroactively and plot score-vs-SQL-conversion-rate. Set the MQL threshold at the score where:

• SQL conversion rate plateaus or peaks (the top 10–25% of leads)
• The volume above that threshold is what your sales team can handle
• SQL conversion rate at the threshold is acceptable to Sales

The score number itself is meaningless. What matters: at this score, X% of leads convert to SQL. That's what Sales is buying when they accept your MQLs.

Step 5: Add decay and review quarterly

Behavioral signals decay over 30–90 days. Demographic and firmographic scores generally don't decay — but should be re-checked annually for changes (job changes, company size changes, tech stack changes).

Quarterly review: pull the last 90 days of scored leads, check whether MQL→SQL conversion rate at threshold is still acceptable. Annual recalibration: full re-run of the model against rolling 12-month data.

Common scoring mistakes (and how to avoid them)

Mistake 1: Scoring inflation

60% of contacts above MQL threshold means scoring is broken — usually because the threshold is too low or behavioral decay is missing. Sales starts ignoring MQLs because too many are unqualified, and the whole program loses credibility. Fix: recalibrate threshold, add decay.

Mistake 2: Scoring under-coverage

Only 5% of contacts above MQL threshold means scoring is too conservative. You're losing pipeline to leads that converted without ever being marketed to as MQLs. Fix: lower threshold, broaden positive signal set.

Mistake 3: No model documentation

Scoring rules live in Marketo or HubSpot but no one knows why they exist. When the original builder leaves, the model becomes untouchable — too risky to change without understanding the original logic. Fix: write down the model, the rationale, the calibration data, and the review schedule.

Mistake 4: Treating account scoring as contact scoring

Summing up contact scores at the account level doesn't produce a meaningful account score — companies with more contacts always score higher regardless of actual intent. Use weighted average, max-of-key-roles, or proper account-level scoring tools (6sense, Demandbase) for ABM scoring.

Industry benchmarks

Per Salesforce's State of Marketing report, high-performing B2B teams report:

• MQL → SQL conversion rate: 25–40% (vs. 10–15% for typical mid-market)
• SQL → SAO (Sales Accepted Opportunity): 50–70%
• SAO → Won: 15–25% (varies wildly by deal size and industry)

If your MQL→SQL rate is below 15%, scoring is the most likely culprit — followed by lead routing and SLA adherence. A MOPs audit separates the causes.

Related: MOPs Audit service, Marketo vs HubSpot vs Pardot, What is a MOPs audit?.