The Discovery Script That Cuts Cycle Time in Half

They drag because discovery is fuzzy.

Not “bad” exactly. Just… loose. A little too friendly. A little too much “tell me about your goals” and not enough “how do you buy something like this, who else is involved, and what happens if you do nothing.”

And then the deal sits there.

It sits in “Next step: follow up” purgatory. It sits while your champion goes quiet. It sits while procurement wakes up three weeks later like, oh right, we should probably look at security now.

If you want to cut cycle time in half, you do not start with better follow ups.

You start with a better discovery script.

Not a robotic one. Not a “read this word for word and never deviate” thing.

A script the way experienced sellers use the word. A planned flow. A sequence of questions that forces clarity early, so the rest of the deal is basically just execution.

This is the exact kind of work we do inside the David Consulting Services 90 Day Method. We pull the founder’s best instincts out of their head, turn them into an actual playbook, and then we tighten discovery until it produces clean deals. The kind that close. Or disqualify fast.

That’s the point.

Why discovery is the real bottleneck

Here is what “normal” discovery looks like in a lot of startups:

You ask what they are trying to do.

They give a broad answer.

You show features.

They seem interested.

You schedule a demo.

They ask for pricing.

You send it.

Then… nothing.

And you assume it is pricing. Or competition. Or timing.

But the truth is usually simpler: you never built a shared, specific problem with real stakes, tied to a decision process that actually exists.

So every next step is optional.

When discovery is tight, a deal gets momentum because you did four things early:

1. You made the problem concrete and measurable.
2. You uncovered the real reason it matters now.
3. You mapped how they will decide, with names, steps, dates.
4. You confirmed what “yes” looks like, including risk and approval.

Everything else is just follow through.

The Discovery Script (copy this, then make it yours)

This is a full script you can use on a first call. It works best when the call is 25 to 45 minutes and you have a clear next step available (a deeper technical demo, a workshop, a proof of concept, whatever makes sense for your deal size).

You will see pieces that look like MEDDPICC, SPIN, Sandler. That is intentional. These frameworks are not competing. They are just different angles on the same truth.

Also, you do not need to ask every question on every call.

But you do need to hit every section before you send a proposal. If you skip one, that missing info usually shows up later as delay.

1) Set the frame (2 minutes)

You say:

“Just to make sure this is useful, I’d love to do this in three parts. First I’ll ask a few questions to understand what you’re trying to solve and what’s driving it. Then I’ll share what we typically see work with teams like yours. If it feels like a fit, we’ll agree on a clear next step with who needs to be involved. Sound fair?”

If they say yes, you are already doing something subtle: you are making the call mutual. Not you performing. Not them interviewing you.

Then:

“Before we jump in, what would make this call a win for you?”

That one line is underrated. It stops you from guessing.

2) The “Why are we talking” layer (5 minutes)

This is where you get them out of vague land.

Questions:

• “What triggered you to look at this now?”
• “What’s happening in the business that makes this a priority?”
• “What have you tried so far, if anything?”
• “What’s not working about the current approach?”

If they give you a fluffy answer like, “We just want to be more efficient.”

Push gently:

“When you say efficient, what does that mean in practice. Fewer hours. Fewer errors. Faster time to value. More pipeline. What are you really trying to improve?”

You are hunting for a before and after picture.

3) Define the problem in numbers (5 to 8 minutes)

If you want cycle time to drop, you need measurable pain. Not because you want to corner them.

Because measurable pain creates urgency that survives internal meetings.

Questions:

• “How are you measuring this today?”
• “What’s the current baseline?”
• “If nothing changes, what does that cost you per month or per quarter?”
• “What does ‘fixed’ look like. What number would make you happy?”

If they do not know the numbers, do not punish them. Most people do not have it ready.

Instead:

“Totally fair. If we had to estimate, are we talking something like 5 percent impact or 50 percent impact?”

Then shut up.

They will pick a range. Now you have something to anchor on.

