Lead qualification: turn prospect information into a justified next step.
Decide which prospect deserves a conversation, which needs clarification and which you cannot serve. Research, a completed evidence record and three fictional decisions make the process inspectable.
Qualify a prospect by checking delivery fit, the actual job to be done, the people involved and a realistic next action. Keep company facts separate from the buyer’s statements and your assumptions. A useful result is a decision with a reason: proceed, clarify, defer or exclude. A score alone is not that decision.
Make a decision about the next step.
A contact can look interesting without having a project. A business can need a service that you cannot deliver. Lead qualification is the work of finding out whether a particular buying situation and your offer can reasonably meet.
Here, a lead is an unconfirmed candidate. A qualified prospect has passed your relevant checks. An opportunity has a specific discussed job and an agreed next action. These are working definitions for this guide; CRM products and businesses use different stage names.
This guide begins after you have a candidate company. The ideal customer profile guide helps define your market. The research review examines broader evidence and experiment design. Here, the deliverable is one reviewable qualification record.
Six sources answer different questions.
| Source | What it examines | Limit for this guide |
|---|---|---|
| Webster & Wind, 1972 | Organizational buying as a decision process. | Conceptual model; not a conversion test. |
| Johnston & Bonoma, 1981 | Buying groups in 31 industrial firms. | Historical setting; not a universal contact hierarchy. |
| Sabnis and colleagues, 2013 | Lead follow-up by 461 sales reps in four firms. | Follow-up behavior; not an optimal score threshold. |
| González-Flores and colleagues, 2025 | Machine-learning prioritization in one B2B software company. | Model evaluation differs from demonstrated live sales gains. |
| HubSpot qualification guide | BANT and practical qualification questions. | Vendor guidance, not independent experimental evidence. |
| MEDDICC methodology resource | MEDDIC and its extended variants. | Practitioner framework, not proof of causal effectiveness. |
We checked original journal pages, a university-hosted paper and the methodology publishers on 6 October 2026. Access levels are listed in the sources. This is a selected synthesis, not a systematic review. We did not pool study effects or establish that one method is best across industries.
The older studies help frame a buying decision. Their age and setting matter. The newer study helps distinguish classification from sales outcomes. None evaluates Anivo or validates the fictional process below.
Write your own boundaries before researching the buyer.
Start with what you actually sell. Write the product or service, region, capacity limits and conditions that would make delivery impossible. This prevents a promising company name from pulling you into a project you cannot support.
A fictional packaging supplier might require a minimum production quantity. A consultant might lack the expertise required for a regulated technical task. A service business might be unable to work in the requested region. These are different exclusion reasons and should be recorded separately.
Check the business identity and relevant activity. Save the evidence address and review date. A product catalogue can establish that a company sells a category; it does not establish purchasing authority, available budget or dissatisfaction with its current supplier.
Use a stopping rule: if a necessary delivery condition fails, exclude this job. If a necessary condition is unknown, clarify it. Do not continue researching decorative details while the condition that determines feasibility remains unresolved.
A title does not explain the whole buying decision.
Webster and Wind’s model treats buying as an organizational process with multiple influences. Johnston and Bonoma’s abstract reports differences between equipment and service buying groups. Neither establishes that a particular job title always controls a purchase.
Our application: ask how this particular job will be evaluated. The person requesting information may use the product, set its specifications or help coordinate the purchase. You need the role in the decision, not just seniority.
| Question about the work | Possible responsibility | What to clarify |
|---|---|---|
| Who notices the packaging problem? | Operations or the product team. | What happens in the current workflow? |
| Who checks specifications? | Quality or production. | What must a sample demonstrate? |
| Who approves the artwork? | Brand or marketing. | Which files and approvals are required? |
| Who authorizes spending? | A budget owner. | What information is needed for approval? |
| Who orders and coordinates delivery? | Purchasing or operations. | How does an approved quote become an order? |
Illustrative responsibilities, not a fixed company organization chart. One person may perform several roles.
Record “approval route not yet known” when that is the truth. A conversation with a useful coordinator can be worth continuing. Do not label someone a bad prospect simply because they cannot sign the final order.
Ask about the job before filling out a framework.
A qualification conversation should clarify a decision both sides need to make. Avoid a long interrogation detached from the buyer’s situation. Explain why a specification, date or approval step changes the work you can offer.
| Question | Why it matters | A useful record |
|---|---|---|
| What needs to change in the current process? | Separates a project from general curiosity. | The job in the buyer’s own terms. |
| Which condition would make a solution unusable? | Finds delivery constraints. | Required specification and its owner. |
| What will you compare when choosing a supplier? | Clarifies evaluation. | Criteria still awaiting confirmation. |
| Who needs to review the proposed approach? | Maps the decision route. | Responsibilities, not guessed authority. |
| What has to happen before spending can be approved? | Clarifies the funding process. | Approval step; amount may remain unknown. |
| Which event determines when this work can begin? | Tests timing without inventing urgency. | An event or date stated by the buyer. |
| Would reviewing a sample answer the next question? | Tests a concrete next step. | An agreed action and its purpose. |
A vague answer is not proof of dishonesty or low intent. The person may not yet know the specification or approval route. Write down the missing information and decide whether finding it is proportionate to the job.
Choose a checklist that fits the buying task.
HubSpot’s guide explains BANT as Budget, Authority, Need and Timeline. The MEDDICC resource describes MEDDIC and its extended variants around value, buying roles and decision processes. We use these as practitioner vocabulary, not independently proved success formulas.
| Approach | Useful situation | Boundary |
|---|---|---|
| Short job checklist | A bounded job with a simple approval route. | Still record the unresolved condition and next action. |
| BANT | A conversation about funding, decision responsibility, need and timing. | Unknown budget is not automatically a failed project. |
| MEDDIC / extended variants | A complex purchase needing a more detailed decision record. | Do not force every early enquiry into a complete enterprise form. |
For this guide’s method, a short checklist is enough when it answers the relevant questions. Add detail when a real buying condition requires it. Do not interpret the number of filled fields as the probability of winning.
When a budget has not been set, ask about the approval process and scope. When timing is unclear, ask which event would create a project. A missing answer and a confirmed incompatibility deserve different decisions.
Keep facts, statements and assumptions in different fields.
- Observed
- A checkable company fact with a source and review date.
- Stated
- What a relevant participant said, with the conversation date and scope.
- Assumed
- Your interpretation, still awaiting confirmation.
- Unknown
- A question the current record cannot answer.
- Conflicting
- Two pieces of information disagree; pause the affected decision.
A buyer’s statement about quantity is useful input. A public product page is a different kind of evidence. Keep both, but do not quietly turn “we might launch this pack” into “production is approved.” Confirmation should be appropriate to the commitment being discussed.
Information also expires. If scope changes, revisit the earlier fit decision. If a person changes roles, revisit the approval route. Preserve the reason for the original decision so the update is understandable.
A qualification record should explain its next action.
Fictional scenario: a packaging supplier offers printed cartons in one service region, with a minimum run of 5,000 units. Fictional Company A asks about 8,000 cartons for a possible product launch. Every quantity, statement and decision in this example is invented for instruction.
| Field | Current evidence | Decision implication |
|---|---|---|
| Offer fit | The requested job is printed cartons in the supplier’s region. | Within the stated service boundary. |
| Quantity | Buyer states 8,000 units; supplier minimum is 5,000. | Quantity fits; verify final specification. |
| Need | Buyer wants to evaluate a carton for a planned launch. | A discussed job exists; launch approval remains unknown. |
| Specifications | Dimensions and artwork are not yet available. | Cannot give a final production quote. |
| Buying roles | Operations coordinates; artwork and spending approvals are unknown. | Ask who will review the sample brief. |
| Timing and funding | Possible launch; no approved date or budget stated. | Do not invent a deadline or order value. |
| Next action | Both sides agree to review dimensions before a sample proposal. | Proceed with clarification, not with an assumed order. |
The minimum quantity is a fictional supplier condition, not an industry standard or Anivo rule.
Evidence summary
“Company A · Printed cartons · Buyer-stated quantity: 8,000 · Final dimensions, artwork approval and funding remain unknown.”
Decision and next action
Proceed with a specification discussion. Request the dimensions and identify who approves the artwork. Do not record an approved order or prepare a final price before the scope is checked.
An original internal note, not a sent message, an Anivo import format or a real customer record.
The next action is small enough to be useful without pretending the sale is settled. If the dimensions later fall outside production capability, revise the decision. A good earlier conversation does not remove a later delivery constraint.
Similar companies can require different actions.
| Fictional case | Evidence that changes the decision | Action |
|---|---|---|
| Company A | A relevant 8,000-unit job; specification review agreed. | Proceed to clarification; final order remains unconfirmed. |
| Company B | A confirmed 1,000-unit one-off job; the supplier requires 5,000. | Exclude this job because delivery economics do not fit. |
| Company C | Relevant 10,000-unit project deferred by the buyer; review agreed for 15 January 2027. | Defer to the agreed review; do not invent current urgency. |
Proceed means the next action is justified. Clarify means a necessary condition is missing. Defer means a relevant job has a stated reason to wait. Exclude means a necessary condition fails, or the buyer explicitly closes this discussion. Record what would change each decision.
These outcomes concern a specific job and offer. Company B might be suitable for a different production method. Company C might later restart its project. Do not turn one decision into a permanent judgment about the business.
A qualified record still needs someone to act on it.
Sabnis and colleagues examine follow-up behavior and organizational processes. Their abstract reports differences associated with representative experience and prequalification. It does not supply a universal handover deadline. Our application is to preserve the qualification reason when the next action is recorded.
- State the specific job and relevant offer.
- Record the evidence, missing condition and exclusion risks.
- Name the next action, its purpose and who will do it.
- Use a date only when agreed or justified by a real review event.
- Record what happened, rather than assuming that a task was completed.
A note reading “good lead” cannot tell the next reviewer why the record matters. A note reading “quantity fits; dimensions needed before a sample proposal” can. Use the same clarity in your own workspace or a document you share with a colleague.
The sales follow-up guide handles the next communication after an actual reply or event. This page handles the decision that communication should serve.
A prediction and a completed sale are different outcomes.
González-Flores and colleagues develop a prioritization model in one B2B software company. Its limitations describe recent CRM integration and restricted assessment of actual conversion outcomes. That is a reason to distinguish model evaluation from observed sales gains.
For your own qualification record, inspect what a number describes. Is it service fit, information completeness, a ranking or a tested probability? Do not interpret a score of 80 as an 80% chance of purchase unless the system actually establishes that meaning.
Review decisions that were later reversed. Did the job change, or was the original record missing something? Recheck exclusions caused only by unknown information. Keep confirmed delivery failures separate from unanswered questions.
Track meaningful later events: a specification confirmed, an evaluation agreed, a job withdrawn, an order placed. A response or meeting is useful information; it is not automatically revenue. The research review explains how to design a broader test when you have enough data.
Connect company research with the next decision.
In Anivo, describe the market and offer to the Research Agent, review its plan and research candidate businesses. Use the company information and qualification context to decide which records deserve your attention.
Check the actual details, move relevant records into CRM and write the qualification reason in a note. Use stages and tasks to organize the work. Record a buyer’s response before revising the decision or preparing the next message.
The card in this article is a manual working format. It does not describe a built-in BANT form, automatic decision approval or a shared team CRM feature. Anivo does not establish a buyer’s budget, authority or purchase intent merely by finding a company.
Read the company-score guide for the meaning and limits of Anivo scores. Use the first sales email guide when the next suitable action is a reviewed introduction.
Start with a real offer, review the candidate companies and keep the reason for your next action beside the record.
A short list may only need a clear working document.
If you already know a few candidate businesses and have direct discussions with them, a document or spreadsheet may be sufficient. Give each record the same evidence labels, decision reason and next action. You do not need another tool merely to reproduce a checklist.
A connected workspace becomes useful when research, notes and follow-through are repeatedly separated or lost. Choose based on the work you actually need to manage. Neither a spreadsheet nor a CRM makes an unsupported qualification judgment accurate.
Before any outreach, review the recipient and the requirements for your intended channel. Keep contact eligibility separate from commercial fit. This article evaluates a business situation; it does not grant permission to contact someone.
Leave one decision another person can understand.
- Offer and delivery boundary: what can you actually provide?
- Candidate and specific job: what buying situation are you reviewing?
- Evidence: what was observed or stated, by whom and when?
- Unknowns or conflicts: which missing fact changes the decision?
- Buying route: who reviews the work and how is approval obtained?
- Decision: proceed, clarify, defer or exclude, with a specific reason.
- Next action: what will be done, by whom, and what would change the decision?
Copy these fields into your own document. Complete the missing-information field even when the record looks promising. If you cannot explain why the next action is justified, keep the candidate under review instead of silently advancing it.
The goal is a better-supported decision, not the largest possible qualified list. A clear exclusion, a well-defined question or a properly deferred job can each be a useful result.
Questions about lead qualification
Short answers about evidence, buying roles and practical decisions.
What is lead qualification?
It is checking whether a candidate’s specific buying situation fits your offer and whether a justified next action exists. Record the evidence, missing conditions and decision reason.
Is qualification the same as lead scoring?
No. A score ranks or summarizes information according to a method. Qualification records whether relevant conditions are met and what action is justified. A number does not replace the reason.
Is a qualified prospect already a sales opportunity?
Not necessarily. In this guide, an opportunity includes a discussed job and an agreed next action. Businesses use different stage labels, so define yours explicitly.
Should I exclude a prospect whose budget is unknown?
Not automatically. Unknown funding differs from a confirmed inability to support the job. Clarify scope and the approval process before deciding.
Do BANT or MEDDIC guarantee a sale?
No. They help organize qualification questions. Their use does not establish a universal winning formula or a validated purchase probability.
Must I speak only to the final decision-maker?
No. A person may coordinate, use or evaluate the solution without signing the order. Clarify their role and the approval route instead of guessing from a title.
Does a high Anivo score prove purchase intent?
No. Review what the score measures and check the company context. Budget, authority, timing and intent still require appropriate evidence.
Can I use the qualification card without Anivo?
Yes. Copy its fields into a document or spreadsheet. It is a manual working format, not an Anivo import file or proprietary qualification feature.
Original sources and access limits
Checked on 6 October 2026. Four academic papers and two practitioner resources. The checklist, questions and fictional decisions are our own practical synthesis; no source tests Anivo.
- Webster & Wind (1972): A General Model for Understanding Organizational Buying Behavior
University-hosted scanned original. Pages 12–14 and 19 reviewed visually. Conceptual framework, not sales-outcome evidence.
- Johnston & Bonoma (1981): The Buying Center: Structure and Interaction Patterns
Publisher abstract and bibliographic information reviewed; full text restricted. Industrial purchasing setting.
- Sabnis, Chatterjee, Grewal & Lilien (2013): The Sales Lead Black Hole
Publisher abstract reviewed; full text restricted. Follow-up research, not a current industry benchmark.
- González-Flores, Rubiano-Moreno & Sosa-Gómez (2025): The relevance of lead prioritization
Open original article. Methods and limitations reviewed; one company, with limited assessment of live conversion after integration.
- HubSpot: Lead qualification
Vendor-authored practical guidance used for BANT terminology, not its promotional performance claims.
- MEDDICC: MEDDIC / MEDDPICC methodology and process
Methodology provider’s account of frameworks and variants. Not an independent effectiveness study.
