The Art of the Discovery Call: How to Turn Conversations Into Customers

The name says it all: discovery call. Not demo call. Not pitch call. Discovery.

The purpose of a discovery call is not to show your product. It's to understand whether this person has the problem you solve, how much it costs them, and whether they're the right person to buy a solution.

The Wrong Way to Run a Discovery Call

The default founder approach:

• 2 minutes of small talk
• 20 minutes of demo
• 5 minutes of questions
• "So, what do you think?"

The problem: you've done all the talking. You've learned almost nothing about whether this person is actually a fit for your product. You've committed them to an opinion before they've told you their situation.

The Right Framework

The 4-part discovery call structure that converts better:

Part 1: Context (10 minutes) Let them talk. Ask:

• "Before I show anything, help me understand your current situation. What does [relevant process] look like for you today?"
• "What prompted you to take this call?"
• "What would a successful outcome look like for you?"

Listen. Take notes. Don't interrupt to pitch.

Part 2: Pain (10 minutes) Dig into the problem:

• "When [problem situation] happens, what's the impact on you/your team/your business?"
• "How are you solving it today?"
• "What doesn't work about that?"

The goal: get them to articulate the cost of the problem in their own words. This is more persuasive to them than anything you could say about your product.

Part 3: Solution (15 minutes) Now you show the product. But frame it as a response to what they told you:

• "Based on what you described, here's the part of [product] that's most relevant to your situation..."
• Only show features relevant to their specific pain points

Part 4: Next Steps (5 minutes) Close to a concrete next step, not "let's stay in touch."

• "Based on what we talked about, does it make sense to do a trial/pilot?"
• "What would you need to see to feel confident moving forward?"

The Signals to Watch For

Strong buying signals:

• They ask about pricing before you bring it up
• They ask "when can I start?"
• They describe how they'd use your product in detail
• They ask about integrations with their existing stack

Weak signals that look strong but aren't:

• "This is really interesting"
• "We should loop in our team"
• "Let me think about it and get back to you"

Move fast on strong signals. Get specific on weak ones ("What specifically do you need to think through?")

---

FounderSequence coaches founders through their early sales conversations. Apply here →