Choose qualification criteria that actually change a decision
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A team can know a lead’s company size, industry, job title and preferred start date—and still disagree about whether to proceed. The problem is not necessarily missing information. It may be that nobody has defined what those answers should change.
To choose lead qualification criteria, start with one offer and one decision. Identify the conditions that make the offer suitable, the evidence that makes action timely, and the uncertainties that need clarification. Keep a proposed criterion only when its possible answers change a named action or resolve uncertainty that matters to that action.
This approach produces a smaller, more defensible assessment—not simply a shorter list of questions. The filled fictional worksheet below shows how to connect each proposed criterion to its rationale, possible answers and decision consequence.
1. Define the decision before choosing the criteria
“Is this a good lead?” leaves too much room for interpretation. Good for which offer, at what stage, and for what next step?
Write a decision statement with a specific action and a realistic alternative. For example: decide whether to offer a scoped discovery session for this service, seek one missing fact first, defer until a named dependency changes, or decline this particular offer.
These outcomes should mean different things:
- Proceed: There is enough evidence of fit and readiness to justify the next commitment.
- Clarify: An unresolved fact could change the assessment, so obtain that fact before committing.
- Defer: The offer could fit, but a known dependency or timing issue prevents progress now.
- Decline this offer: A confirmed requirement conflicts with what the offer can provide.
Define the cost of getting the decision wrong. An exploratory conversation may need only a few checks. Reserving specialist capacity or preparing a detailed proposal warrants stronger evidence. Do not make the initial assessment carry the burden of every later delivery decision.
Keep the scope to one offer. A requirement that rules out a fixed-scope service might be acceptable for a custom engagement. Combining both into one qualification model creates exceptions that look like inconsistent judgement.
2. Separate fit, intent and useful context
Essential fit criteria establish whether the offer can address the stated need within its boundaries. A confirmed mismatch can stop progression for that offer. These criteria should come from actual delivery constraints, not a preferred customer profile copied from another team.
Intent indicators establish whether there is a reason and a practical path to act. A target date, an agreed next step or an identified decision process can change priority. They do not make an unsuitable requirement deliverable.
Useful context helps someone prepare or communicate, but does not determine qualification. A contact’s role may help tailor a discussion even when their title does not change whether the offer fits.
There is also a fourth category: information with no defined use. Familiarity is not a business rationale. If company headcount is being collected because it has always appeared in qualification notes, ask what would happen differently if it were small, large or unknown.
Keep these categories separate rather than collapsing them into a single score. Several positive intent signals should not cancel a confirmed fit failure. Equally, an excellent fit with no current project should not be treated as ready to proceed.
3. Set up a fictional offer with explicit boundaries
Fictional worked example: All offer details, amounts, timings and lead situations in this example are hypothetical. They are not Alactic services, pricing or customer results.
Imagine a provider selling a fixed-scope enquiry-handling review. The service maps one team’s enquiry process, identifies ownership gaps and produces a recommended operating plan. It does not build custom software, run campaigns or execute the recommendations.
For this hypothetical offer, delivery requires an accountable process owner and access to anonymised examples of the current workflow. The hypothetical fee is £4,000. The provider does not commit to completing the work before its available delivery slot.
The qualification decision is whether to offer a scoped discovery session. The provider needs enough evidence to avoid discussing an unsuitable service, but does not need a complete delivery assessment before that session.
Those boundaries explain the worksheet’s choices. Change the offer and some criteria should change too. In particular, the fee, evidence requirements and delivery constraints below are assumptions for this example, not general qualification thresholds.
4. Filled criterion-selection worksheet
Each entry links a proposed criterion to a business reason and an observable decision. “Remove” means remove from this qualification decision; the information might still have a legitimate use elsewhere.
Criterion A: Match between the requested outcome and the service
- Business rationale: A process review cannot satisfy a requirement for someone to build and operate a new system.
- Possible answers: Wants an assessment and operating plan; wants implementation only; wants both; unclear.
- Decision consequence: Continue for an assessment requirement. Decline this offer for implementation-only work. Clarify whether a standalone review has value when both are requested or the need is unclear.
- Keep or remove: Keep as an essential fit criterion. The answers reveal a direct scope conflict.
Criterion B: Access to usable workflow evidence
- Business rationale: The review depends on understanding how enquiries are currently handled.
- Possible answers: Anonymised examples are available; examples can be prepared; no usable evidence can be shared; unknown.
- Decision consequence: Continue when evidence is available. Clarify preparation and ownership when it can be assembled. Defer if that preparation is not yet possible. Decline this offer if its evidence requirement cannot be met.
- Keep or remove: Keep as an essential delivery prerequisite. Do not request unnecessary sensitive material merely to prove access.
Criterion C: An accountable process owner
- Business rationale: Someone must explain the workflow, resolve conflicting accounts and receive the recommendations.
- Possible answers: Owner identified and available; owner identified but unavailable; ownership unresolved.
- Decision consequence: Continue when participation is feasible. Defer around a known availability constraint. Clarify who can take ownership when responsibility is unresolved.
- Keep or remove: Keep as a readiness criterion. Lack of an owner today is not automatically permanent disqualification.
Criterion D: A plausible route to funding
- Business rationale: Both sides need to know whether the hypothetical £4,000 fee can realistically be considered.
- Possible answers: Fee is within an available budget; approval is needed through a known process; funding is unknown; spending is ruled out.
- Decision consequence: Continue when funding is available. Clarify the approval path when approval is needed or funding is unknown. Defer if spending is ruled out until a future planning point.
- Keep or remove: Keep, but assess funding feasibility rather than demanding that the first contact personally controls the budget.
Criterion E: Deadline and its underlying reason
- Business rationale: Timing affects feasibility and priority, but urgency alone says little about fit.
- Possible answers: Flexible target; fixed date compatible with availability; fixed date before possible completion; no target.
- Decision consequence: Continue when timing is compatible. Clarify whether an incompatible deadline is negotiable. Decline this offer if the completion date is both essential and impossible. Do not reject solely because no date exists.
- Keep or remove: Keep as a feasibility check and intent indicator, with those two uses recorded separately.
Criterion F: A specific operational problem worth reviewing
- Business rationale: A review needs a problem against which its recommendations can be judged.
- Possible answers: Describes missed ownership or repeated handoff failures; reports general dissatisfaction; is exploring without a current problem.
- Decision consequence: Continue with a concrete problem. Clarify one recent example when the description is vague. Defer a purely exploratory enquiry unless the discovery session is intended for that purpose.
- Keep or remove: Keep as a relevance and intent criterion. Do not require a financial estimate the lead cannot substantiate.
Criterion G: Company headcount
- Business rationale: Proposed as a shortcut for workflow complexity and ability to pay.
- Possible answers: Small organisation; large organisation; unknown.
- Decision consequence: None reliably follows. The offer concerns one team’s process, and funding is checked directly.
- Keep or remove: Remove from qualification. It duplicates weaker assumptions about facts assessed elsewhere.
Criterion H: Contact’s job title
- Business rationale: Proposed as a shortcut for authority.
- Possible answers: Senior title; operational title; unclear title.
- Decision consequence: Title alone changes nothing. An operational contact may coordinate the purchase; a senior contact may have no involvement in this process.
- Keep or remove: Remove as a qualification gate. Assess ownership and the approval path directly; retain role context only if it helps prepare the conversation.
5. Test whether the answers really change the action
For each retained criterion, run an answer-change test: hold the other facts constant and change only this answer. Would the team take a different action? If not, either the criterion is unnecessary or its consequence has not been defined clearly enough.
Also test combinations. In a hypothetical case, a lead with a clear problem and available funding still wants implementation only. The scope mismatch controls the decision. In another hypothetical case, the need fits and evidence is available, but the process owner returns next month. That suggests deferral with a named dependency, not rejection.
Check for double-counting. A target date, an urgent description and willingness to meet quickly may all reflect the same underlying pressure. Treating them as independent positive signals can make urgency look more persuasive than it is.
A useful worksheet should explain not just why an answer matters, but why it matters more or less than another answer when they conflict.
6. Make uncertainty a state, not a failure
Unknown does not mean no. A contact may not know the funding process, evidence availability or who must participate. Rejecting every unknown favours leads that can articulate their situation clearly, rather than necessarily those the offer can serve.
For each important unknown, specify the smallest useful clarification. For evidence availability, that might be confirmation from the process owner that anonymised examples can be prepared. For funding, it might be identifying the approval step—not demanding a purchase commitment.
Record the criterion, its current status, the supporting evidence and the next action. Distinguish a lead’s statement from the team’s interpretation. “Approval has not been requested” is different from “there is no budget.”
Allow exceptions through an explicit review rather than quiet rule-breaking. If a prerequisite can be met through an alternative, record why that alternative is adequate and who authorised proceeding. Repeated exceptions may indicate that the criterion or offer boundary needs revision.
7. Remove questions without losing necessary safeguards
Reducing questions has a trade-off: less effort at qualification can leave more uncertainty for discovery. The goal is not to eliminate uncertainty, but to place each check before the commitment it protects.
Use three tests when deciding whether to postpone or remove a question:
- Does another criterion already establish the same fact more directly? Headcount is unnecessary here because scope and funding are assessed separately.
- Is the answer needed for this decision or a later one? Detailed delivery logistics may belong after initial fit is established.
- Can the team explain what it would do differently? If every answer leads to the same next step, remove the question from this assessment.
If removing a criterion later causes avoidable reversals, examine the actual failure. Restore the narrow check that would have prevented it, rather than reinstating every familiar question. If a retained criterion repeatedly blocks suitable enquiries, review its rationale and threshold instead of assuming the leads are the problem.
8. Run a decision review before expanding the model
Start with a small, defined review. As a hypothetical pilot, two team members could independently assess ten recent enquiries against the worksheet, using only evidence available at the original decision point.
Compare their actions and reasons. Track disagreements, unresolved criteria, later reversals caused by missed fit requirements, and deferrals without a named dependency. These observations reveal whether the model is usable; they are not proof that it improves sales results.
Review rejected cases as well as progressed ones. Otherwise, the team may notice unsuitable leads that slipped through while missing suitable leads it turned away. Where later outcomes are unknown, leave them unknown.
The next action is concrete: choose one offer, write its next-step decision, and complete a worksheet entry for every proposed criterion. Mark each one keep, clarify, postpone or remove. Before introducing another question, require its owner to name the answer that would change the decision—and the action that would follow.
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