Discovery Framework

Guides sales reps through structured discovery conversations that uncover qualification criteria, quantify pain, and map decision-making processes using real-time question suggestions, qualification scoring, and gap analysis.

Pre-Work Framework

Before a discovery call, establish the context and constraints that will shape your questioning strategy:

1. Who is the prospect? What is their title, span of control, and role in the decision-making process? Are they the economic buyer (controls budget), a technical buyer (evaluates fit), a champion (influences but does not sign off), or an end user (uses but does not buy)? This determines which framework elements to prioritize and whether you need to identify additional stakeholders.

2. What qualification framework should you use? Should you apply MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion), BANT (Budget, Authority, Need, Timeline), SPIN (Situation, Problem, Implication, Need-Payoff), Sandler, or a custom framework specific to your business? MEDDIC is the gold standard for enterprise B2B sales with long cycles and multiple stakeholders. BANT is faster for transactional sales. SPIN is strongest for consultative selling. Confirm the framework before the call.

3. What context do you already have? What have you learned from the cold call, LinkedIn, company research, or previous conversations? What gaps remain? This prevents you from re-asking questions already answered and focuses your discovery on new information.

4. What is the deal stage? Is this an initial discovery call with a new prospect, a deep-dive with a qualified opportunity, or a final validation call before closing? Early-stage discovery prioritizes understanding pain and need. Later-stage discovery prioritizes validating implementation and timeline.

5. Who else should be involved? Do you need to schedule a separate call with the economic buyer, technical buyer, or end users? Or should you ask this prospect for introductions? Identifying this early prevents discovering with the wrong stakeholder.

Core Principles

Discovery Is a Conversation, Not a Checklist

The single greatest discovery mistake is asking a predefined list of questions in order, checking boxes as the prospect answers. This produces surface-level information and prospects who disengage. True discovery is responsive—you ask questions based on what the prospect has told you, not what is on your list. When a prospect mentions a pain point, you dig deeper into that pain (how often does it happen, how is it currently solved, who else does it affect) before moving to the next topic. When they mention a timeline, you explore constraints and dependencies around that timeline. Adaptive questioning signals that you are listening and thinking about their specific situation, not managing a templated call.

Quantify Every Pain Point

Unquantified pain is weak and does not build a business case. A prospect might say "We waste time on manual data entry." Without quantification, that is a vague inconvenience. With quantification, it becomes a business case: "We lose 3 hours per rep per week on manual data entry. With 40 reps, that is 120 hours per week. At fully-loaded cost of $65 per hour, we are spending roughly $312,000 annually on a problem that could be eliminated." Quantified pain justifies budget allocation and urgency. Always push toward numbers—hours per week, number of affected users, financial impact, lost revenue, or customer attrition rate.

Confirm, Don't Assume

As you gather information, track three statuses for each qualification criterion: Confirmed (first-hand evidence), Assumed (indirect signals but no direct statement), or Unknown (no information). Many deals fail because reps assume information they never actually confirmed. An assumed economic buyer is a landmine. An assumed budget is a deal killer. An assumed timeline is a pipeline disaster. When you have a strong signal that something is true but the prospect has not explicitly stated it, ask a confirming question: "Based on what you've shared, it sounds like [statement]. Is that accurate?" This moves assumptions to confirmations and prevents surprises later.

Map the Entire Buying Committee

No deal closes without the economic buyer, no matter how much your champion loves your solution. During discovery, your goal is to understand who else is involved in the decision and what their priorities are. Ask directly: "When it comes to a decision like this, who else typically weighs in? Is it the CFO, the VP of Ops, the IT team?" Then ask about their concerns: "What would be important to [person X] in evaluating this?" This prevents you from being blindsided by an objection from a stakeholder you never spoke to.

Make Discovery About Them, Not About You

