How to Run a Discovery Call That Produces a Proposal

For B2B sales reps, solutions consultants and pre-sales teams who run discovery on deals that end in a written document: a proposal, an RFP response, a scoping deck.

A discovery call is a structured first conversation in which a seller uncovers a buyer's problem, constraints and decision process before proposing anything. In a deal that ends in a written document, the call has a second job most guides skip: it has to capture the raw material that document will be built from. Run it so the transcript, not your memory, becomes the source for whatever you send next.

Key takeaways

• A discovery call is defined by its purpose, not by its position in the pipeline: it exists to uncover the buyer's problem, constraints and decision process before you propose anything.
• Plan 30 to 45 minutes for most B2B deals, and closer to 60 when pre-sales joins and the technical scope is unclear. Call length follows deal complexity, not the other way around.
• Run five moves in order: open with the agenda and the outcome, cover current state before desired state, get the constraints, map who else has to say yes, and close by naming the next document.
• A discovery call has ended well when three things exist in writing: the buyer's own words for the problem, the constraints that will shape scope, and the name of the next document.
• Recording a call is not capturing it. Send the recap within 24 hours and turn the call context into a first draft within 48 hours, before the specifics fade. At Open, an IT services firm, drafting from captured context brought proposal production from two to three hours down to within one hour.

What is a discovery call?

A discovery call is the first substantive sales conversation between a seller and a qualified prospect, used to understand the buyer's current situation, the problem they want solved, the constraints around it, and who decides. It is not a pitch, and it is not a demo. Its output is understanding, on both sides, plus a mutual decision about whether to keep going.

The definitions in circulation do not agree, which matters more than it looks. Some sources call it "the first conversation" with a prospect. Others describe it as an in-depth exploration that happens after an initial contact, and at least one treats it as a synonym for a qualifying call. Those are three different meetings at three different points in a pipeline.

The distinction worth holding: a discovery call is defined by its purpose, not by its position in the sequence. If the conversation exists to gather what you do not yet know about the buyer's world, it is discovery. That can be the first call, and in complex deals it is frequently the third, running in parallel with a technical session and a pricing conversation.

Discovery call vs qualification call vs demo

Teams use these three terms as though they were interchangeable, then wonder why calls run long and end without a next step. They serve different purposes and produce different outputs.

The practical consequence: if you have not run discovery, your demo is a guess. And if your discovery produced nothing you can quote back in writing, you will rebuild it from memory when the proposal is due.

What a discovery call is not

The phrase travels across industries and picks up unrelated meanings, so it is worth clearing three of them out of the way.

• It is not a job interview. In recruitment, some employers use "discovery call" for an informal first screening with a candidate. Same words, unrelated process.
• It is not legal discovery. In litigation, discovery is the formal exchange of evidence between parties, governed by procedure. Nothing in this guide applies there.
• It is not a free consultation. Coaches, agencies and freelancers often use "discovery call" to describe a complimentary intro session that ends in a sales pitch. The techniques overlap, the stakes and the documents do not.

This article is about the B2B version: a deal with several stakeholders, a defined evaluation, and a written document somewhere in the middle.

How long should a discovery call be?

Thirty to forty-five minutes for most B2B deals, and closer to sixty when pre-sales joins and the technical scope is unclear. That answer needs defending, because the published guidance on this question does not agree with itself.

Here is what the most visible sources actually say, checked on 18 August 2026.

The spread runs from 15 to 60 minutes, a factor of four on the same question. More interesting, Google's AI Overview picks the shortest range and states it flatly, which means a rep who asks an assistant instead of reading gets the most aggressive answer without the caveat.

Why the shortest range is the wrong default for complex deals: fifteen minutes is enough to confirm a problem exists. It is not enough to map who signs, what the current workflow costs, and which constraints will shape the scope. Reps feel this. One of the recurring questions in r/sales is literally how anyone does discovery in 30 minutes, with rapport and agenda eating the first third of the call before a single useful answer arrives.

The honest rule is that call length follows deal complexity, not the other way around. A single-stakeholder deal with a known use case fits in 30 minutes. A deal with a technical evaluation, a security review and three stakeholders does not, and pretending otherwise produces a document built on a quarter of the facts.

How to run the call: the five moves that matter

Most discovery frameworks are a list of questions. That is the easy part. What separates a call that produces a usable document from one that produces a warm feeling is sequence and closure. Five moves, in order.

