A lead score is not a decision

A spreadsheet with 2,000 leads can look productive right up until someone has to decide what to do with it.

You may have a score beside every row. You may have firmographic data, job titles, a few intent inputs, and a lot of columns. But when the sales rep asks, "Who should I contact first?" the answer is often still, "Start at the top and use your judgment."

That is not a decision system. It is a ranked spreadsheet.

A score is useful. It helps you sort. But sorting is not the same thing as deciding whether a lead deserves more time, more research, or more spend.

Before you enrich a list, write sequences, or load it into a sending tool, you need a simple answer for every row:

Should we work this lead now?
Should we review it because something is missing or unclear?
Should we suppress it and stop spending on it?

If you cannot answer those questions, the score has not done the hard part yet.

Why a number leaves reps deciding by feel

A 0-10 score looks clear until you ask where the cutoff is.

Is a 7 worth contacting? What about a 6.5 with recent website activity? What if the company fits perfectly but the contact is not the right person? What if the lead has a 9, but the data behind it is old or thin?

Those are normal questions. The problem is when every rep answers them differently.

One rep works every lead above 6. Another only trusts an 8 or higher. A third spends twenty minutes researching a 5 because the company name is familiar. Meanwhile, the rest of the list sits there, and nobody knows which rows are actually worth paying to enrich or sequence.

That is how a list becomes expensive before it becomes useful.

A score should support a decision, not push the decision back onto the person who already has too much to do.

Separate fit from confidence

One thing that causes trouble in lead scoring is putting too much into one number.

Fit and evidence confidence are related, but they are not the same thing.

Fit asks: based on what we know, does this company and person match the ICP?

Evidence confidence asks: how much do we actually know, and how current or reliable is it?

For example, a company could score 8/10 on fit because it is in the right industry, size range, geography, and uses the type of technology your offer helps with. But if the decision maker role is missing and the company description is vague, the evidence confidence may be low.

That lead should not be treated the same way as an 8/10 with a confirmed role, current company information, and clear reasons for the match.

The first may need review. The second may be ready to work.

This is especially important with purchased, scraped, or older lists. A score can look precise even when the source data is not.

Turn the score into three clear outcomes

The practical fix is simple. Keep the 0-10 score if it helps your team compare leads, but give every row an outcome as well.

Work

Use work when the lead meets your core ICP criteria and the supporting data is good enough to act on.

This does not mean the lead is guaranteed to buy. Outbound does not work that way.

It means the row deserves the next spend: research, personalization, enrichment, or a place in the sequence.

A company that matches your target market, employee range, geography, decision-maker role, and relevant business context may score 8/10 or 9/10. If the evidence is current and clear, that is a work row.

Review

Use review when the fit may be there, but the evidence is incomplete, conflicting, or stale.

Maybe the company is a strong match but the contact title is unclear. Maybe the website has changed. Maybe the list says 50 employees while another source suggests 500. Maybe the company is in the right vertical, but there is no way to tell if it serves the market you need.

Review is not a polite way to say "low score."

It means someone can resolve the uncertainty. If no one can resolve it quickly, do not let review become a graveyard for rows nobody owns.

Suppress

Use suppress when the lead does not fit, has a clear exclusion, or lacks enough usable information to justify more spend.

This is the part teams often avoid because it feels like throwing away leads. It is not.

If a row is outside your geography, too small for the offer, in the wrong industry, or missing the basic data needed to contact the right person, suppressing it is a useful decision.

You are protecting your team from spending money and attention on a row that was unlikely to produce anything.

A simple way to run the list check

Before your team launches a new list, use this sequence:

Define the ICP criteria that actually matter. Keep it to the conditions that affect whether your offer fits.
Score each row on a 0-10 scale against those criteria.
Record the evidence for the score, including missing or conflicting information.
Assign work, review, or suppress.
Sample the results with the people who will use the list.

That last step matters.

Take 25 rows across all three outcomes and ask the rep or founder: "Do you agree with this decision? If not, what criterion is missing?"

If people consistently disagree with the decisions, fix the criteria before you run another 2,000 rows through the same process.

Do this before downstream spend

Tools such as Clay can help build a larger qualification workflow. CRM scoring tools can also do useful work once the system is configured.

But a team testing a new list source, territory, or ICP often needs a smaller first step.

Run a contained audit. A 250-row sample is enough to show whether the list is worth taking further.

Look at:

The work, review, and suppress rate
How often the evidence is missing
Whether reps agree with the decisions
What enrichment and sequencing spend you avoid by suppressing bad rows early

You do not need another score just because the current score feels too vague. You need a decision that tells the team what happens next.

FAQ

Should every lead have a 0-10 score?

A score is useful when it reflects clear ICP criteria and helps compare rows. It should not be the only output. Pair it with an action decision and the evidence behind it.

Is a low-fit lead with high intent worth working?

Sometimes, but do not assume activity fixes a poor ICP match. Check whether the activity is relevant and whether your offer can solve a real problem for that company. If not, suppress it.

What is the difference between review and suppress?

Review means the lead may be worth pursuing, but a specific question needs to be resolved. Suppress means there is a clear reason not to spend more time or money on the row.

How large should a first list audit be?

Start with 250 rows when you are testing a new source, territory, or ICP. It is enough to spot a pattern without committing to a full list build or outreach spend.