ProjekinAja. Founder's Playbook Stage 4 · GTM & Sales Lesson 4.4
● Stage 4 · Lesson 4.4

The Discovery Call — Learning While Selling

The best discovery call ends with you knowing more about the customer than they expected anyone to ask — and with them feeling heard, not pitched.

⏱ ~22 min read 🎯 B2B enterprise sales 🔬 MEDDIC framework

🎯 By the end you'll understand

How to structure a 45-minute enterprise discovery call from pre-call research through explicit next step — including the MEDDIC qualification framework (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion), what each question is actually trying to reveal, how to test your value hypothesis without pitching, and — critically — how to qualify out gracefully when the prospect cannot buy. You will also understand the single most expensive mistake founders make: demoing before qualifying.

KEY INSIGHTA discovery call is an intelligence operation, not a pitch

The founder who spends 30 minutes demoing to a prospect who has no budget authority, no active pain, and a 12-month decision freeze has not sold anything — they have given a free product tour to someone who cannot buy. Qualification is not gatekeeping. It is respect for both sides' time.

Most technical founders enter a discovery call thinking: "I need to convince this person my product is great." This is exactly backwards. The job is to gather enough information to answer one question: is this a real deal, and if so, what does it take to close it? Everything else — the demo, the proposal, the case studies — comes after. Discovery that skips qualification wastes everyone's time and pollutes your pipeline with phantom opportunities that evaporate at procurement.

🔑 The information asymmetry flip

A prospect comes into a discovery call with significant information asymmetry — they know their organization, their budget cycle, their internal politics, and their real priorities. You know almost none of this. Your goal is to flip that asymmetry by the end of the call. A good discovery call extracts: the specific metric they are measured on, who controls the budget, what they have tried before and why it failed, who else is involved in the decision, and whether the pain is urgent enough to fund a solution this quarter. If you leave the call without those answers, you have not done discovery — you have done a chat.

HOW IT WORKSThe anatomy of a 45-minute discovery call

Discovery calls have a predictable structure that mirrors the prospect's comfort curve — you earn the right to deeper questions by establishing credibility and genuine curiosity first. Here is how a well-run B2B enterprise discovery call unfolds for a product like Forge.

1

Pre-call research (15 min before) — do not skip this

Before you dial in: look at the company's recent news (audit failures, quality recalls, expansion announcements), the prospect's LinkedIn (their tenure, prior roles, what they care about publicly), any analyst reports on their industry segment, and — if you have it — the trigger event that made them pick up the phone (the inbound form, the cold email that landed, the referral path). The trigger event tells you what pain surface is hot. Write one hypothesis: "I believe their most urgent pain is X, caused by Y, and they are probably currently managing it by doing Z." You will test this hypothesis on the call. Arriving without a hypothesis means you will ask generic questions and get generic answers.

2

Opening frame (0–5 min) — set the agenda explicitly

Start by naming what the call is for and what the prospect will get out of it. "I have 45 minutes with you. What I'd like to do is spend the first 30 understanding your situation so I can tell you honestly whether what we've built is actually relevant — and if it is, we can look at it together in the back 15. Does that work for you?" This accomplishes three things: it signals you are not going to pitch them for 45 minutes, it establishes you as someone who qualifies rather than just sells, and it sets an expectation that the demo is conditional on fit. Prospects respect this. They have sat through too many unsolicited demos.

3

Situation and pain discovery (5–20 min) — open questions only

This is where MEDDIC qualification lives. You are asking open questions about their world — not leading questions about your product. The classic mistake is asking "do you struggle with quality escapes?" (yes/no, leading, confirms your hypothesis) instead of "walk me through what happens at your facility when an inspection misses a defect and it reaches the customer" (open, forces them to describe their actual experience). Past behavior, not future opinion. Specific dollar figures, not vague severity ratings. This mirrors the discovery interview discipline from Stage 1 — selling and learning are not separate activities at this stage of a company.

4

Value hypothesis test (20–30 min) — describe the outcome, not the product

