What Is Lead Scoring? Prioritizing With CRM Data

Lead scoring is a simple prioritisation method that tells you which record to work today instead of calling all of them at once. The goal is not a flawless prediction model; it is a shorter morning list for your sales team.

What is lead scoring?

You give every record a number that reflects its likelihood of closing. That number comes from fields you already have in the CRM plus recent activity. A high score means work it today; a low score means it waits or goes to nurture. Nothing more complicated than that is required to start.

Fit and interest: two signals to keep separate

The most common scoring mistake is blending these two signals into one number. Keep them apart:

• Fit: company size, industry, country, tech stack, budget range. This information rarely changes.
• Interest: pricing page visit, demo request, email reply, content download, meeting accepted. These change fast and go stale fast.

High fit with low interest goes back to marketing. Low fit with high interest gets politely disqualified — enthusiastic but unfit records burn the most time. High on both: call today.

Building a model in five steps

• List your last 50 won deals. Take 50 lost ones too. The model comes out of the difference between the two groups.
• Find the 5 to 7 distinguishing attributes. Mark the fields that show up markedly more often in wins. Fewer than five and the model is weak; more than fifteen and it is unmanageable.
• Assign weights. No complex formula needed: give each signal 5, 10 or 20 points and make the total 100.
• Set thresholds. For example 70 and above is hot, 40 to 69 is follow-up, below 40 is nurture. The hot group must not be bigger than the team can call in a week.
• Add a decay rule. A record with no activity for 30 days should have its interest points reset to zero. Without this rule the list fills up with old records within months.

The CRM fields that feed the model

Scoring is only as good as the data quality in your CRM. At minimum these fields need to be populated:

• Company size or employee count band
• Industry — a closed list, not free text
• Source: which channel the record came from
• Last activity date
• The contact's role or decision authority
• Stage, and the date they entered it

If those fields are filled on less than 80 percent of records, fix data capture before you start scoring. A score calculated on missing data penalises blanks with low points, which hides your good leads.

Backtest the model

Before going live, do this: take records from six months ago, score them using only what was known that day, then look at what actually happened.

The expected result is that the high-score group's win rate is at least twice the low-score group's. If the gap is not that clear, your weights are not doing any work; the model may look fine on paper while never actually changing the ordering.

The most common mistake: using the score as a gate

Never calling low-score records lets the model validate itself. You never touch that group, so no deals come out of it, which looks like proof the model was right.

The fix is simple: call a small sample from the low-score pool every month. You see the model's blind spots and you keep measuring whether the score really discriminates. A score ranks; it does not disqualify.

Run it manually for two weeks

Before you automate anything, run the model by hand in a spreadsheet. Score the list each morning and hand it to the reps. After two weeks, ask three questions: was the ordering sensible, was there a record on the list that should not have been there, and was one missing that should have been?

Those two weeks teach you more than a months-long automation project. Once the model settles, moving it into the CRM is the easy part.

Where to start

The smallest step you can take today: put your last 50 won and 50 lost deals side by side and find three distinguishing fields. A rough three-signal model beats no model by a wide margin, and you will add the rest as you go.

Closync gathers these signals from your CRM data on one screen so scoring and prioritisation run automatically.