Discovery calls typically run 30 to 45 minutes. They are not demos. A common mistake is treating the discovery call as an opportunity to present the product. The rep's job during discovery is to ask questions, listen, and confirm understanding, not to sell. The selling happens in the next meeting.
What a discovery call is for
The discovery call answers five questions the rep needs before they can run an effective demo or make a compelling proposal:
- What is the specific problem? Not the category of problem, the exact pain, with context. "We lose deals at pricing" is not enough. "We lose deals at pricing when we're competing against Vendor X, because reps don't know how to handle the price-to-feature comparison" is what the rep needs.
- What is the goal? What does success look like to this buyer in 6 months? The rep who ties their demo to the buyer's stated goal closes more deals than the rep who shows a standard feature walkthrough.
- Who makes the decision? The person on the call is often not the person who approves the purchase. Discovery is where the rep identifies the full buying committee and finds out who the economic buyer is.
- What is the timeline? Is there a real forcing event, a contract renewal, a new hire starting, a product launch, or is this exploratory with no urgency?
- What are the alternatives? What is the prospect doing now, or considering doing instead? Understanding the competitive situation and the status quo shapes how the rep positions the product.
Without clear answers to all five, the next meeting is a guess.
How discovery calls work in practice
Discovery calls follow a loose structure. Most reps use a framework to keep the conversation on track without it feeling like an interrogation.
SPIN Selling (Situation, Problem, Implication, Need-Payoff) is a widely used discovery framework developed by Neil Rackham and documented in his 1988 book of the same name. Situation questions gather context. Problem questions surface challenges. Implication questions deepen the pain by exploring the consequences of not solving it. Need-Payoff questions get the prospect to articulate why solving the problem matters. The framework works because it follows natural conversational logic, not a checklist.
MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is more commonly used in enterprise sales where the buying cycle involves multiple stakeholders and formal evaluation processes. Discovery under MEDDIC is more structured and often spans multiple calls.
Neither framework works if the rep is reciting questions from memory and not actually listening to the answers. The best discovery conversations feel like two colleagues working through a problem together, which is only possible when the rep has internalized the structure enough to run it naturally.
The off-script moment every discovery call hits
Most discovery call guides describe the framework. Fewer address what happens when the prospect goes off-script.
The rep is running a tight discovery. Three questions in, the prospect says: "Before we get too deep into this, can you just tell me how you compare to Gong? We've been using Gong for two years and we're evaluating alternatives."
This is not a wrench in the process. It's information. The prospect has just revealed something the rep didn't know: they're already using a competitor, they're actively evaluating, and they want a comparison before they're comfortable going further.
The rep who panics and starts pitching against Gong is now in a feature comparison conversation. That's a weak position. The better move is to acknowledge the question, give a direct 2-sentence answer on the key differentiator, and then redirect: "We're a different category entirely, no meeting bot, real-time answers during the live call rather than post-call analytics. Let me ask you this: what's made you start evaluating alternatives now?" That answer shapes the next 20 minutes better than any feature list.
The off-script moment isn't a problem. It's a signal. Reps who can read it and redirect without losing the thread run better discovery calls than reps who rigidly follow a prepared question list.
How long a discovery call should be
Thirty to forty-five minutes is the standard for mid-market SaaS deals. Enterprise discovery often takes longer and spans multiple calls, it's unrealistic to get full MEDDIC information from one conversation with one person.
The bigger risk is running long without a clear agenda. A discovery call that drifts past 50 minutes without covering the key questions produces a lot of notes and little direction. Set a clear agenda at the start ("I have 40 minutes, here's what I'd like to cover") and enforce it.
Ending the call with a clear next step is not optional. "I'll send something over" is not a next step. A booked follow-up with a specific agenda is. The rep who leaves the discovery without a firm next step has handed control of the deal back to the prospect.
What makes a discovery call fail
Pitching instead of asking. The rep hears a pain point and immediately explains how the product solves it. This kills the conversation. Acknowledge the pain, probe it further, and save the solution for the demo.
Accepting the first answer. Prospects give surface-level answers to surface-level questions. "We want to improve rep performance" is not a pain. "Three of our AEs consistently miss quota on deals over 50K and we don't know why" is a pain. The rep who drills to that second answer has something to work with.
Missing the economic buyer question. Who approves this purchase is the most important question in the call. Reps who are nervous about asking it directly often skip it and then spend two more meetings pitching to someone who can't say yes.
Not confirming understanding. Paraphrasing the prospect's answer back to them ("So if I'm hearing you right, the main pain is X, and the consequence is Y, is that accurate?") confirms you understood and often prompts the prospect to add something they left out. Most reps don't do this.
How Sales Copilot by Cluely AI supports discovery calls
Discovery is where Sales Copilot by Cluely AI's full workflow plays out.
Prepare: Before the call, the rep creates a Prospect with a brief (the account context), selects a Discovery Playbook, and attaches relevant materials. The Playbook shapes the answers during the live call: their length and format, whether they appear automatically or only on request, and any instructions the rep writes.
Rehearse: The Real-Time Sales Call Assistant includes an AI roleplay counterpart that runs the discovery from the buyer's side, realistic objections, redirects, and off-script questions included. Reps practice the pivot moment before they're live.
Live: During the actual discovery call, the cockpit hears the prospect's question and surfaces one answer drawn from the Playbook, brief and materials: a line to say, up to two supporting points and, when useful, a question to ask back. When the prospect goes off-script with a question, the answer can include the redirect the rep planned in the Playbook.
Debrief: After the call, automatic feedback identifies what was covered, what was missed, and what to carry into the next meeting.
The full guide to structuring an effective discovery conversation: Discovery Call Preparation. A bank of ready-to-use questions: Discovery Call Questions.
Frequently asked questions
What is a discovery call?
A discovery call is the first structured conversation between a sales rep and a qualified prospect. The rep asks questions to understand the buyer's specific pain, goals, decision process, budget, and timeline, before proposing a solution or running a demo.
How long should a discovery call be?
Thirty to forty-five minutes is standard for mid-market SaaS deals. Enterprise discovery may span multiple calls. The critical factor is covering the five key questions, problem, goal, decision process, timeline, and alternatives, before the call ends, regardless of length.
What questions should a rep ask on a discovery call?
Questions should surface specific pain (not general), consequences of not solving it, who approves the decision, when a decision needs to happen, and what alternatives the prospect is considering. SPIN Selling and MEDDIC provide structured frameworks for sequencing these questions naturally.
What is the difference between a discovery call and a demo?
A discovery call is for understanding the buyer's situation. A demo is for showing how the product addresses that situation. The demo should be tailored to what the rep learned in discovery. Reps who run a demo without discovery first show a generic product that the prospect may not connect to their actual problem.
How do you end a discovery call?
With a specific next step, a booked meeting, a defined deliverable (like a security review or pricing proposal), and a clear agenda for what that next meeting will cover. "I'll follow up" is not a close. A calendar invite with an agenda is.
Related terms
Guides on this topic
See how Sales Copilot supports the conversation. Start in your browser or download the app for Mac and Windows, and check pricing and our Privacy Policy before getting started.