SALES LEADS EXPLAINED
A name and an email address become useful only when the company, buyer relevance and supporting evidence give a sales team a sensible next step.
UK geography; active website supplied; matched target evidence: outbound agency, appointment setting, outbound; Companies House identity; 3 opportunity signal(s); buyer: Founder
A sales lead is a person or account that may be relevant to a commercial conversation. A qualified lead goes further: it meets an agreed company profile, points to a plausible buyer and carries enough current evidence for someone to review it.
There is no universal lead score. For a niche service, a small company with the right operating problem may be better than a famous enterprise with no route to the buyer. Define quality against your offer, territory, timing and capacity.
A reviewable record names the discovery source, the company evidence, the contact evidence and the dates checked. Provider data can accelerate discovery; it should not replace the reason a record belongs in the campaign.
Research can surface a plausible lead. Human review decides whether it is ready for the current campaign, whether the message fits, and whether it should be added to a CRM or held for more evidence.
Teams use these labels differently, so agree their meaning before buying a list or reporting results. In this guide, a lead is an account or person that could be relevant. A prospect has been researched against a defined customer profile. An opportunity is a potential sale supported by a conversation and an agreed next step.
A verified email establishes a contact route. It does not establish budget, an active project, consent to a meeting or interest in your offer. Keep those fields unknown until there is evidence for them.
Use hard exclusions before ranking the remaining records. A high total score should never compensate for a suppressed contact, the wrong country or an unsupported buyer identity.
| Check | Accept when | Hold or reject when |
|---|---|---|
| Company fit | The website supports the required service, market and location. | Only a broad directory category supports the match. |
| Buyer relevance | A current source connects the person to a role relevant to the decision. | The person has left, or their function is unrelated. |
| Contactability | The agreed contact route has a dated verification result. | The address is invalid, uncertain or outside the agreed standard. |
| Evidence | The source, date and reason for inclusion can be inspected. | A generated statement has no supporting source. |
| Freshness | Time-sensitive company and role details have been checked for this use. | The record relies on an old role or an undated claim. |
| Eligibility | The record passes exclusions, duplicate and suppression checks. | It is an existing customer, duplicate, competitor or opt-out. |
Illustrative example; these are fictional companies. The brief is UK commercial roofing contractors serving industrial sites, with an operations buyer. North Quay Roofing Ltd has a service page describing industrial roof maintenance and a current team page naming its Operations Director. A dated contact check and clear suppression check make it suitable for review. Its reason for inclusion is the industrial maintenance service and relevant buyer role; buying intent remains unknown.
Oak Lane Roofing appears under the same directory category, but its website describes domestic repairs only. Reject it for service mismatch. Adding a director’s email would not repair that mismatch. If the service page were ambiguous instead, hold the record and request evidence rather than assuming either outcome.
Company identity, employee count, job title and email verification age at different rates. Keep a checked date for each important field rather than one reassuring date for the whole row. Before activation, recheck the buyer’s role, the chosen contact route and suppression state. Agree refresh intervals with the operator based on the campaign’s timing and risk; no universal expiry period makes every list safe.
Keep valid, invalid, accept-all and unknown results distinct. Verification can reduce uncertainty, but cannot guarantee delivery or a reply. Hunter’s Email Verifier documentation describes syntax, domain and server checks and explicitly recognises that a valid result can still bounce.
A database can suit a broad, well-filtered market when someone on your team owns checking and maintenance. Bespoke research suits briefs where a directory label is insufficient—for example, a particular service, installation capability or buying role. Compare the cost per accepted, usable record after review, not the advertised price per exported row.
In a purely illustrative calculation, a £100 export yielding 20 accepted records costs £5 per accepted record before staff time. A £200 researched batch yielding 80 costs £2.50 before staff time. Those are arithmetic examples, not Keystone results or a forecast.
A useful CRM handover includes stable company/contact identifiers, the brief version, sources and dates, the inclusion reason, verification and suppression states, reviewer, record revision and assigned owner. Keep campaign status separate from lead quality: a well-researched prospect may still be uncontacted.
Merge duplicates through stable identifiers, retain the evidence and record the next action. If a buyer changes role after approval, review the changed record before reuse. See the record example for the delivery fields.
No. Researched outbound contacts may never have heard of your business. An enquiry records an action the person actually took.
Start from the market’s feasible size, the acceptance standard and your capacity to review and follow up. Test a bounded sample before committing to volume.
Record the failed criterion and supporting evidence. Agree correction, replacement, partial-yield and refund terms before commissioning work. See Lead Packs and managed research for the two buying routes.
APPLY KEYSTONE TO YOUR MARKET