Mastering Discovery
Estimated reading time: 11 minutes
Discovery is the heart and soul of sales. Deals are won because of great discovery and lost through poor discovery.
Most founders struggle with discovery because they rush toward the product. They ask questions to qualify the prospect, wait for an opening to pitch, and treat the Demo as the part that actually wins the deal.
I often explain discovery using the analogy of a puzzle. Every time a prospect answers a question, they hand you another piece. As you gather enough pieces, the picture becomes clear: what they care about, what their challenges are, what is driving the decision, and how to sell them. Without enough pieces, you don’t know what you’re looking at, so you end up guessing at how to close the deal.
Discovery is where you understand the prospect’s world, uncover what they care about, build the emotional foundation for the purchase, and determine whether there is a deal worth pursuing.
This article breaks down how to run Discovery Calls that build trust, create excitement, uncover the information you need, and move the deal forward.
What Is a Discovery Call?
A Discovery Call is a conversation designed to understand the prospect’s current situation, challenges, goals, and motivations. Unlike a pitch, the focus is on asking questions, listening, and understanding their world before presenting your solution.
Where Discovery Starts
The Discovery Call is typically the first scheduled call that you’ll have with your prospect and is the foundation for your sales process. Scheduling this call is the primary goal of your prospecting activity.
Note: The Discovery Call starts the Discovery Process. But it doesn’t end there. Discovery should continue throughout every stage of the sales process until the deal is closed.
Discovery Call vs. Demo Call
The Discovery Call is where you establish your understanding. The Demo Call is where you continue discovery while showing how you can help.
Establish your understanding.
- Understand the prospect’s world
- Ask questions and listen
- Uncover problems, goals, and motivations
- Determine whether there is mutual fit
- Establish what needs to be explored next
Show how you can help.
- Connect the product to what you discovered
- Prove value in the prospect’s context
- Continue discovery as new information emerges
- Ask questions throughout the demonstration
- Deepen your understanding
Note: I usually recommend separating the Discovery Call and Demo Call.
Why Most Founders Struggle with Discovery
There are three pillars of sales performance: mindset, behavior, and skill. Mindset is the most important. Below are the common mindset issues that hold founders back while doing discovery.
Their Product-First Mindset
Founders start companies to build things, not to sell them. And many carry the belief that a great product will sell itself. That if you build something genuinely better than what exists, customers will find it, recognize its value, and buy it.
This is almost never true in B2B SaaS. Most of B2B SaaS is sold, not bought. And that has never been more true as the barrier to entry continues to drop and the market floods with good products. GTM strategy and sales execution are what separate winners from everyone else. The best product without great selling loses to an average product with great selling, consistently.
The Product-First Mindset is dangerous in discovery because it heavily colors how founders run calls. If you believe the product is what closes deals, then your demo becomes by far the most important part of your sales process. And discovery becomes an obstacle between you and it. So founders rush through discovery, spending most of it asking feature-related or qualification questions.
They skip vision, dreaming, pain, and excitement entirely because those things feel soft and unrelated to whether the prospect will buy. Instead they ask about integrations, user counts, and the prospect’s timeline. Then they wonder why prospects ghost them after the demo.
The subtler problem is that founders assume prospects share their Product-First Mindset. This isn’t just founders projecting their own product obsession onto prospects. It’s that most founders simply don’t understand how buying decisions are actually made. So they race to the demo because they genuinely believe that they’ll lose the prospect if they don’t. The opposite is true.
Because people buy emotionally and justify logically afterward. Discovery is where that emotional foundation gets built through vision, understanding their world deeply, and making them feel genuinely heard. The demo is where you prove you can deliver on, and tie your solution directly to, what you discovered. Founders who understand this stop seeing discovery as a blocker and start seeing it as the most crucial part of winning the deal.
They Make It About Themselves, Not the Prospect
The pattern I see on almost every founder’s early discovery calls: the prospect is talking while the founder is mentally three steps ahead mapping what they just heard to a feature, preparing their response, waiting for their turn to speak. They’re not in the prospect’s world, they’re in their own.
This is why their talk ratios are often inverted with the founders doing the vast majority of the talking. It should be the prospect speaking 70% of the time. Usually it’s the opposite. What are they discovering?
This self-focus drives the instinct to pitch the moment an opportunity presents itself. A prospect mentions a pain point and the founder pounces. The problem is that pitching ends discovery. The second you shift from asking to telling, you’ve taken the conversation out of the prospect’s world and put it firmly back in yours. And this is almost certainly done before the founder has the full picture.
The fix is deceptively simple and genuinely hard to execute. Every question you ask, every response you give, should be oriented around one thing: understanding their world more deeply. Not demonstrating your competency or knowledge or connecting it to your great product. Just understanding their world. The prospect should always leave a discovery call feeling like the entire conversation was about them.
Discovery Call Goals
A strong Discovery Call should build trust, deepen your understanding, create interest, establish fit, and secure a clear next step.
Build Rapport
Establish trust and connection so the prospect feels comfortable sharing their real challenges openly. People buy from people they trust. That trust starts with rapport. Without it, prospects stay guarded and only share surface-level information.
Understand Their Situation
Understand their vision, current situation, needs, goals, and pain points. Go beyond surface-level answers to uncover the root causes of their challenges.
Cultivate Excitement and Curiosity
Help the prospect envision what becomes possible if they work with you. Generate genuine interest in the positive impact your solution could have on them and their organization.
Qualify or Disqualify
Determine whether there is mutual fit and whether the opportunity is worth pursuing. Your qualification criteria should not be a generic checklist. They should reflect your product, buyer, and sales process.
Schedule the Next Step
Secure a scheduled follow-up while momentum and interest are high. The easiest time to set next steps is while you’re on the call. In SaaS, the next step is typically a Demo Call. However, it could also be a technical call, stakeholder meeting, or proposal discussion.
Qualification Frameworks
Qualification frameworks help you determine whether a prospect is worth pursuing. Each framework has its own strengths and weaknesses. The key is finding one that fits your product, buyer, and sales process. This matters because the wrong framework can cause you to disqualify strong prospects or waste time on weak ones.
Use Frameworks as a Starting Point
If you’re new to qualification frameworks, BANT is a helpful starting point for understanding some of the key things you need to consider. BANT is perhaps the most well-known qualification framework because it is straightforward and intuitive.
Understanding BANT
BANT is helpful when the buyer already understands the problem, has begun forming a buying process, and may already have budget and timing in mind.
It is less useful for complex sales that involve multiple stakeholders, technical requirements, decision criteria, organizational change, and a longer buying process.
Qualification for Disruptive & Emerging Products
BANT and other traditional qualification frameworks often break down when you are selling a disruptive or emerging product.
I’ve never been able to use BANT in my career because I’ve only sold products where prospects were often unaware of our solution and often not even consciously aware that their problem existed. That meant there was often no planned or approved budget and very little urgency initially. Under BANT, many strong prospects would have been disqualified.
That is also true for many of the founders I coach and advise. They are not selling into existing demand. They are creating it.
Standard Qualification vs. Emerging Products
Assumes an Existing Buying Process
- Approved or planned budget
- Defined urgency
- A known solution category
- An active purchasing timeline
The Seller May Need to Create the Buying Process
- No budget may have been allocated
- Urgency may need to be developed
- The solution category may be unfamiliar
- No defined purchasing timeline
Create a Qualification Framework That Fits
Existing frameworks should be used as inspiration, not followed blindly. Your qualification criteria should reflect your product, buyer, and sales process.
When I joined Together, an enterprise mentorship software company, my Sales Team was using BANT. If they had followed it strictly, they would have disqualified too many strong prospects based on their lack of approved budget and timeline. Because the framework did not fit our sales motion, the team largely stopped using it and began under-qualifying prospects instead.
That is the risk of using the wrong framework. Follow it too rigidly and you disqualify strong prospects. Ignore it entirely and weak deals remain in your pipeline.
I solved this qualification problem by replacing BANT with a set of Sales Qualified Lead (SQL) criteria tailored to our product, buyers, and sales process.
Sales Qualified Lead Framework
Here are some of the qualification criteria we used.
Company / Organization Size
> 500 employees
We had decided to focus only on serving enterprise customers.
Number of Users
> 50 users
Our lower-tier plan included 50 users.
Timeline
< 6 months
Timeline for either purchasing or launching their mentorship program.
Budget
> $XX,XXX or strong ability to secure it
Qualification was usually based on their ability to secure budget, rather than already having approval.
Common Discovery Call Mistakes
Most Discovery Calls fail for predictable reasons. The following mistakes weaken trust, shift the conversation into the seller’s world, or prevent discovery from continuing throughout the deal.
Too Many Seller-Centric Questions
Many Discovery Calls fail because they prioritize the seller’s qualification needs over genuine exploration of the prospect’s world.
Strong Discovery Calls help prospects articulate their challenges, clarify what they want, and explore why solving the problem matters. Weak Discovery Calls just extract information.
Qualification matters, and you eventually need to understand things like budget, authority, and timing. However, when those questions dominate discovery, or come before you understand the prospect’s situation, you are extracting information instead of building understanding.
Prospects resist seller-centric questions because they feel interrogated rather than understood.
Seller-Centric vs. Prospect-Centric Questions
“What’s your timeline?”
Serves the seller’s pipeline management.
“Do you have budget?”
Serves the seller’s qualification needs.
“Who approves purchases?”
Serves the seller’s process efficiency.
“What would success look like for you?”
Helps the prospect clarify their vision.
“What challenges are you facing?”
Helps the prospect articulate the problem.
“What excites you about solving this?”
Helps the prospect explore their motivation.
The “Book a Demo” CTA Problem
Many SaaS companies have a “Book a Demo” button on their website but then run a Discovery Call instead.
This creates a trust deficit before you have said a word. The prospect arrives expecting a demo. Instead, you begin asking questions about their situation, challenges, and timeline. From their perspective, it feels like a bait-and-switch.
This mismatch undermines the entire discovery dynamic. The prospect becomes impatient and guarded, wondering when you will get to what they actually came for. It is difficult to build rapport with someone who already feels misled.
It is also bad for the founder. Founders often resist separating discovery and demo because they can feel the misalignment coming. They anticipate the prospect becoming impatient, rush through discovery, and show the product too early.
Match the CTA to the Experience
Book a Demo
Promises the prospect a product demonstration.
Book a Call
Sets the expectation for a conversation, not an immediate product demo.
Treating Discovery Like a One-Time Event
A common mistake in B2B SaaS is treating the Discovery Call as the beginning and end of the Discovery Process.
The initial call gives you the first meaningful pieces of the puzzle, but discovery should continue throughout the sales process until the deal is closed.
New stakeholders, technical requirements, objections, and internal decision dynamics will surface as the deal progresses.
Discovery is a journey, not a destination.
Where Discovery Continues
