Discovery Call Design

A discovery call is the first real conversation between a sales rep and a prospect. Its purpose is to understand whether there's a genuine fit between the prospect's problem and your solution. Not to pitch. Not to demo. Not to close. To discover. The output is a decision: advance to the next stage (demo, evaluation, proposal) or disqualify and move on.

The principle: the prospect should talk 60-70% of the time. If the rep is talking more than 40%, they're pitching, not discovering. Every question should surface information that helps determine fit, urgency, and next steps.

The Discovery Call Structure

The 30-minute framework

Phase 1: Open (3 minutes)

Purpose: Set expectations for the call. The prospect should know what will happen and feel comfortable.

Script framework:

"Thanks for taking the time, {name}. Here's what I'd love to
do in the next 30 minutes:

First, I'd like to understand how your team handles [problem
area] today and what's working or not working.

Then, if it makes sense, I'll share a bit about how we approach
it and we can decide together if there's a reason to keep
talking.

Does that work? Anything you want to make sure we cover?"

Open rules:

• Always set an agenda. A call without an agenda feels aimless. The prospect doesn't know when they'll get to ask questions or when the pitch starts. Set the structure upfront
• Get their input on the agenda. "Anything you want to make sure we cover?" gives them ownership. If they say "I mainly want to understand pricing," now you know their priority
• Don't spend 10 minutes on rapport. "How's the weather in Austin?" burns time. One brief personal comment is fine. Then move to business. Prospects respect efficiency

Phase 2: Situation (7 minutes)

Purpose: Understand their current state before exploring problems. You can't diagnose what's broken without knowing what exists.

Key questions:

Situation rules:

• Don't ask questions you could answer with research. "What does your company do?" wastes the prospect's time. Research this before the call. Ask about the specific process you affect, not the company overview
• "What prompted you to take this call?" is the most important situation question. The answer reveals the trigger (signal) that made them open to a conversation. This is the foundation of the entire deal
• Limit situation questions to 5-7 minutes. Spending 15 minutes on the current state leaves no time for problem exploration. Get the lay of the land and move to pain

Phase 3: Problem (8 minutes)

Purpose: Surface the specific pain. Not hypothetical problems. Real, felt problems that the prospect cares about today.

Key questions:

Problem discovery techniques:

Problem rules:

• Go deep on one problem, not wide on five. A prospect mentions 4 challenges. Don't explore all 4. Pick the one with the most energy behind it and drill deep. Depth beats breadth
• Listen for emotion. When the prospect's voice changes (frustration, excitement, relief), you've hit a real pain point. Lean in. Ask more about that specific point
• Don't solve during discovery. The rep hears a problem and immediately says "We solve that! Let me show you." Resist. Keep asking questions. Understanding the full picture before proposing a solution produces better demos and higher close rates
• The prospect must articulate the problem in their own words. If you're the one describing the problem and they're nodding, you don't have a confirmed need. You have a hypothesis. Push them to say it: "How would you describe the main challenge?"

Phase 4: Implication (4 minutes)

Purpose: Help the prospect connect the problem to a business impact. Problems without impact don't get prioritized. Problems that cost revenue, time, or competitive position do.

Key questions:

Implication rules:

• Help them do the math. "Your 5 SDRs spend 3 hours each on research daily. That's 15 hours/day, 75 hours/week, ~$75K/year in SDR time spent on manual work." This math builds the business case they'll need for internal approval
• If the problem has no business impact, it won't get budget. "It's annoying" is not a business impact. "It's costing us $75K/year in wasted SDR time" is. If you can't quantify the impact, the prospect can't justify the purchase
• Don't spend more than 4 minutes here. Implication questions are powerful but heavy. Too many feels like you're trying to scare them into buying. 2-3 implication questions is enough

Phase 5: Process (4 minutes)

Purpose: Map the buying process. Who else is involved? What's the timeline? How do they typically buy tools like this?

Key questions:

Process rules:

• Always ask "who else would be involved." This is the multi-threading entry point. The answer maps the buying committee. If they say "just me," push gently: "Sometimes teams bring in IT for security review or finance for procurement. Would that apply here?"
• "How have you made a purchase like this before?" reveals the real process. Not the theoretical process. The actual process from the last time they bought a SaaS tool. That's the process this deal will follow
• Don't skip process because the conversation is going well. Excited prospects who love the problem-solution fit still stall on procurement, legal, and budget approval. Map the process now, not after the proposal

Phase 6: Close (4 minutes)

Purpose: Propose a clear next step. The discovery call should end with a specific action and a date.

Good closes:

Close rules:

• Always propose a specific next step with a specific date. "Let's reconnect sometime next week" = the deal dies. "Can we do Tuesday at 2pm with your VP?" = the deal advances
• Include the right people in the next meeting. If the champion mentioned a VP needs to be involved, the next meeting should include the VP. Don't schedule another 1:1 with the champion when the committee needs to be there
• Disqualify honestly. If the prospect doesn't qualify, say so clearly and kindly. "I don't want to waste your time" is more respectful than stringing them along for 3 more meetings. They'll remember the honesty if circumstances change later
• Summarize what you heard before proposing next steps. "So if I'm hearing you right, the main challenge is [problem], it's costing about [impact], and you'd like to have something in place by [timeline]. Does that capture it?" This confirms alignment and shows you listened

Discovery Call Preparation

Pre-call research (10-15 minutes per prospect)

Pre-call preparation rules

• 10-15 minutes is the right investment. Less than 10 and you'll ask questions you should already know. More than 15 and you're over-preparing for a 30-minute call
• Write down 3 specific questions based on your research. Not generic questions from a list. Questions tailored to this prospect. "Your LinkedIn says you're building the SDR function. What made you decide to build vs outsource?"
• Have your hypothesis ready. Before the call, form a hypothesis about their problem based on your research. "Based on their stage and hiring, they're probably struggling with [X]." The hypothesis directs your questions. Validate or invalidate it during the call
• Know their MQL source. If they requested a demo, they're further along than if they downloaded a whitepaper. Adjust your opener: "You requested a demo. What specifically were you hoping to see?" vs "You downloaded our outbound playbook. What caught your eye?"

Discovery Call Do's and Don'ts

Do's

Don'ts

Adapting Discovery by Lead Source

Measurement

Anti-Pattern Check

• Pitching the product in the first 10 minutes. The prospect mentions a problem and the rep immediately says "Great, let me show you how we solve that." This skips the rest of discovery. The rep doesn't understand the full picture. The demo will be generic. Keep asking questions
• Rep talks 70% of the time. The prospect got a pitch, not a discovery call. They leave feeling talked at, not heard. The rep misses critical information. Target 60-70% prospect talk time
• No pre-call research. "So, tell me about your company." This wastes 5 minutes on information that's on their website. Research before the call. Spend the call time on questions that only the prospect can answer
• Yes/no questions dominate. "Do you have a problem with outbound?" "Yes." "Do you have budget?" "Maybe." "Is this a priority?" "Sort of." Replace with open-ended questions: "Walk me through..." "Tell me about..." "What happens when..."
• Ending without a next step. "This was really helpful. I'll send you some info and we can reconnect." This is how deals die. Always propose a specific next step: "Can we do a demo on Tuesday at 2pm with your VP?"
• Skipping the process phase. The conversation went great. Strong need. Strong fit. But nobody asked about the buying process. Two months later the deal is stuck in procurement and nobody saw it coming. Always map the decision process
• Not disqualifying anyone. If 100% of discovery calls advance to the next stage, the qualification bar is too low. 20-40% disqualification is healthy. It means reps are qualifying honestly and not wasting the team's time on bad-fit deals
• Asking all BANT questions in the first 5 minutes. "Budget? Authority? Need? Timeline? OK, you're qualified." BANT is a framework for structured thinking over 30 minutes, not a 2-minute checklist. Weave the questions naturally through the conversation