Back to all articlesLead qualification

Decide what evidence is strong enough to qualify a lead

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A salesperson records that a lead has budget because the prospect liked the proposed price. Another records that the buyer has authority because they led the meeting. A third refuses to qualify an opportunity until the prospect shares internal documents. These are different versions of the same problem: nobody has defined what evidence is enough for the decision being made.

Lead qualification needs evidence proportionate to the claim and the next commitment. A direct statement may be enough to establish interest or justify discovery. Budget approval, technical feasibility, or readiness for a resource-intensive evaluation may need confirmation from someone responsible for that decision, a relevant operational fact, or both. A salesperson’s impression can guide the next question; it should not silently become a verified fact.

The practical goal is not to prove everything. It is to state what each source supports, preserve what remains unknown, and ask for only the evidence that could change the next decision.

1. Define the decision before setting the evidence standard

Qualified is too broad to serve as an evidence standard. Qualified for a short discovery call and qualified for a tailored implementation plan are different judgments. The second commits more effort and depends on more assumptions.

Start each stage rule with a concrete action: continue discovery, involve a specialist, prepare a proposal, or allocate evaluation support. Then identify which claims must be sufficiently supported for that action.

  • For a low-cost, reversible next step: a relevant prospect’s direct account may be enough, with uncertainty recorded.
  • For a resource-intensive next step: confirm the assumptions that would make the work worthwhile or feasible.
  • For a consequential external commitment: resolve the specific dependencies behind that commitment rather than relying on general enthusiasm.

Do not raise every criterion to the highest standard. Requiring budget documentation before an introductory conversation can create friction without improving that decision. Conversely, a promising conversation is not sufficient evidence for promising a delivery timetable.

2. Separate statements, observations, and interpretations

Evidence becomes misleading when its source disappears. A useful qualification record distinguishes three things:

  • Direct statement: what a person reports, including their role and when they said it.
  • Supporting fact: something relevant that was observed or confirmed, with its scope and source.
  • Inference: the conclusion drawn from those inputs.

In a hypothetical example, an operations manager reports that handoffs are being missed. During a walkthrough, the seller observes a shared tracker with unassigned entries. Together, these support a claim that there is a handoff problem worth investigating. They do not establish the total cost of the problem, prove that every team has it, or demonstrate willingness to buy.

A prospect’s statement is not inherently weak evidence. The person responsible for a workflow may be the most useful source about its daily difficulties. But that same person may have limited knowledge of funding approval. Evidence strength depends on the claim, the source’s access to it, and the decision—not just whether a document exists.

Likewise, an operational fact needs a boundary. A sample can establish what appeared in that sample. A successful demonstration can establish what worked under those conditions. Neither automatically proves organization-wide readiness.

3. Use a filled evidence-standard table

Fictional worked example: A sales team is assessing a prospect seeking a better way to manage inbound enquiries. Every person, statement, quantity, and business detail below is hypothetical. The immediate decision is whether to assign a solutions specialist to a scoped evaluation, not whether to declare the purchase certain.

The evidence-standard table below uses expanded rows so each claim retains its source, limits, and decision threshold. A team can copy these fields into a worksheet or qualification record.

Row A — A relevant operational problem exists

  • Qualification claim: Missed enquiry handoffs are a current problem for the service team.
  • Direct statement: The service manager reports that enquiries sometimes remain unassigned after shift changes.
  • Supporting facts: In a prospect-led walkthrough, a recent tracker contains entries without an assigned owner. The manager identifies those entries as unresolved handoffs.
  • Inference limit: This does not establish frequency across all enquiries, financial impact, or the cause of every unresolved entry.
  • Minimum evidence for this decision: A concrete account from the workflow owner plus a relevant example. Met: a scoped evaluation can investigate this problem.

Row B — The prospect wants to change the workflow

  • Qualification claim: The team is willing to explore a different handoff process.
  • Direct statement: The service manager says they want to test whether explicit ownership would help.
  • Supporting facts: The manager agrees to nominate participants and describe the current process before scoping.
  • Inference limit: Willingness to explore is not organizational approval, adoption readiness, or a purchase commitment.
  • Minimum evidence for this decision: An explicit desire to explore change and an agreed next action. Met for evaluation scoping only.

Row C — There is a plausible route to funding

  • Qualification claim: A successful evaluation could enter a funding decision.
  • Direct statement: The service manager says departmental software purchases are reviewed by the finance lead, who has not yet reviewed this proposal.
  • Supporting facts: The finance lead accepts an invitation to a scoping discussion with funding assumptions on the agenda.
  • Inference limit: Meeting acceptance does not establish allocated budget, acceptable pricing, or approval.
  • Minimum evidence for this decision: A named funding route and access to the relevant reviewer before substantial evaluation work begins. Provisionally met; budget approval remains unknown.

Row D — The decision process is sufficiently understood

  • Qualification claim: The seller knows who must participate in deciding whether to proceed.
  • Direct statement: The service manager identifies themselves as workflow owner, the finance lead as funding reviewer, and an IT administrator as technical reviewer.
  • Supporting facts: The finance lead confirms their review role. The IT administrator’s role has not been confirmed.
  • Inference limit: The list may omit another approver. The service manager’s seniority does not prove final purchasing authority.
  • Minimum evidence for this decision: A working role map is enough to schedule scoping. Confirmation of required participants is needed before treating the evaluation plan as agreed. Partially met.