The moment you start explaining your product, features, or company, you have stopped discovering. In discovery, your job is to understand their world, not to insert yourself into it. Spend 80% of the call asking and listening. Spend 20% sharing stories or benchmarks that validate their pain or open new possibilities. Never ask "Can I tell you about us?" during discovery. Instead, ask "Before we go deeper, are you curious about how other teams like yours have approached this?" Discovery is their story, not your pitch.

Build a Business Case, Not Just a Need Statement

Prospects have many needs, but not all of them justify budget allocation. As you discover, weave a business case: here is the current state (situation), here is the problem (pain with quantification), here is why it matters (impact on revenue, cost, efficiency, or risk), here are the consequences of inaction (cost of status quo), and here is the opportunity (what becomes possible if solved). A business case justifies urgency and authority. A list of needs does not.

The Process

Phase 1: Set the Stage and Confirm Scope (2–3 minutes)

Begin the discovery call by confirming that the prospect has time and is in the right context to have a substantive conversation. Establish psychological safety so the prospect will be candid about challenges and constraints.

Structure: "Thanks for taking the time. I want to respect your time, so I have about 30 minutes blocked. Is that still good for you?" If yes, continue: "Great. My goal for this call is to understand [topic], so I can determine whether it makes sense to spend more time together. Along the way, I'll ask some questions about your current situation. Sound good?" This frames discovery as exploration, not a pitch, and sets a time boundary that keeps the conversation focused.

Next, confirm scope: "I want to make sure we cover what matters most to you. What's the one thing you'd like to understand better by the end of this call—either about your situation or about how we might help?" This open question shows respect for their priorities and ensures you are not chasing phantom pain points.

Decision point: Does the prospect seem relaxed and engaged, or defensive and rushed? If defensive, you may need to shorten the call or offer to reschedule. If engaged, proceed to pain mapping.

Exit criteria: The prospect has confirmed time availability, you have established psychological safety, and you understand their primary concern or pain point.

Phase 2: Map Current State and Pain Points (5–8 minutes)

Now begin discovering their situation without pitching solutions. Your goal is to understand how they currently operate, what is working, and what is broken.

Structure: Start with a broad situation question: "Walk me through how your team currently handles [process/function]." Listen for the mechanics, the people involved, the tools they use, and where friction appears. As they describe their current state, listen for spontaneous pain mentions (frustration in their voice, statements like "It's a nightmare" or "We waste so much time").

When you hear a pain mention, do not move on. Dig deeper. "You mentioned you waste time on [X]—tell me more about that. How does that typically happen?" Then: "How often does that impact you?" Then: "How much time per week, roughly, would you say?" Then: "Across how many people on your team does that happen?" Each follow-up question adds specificity and quantification.

As you discover, notice gaps. If a prospect mentions a pain but does not mention the impact on revenue or customers, ask it: "When your team loses 3 hours per week on that task, how does it show up in your numbers? Are customers waiting longer, are deals moving slower, are there other consequences?" Quantification connects abstract pain to business impact.

Decision point: Have you mapped at least 2–3 key pain points? Have you quantified the impact of at least one? If the prospect has shared minimal pain, ask directly: "What's currently not working the way you'd like?" or "If you could wave a magic wand and fix one thing about how your team operates, what would it be?"

Exit criteria: You have documented 2–3 specific, quantified pain points. You understand the current state (tools, people, processes). You have identified at least one pain that is tied to business impact (revenue, cost, efficiency, or risk).

Phase 3: Explore the Problem and Buyer Universe (4–5 minutes)

Once pain is established, explore the problem more deeply. Understand the root cause, who else is affected, and what has prevented them from solving it already.

Structure: "You mentioned [pain]. What's the root cause? Is it a process problem, a tooling problem, a skill problem, or something else?" Listen for their diagnosis. Then: "How long has this been an issue?" Then: "What have you tried so far to address it?" This reveals whether they have attempted solutions and why those solutions failed or are insufficient.