Once you have their situation clearly, test your value hypothesis before showing anything. "Based on what you've described — you're tracking about 3–4 quality escapes per month at roughly $45K per event — you're absorbing around $400K–$540K in direct costs quarterly, not counting the audit risk. We've seen manufacturers in your position cut that by 60–80% in the first 90 days. Does that resonate with what you're hoping to solve, or is the priority actually somewhere else?" This does two things: it shows you listened, and it gives them an easy exit if your framing is wrong. If they say "actually, our bigger problem is audit readiness, not the cost of escapes," you just learned something more important than any demo would have revealed.

5

Conditional demo (30–40 min) — only if qualified

If MEDDIC qualification is passing — pain is real and urgent, you have identified the Economic Buyer, decision process is clear, timeline is live — now show the product. But do not give a generic tour. Show exactly the workflow they just described to you. "You mentioned the inspector tags a defect and it goes into a spreadsheet that operations reviews on Friday — here's exactly how Forge fits into that." Custom demos for qualified prospects. No demo for unqualified ones.

6

Explicit next step (40–45 min) — never leave with "I'll follow up"

Every discovery call must end with a specific, time-bound, mutually committed next step. Not "let me send you some materials." Not "let's reconnect in a few weeks." A specific action: "Can we put 30 minutes on the calendar Thursday to walk through this with your VP Ops? I'll send a one-page summary of what we covered today and what questions I'd want to answer in that session — does that make sense?" If they cannot commit to a specific next step, the deal is probably not real. That is also useful information — better to know now than after three more calls.

Open 0–5 min MEDDIC 5–20 min Hypothesis 20–30 min Demo 30–40 min Next Step 40–45 min frame qualify test if fit commit
The 45-minute discovery call structure. Demo is gated behind qualification — if MEDDIC gaps are too wide, skip the demo and schedule a second call after the missing information is gathered.

CORE CONCEPTMEDDIC — the six questions that decide whether a deal is real

MEDDIC originated at PTC in the 1990s and has been validated across thousands of B2B enterprise deals. It stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. Each letter is a category of information you must extract from a discovery conversation to assess whether the deal is real. Missing any one of them introduces a specific, well-documented failure mode.

Letter What you are asking Forge example question What missing this costs you
M — Metrics What does success look like in their numbers? What is the economic value of solving this problem? "How do you measure the cost of a quality escape at your facility — what actually lands on your P&L when a defect leaves the line?" Cannot size the deal or build a ROI case. Proposal lands as a cost, not an investment.
E — Economic Buyer Who controls the budget? Who can actually sign the check without getting approval from someone above them? "For something in the $50K–$80K range, who at your organization would be the one to approve that? Is that you, or does it go to VP Ops?" You build a champion but miss the real buyer. Deal dies in procurement because champion has no authority.
D — Decision Criteria What criteria will they use to evaluate solutions? What does "good" look like to them? "If you were comparing two options — ours and an alternative — what would be the top three things you'd need to see to feel confident recommending one?" You optimize your demo for the wrong criteria. You show speed; they care about audit trail. You lose on the dimension you never knew mattered.
D — Decision Process How do they actually make this decision? Who else is involved? What are the steps from "yes in principle" to a signed contract? "Assuming this looks like a fit after today, walk me through what happens internally — who else needs to weigh in, and roughly how long does that process take?" You forecast Q3 close; they have a legal review that takes 90 days you didn't know about. Deal slips two quarters and you miss revenue targets.
I — Identify Pain Is the pain real, specific, quantified, and urgent? Does it have a cost that justifies acting now rather than later? "Tell me about the last time a defect got through to a customer — what happened, and what did it cost, end to end?" Pain is vague ("we'd love better visibility"). No urgency. Deal perpetually in "evaluation" stage with no forcing function.
C — Champion Is there someone inside the organization who genuinely believes in the solution and will actively sell it internally? "Is this something you're personally driving, or is this coming from a top-down initiative? How would you describe the internal appetite for solving this right now?" No internal advocate. When you are not in the room, no one is making the case. Competitor who builds a better champion wins.
💡 Ask MEDDIC as conversation, not interrogation

