A qualified deal should survive the rep's memory.

Friday's pipeline review gets to Northstar.

The opportunity is marked qualified, worth $84,000, and due to close September 30. Budget, authority, need, and timing all have green ticks.

The manager asks what happens if Northstar leaves the current process alone.

The rep remembers that reporting is painful. He cannot remember who feels the pain, what it interrupts, or whether the buyer attached a date to fixing it. The notes say "manual reporting, keen to improve".

The CRM has four completed fields and almost nothing another person can use.

Sales qualification should help a team decide where to spend time. It stops doing that when the framework becomes a form-completion exercise. An "economic buyer" field can contain a name without proving that person supports the purchase. A timeline can contain a date the seller invented. The pain field can carry one vague noun for six months.

Ask what the team knows, how it knows, and what remains uncertain.

Use the framework to find gaps

HubSpot defines sales qualification as deciding whether a lead or prospect fits what you sell. Its guidance covers budget, authority, urgency, and business fit. Close's qualifying-question guide adds needs, decision process, stakeholders, and deal risk.

Those categories give the rep somewhere to look. They do not fill the gaps for them.

BANT may be enough for a short, fairly simple sale. A complex opportunity may need MEDDIC or MEDDPICC. A recurring-revenue team may prefer SPICED because it carries the customer's situation, pain, impact, critical event, and decision into later stages of the relationship.

I would choose the smallest shared language that exposes the gaps common in your sales motion. More letters do not make the evidence better.

MEDDICC's own guidance says MEDDIC is not a checklist. A champion can change roles or stop supporting the project. Competition can alter the decision criteria. Qualification changes as the deal changes.

Winning by Design describes SPICED as a diagnostic framework for carrying customer information through the relationship. Diagnostic is the word I would keep. A good framework shows the team where the deal is weak. It does not hand out a passing grade.

Six things I want to see in the record

Most B2B opportunities become easier to inspect when the CRM preserves the following six things.

The problem

Record the current process and the specific failure the buyer wants to change. "Reporting is manual" is a category. "Three regional managers email separate spreadsheets to finance every Friday" describes work.

Ask for the last example. Who was involved? What happened? How did they recover? Concrete stories are easier to verify than adjectives.

The consequence

A problem can be real and still remain below every other priority.

Find the operational or personal consequence. Finance may lose a day reconciling numbers, or a manager may enter the board meeting with an unreliable forecast. Sometimes nobody is badly hurt and the workaround remains acceptable. That last answer is useful too.

The people

Job titles do not explain a buying group. Record who feels the problem, who owns the change, who controls money, who evaluates the solution, and who can stop it.

Treat "champion" as a claim to test. What have they done that they would not do for every vendor? Sharing the internal process, arranging access to a skeptic, and correcting your business case are evidence. Being friendly on calls is not.

The decision

"The VP decides" rarely describes the whole path. Learn how the company moves from interest to approval.

What will each group evaluate? Which meeting grants approval? Does security happen before a commercial decision? Does procurement need a signed business case, an approved vendor form, or both?

A decision process should contain steps, people, and evidence of completion.

The timing

Separate a preferred date from a date with consequences.

"We would like this in Q3" is a preference. "The new territory model starts September 1, so managers need two weeks to learn the workflow" gives the date a reason.

The date may still move. At least the CRM records what would move with it.

The next commitment

Qualification should change what happens next. A useful commitment names the person, action, and date.

"Follow up next week" is a seller reminder. "Maya will bring the finance lead to a 30-minute cost review on Tuesday" shows participation from the buyer.

If there is no mutual next step, keep the opportunity where it is until there is one.

Thin entries and useful entries

The useful entries take more words because each carries an observable detail. A manager can inspect it. A rep can act on it.

Ask like a person

A qualification framework can make a discovery call sound like an audit. The rep runs down an internal list while the buyer waits for the conversation to begin.

Start with what the buyer has already said. Follow the thread.

If they say the forecast takes too long, try:

Then:

Those questions can uncover the problem and consequence without announcing that you have moved from the P to the I in an acronym.

Use plain questions for the rest:

• Who else will have a strong opinion about changing this process?
• What would finance need to believe before it approved the project?
• Once your team agrees, what has to happen before anything can be signed?
• Is the September date tied to another event, or is it the date you would prefer?
• What would be a sensible next step on your side?

Nobody needs all five questions in one call. Qualification accumulates across conversations. The CRM should show the answer, its source, and the date somebody last confirmed it.

Separate what the buyer said from what the seller thinks

Consider this CRM entry:

It sounds confident. It may combine a buyer quote, two seller assumptions, and an old date.

Write the record in three parts:

Seller judgment belongs in the record. Label it so the next reader does not mistake it for something the buyer confirmed.

A linked call moment, meeting note, or email helps when the claim affects forecast confidence. Nobody needs a transcript behind every field. Keep the source for the fields that could change the deal.

Let qualification expire

A qualified opportunity can become unqualified.

An economic buyer may leave, a reorganisation can give the problem to another team, or a competitor can change the criteria. Sometimes the buyer finds a tolerable workaround and the project loses its deadline.

Add two small controls to the CRM:

• Last confirmed: the date someone on the buying side confirmed the information.
• Confidence: confirmed by buyer, inferred by seller, or unknown.

Do not create a scoring model with decimal points. The controls exist to expose stale claims, not manufacture precision.

Revisit the field when the deal changes stages, a key meeting happens, or the claim becomes old enough to affect the forecast. A six-month-old budget answer should not remain green because nobody has asked again.

Inspect one deal in five minutes

The manager does not have to rerun discovery. Pick the qualification gap most likely to stop the deal.

Ask:

1. What did the buyer say or do that supports this field?
2. When was it confirmed?
3. What are we inferring?
4. What changed since then?
5. Which next customer action would strengthen or disprove the claim?

If the rep can answer from the CRM, the record is doing its job. If the answer lives only in the rep's memory, capture it while the conversation is still available and decide whether the buyer needs to confirm it.

The review may reveal that the opportunity is early, politically weak, or missing a reason to act. Leave the field open. An honest gap is more useful than a green tick nobody can defend.

Copy this qualification record

Problem: current process, recent example, and failure the buyer wants to change

Consequence: time, money, risk, delay, or personal cost; include the status quo if it is acceptable

People: problem owner, change owner, economic buyer, evaluators, blockers, and evidence for any champion claim

Decision: criteria, approval steps, paper process, and evidence each step is complete

Timing: desired date, event behind it, and consequence of missing it

Next commitment: buyer action, seller action, owner, and date

Source: meeting note, call moment, email, or document supporting consequential claims

Last confirmed: date and whether the entry is buyer-confirmed, seller-inferred, or unknown

Put these fields where the team already manages opportunities. A qualification document that sits outside the CRM becomes one more version to reconcile.

Quick answers

What are sales qualification questions?

They are questions used to learn whether an account fits, has a problem worth changing, can make a purchase, and has enough internal movement to deserve sales time. Good questions also reveal what the rep does not yet know.

Which sales qualification framework should a team use?

Use the smallest framework that fits the sale. BANT can work for short, simple buying paths. MEDDIC or MEDDPICC suits complex opportunities with several stakeholders and approval steps. SPICED works well when customer context needs to travel from acquisition through customer success.

When is a sales opportunity qualified?

Define this for your own sales motion. A practical minimum is confirmed fit, a relevant problem, a consequence worth examining, access to the buying process, and a mutual next step. Complex deals will require more evidence before the forecast deserves confidence.

Should every qualification field be required?

Required fields can expose gaps, but they also encourage invented answers. Let reps mark a field unknown, inferred, or not yet applicable. Inspect the gaps at stage changes instead of rewarding form completion.

How often should qualification be updated?

Update it when a meaningful conversation changes the account, when the deal changes stages, and when an old claim could affect forecast confidence. Store the last-confirmed date beside consequential fields.

Research note: This article draws on current qualification guidance from HubSpot, Close, MEDDICC, and Winning by Design. LogicNotes added the six-part evidence record, source and confidence controls, five-minute manager inspection, and CRM template.