Next, understand the scope: "Beyond your team, who else in the organization feels this pain?" This begins identifying stakeholders who will need to be involved in a decision. A CFO discovering that a cost problem affects operations, finance, and HR is opening doors to a larger buying committee.

Then ask about constraints: "What's prevented you from solving this already? Is it budget, bandwidth, competing priorities, or something else?" This reveals constraints and objections you will need to address later. It also shows whether they are actively trying to solve the problem (which increases urgency) or have accepted it (which decreases urgency).

Decision point: Have you understood why they have not solved this already? Do you have a sense of who else is affected? Is this a priority they are actively trying to solve, or a nice-to-have?

Exit criteria: You have diagnosed the root cause, understood scope (who else is affected), and identified constraints. You have a clearer picture of whether this is a problem they are motivated to solve.

Phase 4: Uncover Decision Criteria and Process (4–5 minutes)

Before you propose a solution, understand how they will evaluate whether a solution is right. This is where you shift from pain to decision-making.

Structure: "If you were to solve this problem, what would be important to you in evaluating a solution?" Let them answer freely. They might say "It needs to integrate with Salesforce," "It needs to be easy for the team to adopt," "It needs to cut our costs in half," or "It needs to work with our current processes." Document all of these. Then ask: "Is there anything else?" to ensure you have captured all their criteria.

Next, understand the buying process: "Walk me through how a decision like this would happen in your organization. Is it just your call, or would you need to loop in others?" Let them describe the process, the people involved, the timeline, and any approval steps. Do not interrupt—let them paint the full picture.

As they describe the process, listen for who the economic buyer is (the person who controls budget). If it is not clear, ask directly: "When it comes to budget approval, who makes the final call?" and "Would you need sign-off from [person X] before moving forward?"

Decision point: Have you understood their evaluation criteria? Have you identified the economic buyer? Have you understood the decision process and timeline?

Exit criteria: You have documented their decision criteria (3–5 factors that would make a solution acceptable). You have identified the economic buyer and other stakeholders. You have a rough timeline for how a decision might unfold.

Phase 5: Identify Gaps and Champions (2–3 minutes)

As you near the end of discovery, identify what information is still missing and who might champion your solution internally.

Structure: Ask: "Of everything we've discussed, what feels like the biggest obstacle or concern that would need to be addressed?" This surfaces hidden objections or constraints you have not uncovered yet. Then: "If you were to move forward with exploring a solution, what would that look like? Would you want to involve [person X]? Would you run a pilot first?" This helps you understand the realistic next step.

Finally, assess champion potential: "Of the people you mentioned who would be involved, who would be most motivated to solve this?" This is your entry point to advocate for your solution once you begin engaging with the buying committee.

Decision point: Have you identified the information gaps that remain? Do you have a champion candidate?

Exit criteria: You have surfaced any remaining objections. You have identified a potential champion or stakeholder who has the most to gain from solving this problem.

Phase 6: Propose a Next Step (2 minutes)

End discovery with a clear next step. Do not propose a demo or full presentation yet—propose the smallest next step that moves the deal forward.

Structure: "Based on what you've shared, it sounds like [brief business case summary]. I think it makes sense to explore whether [solution] could work for you. What would that look like?" Offer an option: "We could schedule a brief call with our [relevant expert], or I could put together a short summary of how we've solved similar problems. What feels more useful?"

If they agree, confirm the specific next step, timing, and who should be involved. If they hesitate, ask why: "What's making you hesitant?" This surfaces remaining objections that you need to address in a follow-up.

Exit criteria: You have booked a next step (specific date, time, and participants) or you have a clear reason why they are not ready to move forward.

Anti-Patterns

The Checkbox Discovery

Description: Moving through a predefined list of discovery questions, asking each one in order regardless of prospect responses, and treating answers as boxes to check rather than threads to pull.

Why it's harmful: Checkbox discovery produces surface-level information and disengaged prospects. It signals that you are not listening and do not care about their specific situation. Prospects give short answers and do not open up about real challenges. The information you gather is insufficient to build a business case, and the relationship does not deepen.