1. Open with the agenda and the outcome

Say what the call is for, how long it will take, and what both sides should have at the end. Thirty seconds, no more. This is not politeness, it is permission: an agenda stated out loud lets you interrupt a tangent later without friction, because you are returning to something the buyer already agreed to.

State the outcome concretely: "By the end of this I want to understand your current process well enough to tell you honestly whether we are a fit, and if we are, what a proposal from us would need to cover." That sentence sets up the close and gives the buyer permission to disqualify you, which makes them more open, not less.

2. Current state before desired state

Start with what happens today, not with what they want. Buyers describe goals in marketing language and current reality in specifics, and the specifics are what you need. Ask them to walk you through the last time the problem occurred. Who was involved, what did they do, how long did it take, what did it cost them.

Do the research before you ask. Reading their careers page, last earnings call or recent product announcements takes ten minutes and changes the quality of the answers, because a buyer who can tell you have prepared will describe their challenges and their priorities in more detail than one who suspects they are being processed.

This ordering matters for the document you will write later. Goals produce adjectives, current state produces nouns and numbers. A proposal built from adjectives reads like every other proposal. One built from the buyer's own account of last Tuesday reads like it was written for them, because it was.

3. Get the constraints, not just the pain

Pain points are covered by every discovery guide in existence. Constraints are not, and constraints shape scope: a contract with twelve months left, a security review that adds six weeks, a platform decision that cannot be revisited, a budget cycle closing in March.

Ask directly. "What would have to be true internally for this to go ahead this year?" and "What has stopped this from being solved already?" The second question is the more revealing of the two, because it surfaces the failed attempt, the internal objection, or the competitor already in the building.

4. Map who else has to say yes

Stakeholder mapping gets mentioned in half the discovery guides in circulation and skipped in practice, usually because asking feels rude. It is not rude framed as process rather than politics: "When you have bought something like this before, who else was involved and at what stage?"

You want three names: who evaluates, who signs, and who can quietly kill it. The third is the one reps miss. In complex deals the document eventually travels without you, forwarded to someone you never spoke to, so your proposal has to stand alone for a reader whose objections you learned about on this call.

5. Close by naming the next document

End every discovery call by agreeing on what gets written and when. Not "I'll follow up," which commits nothing. Something specific: a scoped proposal by Thursday, a requirements summary for the technical team, a go or no-go on a tender, an outline deck for the champion to circulate internally.

This converts a conversation into a deal stage, and it tells you cheaply whether the discovery worked. If you cannot name the next document without guessing, you did not learn enough, and the fix is to ask for the missing piece before the call ends rather than three days later.

The discovery questions that shape a proposal

Question lists are everywhere. What is missing is the link between the question and the paragraph it will eventually produce. Below, each question is mapped to the section of the written document it feeds, which is a useful test in its own right: if a question does not feed anything, it is filler and you are spending call time you do not have.

Keep them open-ended, with one exception. Open questions produce the language you will reuse in writing, which is the whole point. But once a buyer has described something loosely, a closed follow-up is what turns it into a usable fact: "so that is four people, two days a month, correct?" That confirmation is the sentence that ends up in the proposal.

Two things follow from reading the table right to left. First, you can tell before the call ends whether you have enough to write, by checking which right-hand cells are still empty. Second, the questions worth asking twice are the ones feeding sections your buyer will read without you present.

What happens after a discovery call?

Three things should happen, in this order: a written recap goes to the buyer within 24 hours, the call context is converted into a first draft of the agreed document within 48 hours, and the deal record is updated with what changed. Most teams do the first, skip the second, and do the third badly.

The gap between the call and the document is where deals lose momentum, and it is almost entirely self-inflicted. Nothing about the buyer changed in those five days. What changed is that the seller's memory of the conversation degraded, and the document that finally arrives is a generic version of one that could have been specific.

The 48 hours between the call and the first draft

Detail decays faster than reps expect. The exact phrase the buyer used, the aside about the failed rollout two years ago, the number mentioned in passing: those are gone by Friday, and they are precisely what makes a proposal feel written rather than assembled.

The time cost is what pushes teams past the window. At Open, an IT services and digital transformation firm, producing a proposal from scratch took two to three hours before the team changed how drafting started. Their Engagement Executive, Thierry Wawrzyniak, describes the shift plainly: within one hour the document can be produced, with the remaining effort going into contextualization by the sales and delivery teams rather than into formatting and assembly. He adds a point that gets lost in productivity conversations: "Quality is a real issue. AI smooths it upward."