MEDDIC is a framework for what you need to learn, not a script of questions to ask in sequence. The best discovery calls are conversations where these answers surface naturally through well-placed open questions and active listening. The skill is following the thread — when a prospect says "we had a quality escape last year that cost us a lot," the MEDDIC-trained founder says "what does 'a lot' translate to in your case?" rather than moving to the next prepared question. The quantification reflex is the most important habit to build.

M + I pain + value E + C authority + ally D + D criteria + process ~15% close without both stalls at procurement 60–80%+ close with full MEDDIC
MEDDIC as a progressive filter. Each category you fail to qualify narrows the likely close rate. The specific failure modes differ — missing Economic Buyer kills deals at procurement; missing Champion kills deals when you are not in the room. Close rate estimates are directional, not precise; they vary by product, market, and deal size.

SEE ITDiscovery call simulator — qualify your way through a Forge sales call

⚙ Interactive · Discovery call simulator

You are the Forge founder on a discovery call with Marcus Webb, Director of Quality at Caldwell Precision Components — a 1,200-person tier-2 automotive parts manufacturer. Marcus responded to your cold email about quality escape costs. Play through the conversation by choosing how to respond at each turn. A live MEDDIC score tracks what you have — and have not — learned. The worst path leads to a 30-minute demo to someone who cannot buy.

M
Metrics
E
Econ. Buyer
D
Dec. Criteria
D
Dec. Process
I
Pain
C
Champion
MEDDIC score: 0 / 6
—
—
Result

—

Critical gap: —

Notice what the worst path reveals: a founder who opens with "let me show you what Forge does" spends 30 minutes in a demo and leaves knowing almost nothing about budget authority, decision process, or whether Marcus can actually champion this internally. The deal then goes dark after two unanswered follow-up emails — not because Marcus hated the product, but because he had no authority to move it forward and no urgency to do so. The MEDDIC gaps you see at the end of the bad path are the specific information that would have told you to either slow down or engage the Economic Buyer directly.

IN PRACTICEHow to qualify out — gracefully and usefully

Not every discovery call should end with a next step toward a sale. Sometimes the right outcome is a clear mutual decision that this is not the right fit — now, or possibly ever. Qualifying out is not failure; it is pipeline hygiene that makes your remaining deals better because they receive more attention.

The conditions that warrant qualifying out, and how to handle each:

1

No budget authority and no path to the Economic Buyer

The prospect is genuinely interested but has no budget and no relationship with whoever does. Be direct: "I really appreciate the conversation — from what you've described, the pain is real. But for something at this price point, it sounds like this would need VP Ops sign-off, and it doesn't sound like that's an active conversation internally right now. I'd rather not waste your time or mine on a proposal that's going nowhere. Can I ask — is there a better way in? Could we set up a 20-minute conversation with you and your VP Ops together, where you help me understand what would make this worth their time?" This preserves the relationship, respects their time, and either opens the right door or ends the conversation productively.

2

No urgency — pain is real but has no forcing function

They agree the problem exists but they are not bleeding. They have been living with it for three years and will continue to live with it indefinitely. "It sounds like this is something you've been managing for a while and there's no specific event driving the timeline. That's okay — I don't want to push you toward something you're not ready to evaluate seriously. Can I ask: is there anything on the horizon — an audit, a customer contract renewal, a board review — that would make this more pressing? If not, let me stay in touch and come back when the timing makes more sense." This avoids the trap of forecasting a deal that will never close while keeping a future relationship open.

3

Wrong segment — they are outside your ICP

They are too small (no budget), too large (require capabilities you do not have), or in a vertical you cannot currently serve (medical device with FDA requirements you are not ready for). Be honest about what you have built and who it is for: "I want to be straightforward with you — what you've described around FDA audit trail requirements is something we're building toward but can't fully address today. I don't want to sell you something that won't pass your compliance review. Can I keep you in the loop as we build that capability?" Referrals are also appropriate here — a founder who says "we're not the right fit, but you should talk to Company X" earns a different kind of trust.

⚠ The "maybe" is worse than the "no"

