🔍 Discovery Call Structure Pro — The 30-Min Call That Qualifies + Advances

Discovery Call Plan: FinTech Series B VP Eng, 45→70 engineers scaling

A discovery call structure produces the 30-min call that extracts MEDDICC qualification + advances to next step with clear commitment. Based on 3,000+ call patterns, top-quartile reps have 70/30 listen-talk ratio and end 80% of calls with next-meeting booked; bottom-quartile reps talk 50%+, get vague 'let's follow up' commitments, and lose 60% of deals in the 30 days post-discovery. Your prospect profile — Series B FinTech, engineering scaling from 45 to 70, LinkedIn pain signals, inbound-from-breakup meaning moderate interest — is primed for a strong discovery call. This plan produces 12 MEDDICC-aligned questions, minute-by-minute structure, value-tie bridge, and multi-thread expansion plan.

Pre-Call Research Checklist

Before the call, know:

• [x] Recent LinkedIn post about code review bottlenecks (already have)
• [ ] Specific hiring posts — senior engineer roles last 60 days (use as stage signal)
• [ ] Company funding history + investors (Sequoia/a16z/etc?) — signals what peer comparisons will land
• [ ] Recent blog posts by CTO or VP Eng (what they care about publicly)
• [ ] Tech stack hints (from job posts — Python/Go/TypeScript/etc)
• [ ] Glassdoor reviews for engineering — what engineers complain about
• [ ] Competitor peer companies in fintech scaling (similar stage) — use as reference

Print/screen-visible during call: 3-5 key facts about them ready for mid-call reference.

Call Structure (30 min)

• 0-3 min: Opening (rapport + agenda)
• 3-23 min: Discovery (12 questions, MEDDICC-aligned)
• 23-27 min: Value tie (connect pain to solution)
• 27-30 min: Next step (micro-commitment + booking)

Opening (Min 0-3)

Tone: peer-to-peer, not vendor-to-buyer. They're a VP Eng; you're a credible advisor.

Opening script:

[After initial hello]

'Thanks for making time — I know you're in the middle of scaling from 45 to
70, so this is a busy stretch. Before we dive in, just want to confirm:

- You've got about 30 minutes?
- The main thing I'd like to cover is understanding how code review is
  actually working as you scale, and whether what we built at [companies
  like Vercel/Linear] would be relevant to [their company]. 
- Is there anything specific you want to make sure we cover from your side?'

[Listen for their agenda items]

'Sounds good. Let me start with a few questions so I'm not guessing at what
matters to you.'

Why this works:

• Acknowledges their specific situation (45→70)
• Confirms time
• Sets expectation (discovery, not demo)
• Invites their agenda
• Signals listening-first posture

Discovery Questions (Min 3-23)

Organized by MEDDICC dimension. Use 1-2 per dimension based on what surfaces.

IDENTIFY PAIN (3 questions, minutes 3-8)

Q1 (open-ended, expand their context):

'You mentioned code review bottlenecks on LinkedIn — can you paint the picture for me? What's actually happening when someone opens a PR today?'

Listen for:

• Specific pain scenarios
• Who's affected (seniors, juniors, both?)
• How often + how severe
• Current workarounds

Q2 (dig deeper):

'What's the downstream impact? When PRs sit for 2 days, what happens to the team?'

Listen for:

• Velocity metrics (shipping delayed)
• Morale (senior burnout from endless reviews)
• Business impact (features delayed)

Q3 (historical context):

'When did this become a real issue? Was there a specific moment or has it been building?'

Listen for:

• Urgency signal
• Related triggers (recent hires, new projects, infrastructure changes)

METRICS (2 questions, minutes 8-12)

Q4 (quantify pain):

'Rough estimate — how much senior engineer time is going to code review right now? Weekly hours or percentage of their week?'

Listen for:

• Specific numbers (even rough)
• Whether they've already measured this
• Business value math potential

Q5 (quantify solution value):

'If we could get that back to [specific lower number], what would that unlock? New projects? Ship faster? Fewer hires?'

Listen for:

• Their own business-case math
• ROI framing they'll use internally
• Strategic impact (not just tactical)

ECONOMIC BUYER + DECISION PROCESS (2 questions, minutes 12-16)

Q6 (economic buyer):

'A decision like this — who else would be involved? Is it primarily you, or does CTO/CEO need to weigh in?'

Listen for:

• Real decision-maker
• Approval chain
• Political dynamics

Q7 (decision process):

'If we decided in a month that this is the right fit, walk me through what the actual procurement + onboarding process looks like at [company].'

Listen for:

• Timeline realism
• Procurement hurdles (security review, legal, finance)
• Implementation ownership

DECISION CRITERIA (2 questions, minutes 16-19)

Q8 (what matters):

'When you think about a solution here, what are your must-haves vs. nice-to-haves?'

Listen for:

• Specific requirements
• Table stakes vs. differentiators
• Where your offer might fall short

Q9 (how evaluate):

'If we did a proof-of-concept, what would make it successful from your side? What are you measuring during evaluation?'

Listen for:

• Evaluation criteria
• Pilot scope
• Success metrics for trial

COMPETITION (1 question, minutes 19-21)

Q10 (competitor landscape):

'Are you evaluating other options too? No concerns either way — just helps me understand how to be useful.'

Listen for:

• Named competitors
• 'Build in-house' consideration
• 'Do nothing' as option