That is the argument for compressing the window. Not speed for its own sake, but drafting while the specifics are still available, so human effort goes into judgment instead of reconstruction.

Recording is not capturing

Nearly every B2B call is recorded and transcribed now. Very few transcripts become documents. The recording sits in the call intelligence platform, useful for coaching and deal review, while the proposal gets written from a half-page of notes taken by someone who was supposed to be listening.

That is the real gap, and it is a workflow gap rather than a discipline problem. Reps are asked to split attention between running the conversation and capturing it, and both suffer. Tools that read the transcript directly close the loop: Cobl connects to platforms like Gong, Zoom and Google Meet to use call transcripts as source material for the proposal or response, so requirements and objections come through in the words the buyer used rather than in internal shorthand. Across several calls on the same opportunity, that also solves the consolidation problem, where discovery, the technical deep dive and the pricing conversation each surface something and nobody pulls them together.

One caveat worth stating clearly: a generated first draft is a draft. It gets the structure, the buyer's language and the requirements onto the page, and a human still has to check the claims, adjust the framing and own what goes out. Human validation is not optional on a document that carries a price.

When discovery feeds an RFP response, not a proposal

Sometimes the answer to "what does your evaluation process look like from here" is that a formal process is coming. That changes the output entirely. Instead of one proposal you are looking at a set: a go or no-go decision, a questionnaire, a technical response, and slides for the evaluation committee.

It also changes what you needed from the call. Ask about evaluation criteria, weighting, incumbent suppliers and submission format while you still have an informal channel open, because once the process starts that channel usually closes. If the call surfaced a tender, the next step is not writing, it is deciding whether to bid at all, and that decision is far easier when the discovery notes already contain the criteria.

Worth noting how thoroughly this case is ignored elsewhere. Most discovery call guides never mention an RFP or a deliverable at all. For anyone selling into public sector, construction, IT services or enterprise procurement, that is the half of the outcome nobody writes about.

Discovery in complex deals: several calls, several documents

In enterprise and mid-market deals, discovery is not one call. It is a sequence: the AE runs the first conversation, a solutions consultant runs a technical session, someone else handles security, and pricing gets its own meeting. Each surfaces something the others did not hear.

This is the scenario sales engineers ask about most often. A recurring thread in r/salesengineers asks how a sales engineer should ask discovery questions without stepping on the AE's process, and a related question in r/techsales asks how to stay sharp at discovery when calls span SMB, mid-market and enterprise in the same week. Both are really the same question: how do you keep a consistent standard when the conversation is distributed across people and segments.

Two practices hold it together. Agree in advance which call owns which question, so the buyer is not asked about budget three times. And consolidate context in one place rather than in three sets of private notes, because the document at the end has to reflect all of it. Cobl's July 2026 product update made that consolidation explicit, with every document for a single deal living in one workspace, alongside document analytics that show how many people opened a shared document, how many times, and when it was last viewed.

That last signal is underrated after a discovery call. A proposal opened once and never reopened tells you something. One opened eleven times by four people tells you something else, and neither fact was available to a rep waiting on a reply. If you want the wider view of how these roles fit together, our guide to the pre-sales role, process and tools covers the handoffs in more depth, and teams selling into IT services and telecom face this multi-call pattern on nearly every deal.

Five discovery call mistakes that cost you the document

Not the usual list. These are the failures that show up later, in the writing, rather than in the call itself.

• Treating rapport as the objective. A pleasant call that produces no specifics is a failed discovery call. Buyers on r/sales are blunt about this, questioning why they should attend a discovery call at all when the seller could have done the homework first.
• Collecting pain without collecting numbers. "It takes too long" cannot be written into a proposal. "It takes four people two days every month" can.
• Ending on "I'll send something over." Vague closure produces vague documents and a follow-up sequence that reads like chasing.
• Letting the transcript sit. The recording is not the deliverable. If nothing converts it within a couple of days, you will write from memory anyway and the recording was decoration.
• Writing for the person you spoke to. The document travels. It will be read by a finance stakeholder and a technical reviewer who were never on the call, which is exactly why you asked what they care about.

Turn your next discovery call into a document, not a to-do

Cobl reads your call transcripts, CRM records and company content, then produces the proposal, the RFP response or the deck the deal needs next. Try Cobl for free for 30 days.