The Founder's Guide to Discovery Calls That Actually Convert

TL;DR: Great discovery calls follow a 5-question framework: situation, problem, impact, desired outcome, and timeline. Stop pitching on call one — diagnose first, prescribe second. This framework doubled conversion rates for B2B SaaS founders.

The Call That Changed How I Sell

Early in my sales career at Noldus Information Technology, I had a discovery call with a university research lab. I was excited about our behavioral analysis software and spent 35 minutes showing them everything it could do. The professor was polite, asked a couple of questions, and said she'd "discuss it with her team." I never heard from her again.

Three weeks later, my colleague had a call with a similar lab. He spent the first 25 minutes asking questions. When he finally showed the product, he only demoed two features — the exact two that solved their specific workflow problem. They signed within a week.

Same product. Same type of buyer. Radically different outcome. The difference was discovery.

The 60/40 Rule

On your best sales calls, the prospect should be talking 60% of the time and you 40%. On your average calls, it's probably the reverse. I've listened to hundreds of recorded sales calls from the founders I advise, and the pattern is almost universal: the more the founder talks, the less likely the deal closes.

This isn't about being quiet. It's about being strategically curious. Every minute the prospect talks is a minute they're revealing buying signals, pain points, and objections you'll need to address later.

Set the Frame in the First 90 Seconds

The opening of your discovery call determines everything that follows. If you don't set expectations, the prospect will default to expecting a pitch — and they'll be guarded.

Here's what I coach founders to say: "Thanks for making time today. Before I show you anything, 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?"

This does three things simultaneously: it positions you as a consultant rather than a vendor, it gives you explicit permission to ask probing questions, and it sets up the demo as a natural next step rather than a separate meeting.

Layer 1: Situation Questions (5 Minutes)

Start broad and low-threat. You're mapping the landscape:

"Walk me through how your team currently handles [area your product addresses]."

"What tools or processes are you using today?"

"How big is the team involved in this?"

"How long have you been doing it this way?"

Don't rush this phase. The context you build here makes every subsequent question sharper. If you skip straight to pain questions, you'll sound like a doctor who prescribes medicine before taking your temperature.

Layer 2: Pain Questions (10 Minutes)

Now go deeper. You're looking for problems they feel emotionally, not just logically:

"What's the most frustrating part of that process?"

"If you could change one thing about how this works today, what would it be?"

"When the current process breaks down, what happens?"

"How much time does your team spend on [painful activity] per week?"

The critical skill here is quantifying the pain. "That sounds frustrating" is empathetic but doesn't build a business case. "So your team spends roughly 12 hours a week on manual data entry — at your average salary, that's about €30K per year in labor cost?" That's a number your prospect can take to their CFO. This quantification is also what powers value-based pricing later in your sales process.

Layer 3: Impact Questions (5 Minutes)

Impact questions are the secret weapon most founders skip. They transform a current inconvenience into an urgent problem:

"If you don't solve this in the next 6 months, what happens to [their goal]?"

"How does this affect the team's ability to hit their quarterly targets?"

"Who else in the organization feels the impact of this?"

These questions do your selling for you. When a prospect articulates the cost of inaction out loud, they're essentially writing the justification for buying your solution. They leave the call not just understanding the problem — feeling the urgency to fix it.

Layer 4: Decision Process (5 Minutes)

Before you end, map the buying process:

"Besides yourself, who else would be involved in evaluating a solution like this?"

"What does the decision-making process typically look like at your company?"

"What's your timeline for having something in place?"

"Have you evaluated other solutions? What did you like or not like about them?"

This information is gold. It tells you exactly what needs to happen for this deal to close and who you need to influence. It's also essential context for when you move into the demo phase.

The Close: Always Book the Next Step

Never, ever end a discovery call with "I'll send you some information." That's not a next step — it's a dead end. Instead: "Based on what you've shared, I think it makes sense for me to show you specifically how we solve [their top pain]. I have availability Thursday at 2pm or Friday at 10am — which works better?"

Specific. Concrete. Easy to say yes to.

Discovery is the foundation of every deal. Master it, and the rest of your sales process becomes dramatically easier. Want help refining your discovery framework? Book a free sales audit.