Why Discovery Interviews Are Your Highest-ROI Activity
You have 20 minutes with a VP who controls a $2M budget in exactly the area your technology addresses. What do you do?
Most technical founders do one of two things — both wrong:
- Launch into a demo of their technology (the prospect didn’t ask for this)
- Ask vague questions like “What are your biggest challenges?” (too broad to be useful)
This script gives you a structured 20-minute framework that extracts the specific information you need to (a) validate your product-market fit, (b) build a compelling Phase II commercialization narrative, and (c) qualify whether this prospect is worth pursuing.
Pre-Call Setup (5 minutes before)
Before you get on the call, have answers to these three questions:
- What is this person’s role and what do they control? (Budget, team, process)
- What specific problem do I hypothesize they have? (Based on your research)
- What would a successful outcome from this call look like? (Usually: confirmed pain, quantified impact, next step agreed)
Mindset shift: You are a researcher, not a seller. Your job is to understand their world, not convince them of yours.
The Script: 4 Phases in 20 Minutes
Phase 1: Context Setting (2 minutes)
Open by setting expectations and giving them a reason to talk openly.
"Thanks for making time. Before we dive in — I'm not here to pitch
anything today. We're doing research on how [their industry/department]
teams currently handle [problem domain], and your perspective would be
really valuable.
I'll ask a few questions about your current process, and if anything
we're building seems relevant, happy to share — but no pressure.
Sound good?"Why this works:
- Removes sales pressure immediately
- Positions you as a researcher (higher status than a salesperson)
- Gives them permission to be honest about problems
Phase 2: Current State Mapping (8 minutes)
This is the most important phase. You’re mapping how they currently solve the problem — the people, tools, processes, and pain.
Start broad, then drill down:
"Walk me through how your team currently handles [process/problem].
What does a typical [week/cycle/workflow] look like?"Follow-up probes (use 3–4 of these):
| Probe | What You’re Extracting |
|---|---|
| ”Who’s involved in that process day-to-day?” | Stakeholder map, team size |
| ”How long does that typically take?” | Time cost, inefficiency signal |
| ”What happens when [process] breaks down or gets delayed?” | Severity, downstream impact |
| ”Have you tried to fix this before? What happened?” | Past solutions, why they failed |
| ”What tools are you using for this today?” | Tech stack, integration requirements |
| ”If you could wave a magic wand, what would be different?” | Desired outcome in their words |
Critical rule: When they say something interesting, ask “Can you say more about that?” or “What does that actually look like?” Don’t move on too fast. The gold is in the second and third layers of answers.
Phase 3: Impact Quantification (5 minutes)
Now you need to put numbers on the pain. This is what makes your Phase II commercialization section credible and your future sales conversations powerful.
"You mentioned [specific pain point from Phase 2]. Help me understand
the impact — if I were to put a rough number on it, what does this
cost your team in terms of [time / money / headcount / missed
opportunities]?"Quantification probes:
| Probe | What You’re Extracting |
|---|---|
| ”How many hours per week does your team spend on this?” | Labor cost |
| ”What’s the error rate or failure rate in this process?” | Quality cost |
| ”How many [deals/patients/units] are affected?” | Scale of impact |
| ”What would solving this be worth to your department annually?” | Budget ceiling |
| ”Is this something your leadership has flagged as a priority?” | Organizational urgency |
Note: People often can’t give you an exact number, and that’s fine. “Ballpark” and “rough estimate” are your friends here. Even “Is it more like $100K or more like $1M?” works.
Phase 4: Next Steps & Pilot Criteria (5 minutes)
If the conversation has gone well and there’s genuine pain, transition into understanding what it would take to actually work together.
"This has been really helpful. Based on what you've described,
what we're building might actually be relevant here. If we were
to explore this further, what would that process look like on
your end?"Qualification probes:
| Probe | What You’re Extracting |
|---|---|
| ”What would a successful pilot look like for your team?” | Success criteria |
| ”Who else would need to be involved in evaluating something like this?” | Decision-making committee |
| ”What’s your typical timeline for evaluating new solutions?” | Sales cycle length |
| ”Is there budget allocated for this, or would it need to be created?” | Budget readiness |
| ”Would it be helpful if I shared a brief summary of our approach?” | Permission to follow up |
Close:
"I really appreciate your time. Would it make sense for me to
send over a one-page summary of what we're working on, and we
can reconnect in [2 weeks] if it seems like a fit?"Post-Call: What to Capture (Within 10 Minutes)
Immediately after the call, document:
| Field | Notes |
|---|---|
| Confirmed pain points | In their exact words |
| Current solution/workaround | Tools, processes, people |
| Quantified impact | $/hr/headcount affected |
| Decision-making process | Who else is involved |
| Pilot criteria | What would success look like |
| Next step | What you agreed to do |
| LOI potential | Could this person sign an LOI for Phase II? |
| Quote for proposals | Any verbatim quote you could use (with permission) |
Rules of Engagement
- Never pitch in a discovery call. The moment you start presenting, they stop being honest.
- Listen more than you talk. Aim for a 70/30 ratio — they talk 70% of the time.
- Take notes visibly. If on video, let them see you writing. It signals you value what they’re saying.
- Don’t solve their problem on the call. Resist the urge to explain how your tech fixes everything. That’s for the next meeting.
- Record with permission. “Mind if I record this for my notes?” Most people say yes. This gives you verbatim quotes for proposals.
How Many Discovery Calls Do You Need?
- For Phase II proposal: 8–12 calls across 3–4 target segments
- For product-market fit signal: 5 calls where you hear the same pain unprompted
- For LOI generation: Usually 1 in 3 good discovery calls converts to an LOI
Scheduling tip: Batch discovery calls into 2-week sprints. Do 2–3 per day for 5 days, then synthesize. Spreading them over months means you lose pattern recognition.
This script is part of the Phase II Commercialization Vault — free resources for SBIR/STTR founders navigating the path from Phase I to commercial traction.