ooligo
ENTRY TYPE · framework

Discovery call

Last updated 2026-05-02 RevOps

A discovery call is the first substantive conversation between an AE and a buyer where the goal is not to pitch but to qualify: surface the prospect’s problem, the cost of inaction, the buying process, and whether your solution is a real fit. A great discovery call ends with a mutual decision to continue or to disqualify, and a clear next step on the calendar.

What discovery is actually for

Most discovery calls fail because reps confuse “telling the story” with “running discovery.” Discovery is a diagnostic. You are trying to answer four questions, in order:

  1. Is there a real problem? What is broken today and how is it measured?
  2. Is it worth solving now? What happens if they do nothing for 6 months?
  3. Who decides? Economic buyer, champion, blockers, procurement.
  4. Can we win? Fit, competitive landscape, technical constraints, budget reality.

If you cannot answer all four after the call, you ran a demo, not discovery.

A repeatable structure

A 30-minute discovery call should roughly look like:

MinutePhaseGoal
0-3FrameSet agenda, ask permission, declare you might disqualify
3-20DiagnoseOpen questions on current state, pain, impact, process
20-25BridgeOne or two specific examples of how peers solved this
25-30Next stepConfirm fit, schedule a working session, name attendees

The hardest move is the framing line: “If after this call I don’t think we’re a fit, I’ll tell you. Is that okay?” It earns permission to ask harder questions.

Question patterns that work

  • Current state. “Walk me through how your team handles X today, end to end.”
  • Impact. “What does that cost you in a quarter, in dollars or hours?”
  • Trigger. “Why is this on your plate now and not 6 months ago?”
  • Decision process. “If we agreed today this was a fit, what are the next five steps inside your company?”

Avoid leading questions (“Wouldn’t it be great if…”). Avoid stacking questions. Pause for at least 2 seconds after they finish answering.

Common pitfalls

  • Pitching too early. A demo before you understand the problem is a guess. Hold features for the second call.
  • No disqualification. If every discovery call advances, your pipeline is full of ghosts. A healthy team disqualifies 30 to 50 percent of first calls.
  • No next step on the calendar. “I’ll send you some materials” is a soft close. Book the next meeting before you hang up, with named attendees.
  • Skipping the economic buyer. If you cannot name who signs the contract by the end of the call, you do not have an opportunity yet.
  • BANT vs MEDIC — qualification frameworks that structure discovery
  • MEDDDPICC — enterprise qualification deep dive
  • Champion builder — how to identify the champion you uncover here
  • Gong — call recording and discovery analytics