4) Stakes and impact (this is where deals are made) (5 minutes)

This is the part founders often skip because it feels too direct. It is direct. That is why it works.

Questions:

• “What happens if you don’t solve this in the next 90 days?”
• “Who feels the pain most when this breaks?”
• “Is this tied to a bigger initiative. Revenue target. Launch. Renewal. Hiring plan?”
• “What’s the internal consequence if this slips?”

You are looking for business impact, and you are also looking for personal impact. Because decisions are made by humans.

A simple follow up that gets surprisingly honest answers:

“Why do you personally care about getting this right?”

You will hear things like, “My CEO is on me about this.” Or, “My team is burning out.” Or, “We’re going to miss the board plan.”

Now the deal has weight.

5) Current workflow and constraints (5 minutes)

You need to know what you are replacing, integrating with, or asking them to change.

Questions:

• “Walk me through how this works today, step by step.”
• “Where does it break most often?”
• “What tools are involved right now?”
• “What constraints do we need to respect. Security. Compliance. Data. IT.”

If you sell into enterprise, do not wait until the end to ask about security and procurement.

That is how you add 30 days by accident.

6) The decision process (this is the cycle time lever) (8 to 12 minutes)

This is the section that halves cycle time when you finally start doing it consistently.

Most sellers ask, “Who is the decision maker?”

That question is too blunt and also kind of naive.

Instead, map the whole path.

Questions:

• “How do decisions like this typically get made there?”
• “What are the steps between today and a signature?”
• “Who else will weigh in. Even informally.”
• “Has budget already been allocated for something like this, or do we need to build a business case?”
• “What is the timeline you’re working toward, and what’s driving that date?”
• “What could slow this down internally?”

Then ask the key one:

“If we get to the end and this is clearly the right solution, what could still cause you to say no?”

That surfaces hidden landmines early. Legal. A preferred vendor. A VP who hates change. A security requirement. A political fight.

You want those now, not after proposal.

7) Qualification without being weird (3 to 5 minutes)

You do need to qualify. But you can do it in a way that feels like a normal conversation.

Questions:

• “What budget range did you have in mind for solving this?”
• “Is there an existing vendor or internal build being considered?”
• “What would make this a no brainer investment?”

If they push back on budget, you can say:

“Totally fair. The reason I ask is I don’t want to recommend a path that’s unrealistic. We see teams solve this with anywhere from X to Y depending on scope. Where do you think you’ll land?”

It is calm. It is adult. It works.

8) Confirm the win criteria (2 minutes)

This is where you reduce rework later.

You say:

“Let me play this back to make sure I’ve got it.”

Then summarize:

• their trigger
• the impact
• the desired outcome
• the timeline
• the decision path

Then ask:

“What did I miss. Or what would you change?”

If they correct you, good. Now it is shared reality.

9) Close the call with a mutual next step (2 minutes)

Do not end with “I’ll send some info.”

End with a calendar based step tied to their process.

You say:

“Based on what you shared, the next step I’d suggest is X. It would include Y people on your side, and we’d cover Z so you can decide whether to move forward. If we do that by next week, does that keep you on track for your timeline?”

Then:

“Who else needs to be in that meeting so we don’t have to re run it later?”

That one question alone cuts weeks off deals. Because you stop doing the same demo three times for three different stakeholders.

The “cuts cycle time in half” part, explained simply

Cycle time drops when:

• You stop proposing before the decision process is mapped.
• You stop demoing before the problem is quantified.
• You stop chasing “interest” and start aligning on a plan.

A lot of founders think speed comes from pushing harder.

But speed comes from removing ambiguity.

Ambiguity creates internal delay. Internal delay creates ghosting. Ghosting creates your pipeline forecast turning into fiction.

Common mistakes that quietly add 30 to 60 days

You accept “we’re evaluating options”

Options for what, exactly. Against what criteria. By when. With who.

You let “send me pricing” happen too early

Pricing is not a step. Pricing is a tool.

