Most founders doing founder-led sales don't lose deals in the close. They lose them weeks earlier, by spending three calls and a custom demo on someone who was never going to buy. That's a qualification problem, and the fix is a handful of discovery questions you ask on purpose instead of hoping the answers show up.

This post compares the two sales frameworks people reach for most, BANT and MEDDIC, and turns them into a short qualification checklist you can actually use on a sales call this week.

Why qualification is a sales skill, not a form

Qualification sounds like CRM admin. In practice it's a conversation skill: asking a direct question about budget or decision-making without sounding like you're reading a checklist. Engineers and founders who move into sales often skip it because it feels rude. The result is a pipeline full of friendly people who will never sign.

A good rule: if you can't answer "who signs, why now, and what happens if they do nothing," the deal isn't real yet. It's a conversation.

BANT: the fast filter

BANT stands for Budget, Authority, Need, Timeline. It's old, simple, and still useful as a first pass.

  • Budget: Is there money, or a way to get it?
  • Authority: Are you talking to the person who decides, or someone who can introduce you?
  • Need: Is there a real problem, in their words?
  • Timeline: Is something forcing a decision soon?

Where BANT works: short sales cycles, smaller deals, SDR tips for a first call where the goal is "is this worth a second meeting?"

Where it breaks: it treats budget as a yes/no gate. In B2B sales, especially SaaS sales to companies that have never bought a tool like yours, budget often doesn't exist until the need is clear. Asking "do you have budget?" on minute four mostly gets you "not really."

MEDDIC: the deal map

MEDDIC stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. It's heavier, and it's built for deals with more than one person involved.

  • Metrics: What number gets better if this works?
  • Economic buyer: Who controls the money?
  • Decision criteria: What will they compare options on?
  • Decision process: What steps happen between "yes, interesting" and a signature?
  • Identify pain: What hurts today, and what does it cost?
  • Champion: Who inside wants this to happen and will sell it when you're not in the room?

Where MEDDIC works: account executive work on larger deals, anything with procurement, security review, or a committee.

Where it breaks: run all six letters on a first call and it feels like an interrogation. MEDDIC is something you fill in across calls, not a script for one.

The founder version: five discovery questions

If you're a founder or a solutions engineer running your own sales calls, you don't need to pick a camp. Use BANT's speed on call one and MEDDIC's depth as the deal grows. Here are five discovery questions that cover most of both, worded so they sound human:

  1. Pain: "What made you take this call now, instead of six months ago?"
    This gets need and timeline in one question. If the answer is "just curious," that's useful too.

  2. Cost of doing nothing: "If nothing changes, what does that look like by the end of the quarter?"
    This is your Metrics and Identify pain. Listen for a number or a consequence.

  3. Decision process: "Say you love this. What happens next on your side before you could start?"
    Much softer than "who's the decision maker?" and it usually reveals the economic buyer and any review steps.

  4. Decision criteria: "If you were comparing a few options, what would make one the obvious pick?"
    Now you know what you're being judged on, and whether you can win on it.

  5. Champion check: "Who else would care about this, and how would you explain it to them?"
    If they can explain it well, you may have a champion. If they hesitate, you have work to do.

Notice there's no budget question. Budget usually comes out of question 3 ("we'd need to get it into next year's plan") or you raise it once the value is clear: "Based on what you've told me, does a price in this range make sense to take forward?"

A quick sales call checklist

Before you end any discovery call, check you can answer these. If you can't, ask before you hang up.

  • [ ] What problem they have, in their words
  • [ ] Why it matters now
  • [ ] What it costs them to do nothing
  • [ ] Who else is involved in the decision
  • [ ] The next concrete step, with a date

That last line matters most. "I'll send some info" is not a next step. "Thursday at 2 with you and your head of sales" is.

What qualification sounds like when it goes wrong

Two common failure modes:

The interrogation. You ask all five questions back to back, the prospect gets shorter answers each time, and you leave with notes but no trust. Fix it by following up on each answer before moving on: "You said the team ramps slowly. Slow how?"

The polite avoidance. You sense a weak deal but don't want to ask the hard question, so you book another demo. Fix it by naming it: "Honest question, it sounds like this isn't a priority until next year. Is that right?" People respect that, and a clean "no" frees your calendar.

How to get better at it

Qualification questions feel awkward the first twenty times you ask them out loud. Reading a sales framework won't fix that; saying the words will. Sales role play with a colleague works if you can get the time. Pick one question from the list above and use it on every call this week until it sounds like you.

That's the kind of sales practice we're building at Kulissa: realistic conversations with virtual customers who push back, go vague, or dodge the budget question, so the hard questions feel normal before a real deal depends on them. If that sounds useful, have a look at kulissa.com.