Build a scoring model your sales team trusts, on HubSpot's lead scoring tool.
Most lead scoring does not fail because the maths is wrong. It fails because it scores the wrong signals, nobody revisits it, and sales quietly stops trusting the number. Within a quarter the "hot" list is full of newsletter subscribers while your best-fit buyers sit in the nurture pool.
If you run HubSpot, there is a second problem. The old "HubSpot Score" property stopped updating on 31 August 2025. Any workflow, list or report still pointing at it is working off frozen data.
Here is how to rebuild scoring on HubSpot's Lead Scoring tool so the output drives sales action, not another dashboard nobody opens.
The failure patterns worth naming before you build:
One number for two different questions. Fit (how well someone matches your ICP) and engagement (how interested they are right now) answer different things. Blend them into a single score and a great-fit prospect who has gone quiet looks identical to an active lead you would never sell to. A contact at a competitor browsing your site heavily scores high on activity while being a guaranteed no.
Treating a job title as intent. Seniority and company size matter for fit. They tell you nothing about whether someone is in-market this week. Behaviour does.
A threshold so low everything clears it. If a newsletter signup and a demo request land in the same band, the score is decoration.
Set once, never revisited. Buying behaviour shifts, your ICP sharpens, the product moves on. A model built a year ago is scoring a company you have outgrown.
No negative signals, no decay. Points only ever go up, so a contact who grabbed one guide eight months ago still reads as warm.
The Lead Scoring tool (Marketing Hub Professional and Enterprise) is more flexible than the legacy property in a few ways worth understanding first:
One ceiling to plan around: the total tops out at 100 points on Marketing Hub Professional and 500 on Enterprise. Build your bands to fit your tier.
Pull your recent closed-won deals and look for what they share. Not the logos you want. The ones you win and keep.
This becomes your fit criteria. If you struggle to describe your best customer in a sentence, the model will guess for you.
Go to Marketing > Lead Scoring and click Create Score. Set up a Contact Fit Score and a Contact Engagement Score as two scores, not one merged number. (Create score with AI gives you a starting point if you want one.)
Keeping them apart is the whole point. Sales sees "great fit, low engagement" (worth a proactive nudge) and "high engagement, poor fit" (worth a polite no) at a glance.
Score fit on contact and company properties: role, seniority, industry, headcount, revenue.
Score real buying signals over vanity actions:
Then apply the two features keeping engagement current:
Set Score Limits so one repeated action does not dominate the result.
Points should come off as well as on. Build these as criteria or lists:
Sort the scores into bands and agree with sales what each one triggers. Grades (A/B/C) for fit and numbers (1/2/3) for engagement pair well. An A1 is a best-fit, actively engaged lead. A C3 is an engaged poor-fit you usually decline.
Write down what each band means in practice:
If sales does not own the bands, they will not work them.
A score sitting in a property changes nothing. Wire it into the day-to-day:
Review the bands against real outcomes each quarter. If your A1s are not converting better than your B2s, the criteria are wrong, not the leads.
Do not build all of this in week one. A workable order:
Scoring is a model you tune as you learn what your best customers do, not a one-off build.
Lead scoring earns its place when it tells a small sales team where to spend its hours. Fit tells you who is worth winning. Engagement tells you who is ready now. Keep them separate and current, and make sure a high score triggers an action rather than a quarterly argument about lead quality.
If your scoring is still running on the retired property, or you have rebuilt it and sales still does not trust the output, the model and the process underneath it have usually drifted apart. Book a call with ROC and we will show you where, and what to fix first.