A qualified "no" from a prospect — "we're not ready right now" or "this isn't the right fit for us this year" — is infinitely more valuable than a vague "let's stay in touch." The vague response costs you follow-up cycles, mental bandwidth, and pipeline distortion. It also costs the prospect — they feel vaguely guilty for not responding to your follow-ups. The honest disqualification is an act of respect. It also produces useful signal: if you are getting "no" on budget authority repeatedly, you may have an ICP problem. If you are getting "no urgency" repeatedly, you may have a positioning problem.

FORGEForge at 8 customers — what the discovery pattern reveals

Forge has now closed 8 customers at $320K ARR. Every single one was closed by the founder personally. At this stage, the value of each discovery call is not just the potential revenue — it is the pattern extraction that will eventually become a repeatable sales playbook.

🔑 The repeatable Forge discovery pattern

Across 8 closed deals, the Forge founder has now run enough discovery calls to see the pattern. The trigger event that predicts deal urgency: a recent quality escape or audit failure in the last 90 days. The champion role that predicts internal advocacy: Director of Quality (not ops, not IT — quality). The Economic Buyer who can actually sign: VP Operations or COO. The deal-threatening question that uncovers decision process: "Have you evaluated solutions like this before, and what happened?" (Previous failed evaluations reveal political landmines and procurement bottlenecks.) Decision timeline: consistently 60–90 days from first discovery call to signed contract when a trigger event is present; 6–18 months when it is not.

This pattern — ICP, trigger event, champion role, Economic Buyer, decision timeline — is now being documented in Forge's first sales playbook. It is the difference between "the founder can sell" and "Forge has a repeatable revenue mechanism." The playbook does not replace founder-led sales yet, but it makes the founder's discovery calls more efficient and begins to encode the knowledge that a future sales hire will need.

MEDDIC elementForge pattern (derived from 8 deals)Deals where this was missing → outcome
MetricsQuality escape cost: $30K–$80K per event; 2–6 events/year; ROI case = 3–8x in year 12 deals where cost was "unknown" → stalled at proposal stage; both restarted only after founder walked them through a cost model
Economic BuyerVP Ops or COO; always needed in at least one call before close1 deal lost: champion (Dir. of Quality) left the company before EB sign-off. No EB relationship = deal dead.
Decision CriteriaTop 3: accuracy (defect miss rate), integration ease (existing MES), audit trail output1 deal nearly lost: founder demoed speed; prospect cared about audit trail. Saved only by late-stage follow-up call.
Decision ProcessChampion recommends → VP Ops approves → Procurement issues PO (30–45 day additional lag)2 deals forecast for Q-end slipped one quarter due to undiscovered procurement lag
PainTrigger: quality escape or audit failure within 90 days. Without trigger, timeline is 6–18 months.3 calls with no recent trigger. All 3 went to "evaluation" stage and have not progressed in 6+ months.
ChampionDir. of Quality who has personally been blamed for an escape. High personal urgency.1 deal lost to competitor with stronger champion relationship despite inferior product.

WEAKNESSWhere this bites

✗ The demo-first call — the most expensive mistake in enterprise sales

The pattern is consistent and well-documented among technical founders: they open a discovery call with "let me show you what we've built." The prospect, being polite, watches the demo. The founder, reading engagement signals that are actually politeness, leaves the call feeling great. The follow-up email gets no response. The deal sits in the CRM at "demo completed" for three months until someone marks it lost. What actually happened: the founder spent 30 minutes pitching to someone with no budget authority, no urgency, and no internal political will to champion the product. The demo revealed nothing about fit. The prospect felt no obligation because they were pitched to, not consulted. A discovery call that starts with a demo is not discovery — it is a one-way broadcast that cannot learn anything.

✗ Skipping the Economic Buyer until late in the process

Champions are enthusiastic. They schedule calls, respond to emails, and give you positive signals that feel like a progressing deal. The champion is not the deal — the Economic Buyer is the deal. Founders who build deep champion relationships but never establish a direct connection to the EB discover this truth at the worst possible time: when the champion presents internally and the EB says "interesting, but not a priority this year." You have no relationship with the EB, no ability to influence their prioritization, and no fallback. Every discovery process must include an explicit strategy for getting the EB into a call — ideally by call two or three, not at proposal time. The question "what would it take to get 20 minutes with your VP Ops before we put together a formal proposal?" should be asked early.

