A discovery call is a structured sales conversation where you qualify a prospect, understand their pain, and determine whether your product is the right fit - before showing anything. It’s not a demo, not a pitch, and not a product walkthrough. It’s a diagnostic conversation that determines whether the next step makes sense at all.
Why Discovery Is the Most Important Call in Your Sales Process
I’ve been in B2B SaaS sales for over 5 years. Across €4M+ in closed revenue, the single biggest leverage point I’ve found is not the demo, not the proposal, not the follow-up sequence. It’s the discovery call.
Here’s why: every other step in your sales process is downstream of discovery. A bad discovery leads to demos that miss the mark, proposals that get ignored, and deals that die because you never understood what the prospect actually needed. A good discovery call makes everything that follows easier - sometimes dramatically so.
I’ve had discovery calls where the prospect essentially sold themselves. By the end of 25 minutes, they’d articulated their pain, described the cost of not solving it, and explained why they’d looked at three competitors and found them lacking. All I had to do was show them the two features that solved their specific problem. Signed two weeks later at full price, no discount discussion.
That outcome doesn’t happen without discovery. It happens because of it.
Discovery Call vs Demo: What’s the Difference?
Founders who are new to structured selling often blur the line between a discovery call and a demo. The distinction matters a lot.
Discovery call: You ask questions. The prospect talks. Your goal is to understand their situation, their pain, and whether there’s a real fit. No slides, minimal product talk.
Demo: You show the product. But only the features that are directly relevant to what you learned in discovery. The demo is the prescription; discovery is the diagnosis.
The most common mistake I see founders make is collapsing these into one call: they spend 10 minutes on “quick discovery questions” and then pivot to a 40-minute product tour. That approach consistently underperforms. The prospect doesn’t feel understood, the demo is generic, and there’s no momentum toward a close.
Keep them separate. Run a clean 30-minute discovery. Book the demo for a separate session, tailored to what you learned. This two-step process closes more deals than any single-call approach I’ve tried.
The Four Pillars of a Discovery Call
There are many discovery frameworks out there - SPIN, MEDDIC, BANT, GPCTBA/C&I. They all have merit. After testing most of them, here’s the simplified four-pillar structure I use and teach to the founders I work with:
Pillar 1: Situation
Understand what they’re doing today. Not what they wish they were doing - what they’re actually doing. Current tools, current process, team size involved, how long they’ve been doing it this way. This is low-threat context-building. You’re not probing for pain yet, you’re mapping the landscape.
Good situation questions:
- “Walk me through how you currently handle [area]."
- "What tools are you using today for this?"
- "How many people in your team are involved in this process?”
Pillar 2: Problem
Where does the current situation break? What’s frustrating? What takes too long? What’s costing them money or slowing down growth? This is where you listen carefully and help them articulate pain they may have normalized.
Good problem questions:
- “What’s the most frustrating part of that process right now?"
- "If you could change one thing about how this works, what would it be?"
- "When does the current process typically break down?”
Pillar 3: Impact
The impact questions are where most founders leave money on the table. They find the problem and then immediately jump to the solution. That’s a mistake. The prospect hasn’t felt the full weight of their problem yet. Impact questions do that work.
”If you don’t solve this in the next 6 months, what happens to your [goal]?”
When a prospect answers that question out loud, they’re generating their own urgency. They’re writing the business case for buying your product. You didn’t do it - they did. And the things people say out loud to themselves are infinitely more convincing than anything a salesperson can tell them.
Pillar 4: Decision
Before you end, you need to understand the buying process. Not aggressively - just clearly. Who else is involved? What does the evaluation process look like? What’s the timeline? Have they looked at other solutions?
This pillar tells you whether the deal is real and what it takes to close it. A prospect who has no timeline, no budget, and no decision-making authority is a bad investment of your time, no matter how good the fit seems. Find this out in discovery, not after three demos and a proposal.
How to Open a Discovery Call
The first 90 seconds set the tone for everything that follows. If you don’t frame the conversation, the prospect will default to expecting a pitch - and they’ll be guarded.
Here’s what I use and teach:
“Thanks for making time. Before I show you anything about what we do, I’d love to spend 20-25 minutes understanding your current situation - that way I can focus on what’s actually relevant to you rather than giving a generic overview. Does that work for you?”
This does three things: it positions you as a consultant, not a vendor. It gives you permission to ask probing questions. And it sets up a focused demo as the natural next step rather than another awkward ask. Most prospects respond positively because it’s different from every other sales call they’ve been on.
The Right Length for a Discovery Call
Thirty minutes. That’s it.
I know some enterprise AEs run 60-minute discovery calls. That’s appropriate when you’re selling €100K+ deals to large organizations with multiple stakeholders. For most B2B SaaS founders selling sub-€50K deals, 30 minutes is enough to qualify fully and set up next steps.
If you can’t get what you need in 30 minutes, one of two things is true: you’re asking the wrong questions (likely), or the prospect isn’t a real opportunity (possible). Neither problem is solved by making the call longer.
The tightest discovery calls I’ve run were 18-22 minutes. Two of those turned into €40K+ deals. The length of the call has almost nothing to do with the size of the outcome.
Why Founders Should Run Discovery Calls Themselves
A lot of founders ask me when they should hire someone to do discovery calls so they can focus on product or strategy. My answer is always the same: do your first 20-50 discovery calls yourself, no exceptions.
Here’s why. Discovery calls are market research disguised as sales conversations. Every call teaches you something about how your target market thinks about their problems, what language they use, what objections come up repeatedly, and what selling points actually land. This information is worth more than anything a market research firm can give you.
The founders who do their own discovery calls early build a competitive advantage that compounds over time. Their positioning gets sharper. Their sales process gets tighter. Their product roadmap gets clearer. The founders who hand off discovery too early end up with a sales team running a process the founder doesn’t fully understand - and they wonder why things don’t convert.
When you do eventually delegate, make sure you’ve documented what works and what doesn’t in enough detail that it transfers. That’s the foundation of a repeatable sales motion.
Common Discovery Call Mistakes
Pitching during discovery. The moment you shift from questions to selling, you lose the diagnostic advantage. Prospects become guarded. You stop learning. If they ask “so what does your product do?” early in the call, say: “I’ll walk you through exactly that in a few minutes - first, can I understand a bit more about your current setup?” Then get back to questions.
Taking over with your story. “We help companies like yours…” “We’ve seen this problem a lot…” These statements feel natural to you but they take time away from the prospect talking. Every minute they talk is a minute you’re learning. Every minute you talk is a minute you’re guessing.
Skipping impact questions. You found the problem, you’re excited, you want to show the solution. Resist. The impact question is what makes the problem feel urgent. Without it, you’ll often get positive feedback from prospects who never buy.
Not booking the next step before hanging up. Never end with “I’ll send you some information.” That’s not a next step, it’s a soft rejection you’ve just agreed to. Always close on a specific next action: “Based on what you’ve shared, it makes sense to show you how we solve [specific pain]. I have Thursday at 2pm or Friday at 10am - which works better?”
| Deal Size | Discovery Format | Stakeholders | Typical Timeline |
|---|---|---|---|
| Under €10K ACV | One call, 20–30 min | 1–2 decision-makers | 1–3 weeks to close |
| €10K–€50K ACV | One thorough call, 30 min | 2–3, possible follow-up | 3–8 weeks to close |
| €50K+ ACV | 3–4 discovery conversations | Multiple stakeholders mapped separately | 8–20+ weeks to close |
Discovery Calls at Different Deal Sizes
The structure above applies broadly, but the depth varies by deal size.
Under €10K ACV: One discovery call, 20-30 minutes. Move to demo quickly. The buying process is usually simpler, one or two decision-makers, shorter cycle.
€10K-€50K ACV: One thorough discovery call, 30 minutes. Potentially a follow-up stakeholder call before the demo if multiple decision-makers are involved.
€50K+ ACV: Multiple discovery conversations. Map each stakeholder separately. Understand technical, business, and executive buying criteria independently. Discovery here can take 3-4 calls across different stakeholders before you ever show the product.
The bigger the deal, the more discovery work earns its time back. A €120K deal I closed a few years back involved four separate discovery conversations before a single demo slide appeared. That might sound inefficient. In practice, by the time I showed the product I knew exactly what would close the deal and showed only that.
How Discovery Connects to Your Whole Sales Process
Discovery isn’t an isolated step. It’s the foundation everything else is built on:
- What you learn in discovery shapes your demo (show only what’s relevant)
- The pain and impact you uncover shapes your proposal (build the ROI case from what they told you)
- The decision process you mapped shapes your follow-up sequence (know who to keep warm and on what timeline)
- The objections you surface shape how you handle them later (you’re not surprised in the proposal stage)
Founders who skip structured discovery end up improvising at every stage. The ones who run clean discovery calls build a sales process that gets better over time because they’re building it on actual customer intelligence, not guesses.
If you want to sharpen your discovery process or build a repeatable sales motion from what you learn in discovery, let’s talk. I work with B2B SaaS founders at the earliest stages of building a sales function, and discovery is almost always where we start.
Want this run on your pipeline?
€500, 90 minutes. Credited against any Build.