An explainable B2B lead score uses documented rules to estimate project fit and buying intent. Store the reasons behind the score, flag missing information separately, and use the result to prioritize review. A high score is a reason to look sooner. Sales still qualifies the enquiry.
Imagine two enquiries arriving on the same afternoon. One is a referral asking for a CRM integration but says little about timeline. The other requests a demo tomorrow for a product your team does not offer. If your CRM ranks both on urgency alone, the second enquiry wins. Keeping fit and intent separate makes the decision easier to explain.
What should a B2B lead score measure?
Fit asks whether the team can deliver what the prospect needs. Intent asks how actively the prospect is evaluating a solution. Missing information asks what you still need to learn. In an early version, use fields that can be traced back to something the prospect explicitly said or the sales team verified.
| Signal | Example rule | Evidence |
|---|---|---|
| Requested service matches an offering | +30 fit | Selected service or verified enquiry text |
| Required integration is supported | +15 fit | Named platform checked against your capabilities |
| Prospect asks for a proposal or demo | +25 intent | Explicit request in the form |
| Prospect states a decision window within 60 days | +15 intent | Stated deadline or procurement window |
| Required service is outside scope | Manual review | Sales confirms a mismatch |
| Budget or timing is missing | Flag for discovery | Field is empty or unclear |
These weights are illustrative. A small team can start with fewer signals. Avoid awarding points twice when two fields merely restate the same evidence. A form selection and a message that both ask for a demo represent one demo request.
Worked example with two enquiries
Enquiry A asks for a supported CRM integration and a proposal. The decision date is unknown. It scores 45 for fit and 25 for intent, with a missing timeline flag. The reviewer can prioritize it and ask one concrete follow-up question about the decision window.
Enquiry B asks for a proposal within 30 days, but names a service outside your delivery scope. It scores 40 for intent and triggers scope review. A sales representative can verify the mismatch before declining or routing it to a partner.
One way to represent Enquiry A is:
{
"enquiry_id": "ENQ-2048",
"rule_version": "v1",
"fit_score": 45,
"intent_score": 25,
"reason_codes": ["service_match", "integration_supported", "proposal_requested"],
"missing_fields": ["decision_window"]
}
Record the rule version and evaluation time when you save this result. If the score changes after discovery, retain the previous evaluation so the team can see which new information affected priority.
How do you check whether the score helps?
Run the first version alongside your existing process. Ask reviewers to record whether each enquiry was qualified, disqualified, or still under review. Compare qualification rates across score bands and sample low-scoring enquiries that later qualified.
Watch for patterns. If prospects with sparse forms are often qualified after a call, your scoring rules may be rewarding form completion more than actual fit. If two reviewers interpret a signal differently, tighten its definition before adjusting its weight.
Should high-scoring leads bypass qualification?
Use the score to decide who reviews an enquiry and when. Keep the qualification decision and its evidence in the CRM. This gives you a way to compare scoring rules against outcomes and correct them when your offering or buyer mix changes.
Top comments (0)