Discovery Call Structure Cheat Sheet

The 30-Minute Flow

Print this. Keep it next to your keyboard for your first 20 discovery calls, then let it become instinct. The order matters more than the wording — problem before qualification, qualification before vision, vision before next steps. Selling out of order is the single most common reason discovery calls fail to convert to a next step.

Talk-time target for the whole call: you talk ~30%, they talk ~70%. If you notice you've talked for more than 45 seconds straight, stop and ask a question.

---

0:00–2:00 — Open & Frame

Objective: Earn the right to ask hard questions later by setting a clear, low-pressure agenda.

Say this:

"Thanks for making time, [Name]. Here's what I'd love to do in the next 30 minutes: spend the first chunk understanding what's driving this for you right now, then ask some pointed questions about how you'd evaluate and decide on something like this — and if it looks like a fit on both sides, we'll figure out a sensible next step together. If at any point it's clearly not a fit, I'll tell you. Sound fair?"

Green flag: They add to the agenda ("Actually, can we also cover X?") — that's engagement. Red flag: They say "just show me what you've got" — reframe: "I will, but 10 minutes on your situation means I show you the right thing, not a generic demo. Deal?"

---

2:00–5:00 — Context & Stakes

Objective: Find the trigger event. Nothing changes without one.

Ask:

• "What made now the right time to look at this, versus six months ago or six months from now?"
• "What happens if nothing changes here in the next two quarters?"
• "Who else is feeling this besides you?"

Green flag: A specific date, event, or number ("Our renewal is in September," "We lost two reps to this last quarter"). Red flag: Vague answers ("Just always looking to improve") — the deal has no urgency yet. Probe once more, then flag it internally as a longer-cycle, lower-priority opportunity.

---

5:00–15:00 — Situation & Problem Discovery (longest block — protect this time)

Objective: Understand current state, the specific problem, and its business impact in their words, not yours.

Ask, in this order:

1. "Walk me through how this works today, end to end."
2. "Where does it break down, or where does it get painful?"
3. "How are you handling that today — workaround, spreadsheet, nothing?"
4. "What does that cost you — in time, money, morale, or risk?"
5. "If we fixed only one part of this, which part would matter most?"

Rule: Ask "what does that mean for your team / the business?" after every pain point. A stated problem without a quantified impact is not yet a qualified problem.

Green flag: They start explaining internal politics or naming names unprompted — high engagement. Red flag: One-word answers, checking phone, "it's fine, just exploring" — this call may need to end early with a lighter next step (send info) rather than push toward qualification.

---

15:00–22:00 — Qualification

Objective: Confirm budget, authority, timeline, and decision process without sounding like an interrogation. Frame it as helping them, not gatekeeping.

Bridge line:

"This sounds like a real problem worth solving. So I don't waste your time later, can I ask a few practical questions about how a decision like this would actually get made at [Company]?"

Ask:

• "Has budget been allocated for this, or would it need to be created / reallocated?"
• "Besides you, who else needs to sign off before this moves forward?"
• "What's driving the timeline — is there a date this needs to be solved by?"
• "What does your evaluation process usually look like for something in this range?"
• "Have you looked at other ways to solve this — internally built, another vendor, or doing nothing?"

Green flag: Specific names, a real number, a real date. Red flag: "I'd have to check" on every question — you're likely talking to an influencer, not a buyer. Note it, and plan to multithread before the next call.

---

22:00–26:00 — Vision & Mutual Fit Check

Objective: Paint the "after" state in their language and confirm — out loud — that both sides see a fit.

Say this:

"Based on what you've told me — [restate the trigger, the pain, and the impact in their words] — here's roughly how companies like yours use this to fix that. [1–2 sentence relevant example, not a feature list.] Does that track with what you're picturing?"

Then ask directly:

"Genuinely — on a scale of 1 to 10, how much of a priority is solving this right now?"

Green flag: 7+ with a reason attached. Red flag: 4–6, or a number with no conviction behind it — do not push to next steps yet; ask what would move the number up.

---

26:00–29:00 — Next Steps / Mutual Action Plan

Objective: Leave with a specific, dated, two-sided commitment — not "I'll follow up."

Say this:

"Here's what I'd suggest: I'll [send X / prepare Y] by [date]. On your end, could you [loop in Z / gather the data on W] by [date]? Then let's get 30 minutes on the calendar for [specific date/time] to go through it together — does that work?"

Rule: Never end a discovery call with only your next action. A next step with no ask of them is a signal the deal isn't real yet.

---

29:00–30:00 — Close & Confirm

Say this:

"Great — I've got you down for [their action] by [date], and I'll have [your action] over by [date]. I'll send a quick recap by email in the next hour so we're both aligned. Anything I should have asked you today that I didn't?"

That last question routinely surfaces the real blocker.

---

If You're Running Long

Cut blocks in this order — never cut Qualification or Next Steps:

1. Trim Context & Stakes to one question.
2. Trim Vision to a single sentence.
3. Never cut Situation & Problem Discovery or Qualification — without them you have nothing to qualify or forecast on.