✗ Confusing enthusiasm with qualification

Enterprise prospects are often genuinely interested in your product. Interest is not a buying signal — it is a curiosity signal. The difference: a qualified buyer has a specific pain with a known cost, authority to approve spending, an active evaluation process with a timeline, and a personal stake in solving the problem. An interested prospect has none of those things and may never develop them. Founders who mistake enthusiasm for qualification build a CRM full of "warm" prospects who will never buy, produce revenue forecasts that are fiction, and waste follow-up cycles that should go to real deals. The question "do you like what you see?" tells you nothing. The question "what would need to happen for you to move forward in the next 90 days?" tells you everything.

KEY INSIGHTHow this connects

  • 1.4 · The Discovery Interview — Extracting Truth from Humans — the open-question discipline and past-behavior framing you built in Stage 1 are directly applicable here. A discovery call is a discovery interview with commercial stakes added. The same instinct that makes a great customer interview — following the thread, resisting the urge to pitch, quantifying vague answers — makes a great sales discovery call. The frameworks compound.
  • 4.1 · Positioning — The One Thing You Want to Own — your positioning work determines what value hypothesis you are testing in the discovery call. If your positioning is sharp, you can state the hypothesis in one sentence and get a fast confirmation or correction. If your positioning is vague, you will give a different pitch to every prospect and never accumulate learnings across calls.
  • 4.2 · Founder-Led Sales — Why You Cannot Delegate This Yet — discovery calls at this stage are not just sales activities; they are product and market intelligence. The reason you cannot delegate them yet is that the learnings from each call — about decision criteria, buying process, champion profiles, competitive threats — must flow directly into your product roadmap and positioning. A sales rep loses information in translation; the founder captures it and acts on it.
  • 4.3 · Cold Outreach That Actually Works — the trigger event that got this prospect to respond to your outreach should shape your discovery call opening hypothesis. If they responded to an email about audit risk, lead with audit risk questions. The outreach and the discovery call are the same motion — you are testing hypotheses about pain and urgency across both.
  • Next: 4.5 · The Buying Committee — Understanding Everyone Who Can Kill Your Deal — the Economic Buyer and Champion you identify in discovery are just two members of a larger buying committee. Lesson 4.5 maps all the stakeholders — including the skeptics you will never meet directly — and how to influence each one.

GLOSSARYKey terms

MEDDIC
A B2B enterprise sales qualification framework standing for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. Each element represents a category of information that must be confirmed before a deal is considered qualified. Originated at PTC in the 1990s and widely used in enterprise SaaS. Missing any element introduces a specific, predictable deal failure mode.
Economic Buyer (EB)
The person in a prospect organization who has discretionary authority to approve the budget for a purchase without requiring additional sign-off from above. Distinct from the champion (who advocates internally) and the end user (who uses the product). The deal does not close without EB engagement.
Champion
An internal advocate at the prospect organization who believes in the solution and actively sells it within their organization when you are not in the room. A strong champion has credibility with the Economic Buyer and personal urgency to solve the problem. Building a champion without an EB relationship is a common deal-killing mistake.
Trigger event
A recent development at the prospect organization that creates urgency to solve a specific problem: a quality escape, an audit failure, a new customer requirement, a leadership change, a regulatory deadline. Trigger events predict deal velocity — prospects with a trigger event in the last 90 days close significantly faster than those without one.
Explicit next step
A specific, time-bound, mutually committed action that both the founder and the prospect agree to at the end of a discovery call. Contrast with implicit next steps ("I'll follow up") that create no obligation and often produce no action. The inability to commit to an explicit next step is itself a qualification signal — it usually means the deal is not real.
Value hypothesis test
The point in a discovery call where the founder summarizes what they have heard about the prospect's pain, quantifies it in the prospect's terms, and states the outcome their product delivers — asking the prospect to confirm or correct that framing. This is distinct from pitching: it invites correction before any product is shown, and the prospect's response reveals how accurate your understanding is.
Qualify out
The explicit mutual decision, reached during or after a discovery call, that a deal is not the right fit at this time — because of missing budget authority, insufficient urgency, wrong segment, or misaligned decision timeline. Qualifying out is not failure; it is pipeline hygiene that concentrates resources on real deals and produces honest market signal.

