The Problem With Most Discovery Call Prep
You block 30 minutes on your calendar for a discovery call. You have 15 minutes to prepare before the meeting starts. You Google the company, glance at their LinkedIn, and pull up your CRM. Maybe you jot down three questions. Then the calendar reminder hits and you're live.
Some calls go great. Some fall flat. And you're never quite sure why.
The reps who consistently run good discovery calls aren't just naturally better. They're running a system. They know what to prep, in what order, and how deep to go. That system compresses all the random ad-hoc research into a focused 20-minute prep cycle that gets the job done.
Here's the framework that works.
The Three-Layer Discovery Prep Framework
Think of discovery prep as three concentric layers: company, individual, and conversation strategy. You work from the outside in.
Layer 1: Company Context (5 minutes)
Start with what you can learn fast about their business. You're not reading their entire investor deck. You're getting enough context to sound credible and ask smart questions.
Pull up their website. You're looking for:
- What they do (one sentence)
- Who they sell to (industry, company size)
- Recent announcements or news (funding, product launches, acquisitions)
- Obvious business problems from their website messaging
Then check LinkedIn company page. Look at: recent hires (what functions are they growing), employee count growth (are they scaling fast), recent posts (what are they talking about publicly).
One search on your industry news source. If they're mid-market or above, there's likely something recent. One acquisition announcement or product launch tells you what direction they're heading.
Five minutes maximum. You're not digging deep. You're building a frame.
Layer 2: Individual Context (5 minutes)
Now look at the person you're talking to.
LinkedIn: Read their last 2-3 posts and their about section. You're figuring out: what are they focused on, how long have they been in this role, who are they connected to internally.
Recent email history (if your email is connected to CRM): Skim their last 3-4 emails to you. What pain points did they mention? What projects were they asking about?
Your CRM notes: This is critical if you've talked before. What did they care about last time? What did they commit to? Did they follow up the way they said they would?
You're building a sense of who this person is, what matters to them, and what their last interaction with you or your company looked like.
Five minutes. Don't read their entire LinkedIn history.
Layer 3: Call Strategy (10 minutes)
This is where prep transitions from research to planning.
Start with your discovery call objective. What do you need to learn to move this deal forward? This isn't vague. It's specific:
"I need to understand their current vendor situation and the timeline for a decision."
"I need to find out who else has a say in this and whether procurement is involved."
"I need to understand what problems they're having with their current solution and which one is most painful."
One clear objective. Everything else flows from that.
Then, build your question architecture. You're not winging this. You know roughly where you're going.
Open question: How are they using whatever solution you sell into right now? (If they don't use one, it's "How are you handling X process right now?")
Discovery questions: Based on what they said, dig into the ones that matter to your objective. If your goal is to understand their decision timeline, discovery questions focus there. If your goal is to map stakeholders, ask about who's involved in decisions.
Confirmation: At the end, confirm what you learned against your objective. "So it sounds like timeline is your biggest constraint. Am I understanding that right?"
Write these questions down. Not word-for-word (that sounds scripted and bad). But bullets that anchor your thinking.
Then, anticipate one objection or obstacle. If they're currently using a solution and they're happy with it, how will you probe there without sounding like you're attacking their choice? If they don't have budget, how will you uncover whether it's a real constraint or a stalling tactic?
One anticipated objection. You don't need to memorize a response. You just need to have thought through the pivot.
The Pre-Call Checklist
The night before (or 15 minutes before if you're scheduling tightly):
- Company context research done. You can speak credibly about their business.
- Individual context loaded. You know who you're talking to and what they care about.
- Call objective written down. One sentence.
- Three to five discovery questions drafted (bullets, not word-for-word).
- One anticipated objection thought through.
- Calendar is clear for 35 minutes (5 minutes over the call time for notes).
- You have a pen and paper or your CRM notes open.
That's it. You don't need to memorize this. You just need to have done the thinking.
The Specific Discovery Call Frameworks
Every discovery call follows one of these patterns. Knowing which one you're running saves time and keeps you organized.
The Situation-Complication-Implication Framework
This is for prospects who already know they have a problem.
Situation: "So you're using [current solution]. Tell me how that's working for you."
Complication: "When you say it's slow, what does that cost you? How often does that slow-down happen?"
Implication: "So if we could cut that down by 50%, what would that unlock for you?"
You're not selling. You're connecting their situation to the impact it has. The implication is where they start to feel the weight of their problem.
The Three-Circle Framework
Use this when the prospect doesn't know they have a problem yet, or when they're early stage and exploring.
Circle 1: What are you using now? How is it working? (Current state)
Circle 2: What would ideal look like? What would be better? (Future state)
Circle 3: What's the gap? Why isn't that happening now? (The problem)
You're not telling them the gap. You're helping them see it. "You're saying ideal is X and you're doing Y. What's keeping you from going from Y to X?"
The Stakeholder Mapping Framework
Use this when you know the problem but you need to understand who's involved in the decision.
Start with the person you're talking to: "In this situation, who else would have a say?" Then go down the layers: economic buyer (who controls the money), technical buyer (who has to implement it), user buyer (who uses it), and champion (who's pushing for a solution).
You don't grill them. You ask: "Who would you loop in if you decided to move forward?"
When Your Prep Falls Short
Real talk: Sometimes you're calling with minimal prep. You got a referral five minutes before the call. The prospect surprised you with a call at 2pm and you jumped on it. Your prep was 60 seconds of skimming their LinkedIn.
That's okay. Most discovery calls can work with minimal prep because you're not supposed to be the expert in the room. They are.
Here's what you do: Be honest about your knowledge. "I pulled up your company page but I haven't had time to get deep. Help me understand your business."
Then follow one of the frameworks above. The framework carries you. You don't need perfect prep to run a good discovery call. You need a structure.
This is the kind of real-time guidance that next-generation coaching tools are being built to provide. Cinder, for example, is designed to surface relevant context and coaching during live calls -- so even when your prep falls short, you have support in the moment. Cinder is launching soon, and you can sign up for early access at getcinder.ai.
The Prep-to-Call Bridge
The moment before you click join on the video call:
Take one breath. Look at your call objective. Ask yourself: "What is the one thing I need to learn today?"
Then go in. The prep is done. Now it's about listening.
The reps who run the best discovery calls aren't the ones who memorize the most facts about the prospect. They're the ones who do focused prep, then let the conversation breathe. They ask good questions and they listen. They follow the framework lightly, not rigidly.
Prep gets you ready. But the call itself is where discovery happens.
Saving Time on Discovery Prep
If you're running 8-10 discovery calls a week, prep adds up. You don't have 20 minutes per call.
Here's how to compress it:
- Save time on company research by using 2-3 trusted sources (Crunchbase, LinkedIn, your industry news source). Don't Google randomly.
- Use CRM to its fullest. If you're entering call notes, you don't have to re-discover the same things next call.
- Pre-write your frameworks once and reuse them. Don't invent new questions for every call.
- Batch research. Set aside 15 minutes Monday morning to pull context on all your week's calls at once.
The goal isn't to become a researcher. The goal is to have enough context to ask smart questions and listen well.
What Really Makes Discovery Calls Work
Great discovery calls have one thing in common: the rep is genuinely curious and genuinely prepared.
Your prep signals that you care. It also builds the confidence you need to listen instead of selling. When you know your objective and your questions are drafted, you're not white-knuckling. You're asking, listening, learning.
That's when discovery works. That's when you actually qualify. That's when you set up the next stage with clarity instead of hope.
Prep doesn't have to be perfect. But it has to be done.
Cinder is a real-time coaching tool for sales reps, launching soon. Sign up for early access at getcinder.ai.