The Discovery Call Checklist That Actually Works

A discovery call works when three things line up: you walk in with a hypothesis (not a blank page), you spend more time on the buyer's mechanics than your product, and you leave with a written next step already on both calendars. Everything below is the tactical version of that: what to prep the night before, the questions that actually move a deal, and how to close the call so momentum survives the next 72 hours.

Prep: the 20-minute pre-call routine

Most weak discovery calls are lost before they start. The rep opens Zoom, glances at the LinkedIn tab, and improvises. That's fine for a first-touch qualification chat. It's malpractice for a booked discovery slot with a stakeholder.

A tight prep routine covers five things:

1. The account's last 90 days. Funding, headcount changes, product launches, exec hires, earnings language if public. You're looking for a reason this project is happening now.
2. The buyer's role signal. Not their title, their scope. A VP RevOps at a 200-person Series C owns different problems than the same title at a 4,000-person public company. Read their last two LinkedIn posts and any conference talks. You'll often catch the exact vocabulary they use for the problem you solve.
3. A written hypothesis. One sentence: "I think they're feeling [pain] because [trigger], and the cost of not fixing it is [consequence]." You will be wrong about part of it. That's the point. You're giving the buyer something specific to correct, which is faster than making them narrate from scratch.
4. Two peer references ready to name-drop. Same segment, same rough stage, ideally a problem the prospect just described in your outbound thread.
5. The disqualification criteria. Decide, before the call, what would make you politely end the process. Wrong tech stack, no budget cycle for nine months, a champion with no exec access. Writing this down beforehand is the single strongest defence against happy-ears pipeline.

If prep runs longer than 20 minutes on a routine discovery, you're researching instead of selling. If it runs shorter than 10, you're winging it.

The question set that actually earns information

Discovery questions fail in two directions. Too generic ("What are your priorities this year?") and the buyer gives you a press-release answer. Too product-shaped ("How are you currently handling multi-touch attribution?") and you've leaked what you sell before understanding whether they need it.

The questions that work sit between those poles. They're specific enough to signal competence, open enough to let the buyer talk about their actual world.

A working sequence for a 30-minute call:

Opening (2–3 min). Confirm time, confirm agenda, confirm outcome. "I've got us for 30. I'd like to spend the first 20 understanding how [function] runs today and what prompted the conversation, then walk through whether it makes sense to keep going. Fair?" Getting an explicit yes here is what makes the "next steps" conversation later feel natural rather than pushy.

Context (5–7 min).

• "Walk me through how [the process you affect] works today, from [trigger event] to [outcome]." Let them narrate. Interrupt only to clarify handoffs and owners.
• "Where in that does it break down most often?"
• "What have you already tried?" This one is underused. It tells you what's off the table and what internal politics you'll inherit.

Impact (5–7 min).

• "When [the break] happens, what's the downstream effect?" You want a specific consequence, ideally quantified by them, not you.
• "Who else feels it?" Maps stakeholders without asking "who else is involved in this decision," which every buyer has been trained to deflect.
• "If nothing changes in the next two quarters, what does that look like?"

Buying process (5 min).

• "You mentioned this is a priority now. What changed?" Trigger events are the single best predictor of a deal actually closing.
• "How does something like this typically get funded and approved here?" Note the word typically. It invites description, not commitment.
• "Who else would want to weigh in before you'd feel confident moving forward?"

Test close (2–3 min).

• "Based on what you've described, it sounds like [reflected summary]. Am I hearing that right?"
• "If we could show you [specific outcome tied to their words], would that be worth an hour with [next stakeholder] in the next couple of weeks?"

The order matters more than the exact wording. Context before impact, impact before process, process before any hint of a next-step ask.

Reading the call in real time

A checklist is only as good as the rep's ability to abandon it when the call goes somewhere better. Two signals to watch for:

The buyer volunteers a metric. When a prospect says "we're losing about a day a week per rep to this," stop advancing the script and dig. Ask how they measured it, when they last checked, and whether their manager agrees. Buyer-supplied numbers are the raw material for the business case you'll write later. Interviewer-supplied numbers get argued with in procurement.

The buyer gets vague when you ask about process. "We'll figure that out when we get there" or "I basically own this" on a six-figure purchase are yellow flags, not green ones. Push once, gently: "Totally fair. Just so I don't create work for you later, has a project this size gone through here before, and if so what did that path look like?" If the answer is still hand-wavy, that's your qualification signal.

Closing the call: the next-step discipline

The last five minutes decide whether the deal has a pulse next week. Three moves, in order:

Recap what you heard, in their language, not yours. "So the picture is: [pain] is costing [consequence], you've tried [X], and the reason it's live now is [trigger]." If any part is wrong, they'll correct it, and you've saved yourself a bad follow-up email.

Propose a specific next step, with a specific person, on a specific date. Not "let's regroup next week." Instead: "The natural next step is a 45-minute working session with you and [name from ops]. I'll bring [artifact]. Does Tuesday the 14th at 10 work, or is Thursday better?" Put it on the calendar before you hang up. A meeting booked live holds; a meeting promised by email slips.

Send the recap the same day, before end of business. Bullet the pains in their words, the impact figures they gave you, the agreed next step, and the open questions you still owe answers on. This document becomes the shared source of truth for the rest of the deal, and it's the single artifact that survives internal forwarding when your champion loops in their boss.

The takeaway

• Write a one-sentence hypothesis before every discovery call. If you can't, you haven't done enough research to be in the meeting.
• Ask context, impact, and process questions in that order. Reversing it makes buyers defensive and makes forecasts optimistic.
• Treat buyer-supplied numbers as gold and interviewer-supplied numbers as liabilities. Only the first kind survives procurement.
• Book the next meeting on the call, not after it, and send a same-day recap in the buyer's own language.