Most teams do not have a lead problem, they have an order problem. Enquiries arrive, they all look much the same in a list, and whoever happens to be at the top gets called first. A score is just a way of putting that list in a sensible order before anyone picks up the phone.
Score on evidence, not on enthusiasm
Two kinds of signal are worth scoring. The first is fit: is this the sort of work you do, for the sort of business you serve, somewhere you can deliver. The second is intent: did they ask about cost, mention a deadline, or try to book something.
Fit tells you whether the lead is worth your time at all. Intent tells you how soon. A lead that scores well on both is the one to call today.
Start with five signals, not fifty
A score made of five things your team can explain will be used. A score made of thirty weighted factors will be quietly ignored, because nobody trusts a number they cannot reason about.
These five cover most service businesses, and every one of them can be read straight off a form or a conversation.
Checklist
- The service they asked about is one you actually offer
- They are in a country or region you can serve
- They gave a working business email or phone number
- They mentioned a timeline, a deadline, or an event driving the work
- They asked about cost, scope, or availability
Make the score change something
A score that sits in a column and changes nothing is decoration. Decide what each range actually does before you build it.
Three bands are usually plenty. The top band gets a call the same day. The middle band goes into the normal follow-up sequence. The bottom band gets useful information and no phone call. If you cannot describe the difference between two bands in a sentence, you have one band too many.
Subtract as well as add
Job applications, competitor research, and enquiries from places you do not serve all arrive through the same form as real work. Scoring these down is more useful than deleting them, because you keep the count and can see whether a particular channel is sending you noise.
Be careful with one common rule. A personal email address is a weak negative signal on its own, since plenty of small businesses use one. Pair it with something else before it costs the lead any points.
Check the score against what actually closed
Once a month, look at the work you won and the score those leads had when they arrived. If your high scores are not the ones closing, the signals are wrong.
When that happens, change a signal rather than adding another one. Scores drift towards complexity on their own, and the useful ones are kept deliberately simple.
The takeaway
Choose five signals you can observe, sort leads into a small number of bands that each trigger something different, subtract for work you cannot take, and test the model against closed business once a month. A simple score your team trusts beats a detailed one they work around.
Would you like this running in your business?
Tell us how you handle this today and we will show you what the automated version looks like for your tools and your team.