Run a 30-min sales discovery call that advances

What you’ll do

You'll open with 5-10 min of small talk and explicit agenda setting. Give a 60-second intro then stop. Spend 15-20 min on the problem (not the solution), listening 70%, talking 30%. Probe for the rest of the buying committee. Lock the next step on the calendar live before you hang up. And disqualify gracefully when it's obviously not a fit.

The steps

1. 01
   Open with 5-10 min of small talk and agenda setting

   Min 0-5

   The first 5-10 minutes are for rapport and framing. Start with light small talk (where are they based, how's their week). Then set the agenda explicitly: 'The goal for today is to figure out if it makes sense to keep talking. I'll ask a few questions about what you're working on, then if it makes sense, we'll talk about whether we can help. Sound good?' This gives both sides permission to disqualify gracefully.

   • Find one piece of common ground in small talk: shared connection, similar background, recent industry news. 30 seconds of authentic conversation lowers the temperature for the rest of the call.
   • Set the agenda out loud. Explicit framing prevents the prospect from feeling pitched at and gives you permission to dig into discovery.
   • End the agenda with a yes/no question that earns their buy-in: 'Does that work?' If they push back on the structure, address it now — not 20 minutes in.

   ↳ Reference: Discovery call architecture
2. 02
   Give a 60-second intro to your company, then stop

   Min 5-7

   Brief, calibrated, then back to them. 'We work with [companies like yours] and typically help with [problem 1], [problem 2], [problem 3]. Was there anything specific that brought you to this call?' This does two things: anchors them on what you actually do (so they don't waste time asking) and surfaces what they're hoping to get out of the conversation.

   • Name 3 problems you solve, not 1. This lets the prospect self-identify which one matters to them.
   • End with the open question: 'Was there anything specific that brought you to this call?' This is the highest-yield question of the entire call.
   • Don't go past 60 seconds. The temptation to keep going (mission, vision, founding story) loses the call. They came to talk about themselves; let them.

   ↳ Reference: The 70/30 rule
3. 03
   Spend 15-20 min on the problem, not the solution

   Min 7-25

   This is the call. Ask deep questions about the problem. Listen 70%, talk 30%. The goal is to leave the call with a complete understanding of what they're trying to solve, what they've tried, why it hasn't worked, who else cares, and what 'fixed' would look like. If you walk away with that understanding, the rest of the deal is straightforward.

   • Core questions (steal these): 'What made you decide to take this call?' / 'How long have you had this problem?' / 'Who else does it affect?' / 'How do you quantify the impact?' / 'Why haven't you solved it already?' / 'What's your budget?' / 'How does your org buy software?' / 'Who else needs to weigh in?'
   • The pinnacle of discovery is getting them to explicitly say: 'These are my top 3 problems. If we don't solve them, it costs us $X. I think your solution will solve it.' If they say this out loud, the deal is mostly closed.
   • Don't demo. Don't pitch features. Earn the demo — make them want it by the end of the call.

   ↳ Reference: Qualification frameworks
4. 04
   Probe for the rest of the buying committee

   Min 20-25

   Before you leave the call, you need to know who else has to be in this decision. Ask directly. Most prospects will name 2-3 people unprompted; the ones they don't name (security, IT, compliance, finance) are the ones that kill deals in week 8. Surface them now while you can plan around them.

   • Direct asks: 'Who else would need to be part of this decision?' / 'Walk me through how your company has bought software like this before.' / 'Who controls the budget for this?'
   • Probe for hidden veto-holders: 'When you've bought tools like this in the past, has security review been an issue?' / 'How does your data team usually weigh in?'
   • If they're the sole decision-maker on a deal that should have a committee, that's a signal — either they don't have authority or you're talking to the wrong company size.

   ↳ Reference: Multi-thread playbook
5. 05
   Lock the next step on the calendar before you hang up

   Min 25-30

   The single biggest difference between deals that advance and deals that die is whether the next step gets booked live. Don't say 'I'll send you a calendar link.' Pull up your calendar on screen-share and offer two specific times. If they hedge, you didn't earn the next step — and now you know to adjust.

   • If the call went well, the next step is a deeper demo or a meeting with another stakeholder. Book it.
   • If they hedge on a next step, do the closing test: 'Based on what you've shared, would it make sense to look at a 60-min walkthrough next week?' Their answer tells you whether you have a real deal or not.
   • Always send a recap email within 2 hours of the call: 1-2 sentences on what they said the problem was, what you proposed, the agreed next step. This is the artifact your champion uses internally.

   ↳ Reference: Meeting booking mechanics
6. 06
   If it's not a fit, disqualify gracefully and quickly

   Whenever signal is clear

   Some calls become obvious no-fits in the first 15 minutes — wrong size, wrong budget, wrong problem. Disqualify out loud rather than slogging through 30 minutes of polite questions. 'Based on what you've told me, I'm not sure we're the right fit right now. Here's what would have to change for that to flip.' This earns you respect, frees the prospect, and keeps your pipeline clean.

   • A graceful disqualification often leads to a referral. 'I know someone at [other company] who might actually have exactly this problem — want me to intro?'
   • Track every disqualification in your CRM with the specific reason. The pattern across 20-30 calls tells you whether your ICP is too broad.
   • Most founders spend too long in calls with bad-fit prospects because saying 'this isn't a fit' feels rude. It's the opposite — you're respecting their time.

   ↳ Reference: Segmentation architecture

What goes wrong

The failure modes that catch most founders.

• You demo too early

  Founders jumping into a demo within the first 15 minutes is the single most common discovery mistake. The demo kills the discovery conversation — once they see the product, they react to features instead of their problem. Earn the demo. Don't show it until you've validated the problem is real and big.

• You talk more than you listen

  Your default is to talk because you're nervous, excited about the product, or afraid of silence. The 70/30 listen-talk rule is harder than it sounds. If you find yourself talking for more than 3 consecutive sentences, you've slipped into pitch mode. Stop and ask a question.

• You ask vague questions and accept vague answers

  'How important is this to you?' produces 'pretty important' as the answer. 'What happens if you don't solve this by end of quarter?' produces real information. Specificity in your questions forces specificity in their answers.

• You don't ask about the buying process

  If you don't know how they buy by the end of the call, you'll be surprised in week 8 by procurement, security review, or a decision-maker you didn't know existed. Ask: 'How does your company buy software like this? Who needs to sign off?'

• You let the call end with 'I'll follow up'

  If you don't have a specific next step on the calendar by the end of the call, you don't have a next step. Lock it live, on the call. 'I'll send a calendar link' is where deals go to die.

• You don't disqualify when it's clearly not a fit

  30 minutes spent in a call with a bad-fit prospect is 30 minutes you didn't spend with a good-fit prospect. Disqualify gracefully and quickly. The prospect will respect you more, not less.

Want the technical depth?

The chapters with the full reference detail.

• → Discovery call architecture (full reference)— The 30-minute frame with the 60-80% advancement rate
• → Qualification frameworks— BANT, MEDDIC, SPICED as conversation architecture
• → Run customer discovery (Mom Test)— The pre-PMF version of discovery — for product validation, not sales advancement
• → Multi-thread enterprise deals— What you do after you've mapped the committee
• → Handle the 4 canonical objections— When the discovery surfaces resistance