Example (BAD): You: "Do you have budget for this?" Prospect: "We have some budget." You: "Great. Is the CFO involved in decisions like this?" Prospect: "Sometimes." You: "Got it. When would you want to implement?" Prospect: "Sometime next year."

Example (GOOD): You: "Budget is something we should understand. Take me through how budget decisions work in your organization. Is there a specific process or approval needed?" Prospect: "It depends. If it is under $50K, my director and I can approve it. Over that, it goes to the CFO." You: "Got it. So for a decision like this, would it likely be under or over $50K?" Prospect: "Probably over." You: "Okay. Has the CFO been open to investments in this area before?" Prospect: "It depends. They would need to see ROI." You: "What kind of ROI would they want to see?" This approach gathers deeper information and reveals constraints and decision criteria.

The Unquantified Pain Trap

Description: Accepting vague, emotional statements of pain without pushing toward numbers, metrics, or business impact. Treating "We're losing time" or "It's frustrating" as sufficient qualification.

Why it's harmful: Unquantified pain does not justify budget or urgency. A prospect who says "We waste time on manual entry" might tolerate that pain forever because they have not connected it to a dollar impact. A business case requires numbers: hours lost, people affected, annual cost, revenue impact, or customer consequence. Without numbers, you cannot justify a purchase price or timeline.

Example (BAD): Prospect: "Our sales process is really slow." You: "Understood. That sounds frustrating. How do you think we might help?" [Moves to next topic without quantifying]

Example (GOOD): Prospect: "Our sales process is really slow." You: "I hear that. Walk me through what slow means. How long does it take from first conversation to close?" Prospect: "Right now, about 6 months for enterprise deals." You: "Six months—is that where you want to be, or is that a problem?" Prospect: "It's longer than we'd like. Our competitors close in 4 months." You: "What does the extra 2 months cost you in terms of—are deals falling off, are you losing to competitors, or is it just lost revenue during those months?" Prospect: "Probably losing 20% of deals we could win if we were faster." You: "20% of enterprise deals—roughly, what does that add up to annually?" Prospect: "Maybe $5 million in lost annual revenue."

Assuming the Economic Buyer

Description: Discovering with a strong champion or influencer but never confirming who controls budget or makes the final decision. Assuming the person you are talking to has more authority than they actually do.

Why it's harmful: You can do perfect discovery, uncover all the pain, align everything with a champion—and then a previously unmet economic buyer kills the deal because they were never involved in conversations or do not see the value. Months of progress evaporate. Additionally, deals stall because budget questions go unanswered or budget holders have different priorities than your champion.

Example (BAD): You spend 4 weeks discovering with the VP of Sales, who loves your solution. You assume she can approve a $200K annual spend. You present to her, she is excited, and she says "Let me get executive alignment and we will be good to go." Two weeks later, she tells you the CFO thinks it is too expensive and wants to wait until next year. Your deal stalls because the CFO was never in the conversation.

Example (GOOD): Early in discovery: "If you want to move forward with this, walk me through the approval process. Who would need to sign off?" Prospect: "I can push it through up to $100K. Anything bigger needs CFO approval." You: "Got it. So if this is a $150K investment, we would need to involve the CFO early. Would that make sense—should we loop them into a call or should we wait until you've validated the approach?" By confirming, you build the right buying committee early.

The Feature Dump During Discovery

Description: Asking discovery questions but then immediately pivoting to pitching features, product capabilities, or explaining your solution before the prospect has had a chance to articulate their priorities.

Why it's harmful: You shift from learning mode to selling mode too early. You stop discovering and start positioning. The prospect gives shorter answers because they are defending against a pitch. You miss nuance. You do not build a business case—you just describe a solution that may or may not match their needs.

