Discovery call framework

Discovery Call Framework

When to use

Structure a 30-minute initial discovery call with a prospect. Works for SaaS AEs, consultants, service providers. Goal: uncover timeline, budget, decision criteria, and pain depth, not to pitch features. Higher Levels AE Mastery minute-by-minute framework.

The framework

1. Intro + small-talk (2 minutes): Use research-backed personalized questions to build rapport. Avoid generic weather talk. Reference something specific about them or their company.

2. Discovery (18 minutes): Uncover the six essentials:

   • Timeline: when they need to implement / decide
   • Urgency: pain severity and competitive pressure pushing them now
   • Decision maker: who actually signs off; confirm if it's your contact
   • Evaluation criteria: how they'll measure success or rank vendors
   • Budget: do they have money allocated, or is it constrained?
   • Competitive situation: who else are they evaluating?

3. Pitch/Demo (6 minutes): Show 1–3 features directly tied to discovered pain, not a feature dump. Recap what you heard before showing anything.

4. Close (4 minutes): Confirm next steps on the call, propose a specific date and time, send calendar invite live (no follow-up email later).

How to apply it

A mid-market SaaS company lands an inbound demo request from a VP of Sales at a logistics software firm. The rep sees the VP's LinkedIn and notes they published about hiring challenges and team turnover. Call opens:

Rep: "I noticed you posted recently about scaling your sales team. Is that something you're actively working on this quarter?"

VP: "Yeah, we're understaffed. Been hiring but it's slow."

Rep: "How many open headcount are we talking, and when do you need them filled?"

VP: "Three or four roles. Ideally by Q3, but honestly we're flexible."

That's timeline + urgency signal. The rep pivots to decision and budget:

Rep: "Who else is involved in finalizing hires on your team, your CHRO, your manager above you?"

VP: "HR owns the posting process, but I decide who we interview and who gets an offer."

Rep: "Got it. Has your budget for this hiring push been approved, or is that still being finalized?"

VP: "It's approved. We've allocated $150k for headcount and $20k for hiring tools."

Eighteen minutes in, the rep has timeline (Q3), urgency (low, they're flexible), decision maker (the VP + HR collaboration), and budget ($170k). The rep recaps:

Rep: "So you're looking to hire three to four folks by Q3. HR drives the process, you drive the final decision. And you've got budget allocated for both roles and tools. Is that right?"

VP: "Exactly."

Rep: "The reason I ask is that a lot of teams like yours are using [tool name] to reduce hiring cycle time. Want to see how it works for your use case?"

The rep shows two features: automated screening and interview scheduling. Specific to the VP's workflow, not a product tour. Four minutes of close:

Rep: "What's your next step with this? Do you want to trial it with one open role, or would you want to involve your HR team first?"

VP: "Let me loop in my HR lead. We could do a pilot with our next opening."

Rep: "Perfect. Let's get your HR lead scheduled for Thursday at 2 PM to walk through the same workflow. I'll send the calendar invite now, does Thursday work for you both?"

VP: "Yeah, send it over."

The rep sends the invite live on the call, confirms the time, and ends with "I'll include a summary of what we discussed so your HR lead has context. See you Thursday." Discovery complete, next step locked, no ambiguity about who's involved or what's being evaluated.

Common traps

1. Feature dumping in the demo slot: You skip discovery or rush it, then spend all six demo minutes showing features. You pitch what you think is cool, not what they care about. Result: "Interesting, but not urgent" and a stalled deal.

2. No decision-maker confirmation: You get excited talking to a friendly contact (usually middle-level), assume they're the buyer, and don't ask who else needs to sign off. Three weeks later, they say "I need to check with my VP." You're back to zero.

3. Vague next steps: Call ends with "I'll follow up next week" or "Let's schedule a demo soon." No date. No calendar invite. You email Monday; they don't respond for four days. Momentum dies.

4. Not recapping before the demo: New stakeholder joins mid-call and doesn't know what was discussed. You start the demo cold, and it lands flat. Always recap the pain and criteria first.

5. Budget avoidance: You assume they have budget or are too polite to ask. Weeks into qualification, they reveal "We're not spending anything this year." Wasted discovery.

Source credits

• Higher Levels AE Mastery (Kris & Eric): Minute-by-minute call framework, discovery essentials (timeline, urgency, decision maker, evaluation criteria, budget, competitive situation), active discovery principle