Ask most reps how they prepare for discovery calls and they'll describe the same routine: memorize the question list, run through it in order, check the boxes on the call itself. Current tools, team size, budget owner, timeline, pain points. The questions come out smoothly because they've been said out loud a dozen times before the call ever happens.
And then the call still goes nowhere. The rep gets answers to all six questions, writes them in the CRM, and still can't tell you, an hour later, what the buyer's actual problem is or whether they'd pay to fix it. That's not a question problem. Rehearsing the list only trains the easy half of discovery: asking. It does nothing for the hard half, which is knowing what to do with the answer you just got.
What discovery call practice actually needs to train
A question list gets you an answer. It doesn't get you the follow-up that turns a flat answer into a real one, and that follow-up is where discovery calls are actually won or lost.
Noticing when an answer is worth chasing. Buyers rarely announce their real problem on the first pass. They give a reasonable, slightly vague answer, and the rep who's focused on getting through the list moves straight to question four. The rep who's actually listening hears the one word that doesn't quite add up, "it's fine, mostly," and stops to ask what "mostly" is covering. Practice built around reciting questions never trains that pause, because there's no consequence for skipping it.
Telling a real cost from a shrug. Not every answer hides something. Some buyers genuinely don't have a pressing problem yet, and chasing every answer with a follow-up wastes the call and makes the rep sound like they're fishing. The skill is distinguishing a shrug from a real, specific cost, and that only gets trained against a buyer whose answers vary from call to call, not a script that plants the same reveal every time.
Slowing down instead of stacking questions. A rep running through a memorized list under time pressure tends to ask two or three questions in one breath: "How are you handling that today, and who's involved in that decision, and what's your timeline?" The buyer answers the easiest one and the other two disappear. Discovery call practice needs to build the discipline of asking one thing, actually waiting, and following up on what comes back before moving to the next topic.
Get those three in place and a rep stops running an interview and starts running an actual conversation, one where the questions serve the follow-up instead of being the whole performance.
Worked example: the same discovery call, run two ways
Below is a fictional AE, Alicia, at a workforce scheduling company called Rosterly, on a discovery call with Devon, a fictional operations manager at a mid-size food manufacturer called Briarwood Foods.
Run as a question checklist:
Alicia: So walk me through how scheduling works today. Are you using a tool for it, or is it more manual?
Devon: We've got a scheduling tool, it's fine, mostly. It's built into our HR system.
Alicia: Got it. And how many locations are you managing with it?
Devon: Four right now, growing to six by next year probably.
Alicia: Okay, and who owns the decision if you were to look at something new here?
Devon: That'd probably be me and our VP of Ops.
Every answer got recorded. None of it got followed up on. "It's fine, mostly" is doing a lot of work in that sentence, and Alicia moved past it in under two seconds because the next line on her list was location count. By the end of the call she has four data points and zero insight into whether Briarwood actually has a problem worth solving.
Run by following the interesting answer:
Alicia: So walk me through how scheduling works today. Are you using a tool for it, or is it more manual?
Devon: We've got a scheduling tool, it's fine, mostly. It's built into our HR system.
Alicia: "Mostly" is doing some work in that sentence. What's the part that isn't fine?
Devon: Honestly, it doesn't handle shift swaps well. People end up texting a manager directly and it gets tracked on a whiteboard half the time.
Alicia: That sounds like it eats someone's time every week. Who's dealing with that, and roughly how often?
Devon: Our shift leads, probably daily at each location. It's not a huge deal, but it's constant.
Alicia: Four locations, daily, that adds up fast. Is that the kind of thing that would actually move the needle if it went away, or is it more of an annoyance?
Alicia asked one fewer question than the checklist version and learned dramatically more. She caught the hedge in "fine, mostly," asked what it meant instead of logging it and moving on, and turned a generic answer into a specific, recurring cost: daily manual shift-swap tracking across four locations, owned by shift leads. She still doesn't know if Briarwood will buy, but she now knows what she'd need to show them to find out, which is the actual point of a discovery call.
Common mistakes in discovery call practice
Practicing the list until it's smooth and stopping there. A fluent question list feels like progress because it sounds confident. It isn't discovery until the rep is doing something with what comes back.
Rehearsing against a buyer who over-explains. A colleague roleplaying the buyer, trying to be helpful, will often volunteer the interesting detail without being asked. That trains a rep to expect answers that don't require digging, which real buyers rarely give.
Treating every question as equally important. Some questions on a standard list (timeline, budget owner) matter for qualification but reveal little about the actual problem. Practice should weight the open-ended questions, where the buyer's own words matter, over the checkbox ones.
Never varying the vague answer. If a rep only ever practices against the same one or two hedges, "it's fine" and "we're pretty happy," they build a script for those two moments and freeze on the third kind of non-answer. Vary what the buyer deflects with between sessions.
Scoring completeness instead of depth. It's easy to grade a discovery call on whether every field in the CRM got filled in. That rewards the checklist behavior this practice is supposed to fix. Score whether the rep found one thing on the call they didn't already know before it started.
A discovery call isn't a form the buyer fills out through you. It's the only part of the sales process where the buyer tells you, in their own words, what's actually costing them something, if anyone bothers to ask twice. Rehearsing the question list builds fluency in asking. Rehearsing the follow-up, against a buyer who won't hand over the real answer on the first try, builds the skill that actually decides whether the rest of the deal has anything to work with.