Example (BAD): Prospect: "We struggle with sales cycle length." You: "That's actually something we address really well. Our platform has workflow automation, real-time visibility into deals, AI-powered forecasting, and integrations with Salesforce that help teams close faster. Let me show you..." [Launches into product feature overview]

Example (GOOD): Prospect: "We struggle with sales cycle length." You: "Tell me more about that. What's driving the length—is it discovery, procurement, internal approvals, or something else?" Prospect: "A lot of it is visibility. Deals sit in stages too long and reps do not realize they're stalled." You: "Okay, so lack of visibility is causing deals to get stuck. How does that show up? Are deals just waiting, or are they falling off?" Prospect: "Both. Reps are not proactive enough because they do not know a deal is stuck." You: "Got it. Before I talk about how we might help, let me understand the impact. Across your team, how many deals a quarter would you estimate are affected by this?" [Continues discovering impact and decision criteria before positioning]

The Authority Assumption

Description: Never asking whether the person you are talking to is the right decision-maker or whether the decision will require input from others. Assuming that a director, VP, or department head can make a unilateral decision.

Why it's harmful: Not all VPs are economic buyers. Some require CFO approval, CEO approval, or board approval. Some defer to technical teams. You spend time discovering with someone who cannot sign off. Then you are blocked or your deal stalls because you did not map the actual decision-making power early.

Example (BAD): You discover with a Head of Sales, build great rapport, align on pain, and near the end of the call, she says "Great. Let me review this with the CFO and get back to you." You realize she was never going to make the decision unilaterally.

Example (GOOD): Early in discovery: "Who all would be involved in evaluating a solution like this?" Prospect: "My team, definitely. Probably IT because of integrations. And if it is a significant spend, our CFO." You: "What would be a significant spend from their perspective?" Prospect: "Anything over $50K annually." You: "Got it. So if this is a $60K decision, we should involve the CFO. When would make sense to loop them in?" By confirming, you build the right audience from the start.

Discovering Without a Framework

Description: Asking discovery questions without anchoring to a structured qualification framework. Each call is unorganized, relies on intuition, and produces different information depending on the rep.

Why it's harmful: Without a framework, discovery is inconsistent. One rep discovers MEDDIC elements, another discovers BANT elements. Different reps focus on different criteria. Scoring deals becomes subjective. You cannot accurately forecast because qualification criteria differ across reps. Teams with organized discovery (MEDDIC, BANT, SPIN) close higher percentages and have better visibility.

Example (BAD): Reps ask whatever comes to mind, resulting in inconsistent discovery depth and uneven qualification.

Example (GOOD): Implement MEDDIC across the team. Every discovery call maps to the same six criteria: Metrics (how will success be measured), Economic Buyer (who controls budget), Decision Criteria (what makes a solution acceptable), Decision Process (how will they decide), Identify Pain (what is broken), Champion (who will advocate internally). Every rep scores each element as Confirmed, Assumed, or Unknown. Forecasting is consistent and accurate.

Output Format

After a discovery call, this skill produces a structured summary with the following components:

Discovery Summary:

• Prospect name, title, company, date of call
• Current situation: Operating model, tools, people, processes
• Pain points (with quantification):
  • Pain #1: [Description] — Impact: [Quantified impact]
  • Pain #2: [Description] — Impact: [Quantified impact]
• Decision criteria: 3–5 factors that would make a solution acceptable
• Buying committee: [Economic buyer], [Technical buyer], [Champion], [Other stakeholders]
• Timeline: Realistic decision timing based on their process
• Qualification scorecard (using chosen framework):

  Criterion	Status	Notes
  Metrics	Confirmed/Assumed/Unknown	[Details]
  Economic Buyer	Confirmed/Assumed/Unknown	[Details]
  [Additional criteria]	Status	[Details]

• Gaps: Information still needed to qualify or advance the deal
• Next steps: Specific meeting or deliverable with date and participants
• Champion assessment: Who is most likely to advocate internally?

