How to Prepare for a Discovery Call
Most discovery calls do not fail because of what happens on the call. They fail because of what did not happen before it. Preparation is the single biggest lever a seller controls before a prospect says a word — and it is mostly a repeatable routine rather than a talent.
Why discovery calls fail before they start
The recurring causes are all upstream of the conversation. Poor research, so the rep knows little about the company, the industry or the person. Generic questions, closed or copied from a script without thought. Identical five-minute preparation regardless of deal size. Talking too much, filling silence with pitching instead of listening. Visible uncertainty about the product or the buyer's situation. And no practice beforehand, so the rep is hearing their own talk track out loud for the first time, live, with a real buyer.
None of these are solved by being sharper on the call. They are solved before it.
What a discovery call is actually for
A discovery call is the first substantive conversation between seller and prospect, focused on understanding the buyer's situation before proposing anything. The purpose is to establish whether there is a real problem, a real need and a real fit.
A successful call ends with clarity rather than rapport — clarity on the problem, the stakeholders, the timeline, and whether a next meeting is warranted. A call can feel friendly and still fail if it produces no usable information. By the end, a prepared seller should be able to answer four questions: what is the problem, who feels it, what happens if it is not solved, and what does the buyer need to see to move forward.
The preparation routine
Work through these in order, scaling depth to deal size:
- Research the company — website, recent news, funding, product changes, leadership statements. This gives you relevant questions instead of generic ones.
- Research the person — role, tenure, background, anything they have published. Frame questions around what they are personally accountable for.
- Review previous interactions — CRM, past emails, SDR handoff notes. Re-asking something already answered signals inattention.
- Check against your ICP — note where they fit cleanly and where they diverge, which tells you which risks to probe early.
- Draft questions in advance. Questions written under pressure are shallow; questions prepared beforehand can be layered.
- Identify the two or three likely objections for this industry, size and role, and think through a calm response.
- Decide the target next step before the call — a demo, a technical review, a meeting with another stakeholder. Without one, calls end in "let's stay in touch".
- Prepare the environment and yourself — test audio and video, close distractions, and reset between calls so frustration from the last one does not carry over.
The questions worth drafting
Organise by category so the call flows instead of feeling like an interrogation. Business goals and current-process questions build context: "what are you trying to achieve this quarter that depends on solving this?" and "walk me through how your team handles this today". Pain-point questions uncover urgency — "what is the most frustrating part of that process?"
Decision-making, budget and timeline questions qualify the opportunity, and land better once some trust exists: "besides yourself, who else would weigh in on a change like this?", "has budget been allocated, or would this be a new request?", "what is driving the timing?" Success-metric and next-step questions turn the conversation into a plan: "if this were solved perfectly, what would that look like in six months?" and "based on what we have covered, what would you want to see next?"
Not every category needs a question on every call, but touching most of them produces a complete picture.
Preparation mistakes
Researching too little signals the meeting is not a priority. Researching too much is its own failure — spending an hour on a twenty-minute call wastes time and tends to produce over-scripted, robotic conversations. If you cannot summarise the company in two sentences beforehand you have done too little; if you have spent longer researching than the call will last, too much.
Preparing a pitch instead of questions misunderstands the purpose entirely. Preparation should reduce talk time rather than increase it — the best-prepared reps often say less, because their questions are sharper. Ignoring likely objections leaves you caught out by pushback that was predictable in hindsight. And treating every prospect to the same unchanging five-minute routine produces shallow calls on exactly the accounts that matter most.
The step most reps skip
Practising the conversation. Saying your questions out loud beforehand is different from reading them silently, and it is where preparation usually stops. Reading a list of questions is not the same as asking them inside a live, unpredictable conversation where the answer you get is not the answer you expected.
DUODIAL exists for that step: rehearse the discovery call against an adaptive AI buyer beforehand, so the first time you hear your own questions out loud is not in front of a paying customer. The Call Analyzer then reports talk-to-listen ratio and questions asked versus recommended, which is the metric pair that most directly shows whether a discovery call stayed buyer-led or quietly became a pitch. It complements research and playbooks rather than replacing them.
Ready to drill what you just read?
Create your free DUODIAL account to start practicing with the simulator, analyzer, and the rest of the toolkit.