CHAMPION + TIMING (2 questions, minutes 21-23)

Q11 (champion signal):

'If this works out and makes a real difference, what does that mean for you personally? Is it a big win for the year?'

Listen for:

• Personal incentive alignment
• Career-level stakes
• Whether they'd champion internally

Q12 (timing):

'If this is a fit, when would you ideally want it in place?'

Listen for:

• Urgency (Q3 vs. 'maybe next year')
• Specific drivers for timing (board meeting, hiring wave)

Value Tie (Min 23-27)

Bridge their stated pain → your specific solution:

'Based on what you've described — senior engineers spending ~30 hrs/week on
review, bottleneck getting worse with hiring wave, timing around [specific
trigger they mentioned] — I think there's a strong fit. Here's the specific
reason:

We're not Copilot (I know you have that). We're the review side. We handle
~70% of routine review work — style, bugs, patterns — automatically. Senior
engineers only see the 30% that actually needs their judgment. 

At Vercel, that meant senior engineers went from 30%→10% of their week on
review. The arithmetic across your 10 senior engineers = ~80 hours/week back.
At [company]'s scale, that's a meaningful hiring-plan difference.

Does that sound directionally right for [company], or am I over-indexing on
the review piece?'

Why this works:

• Mirrors their exact language
• Quantifies specifically to their team
• Differentiates from Copilot (they already have it)
• Uses peer reference (Vercel = credible for Series B)
• Invites disagreement (shows genuine interest in fit, not just pitch)

Next Step (Min 27-30)

Micro-commitment close:

'Here's what I'd suggest as next step: a 45-min technical deep-dive with
you + 1-2 senior engineers who'd be hands-on with this. I can have someone
from our side show the actual tool on real codebases like yours.

After that, we can talk about whether a 2-week pilot makes sense. Deal?'

[Wait for yes]

'Great. Does Tuesday 2pm or Wednesday 10am work better for you?'

[Get specific calendar commitment]

'I'll send the invite today. Who else should I include on the calendar invite?'

[Get names for multithreading]

Why this works:

• Specific next step (not 'I'll follow up')
• Bite-sized commitment (45 min, not 2-hour demo)
• Multi-stakeholder seeded (1-2 senior engineers)
• Calendar booked ON THE CALL (not 'let me check my calendar')
• Multithreading activated (additional names captured)

Post-Call Writeup Template

Within 1 hour, write this in your CRM/notes:

PROSPECT: [Company] — [Name], VP Eng
CALL DATE: [date]
OUTCOME: [advanced to technical demo / qualified out / stalled]

MEDDICC SCORING (1-5 scale):
- Metrics: X/5 [note: quantified pain or not]
- Economic buyer: X/5 [named buyer + status]
- Decision criteria: X/5 [clarity on requirements]
- Decision process: X/5 [timeline + procurement clarity]
- Identify pain: X/5 [pain strength + clarity]
- Champion: X/5 [is VP Eng a likely champion?]
- Competition: X/5 [competitive landscape known]

KEY PAIN:
- [Specific pain statement they made]
- Quantified: [their numbers]
- Urgency driver: [why now]

STAKEHOLDERS:
- Primary: [VP Eng name]
- Economic buyer: [CTO name if identified]
- Others: [any mentioned]

NEXT STEP:
- Technical deep-dive scheduled: [date]
- Attendees: [who]
- Prep needed: [what to prepare]

RISKS:
- [Any red flags]
- [Any competing priorities]

SCORE: [0-100 probability of closing]

Red Flags To Watch

During call, these patterns suggest stall-risk:

1. Can't articulate 'why now' → not ready this quarter

2. Only VP Eng involved, CTO not mentioned → economic buyer missing

3. 'We built something internal already' → competition = status quo, hard to displace

4. Vague timeline ('maybe this year') → low urgency

5. Evaluating 5+ options → either thorough or not close to decision

6. Can't quantify pain → might be curiosity, not priority

7. No specific champion incentive → no internal advocate if you need one

If 3+ flags: lower forecast probability, plan for longer cycle.

Multithreading Plan

Seeds to plant during discovery:

• 'Would CTO typically weigh in on a decision like this?' (establishes need to include)
• 'Who else at [company] is thinking about engineering velocity?' (identifies peers)
• 'Who would actually use the tool day-to-day?' (identifies end-users)

After discovery, before next call:

• LinkedIn research: CTO name + Head of Platform if exists
• Proposal for next call: include VP Eng + 1-2 senior eng + ideally CTO observer

Multithreading scripts:

• 'I'd love to include [CTO name] in the technical deep-dive. Should I add directly to the invite, or should you make the intro first?'
• 'For the pilot conversation, [CTO] likely wants visibility. Happy to prep materials specifically for their angle (ROI + strategic fit).'

Key Takeaways

• 30-min call structure: 3-min open + 20-min discovery (12 MEDDICC questions) + 4-min value tie + 3-min next step.
• 70/30 listen-talk ratio. You are discovering, not demoing. Record calls + audit own talk time — most reps shocked.
• 'Why NOW' is highest-value question. Without urgency answer, deal won't close this quarter. Use this as qualification gate.
• End with micro-commitment booked ON the call (Tuesday 2pm, not 'I'll follow up'). 4x better next-meeting attendance than 'follow up later.'
• Post-call writeup within 1 hour, MEDDICC scored. This is how discovery becomes useful sales intel for the pipeline + team-level forecast.