Task-Specific Questions

When Preparing for a Discovery Call

• Which framework will you use to guide the conversation (MEDDIC, BANT, SPIN, custom)?
• What context do you already have about this prospect (from cold call, LinkedIn, company research)?
• Which 2–3 pain points are you hypothesizing they might have, and which questions will you ask to explore them?
• Who do you expect to be the economic buyer, and are you prepared to ask about the full buying committee?
• What is the realistic next step you are hoping to achieve—discovery of additional pain, validation of a pain, introduction to a stakeholder, or agreement to a demo?

When Analyzing a Completed Discovery Call

• Did you ask about current state and pain first, or did you pitch solutions too early?
• For each pain mentioned, did you push toward quantification (hours, cost, revenue impact)?
• Did you confirm the economic buyer and map the full buying committee?
• Did you understand their decision criteria and decision process?
• Did you end with a specific next step (date, time, participants) or a vague "I'll follow up"?
• Using your chosen framework, what is the status (Confirmed/Assumed/Unknown) for each criterion?

When Qualifying or Disqualifying Deals

• Is the economic buyer confirmed and engaged, or are you assuming authority?
• Has pain been quantified, or is it still vague?
• Do they have budget authority or a realistic path to budget?
• Is the timeline realistic, or are they a perpetual "let me think about it"?
• Have you identified a champion who will advocate internally, or is buying committee adoption uncertain?

Quality Checklist

Before, during, or after using this skill, verify the following:

1. Framework alignment: You selected a qualification framework (MEDDIC, BANT, SPIN) and anchored the call to that framework. Every question serves that framework.

2. Pain quantification: For at least one pain point, you pushed toward numbers—hours per week, financial impact, number of affected people, or revenue consequence.

3. Economic buyer identified: You confirmed (not assumed) who controls budget and whether they need to be involved in this stage of the deal.

4. Decision criteria documented: You asked "What would be important to you in evaluating a solution?" and documented 3–5 specific criteria (not vague things like "ease of use").

5. Buying committee mapped: You asked "Who else would be involved in a decision like this?" and identified the technical buyer, economic buyer, champion, and end users.

6. Listening ratio: You estimate you talked 30–40% of the time and listened 60–70%. If you talked more, you pitched instead of discovering.

7. Discovery first, positioning later: You did not pitch your product during discovery. You only asked about their world until Phase 5.

8. Clear next step: The call ended with a specific next step (meeting date/time, deliverable, introduction) or a clear reason why they are not ready to move forward.

9. Framework scorecard complete: For each criterion in your chosen framework, you assigned a status: Confirmed (first-hand evidence), Assumed (indirect signal), or Unknown (no information yet).

10. Gaps identified: You documented what information is still missing and what question or conversation will fill that gap.

Related Skills

• Cold Calling Mastery — Tactics for reaching prospects and earning the right to a discovery conversation.
• Objection Handling — Strategies for handling objections that appear during discovery (timeline, budget, internal alignment concerns).
• Deal Qualification — Criteria and frameworks for determining whether a qualified opportunity is worth pursuing or should be disqualified.
• Demo Scripting — Structuring a product demonstration that addresses the decision criteria uncovered during discovery.

Example Prompts

• "Help me structure a discovery call for a prospect in the enterprise SaaS space. I want to use MEDDIC. What questions should I ask first?"
• "I'm discovering with a champion but I'm not sure who the economic buyer is. Give me a script for asking directly without damaging rapport."
• "What's the next question I should ask? The prospect just told me they lose 2 hours per rep per week on data entry."
• "Score this discovery call transcript using MEDDIC. Which criteria are confirmed, assumed, or unknown?"
• "I think I have a deal, but I'm not certain about the timeline. What questions should I ask to validate whether it's really Q2 or whether it's actually Q4?"
• "Help me map the full buying committee. I've talked to the VP of Operations, but I need to understand who else influences this decision and what their concerns are."