If they ask early, respond with:

“Happy to. Before I send numbers, can I ask two quick questions so I don’t send something irrelevant?”

Then ask about scope and decision process. Every time.

You confuse a champion with a decision process

A champion is a person. A process is a machine.

You need both.

You treat procurement like a surprise boss fight

Bring it in early. Even if it is just, “Do you know what procurement will require once we get alignment?”

How to implement this in your team without making it robotic

1. Put the script in your CRM as a call checklist.
2. Train reps to master the sections, not memorize the lines.
3. Review calls and score them on coverage, not charisma.
4. Track one metric: % of deals with a documented decision process within 7 days of first call.

If your CRM is messy and no one logs this stuff, that is also normal. Fixable, but normal.

This is another thing we handle inside David Consulting Services. Discovery does not live in a Google Doc. It lives in the pipeline. If it is not in the opportunity notes, it basically does not exist.

A simple one page Discovery Notes template (use this)

Copy and paste this into your CRM.

Trigger:

Why now:

Current approach:

What’s broken:

Baseline metrics:

Impact (business):

Impact (personal):

Desired outcome:

Timeline and driver:

Decision steps:

Stakeholders:

Budget range:

Risks / blockers:

Next step (date/time):

If you can fill this in after the first call, your proposal process becomes easy. Your follow ups become specific. And your forecast gets less embarrassing.

If you want help tightening this for your exact motion

Every startup has its own wrinkles. Deal size. technical depth. security. champions who need ammo. founders who still do half the selling.

If you want this discovery script adapted to your ICP, and then turned into a repeatable playbook your first reps can actually run, that is literally the point of the 90 Day Method at David Consulting Services.

You can read through the method, see how it works, and book a consultation call if it feels like the right time.

Wrap up

A faster sales cycle is usually not a “sales enablement” problem.

It is a discovery problem.

Get discovery tight and the rest of the deal stops being a guessing game. You will know what they care about, how they decide, who can block it, and what “done” looks like. Then you just… move.

And if the deal is not real, you will know that faster too.

That is still a win.

FAQs (Frequently Asked Questions)

Why do most B2B sales cycles drag and how can discovery impact this?

Most B2B sales cycles drag not because the product is confusing but because the discovery process is fuzzy and too loose. Improving discovery with a clear, planned flow of questions that clarify the buyer's decision process and stakes can cut cycle time significantly by turning deals into clean, executable opportunities.

What common mistakes occur during the discovery phase in startups?

Common mistakes include asking broad questions like 'What are you trying to do?', showing features prematurely, and failing to build a shared, specific problem tied to a real decision process. This leads to optional next steps and stalled deals due to lack of urgency and clarity.

What are the four key outcomes of a tight discovery process that accelerate deal momentum?

A tight discovery process achieves: 1) Making the problem concrete and measurable; 2) Uncovering the real reason it matters now; 3) Mapping how decisions will be made with names, steps, and dates; 4) Confirming what a 'yes' looks like including risk and approval. These create clarity that drives deals forward efficiently.

How should a discovery call be structured for maximum effectiveness?

A discovery call should be structured in three parts: first, set the frame by agreeing on mutual goals for the call; second, explore why you are talking by uncovering business triggers and priorities; third, define the problem in measurable terms and understand stakes and impact. This flow ensures clarity and sets up clear next steps.

What types of questions are essential during discovery to uncover real pain points?

Essential questions include: 'What triggered you to look at this now?', 'What’s happening in your business that makes this a priority?', 'How are you measuring this today?', 'What does it cost if nothing changes?', and 'What happens if you don’t solve this soon?' These help quantify pain and urgency.

How does David Consulting Services' 90 Day Method improve B2B sales discovery?

David Consulting Services' 90 Day Method extracts founders’ best instincts into an actionable playbook that tightens discovery until it produces clean deals that either close quickly or disqualify fast. It emphasizes planned questioning flows that create clarity early, reducing sales cycle times significantly.