25 Best Questions for Discovery Calls That Qualify

The short answer: the best discovery questions ask how the buyer's work actually happens, not how they feel about your product. Run the same five front-door questions on every call, then branch by where the work backs up. In the Series D rebuild where we landed these, attendance moved from 67% to 81% and email bookings doubled in four weeks. Same team, same products.

I've hired and trained 100+ SDRs over the past decade. The discovery calls fall apart because the questions asked were built around what the company sells instead of around how the buyer works.

Last year I rebuilt the SDR motion at a Series D HR tech company. Around 200 employees, a flagship product they'd been selling for more than a decade, and two newer products that had just come to market. The reps were good. The problem was that all three products had a pitch and only the flagship had real discovery behind it.

So the calls went like this. The rep ran the flagship discovery they'd been running for years, got a reasonable answer, then bolted a second and third product pitch onto the end of it. The buyer, who hadn't agreed they needed anything yet, got asked to react to two more things. Nobody was lying and nobody was lazy. The call had just turned into a product survey.

I've seen this at every multi-product company I've worked in. Call it discovery by product line: one qualification script per SKU, run back to back, and a buyer who leaves having answered questions about products they never said they needed.

More questions won't fix that. One front door and a few branches will. Ask how the work actually happens, then let the answer tell you which product is the way in.

Here are the 25 questions we landed on, and what to listen for after each one. The examples come from L&D and HR tech because that's where I did the work. The structure moves to any company selling more than one thing.

Five questions every rep asks, no matter what they end up selling

This is the front door. Same five questions on every call, before anyone knows which product is in play.

• "Walk me through what happens when a team tells you they need training on something new."

• "Who builds it, who approves it, and how long does that take from the request to something live?"

• "What's in your system right now that nobody finishes?"

• "What did you have to say no to last quarter because there wasn't time to build it?"

• "How do you decide who should get what training, and who makes that call?"

The first question does more work than the rest of the script combined. If the buyer can't describe how the work happens today, they probably don't own the problem, and you're likely talking to someone who got assigned to gather options.

What you're listening for is where the work backs up. A team that says "we go find a course, we vet it, it takes two weeks" has a sourcing problem. A team that says "we can't buy this, it's about our own equipment" has an authoring problem. A team that says "honestly, we assign the same thing to everyone" doesn't know what their people can already do.

Same five questions. Three completely different products at the end of them.

When the answer points at content they can buy

• "How much of what your people need can you buy off the shelf today?"

• "When you go looking for training on a topic, where do you look first and how long does vetting take?"

• "Who decides a course is good enough to put in front of your people?"

• "How do you know whether something you bought actually got used?"

• "What happens when a team asks for training on a topic you have nothing for?"

That last question is the pivot. It sounds like a content question and it's really a routing question. If the answer is "we buy something close enough and hope," you're still in the library conversation. If the answer is "we build it ourselves, badly, when we have time," the call just moved.

Curation is worth money when the buyer can tell you what bad content costs them, so ask what happened the last time they rolled out something nobody finished.

When the answer points at content that doesn't exist yet

• "What training exists only in someone's head right now?"

• "What's sitting in PDFs, decks, or a handbook that should be a course and isn't?"

• "When a policy or a procedure changes, how does the training get updated, and how long does that take?"

• "Who on your team has instructional design experience, and what happens when that person is at capacity?"

• "Is anyone retiring or moving on in the next year who's the only one who knows how something works?"

Almost nobody asks that last one, and it surfaces urgency with an actual date attached to it. It sounds like a training question. It's a risk question.

Watch for the answer that arrives as a compliment: "our team is amazing, they just know how to do it." That usually means one person knows how the thing works and nobody ever wrote it down. Ask how long that person is planning to stay.

When the answer points at not knowing what their people can do

• "How do you know what skills you actually have across the org today?"

• "Are you assigning training by role, by request, or by compliance calendar?"

• "What do your managers see about their team's development, and what do they have to come to you for?"

• "How often do you fill a role from the inside, and what makes it hard when you can't?"

• "What happens when leadership asks you to show what learning did for the business?"

The last question separates a project from a line item. An L&D leader who can't answer it is under pressure, whether or not they say so on the call, and that pressure is your why-now.