ACTIVE RECALLCheck your understanding

Answer in your own words first, then reveal.

1A prospect watches your demo enthusiastically and says "this is really impressive — we'd love to explore this further." What MEDDIC information do you still not know, and what is your next move?›

Enthusiasm is not qualification. After this response you almost certainly lack: Metrics (what does this problem cost them in their numbers?); Economic Buyer (who can actually approve the budget, and is it them?); Decision Process (what steps happen from "we'd like to explore" to a signed contract?); and possibly Pain (is the problem urgent and quantified or vaguely aspirational?). Your next move is not to send a proposal — it is to book a follow-up with the explicit goal of answering these questions. A good closing question: "I'm glad it resonated. To figure out if and how we could actually work together, it would help to understand a bit more about how a decision like this gets made on your side. Can we spend 20 more minutes on that before I put anything formal together?"

2Why is the Director of Quality often the champion but not the Economic Buyer in a Forge sale — and why does this distinction matter operationally?›

The Director of Quality is the person who experiences the pain most directly — quality escapes affect their performance metrics, their team's workload, and their professional reputation. They are highly motivated to solve the problem and can articulate the technical value of the solution. But they typically do not control capex or opex budgets large enough to approve a $50K–$80K annual contract unilaterally — that authority sits with VP Operations or COO. The distinction matters operationally because: if the Director of Quality is your only relationship, the deal dies the moment it goes to budget review and the VP Ops says "interesting, but not a priority." The operational implication: by call two at the latest, you should be asking your champion to bring you into a conversation with their VP Ops — framed not as a sales call but as a cost justification conversation. "Would it make sense to show your VP Ops the ROI model we built together so they understand what you're solving for?" gives the champion a way to escalate internally that helps them, not just you.

3What is the difference between a trigger event and a generic problem, and why does the presence of a trigger event matter so much for deal velocity?›

A generic problem is a standing condition that the organization has been living with for an extended period: "we always have quality issues." It produces interest but rarely urgency. A trigger event is a recent, specific occurrence that has changed the cost or visibility of that problem: a quality escape that reached a major customer last month, an ISO audit finding that requires a corrective action plan within 90 days, a new customer contract that requires statistical process control certification. Trigger events matter for deal velocity because they create a forcing function — a reason to evaluate and decide now rather than in six months. Prospects with trigger events have a deadline they did not choose; prospects without one will evaluate indefinitely at their own pace. The Forge discovery pattern shows this empirically: deals with a trigger event in the last 90 days close in 60–90 days; deals without one have not progressed in 6+ months. In discovery, the right question is not "do you have quality problems?" (generic) but "has anything happened recently that has made this more urgent?" (trigger-seeking).

4A prospect says "we've been managing this manually for three years and it works well enough — we're just exploring options." How do you handle this, and what does your answer tell you about the deal?›

This is a clear "no urgency" signal. Three years of status quo with "works well enough" means there is no forcing function and no personal stake in solving this now. The right response is to acknowledge it honestly rather than push: "That makes sense — if it's been manageable for that long, I don't want to push you toward an evaluation you're not ready for. Can I ask: is there anything on the horizon that might change that calculus — a new customer requirement, an upcoming audit, anything like that?" If they say no, this is a qualification-out conversation. You might say: "Then the honest answer is probably that the timing isn't right. I'd rather keep you in mind for when something changes than spend three months in an evaluation that doesn't go anywhere for either of us. What would be the best way to stay in touch without pestering you?" What this tells you about the deal: it is not a deal right now. More broadly, if you are having this conversation frequently, it signals either that your outbound targeting is finding people without trigger events (ICP/trigger problem) or that your positioning is attracting "exploring" behavior rather than active evaluation (positioning problem). Both are fixable with the data these conversations produce.

Next: understanding the full buying committee — and everyone in it who can kill your deal →