Row E — The proposed scope is technically plausible

  • Qualification claim: The evaluation can test the required workflow within an agreed scope.
  • Direct statement: The service manager describes a shared enquiry queue and a need to assign ownership.
  • Supporting facts: A workflow walkthrough confirms the assignment steps. Required data access and any dependencies have not been reviewed.
  • Inference limit: Understanding the workflow does not confirm product support, available permissions, or implementation effort.
  • Minimum evidence for this decision: Enough detail to brief a specialist is present. Technical feasibility remains open until the specialist checks the requirements against actual capabilities and constraints.

Row F — The timing is actionable

  • Qualification claim: The prospect can participate in an evaluation during its proposed period.
  • Direct statement: The service manager wants a new process in place before a planned service expansion.
  • Supporting facts: A scoping meeting is booked, but participant availability for the evaluation is unconfirmed.
  • Inference limit: A desired completion date does not establish available staff time or a feasible delivery date.
  • Minimum evidence for this decision: A reason for timing is enough for scoping. Named participants and agreed availability are required before reserving evaluation support. Not yet met for that reservation.

Result: Proceed with a bounded scoping meeting, not an unrestricted specialist commitment. Use the meeting to confirm the review roles, check technical dependencies, and agree participant availability. The evidence supports further investigation; it does not support recording budget, feasibility, and timing as fully confirmed.

4. Ask for the smallest useful confirmation

Once a gap is visible, choose the least burdensome way to close it. More evidence is not automatically better evidence.

For a funding-route question, confirmation from the responsible reviewer may be more useful than a broad request for internal financial documents. For workflow fit, a prospect-led walkthrough may answer the question without exporting operational records. For timing, an agreed schedule with named owners is more relevant than another declaration of urgency.

A useful request explains its decision purpose. In the fictional example, the seller could ask whether the finance lead can confirm the review process before specialist time is reserved. That is narrower and easier to answer than asking the prospect to prove they have budget.

Before requesting anything, ask:

  1. Which unresolved claim would this evidence address?
  2. Could the answer change our next action?
  3. Can a narrower confirmation answer the same question?
  4. Can we record the conclusion without retaining unnecessary underlying material?

If the answer will not affect the decision, defer the request. Qualification should reduce uncertainty that matters, not accumulate documents.

5. Record uncertainty without turning it into a score

A single confidence score can conceal different problems. Budget could be unknown, technical fit partially supported, and interest directly stated. Averaging those into a high qualification score makes the record look more settled than it is.

Use explicit claim states instead:

  • Reported: a named source has stated the claim.
  • Supported: relevant evidence backs the claim within a stated boundary.
  • Unknown: the necessary information has not been obtained.
  • Contradicted: available sources disagree or directly oppose the claim.
  • No longer current: the evidence may not describe the present situation.

These are proposed working labels, not a required software configuration. Pair each state with the decision threshold. A reported need may meet the discovery threshold; a reported approval from someone outside the approval process may not meet a proposal threshold.

Record when the evidence was obtained and what would trigger a recheck. A change in sponsor, scope, price assumptions, or target date can make earlier evidence insufficient. Recheck affected claims rather than restarting qualification from scratch.

6. Resolve conflicts and failed assumptions explicitly

When evidence conflicts, do not select whichever version keeps the opportunity moving. Name the disagreement and pause only the decision that depends on it.

In a hypothetical continuation, the service manager believes funding is available, but the finance lead says no allocation has been made. The correct record is not budget confirmed. It is that the workflow owner expects funding, while the responsible reviewer reports no current allocation. Discovery might continue, but a costly evaluation may need to wait or shrink.

Several recurring failures deserve specific recovery actions:

  • Enthusiasm became authority: replace the authority claim with a role map and confirm who reviews what.
  • A sample became a universal claim: narrow the conclusion to the observed scope and investigate only the variation relevant to the decision.
  • Repeated statements appeared to be corroboration: check whether they all came from the same original source. Repetition does not create independent support.
  • A completed field became assumed truth: review the source behind the field, not just whether it is populated.
  • Evidence is unavailable: distinguish unknown from false. Choose a smaller next step, defer the decision, or explain why the missing evidence prevents further commitment.

A useful recovery record contains the corrected claim, the affected commitment, and the next evidence request. It should not merely replace one confident label with another.

7. Calibrate standards against observable decisions

Evidence standards should make decisions clearer without making qualification needlessly expensive. Review both sides: commitments made on weak assumptions and opportunities delayed by unnecessary proof requests.

For a hypothetical review of ten recent opportunities, examine one stage transition per opportunity. Record whether the decisive claims had identifiable sources, whether their limits were visible, and whether the evidence met the stated threshold. Then check what happened next: was work paused because an assumption failed, did scope need revision, or was a requested document never used?

Those observations can reveal where to change the standard. Repeatedly discovering an unnamed reviewer after proposal work suggests confirming the decision process earlier. Repeatedly collecting detailed records that do not affect discovery suggests lowering that early-stage burden. These are diagnostic signals, not proof that one qualification rule caused a sales result.

Next action: Before your next pipeline review, choose one stage and write its next commitment at the top of a worksheet. Add the six evidence rows above, adapting only the claims that matter. For each opportunity reviewed, count unsupported decisive claims and assign each one a specific action: ask, confirm, narrow the commitment, or accept the uncertainty explicitly. The immediate outcome is measurable: fewer decisions resting on unlabeled assumptions, without requiring every prospect to prove everything.

Lead qualificationSales operationsEvidence standardsCRM

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications