# Running a discovery call that qualifies

> A discovery structure that surfaces budget, committee and timeline in one call, with a question bank, disqualification rules and what to send in follow up.

Source: https://saas-marketing.net/guides/saas-discovery-call-framework/
Topic: SaaS Sales
Type: guide
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/saas-discovery-call-framework/

## Short answer

A SaaS discovery call should run 30 minutes in four blocks: 3 minutes framing, 15 minutes on current process and cost of inaction, 7 minutes on decision process, committee and budget source, and 5 minutes setting a mutual next step. Top performing reps talk roughly 45 percent of the time and ask more questions than average reps. Discovery exists to disqualify, so a team converting more than 80 percent of discovery calls into opportunities is collecting names rather than qualifying deals.

## Key takeaways

- Gong analysis of sales calls puts top performer talk time near 45 percent, meaning the buyer speaks more than half the call.
- Ask about the trigger event before the problem: what happened in the last 60 days that started this search.
- A discovery to opportunity conversion rate above 80 percent means your team is not disqualifying anything.
- Budget source matters more than budget size: an existing line item beats a hypothetical approval every time.
- Write six CRM fields before the call counts as complete, or the qualification never survives the handoff.
- Disqualify out loud and politely, because a clean no this quarter is worth more than a stalled deal for three.

---

Most discovery calls are demos with a polite five minute preamble. The rep asks two context questions, hears one pain point, and spends twenty three minutes clicking through an interface while the buyer says "interesting" at intervals. Then the deal stalls in month two because nobody ever asked who signs. Discovery has one job and it is not to impress anyone. It is to find out, fast, whether this deal can actually close.

## What does a 30 minute discovery call look like minute by minute?

Four blocks, and the proportions matter more than the exact questions. Spend the middle half of the call on how the work happens today, because that is where every other answer comes from.

| Block | Minutes | Purpose | What success looks like |
| --- | --- | --- | --- |
| Frame and permission | 0 to 3 | Agree the agenda and that you may ask hard questions | Buyer agrees to an outcome for the call |
| Current process and cost | 3 to 18 | How it works now, what it costs, what triggered the search | You can describe their week without the product |
| Decision and money | 18 to 25 | Committee, process, budget source, timeline, competing projects | Two names and one budget source |
| Mutual next step | 25 to 30 | Specific date, named attendees, what each side brings | Calendar invite accepted before you hang up |

The framing block is three sentences and it earns the rest. Something like: I have got about six areas I want to understand, some of them will be blunt questions about budget and process, and if it turns out we are not a fit I will tell you on this call. Buyers relax visibly when you say that, and it gives you licence to ask the money question later without it feeling like a swerve.

Gong's analysis of recorded B2B sales calls puts top performer talk time at roughly 45 percent, with better reps asking more questions and spreading them across the call rather than front loading. Pull ten of your team's recordings and check the ratio before changing anything else. It is usually the biggest gap and the easiest to coach.

## What should the question bank contain?

Organise questions by what they uncover, not by a stage model. Reps need to know why they are asking, otherwise the bank becomes a script they read at people.

**Trigger event.** What happened in the last 60 days that made this a priority? Who noticed first? What did you try before booking this call? The trigger is the most predictive single answer on the call. No trigger means no urgency, whatever else you hear.

**Current process and cost of inaction.** Walk me through how this gets done today, step by step. Who touches it? How many hours a week? What breaks when it goes wrong? What happens if you do nothing for another six months? That last one separates a real problem from an interesting one.

**Success metric.** What number would have to change for someone to call this a good decision in twelve months? Who owns that number? Is it on anyone's objectives this year? A metric with no owner means no internal advocate.

**Decision process and committee.** Who else will be in the room? Who has vetoed a purchase like this before? What did your last software purchase of this size look like, from first call to signature? Asking about the last purchase is far more reliable than asking about the hypothetical future one, because people describe history accurately and forecasts optimistically.

**Budget source.** Where would the money come from? Is there an existing line item, or would this need new approval? Which budget did your last tool in this category come out of? An existing line item is worth more than a large number with no home.

**Timeline and competition for attention.** What else is competing for the same budget and the same implementation time this quarter? The most common thing you lose to is not a competitor, it is a data migration project that eats the team for five months.

## When do you disqualify, and how do you say it?

Four qualification elements: trigger, owned metric, budget source, named second stakeholder. Missing one is a nurture case. Missing three, say so before the call ends.

The language matters less than the directness. "Based on what you have told me, I do not think you should buy this right now, and here is why" is a sentence that costs you nothing and buys you enormous credibility. Half the time the buyer argues with you and reveals urgency you had not found. The other half you have freed a slot on your calendar and their afternoon.

If your discovery to opportunity rate sits above 80 percent, your team is not qualifying, it is collecting. That looks fine on this month's pipeline review and terrible on next quarter's close rate. I would rather see 50 percent conversion with a 30 percent close rate than 90 percent conversion with 8 percent. Check both numbers together, always.

Frameworks help here if you use them as a checklist rather than a script. [MEDDPICC](/glossary/meddpicc/) works well for enterprise deals with long committees, and the difference between it and older approaches is covered in [MEDDIC vs BANT](/comparisons/meddic-vs-bant/). BANT still works fine for transactional deals under 15,000 dollars where the buyer and the budget holder are the same person.

## What has to be in the CRM before the call is complete?

Six fields, written the same day, in the buyer's words rather than your summary of them.

**Post call CRM requirements**

A call without these fields did not happen, as far as the pipeline is concerned. This is a manager enforcement job and it is deeply unpopular for about six weeks, after which forecast accuracy improves enough that nobody argues. The [sales enablement operating system](/playbooks/saas-sales-enablement-operating-system/) covers how to make that stick without turning every one to one into an admin review.

## What goes in the follow up email?

Under 200 words, sent within two hours, structured in four parts.

**The recap that doubles as a qualification test**

That last step is the cheapest qualification signal you will ever get. A genuinely motivated buyer confirms a recap. A polite one does not, and now you know in week one instead of month three.

## How do you coach discovery without sitting on every call?

Record everything and review selectively. Conversation intelligence platforms make this tractable: pull the five calls with the highest talk time, the five longest monologues, and the five that converted, and review one of each per rep per month. Twenty minutes of listening beats an hour of pipeline discussion. The [conversation intelligence tools](/tools/conversation-intelligence-tools/) roundup covers what to look for when choosing one.

Three metrics worth tracking per rep, all available from recordings:

- Talk to listen ratio, target near 45 percent.
- Number of questions asked, with the better reps consistently higher.
- Longest uninterrupted monologue, which is the fastest tell for a rep who is demoing instead of qualifying.

Do not coach all three at once. Fix monologue length first, because it mechanically improves the other two.

## What discovery cannot do

Two honest limits. Discovery cannot create urgency that does not exist. A rep who is excellent at questioning will simply find out faster that the deal is not real, which is the value, but leaders sometimes buy discovery training expecting it to manufacture pipeline and it does not.

It also degrades under quota pressure. In the last three weeks of a quarter, disqualification rates fall across almost every team I have seen, because nobody wants to remove a name from a pipeline they are measured on. Build the correction into your process by reviewing late quarter opportunities against the same four elements in the first week of the following quarter, and expect to cull some.

## Start here

Take ten recorded calls from last month, score each against the four qualification elements, and count how many have all four. That number, not your conversion rate, tells you whether discovery is working. For most teams it comes in under three out of ten and the room goes quiet.

Then hand your team the [discovery call script and question bank](/templates/saas-discovery-call-script/) and run a live role play before letting anyone use it in a real call. If you are building the motion from scratch, the [startup sales strategy playbook](/playbooks/saas-startup-sales-strategy/) sets the stage model this fits into, the wider [SaaS sales strategy](/saas-sales/) hub covers the rest of the funnel, and the [sales playbook template](/templates/saas-sales-playbook-template/) gives you somewhere to write it all down. Once discovery quality improves, watch the effect in the [sales velocity calculator](/calculators/saas-sales-velocity/), where it usually shows up as a shorter cycle rather than a higher win rate.

## Frequently asked questions

### What questions should you ask on a SaaS discovery call?

Ask what happened in the last 60 days that started this search, how the work gets done today and what that costs, what specific metric would have to move for this to be worth buying, who else has to agree, where the budget would come from, and what happens if they do nothing. Those six areas surface almost every reason a deal will later stall.

### How long should a discovery call be?

Thirty minutes for most mid market SaaS deals, forty five for enterprise where multiple stakeholders join. Sixty minute first calls usually mean the rep is demoing, which turns discovery into a product tour and skips qualification entirely. If you genuinely need more time, book a second call and treat the willingness to take it as a buying signal.

### What is a good discovery to opportunity conversion rate?

Between 40 and 65 percent for most B2B SaaS teams with reasonable lead quality. Above 80 percent almost always means reps are advancing anything with a pulse, which shows up two stages later as a bloated pipeline with a terrible close rate. Below 30 percent usually points to a lead quality or targeting problem rather than a discovery skill problem.

### How much should a salesperson talk on a discovery call?

Around 45 percent of the time, according to conversation intelligence analysis of recorded B2B calls by Gong and similar platforms. Top performers also ask more questions across the call and spread them more evenly rather than front loading an interrogation. If your recordings show reps at 70 percent talk time, that is the single most influential coaching fix available.

### When should you disqualify a prospect on a discovery call?

When there is no trigger event, no owned metric, no budget source and no named second stakeholder. One missing element is a nurture case. Three missing means say so on the call. Disqualifying out loud is faster and more respectful than three months of polite follow up emails neither side believes in.

### What should you send after a discovery call?

A recap email within two hours containing what you heard in their words, the metric they said mattered, the agreed next step with a date and named attendees, and one relevant resource. Keep it under 200 words. The recap doubles as a qualification test: if nobody confirms it, the urgency you thought you heard was not real.

### Should you demo on a discovery call?

Only a short targeted view if the buyer insists, and only after the current process questions. A full demo before you know their metric means you are showing features at random and training the buyer to evaluate you on interface rather than outcome. Saying you would rather show the two things that matter to them next week is usually accepted.