Be careful in this branch. It produces the most enthusiastic conversations and the slowest deals, because "we should really understand our skills" is easy to agree with and hard to fund. Push on who feels the pain, not on who likes the idea.

Interest is not urgency. Somebody has to be uncomfortable.

Five questions that decide whether this is a deal at all

• "What does this cost you today in time, headcount, risk, or turnover?"

• "What happens if nothing changes before your next hiring wave or compliance cycle?"

• "What have you already tried, and why didn't it stick?"

• "Who signs, and who else has to be comfortable before they do?"

• "What's the process from this conversation to a signed agreement, and what's driving the date?"

Don't force ROI math on a first call. A director may not know what a broken process costs to the dollar, and pushing for the number before they trust you turns the conversation into an interrogation. Directional is fine on call one. "We're onboarding 300 seasonal people in March and it takes us three weeks to build a course" is enough to work with.

"What have you already tried" does more work than it looks like it does. When somebody says "we bought a tool last year but nobody owned the rollout," that's not a product gap. That's an operating gap, and it should change how you sell from that sentence forward. Stop pitching features harder. Show ownership, implementation structure, reporting, and the handoff. Tools amplify clarity or confusion, they do not fix it.

I'd also argue the status quo is your real competitor, not the other vendor in the evaluation. Talking is cheap. Somebody has to accept the cost and the disruption of changing how work gets done, and that person needs a reason that survives their next budget conversation.

What to listen for after each answer

I train reps to listen for four things in the answers: a measurable problem, a defined owner, a reason to act now, and a credible path to a decision.

A prospect who describes an expensive problem but can't name an owner is account intelligence, not an opportunity. A prospect with an executive sponsor and no capacity to implement needs a different timeline, not more pressure. A prospect with budget, urgency, and a decision path can still be a bad fit if what you sell doesn't touch the workflow they just described.

This is also where multi-product teams get sloppy. Two products can both be technically relevant to the same account, and that doesn't mean you pitch both. Pitch the one attached to the pain the buyer described in their own words. The second one keeps, and it lands better in the follow-up, in writing, where it doesn't cost you the call.

Discovery consistency is a management problem

Individual reps run good discovery calls. Teams run inconsistent discovery, and I believe that's a management problem before it's a rep problem.

I see the same pattern almost everywhere: every rep sells differently. Different definition of urgency, different bar for what counts as qualified. When that's true, the forecast turns into a debate and no amount of question training fixes it. The fix is a documented sales motion with shared definitions and exit criteria.

What fixes it is structure. In that Series D rebuild, discovery was one piece of a broader change, and the pieces holding it up were mechanical. A call scoring rubric in Gong, so every conversation got measured against the same bar. Weekly SDR to AE syncs with a short meeting debrief template, so what the SDR learned actually reached the AE instead of the prospect getting re-discovered two weeks later and feeling it. Four defined lead pools with their own playbooks instead of one undifferentiated queue.

We also stopped training reps on the products and started training them on the problems. The exercise is simple. Complete this sentence about your buyer: "you know how frustrating it is when…" A rep who can finish that sentence three different ways for three different buyers doesn't need a script. A rep who can only finish it one way will run the same discovery call for the rest of their career, no matter how many products you launch.

Four weeks after the ICP and workflow shift, meeting attendance moved from 67% to 81% and the booking rate over email doubled. Same team, same products, same calendar. What changed was the operating layer underneath the calls.

Systems beat heroics.

The best discovery calls leave behind a decision record, not a collection of agreeable answers.

Questions sales teams ask about discovery

What is the best first question on a discovery call?

"Walk me through what happens when a team tells you they need X." If the buyer cannot describe how the work happens today, they probably do not own the problem, and you are likely talking to someone assigned to gather options. That one question does more work than the rest of the script combined.

How do you run discovery when you sell multiple products?

One front door, a few branches. Same opening questions on every call, before anyone knows which product is in play, then let the answer route the conversation. Pitch the product attached to the pain the buyer described in their own words. The second product keeps. It lands better in the follow-up, in writing.

How do you make discovery consistent across a team?

Structure, not scripts: a documented sales motion with shared definitions and exit criteria, a call scoring rubric so every conversation is measured against the same bar, and SDR-to-AE debriefs so what the SDR learned reaches the AE. Every rep selling differently is a management problem before it is a rep problem.