Lead Quality Autopsy —
Section 01 of 04

SDRs inherit lead records with activity data, not intent data. A page view is not intent. A whitepaper download is not intent. A form fill on a generic piece of content is the digital equivalent of someone picking up a brochure in a waiting room. The question forces a distinction between presence and signal.

If the SDR cannot name a specific, timestamped action tied to a real problem signal, the lead has not indicated anything. They have visited a page. Visiting a page is not intent. It is presence. Presence does not pay quota.

Lead scoring systems award points for each ICP criterion independently. A marketing director at a 20-person startup in the wrong industry might score well on role. A 500-person company in the right industry with the wrong contact scores well on firmographics. Neither is a qualified lead. The question requires all three to be true simultaneously.

A lead that matches on two of three ICP criteria is not a qualified lead. It is a partial match. Partial matches produce partial conversations that produce no pipeline. The SDR who calls a partial match is optimising for activity, not outcome.

Intent data says the company is researching a topic. That is not the same as experiencing a problem. A company can research your category for competitive intelligence, academic curiosity, or because an analyst report mentioned it. The question demands evidence of the problem itself, not evidence of research interest.

If the SDR cannot point to evidence — a job posting that signals the pain, a press release that describes the trigger, a technology signal that shows the gap, a recent event that creates urgency — the problem is assumed, not confirmed. Assumed problems produce conversations. Confirmed problems produce pipeline.

Marketing automation passes leads based on the person who triggered the lead score — not based on their proximity to a buying decision. An end user who downloaded a whitepaper because their manager asked them to is not a buying signal. It is a delegation signal. The question forces role clarity before the first outreach attempt.

An end user downloading a whitepaper is not a buying signal. It is a learning signal. The SDR who calls the end user expecting a discovery call about budget and timeline is about to spend 20 minutes explaining what the product does to someone who cannot buy it. That call produces no pipeline. It produces activity metrics.

Lead scoring systems are engineered to produce leads. A single high-value action — a pricing page visit, a demo request page hover — can push a contact over the MQL threshold. A single action is statistically indistinguishable from accidental discovery. Repeated engagement across multiple touchpoints is a pattern. A pattern is evidence.

Two or more engagements, across different content or touchpoints, suggest deliberate interest. One event suggests nothing except that the person is on the internet. The SDR who treats single-signal leads the same as multi-touch leads is not prioritising. They are hoping.

Technology stack data tells you whether the company already has a solution in your category, whether they're likely mid-contract, and whether their infrastructure is compatible with your product. Evaluation signals — job postings for roles that suggest a review is underway, recent removal of a competitor's tool — tell you whether the timing is right. Both are available before the first call.

A company that recently installed a competitor's product is not in active evaluation. A company whose existing contract in your category expires in 90 days may be. Technology stack and renewal signals are the difference between good timing and wishful thinking. The SDR who does not check is leaving timing to chance.

CRMs accumulate history. A company that appeared in the funnel 18 months ago, went through a full discovery process, and was disqualified because the budget ceiling was too low has not become a better lead because a new employee downloaded a report. The disqualification reason is still the disqualification reason. The question forces CRM archaeology before the first dial.

A company that was disqualified for a structural reason has not changed because of a new MQL. A company that was previously disqualified because the champion left and now has a new champion in the right role is a different situation. The history is the context. The SDR who calls without the context is starting from zero on a lead that has already told you something.

Even a qualified contact at a qualified company is not a pipeline-producing lead if they lack the internal reach to initiate a buying conversation. A mid-level manager who is interested in the product but reports to the economic buyer — and has no mandate to propose new vendor relationships — cannot start the process. The question separates interested contacts from actionable ones.

An SDR's time is finite. A conversation with someone who cannot influence the buying decision, cannot access the economic buyer, and cannot sponsor an internal evaluation is not a qualified conversation. It is a relationship that costs time and produces no pipeline. The SDR who cannot answer this question before the call has not done the pre-call work.

Qualification frameworks describe the ideal. Disqualification frameworks describe the exit criteria. The question forces the SDR to articulate — before the call — what characteristics would make this lead a guaranteed waste of time, and then to hold the actual lead against that description. Most SDRs have never been asked to do this. Most SDR teams have never written it down.

Every SDR team knows what a bad-fit lead looks like in retrospect. The lost deals, the no-shows, the prospects who went dark after two calls — they share characteristics. If you cannot describe the disqualification profile, you cannot apply it. Write it down. Run this lead against it. If it matches on more than two characteristics, disqualify it before the call.

Non-response is data. An SDR team that has no defined response to non-response will continue calling indefinitely, consuming capacity on leads that have already answered the qualification question — silently. The question forces the protocol into the pre-call planning, not the post-failure rationalisation. Define the exit before you start.

A lead that does not respond to three thoughtful, personalised outreach attempts is telling you something. The message did not land, the timing is wrong, the contact is not the right person, or the lead was never going to convert. The protocol should be defined in advance: recycle, disqualify, or escalate to a different contact. An SDR who continues without a defined protocol is not working a lead. They are hoping.