What Discovery Questions Earn a Second Meeting in SaaS Sales?

Your AEs are demoing on the first call and calling it discovery

Pull up any first call on your team's calendar. Odds are the AE spent eight minutes on rapport and qualification, heard one pain point, said "that is exactly what the product solves," and shared their screen. The prospect watched forty minutes of features. At the end the AE asked "does this look like something that could work for you," the prospect said "yeah, this is interesting, send me some information," and the deal went into stage two with a close date the AE made up.

That call felt productive. It was not. The AE learned nothing they could use to build urgency, nothing about who decides, and nothing about the cost of the status quo. The prospect learned about your product, which means they can now evaluate it without you. You gave away the demo and got nothing for it. The second meeting, if it happens, will be the prospect asking for pricing so they can compare you to two other vendors.

What discovery has to uncover before anyone shares a screen

Real discovery is a structured conversation with an outcome. The outcome is a picture of the prospect's problem sharp enough that the demo, when it happens, is built around it. Three things have to come out. First, the cost of the problem in the prospect's own numbers: hours, headcount, churn, missed revenue, whatever they measure. Second, the buying group: who else feels this problem, who signs, who can kill it. Third, the consequence of doing nothing, in the prospect's words, not the AE's.

An AE who has those three things can end the call with a reason for the second meeting that the prospect agrees with. "You said this is costing your team roughly a day a week and your VP is the one who owns that number. Would it make sense to have her on the next call so she sees exactly how this would work for her workflow?" That is a second meeting with a purpose and a second stakeholder. "Let me send you a recap" is neither.

• The cost of the problem, in the prospect's own numbers
• Who else feels it, who signs, who can kill it
• What happens if they do nothing this quarter
• A next meeting with a purpose and a named attendee

The questions that earn the second meeting

The questions are not clever. They are patient. When the prospect names a pain, the AE asks what that costs, then asks how they know, then asks who else cares. When the prospect says "we are looking at a few options," the AE asks what would make one option the obvious choice. When the prospect says "this is a priority for us," the AE asks what happens if it is still not solved in six months. Each question goes one level deeper than the prospect expected to go.

The hardest part is not asking. It is not answering. Most AEs hear a pain and rush to solve it, because solving feels like selling. Train them to sit in the problem for one more question. "Tell me more about that." "How long has that been going on?" "Who ends up cleaning that up?" Five or six of those and the prospect has built the business case for you, in words you can repeat back on the proposal.

This is a skill, and skills need reps. An AE who has run the deeper questions fifty times against a realistic buyer will run them on a live call. One who heard them once at a kickoff will not. Revenue OS gives AEs an AI buyer to practice against by text or live voice, with 5 personas plus custom at 3 difficulty levels, scored in about 60 seconds on script adherence, objection handling, close attempt, energy and tone, and follow-up setup. A discovery call with no close attempt for the next meeting scores accordingly.

The talk-to-listen ratio tells you who is doing discovery

You do not need to watch every first call to know whether discovery is happening. You need one number per call: how much of it the AE spent talking. On a real discovery call the prospect talks more than the AE. On a disguised demo the AE talks for most of the hour. That ratio is measurable on every recorded call, and it separates the AEs who ask from the AEs who present without anyone reviewing the transcript.

When the ratio is off, the fix is specific. Pull up the moment the AE stopped asking and started pitching. Usually it is right after the first pain the prospect named. That is the coachable moment: not "do better discovery," but "at minute nine, when she said onboarding takes three weeks, ask what that costs before you show her anything." One sentence the AE can act on tomorrow.

Score the first call against your own discovery process

Write your discovery process down. Not the methodology you bought, your version of it: the four or five things an AE must uncover, the question that opens each one, and the way the call ends. That document is what your first calls should be scored against. If the AE never asked who else is involved, the score should say so.

Intel Suite scores every recorded call on six skills, including talk-to-listen ratio and follow-up setup, plus your own process at 60% weight. Tag the Zoom meeting and it scores itself and syncs to HubSpot. The best and worst moment are timestamped. A first call under 80 becomes a redo due 6pm the next business day against an AI buyer seeded with the real prospect's words, so the AE practices the exact question they skipped, with the exact prospect who deserved it.

What changes when discovery is real

Second meetings get booked on the first call, with a purpose and a named attendee, instead of being chased by email. Demos get shorter, because they only show the three things the prospect said they cared about. Proposals stop being a price list and start repeating the prospect's own cost of the problem. And the champion who used to go dark has a reason to answer, because the AE is following up on something the champion said mattered.

None of that takes a bigger team or more pipeline. It takes an AE who asks one more question, a way to see whether they did, and a fix by the next business day when they did not. That is how a founder turns a first-call habit into a shorter cycle and a forecast worth sending to the board.