Lead scoring for a small sales team: a model you can build in an afternoon and trust

Lead scoring is a way of ranking new leads by how likely they are to become customers, so the team calls the most promising ones first. Each lead collects points for things that predict a sale, such as matching your ideal customer or asking for pricing, and loses points for things that predict the opposite. The total is a single number you can sort a list by.

For a small team the goal is modest and practical: decide in which order to answer today's enquiries, and which ones to hand to an automated sequence instead of a person. This guide shows how to build a score with two halves, how many signals you need, how to set thresholds, and how to check the model against deals you have already won and lost.

Two halves: fit and engagement

A single blended score hides the most useful distinction. Split it into two parts and read them separately.

• Fit answers "is this the kind of company we win?" It comes from facts about the lead: industry, company size, country, the role of the person who wrote, the product they asked about. Fit changes rarely.
• Engagement answers "are they ready to talk now?" It comes from behaviour: requesting a quote, booking a call, replying to an email, opening a pricing page. Engagement changes daily and should fade.

The two halves lead to different actions. High fit with high engagement is a call today. High fit with low engagement is a lead to nurture: the right customer at the wrong moment. Low fit with high engagement is a polite, quick conversation, often a referral elsewhere. Low fit with low engagement can be closed without guilt. A team that reads only one blended number cannot tell the second case from the third.

Where each half gets its data

Fit data usually arrives with the lead: the web form asks for company size and role, the email domain hints at the company, the source says which campaign or partner sent it. When the form does not ask, the first salesperson to touch the lead fills in two or three fields, which is a good reason to keep the fit list short. Engagement data arrives over time from events the CRM already records: a quote request, a booked meeting, a reply in the shared inbox, a click in a campaign email. If an event happens outside the system, for example a call from a personal phone, it does not exist for the score until someone logs it.

A starter points table

Begin with six to ten signals you can actually capture. Every signal on the list must exist as a field on the lead or as an event you record; a signal you cannot see is a guess. The table below is an example for a B2B service company, with round numbers on purpose.

Two rules keep the table honest. First, use few distinct values: 10, 15, 20, 30. Precision such as 17 points suggests a confidence nobody has. Second, give disqualifiers large negative values, so one hard "no" outweighs several soft signals.

Thresholds that trigger an action

A score is useful only when crossing a line changes what happens next. Define three bands and write down the action for each:

1. Hot (for example, 60 and above): assigned to a salesperson at once and answered the same working hour. If you need the reason for that speed, see why response time decides so many leads.
2. Warm (30 to 59): answered the same day, with a short qualifying question rather than a full pitch.
3. Cold (below 30): no manual follow-up; the lead joins a nurture sequence and is re-scored if it engages.

Where the lines sit matters less than the fact that everyone uses the same ones. Set them from your own data (the next section shows how), and resist the urge to add a fourth band until the first three are used consistently.

Let engagement fade

Behaviour has a shelf life. A demo request from last week means far more than one from last spring. The simplest form of decay is to count engagement events only within a window, such as the last 30 days, or to halve engagement points after a month. Fit points do not decay; a company of the right size stays the right size.

Check the model against deals you already closed

A scoring model is a hypothesis about what predicts a sale, and you already hold the evidence. Before the team relies on the number, run this test:

1. Take the leads from the last two quarters that reached a decision: converted to a won deal, or lost.
2. Score each one with the new table, using only what was known when the lead arrived.
3. Sort by score and split the list into bands. Count how many leads in each band became won deals.

A working model shows a clear staircase: the hot band converts much better than warm, and warm better than cold. If the bands convert at similar rates, one or two signals are carrying the whole score or pointing the wrong way. Remove signals one at a time and watch which removal flattens the staircase; that is the signal doing the work.

Then look at the exceptions. Won deals that scored cold reveal a signal you are missing. Lost deals that scored hot reveal a signal that overstates intent, such as downloads that come mainly from researchers.

Mistakes that make scores ignored

• Too many signals. Thirty rules produce a number nobody can explain. When a salesperson asks why a lead scored 74 and the answer takes a paragraph, the score stops being used.
• Rewarding data entry. If filled-in fields earn points, leads entered carefully outrank leads entered in a hurry. Score the values, not their presence.
• No feedback loop. Markets shift. Re-run the check against closed deals every quarter and adjust one or two weights at a time.
• Scoring instead of answering. A score sets the order of the queue; it is not a reason to leave cold leads unanswered for a week. Even a cold lead deserves an automatic acknowledgement.

How Nextora supports lead scoring

In Nextora a lead record carries its score on the left of the card, beside status, contact details, assignees and custom fields, with the conversation across every channel on the right. Fit signals live as fields: built-in ones such as source, plus custom fields your team adds directly in the leads table (a select for industry, a number for company size), which then work in filters and sorting like any other column.

Automations do the bookkeeping. A workflow can start when a lead is created, with a Conditions block that lets it run only for leads that match, for example a given source or status, and its steps can change a field, create a task or notify a person. That is enough to assign hot leads to someone at once and to send cold ones into a campaign. The lead list sorts and filters by any column, so "unanswered leads, highest score first" is a saved view rather than a report.

For checking signals against outcomes, Activity analytics has an Impact on conversion block: for each activity type it splits deals into those where the activity happened and those where it did not, and compares their win rates. It is a direct way to see whether a meeting or a reply really moves the odds before you give it points. The CRM page shows leads, deals and analytics together.

An afternoon plan

1. List the six to ten signals you can see on today's leads, split into fit and engagement.
2. Give each round points and give disqualifiers a large negative value.
3. Score last two quarters' decided leads and check for the staircase.
4. Set three bands and write one action for each.
5. Add a 30-day window to engagement points and put a quarterly review in the calendar.

Scoring works best on clean records. The five records a CRM actually needs explains where a lead ends and a contact begins, and forms that reach the CRM covers how to make sure the fields a score depends on are captured in the first place. Once leads become deals, stages with exit criteria take over the job of saying how close each one is.