There's a version of "we're being thorough" that's actually just "we're slow," and buyers can tell the difference. A proposal that arrives eight days after discovery has to work harder to win than one that arrives in two — not because buyers are impatient for its own sake, but because momentum from the call fades fast.

Overview

Speed after discovery is one of the few sales variables a team fully controls. You can't control a buyer's budget cycle or a competitor's pricing, but you can control how long it takes to turn a conversation into a document. Teams that treat this as a real metric — not just an informal "get to it when you can" — tend to close more of what reaches the proposal stage.

The problem

Delay between discovery and proposal usually comes from a few specific places:

  • The rep is waiting for "a good block of time" to build the deck properly, which keeps getting pushed by other calls.
  • Pricing needs sign-off from someone else on the team, and that approval loop isn't fast.
  • The deck has to be built close to from scratch each time because there's no reusable structure.
  • Nobody owns the deadline — "I'll get you something soon" isn't a commitment either side can track.

Buyer attention decays measurably during this gap. Once a call ends, the buyer's urgency is highest in the first day or two — after that, other priorities crowd back in, and a proposal that shows up later has to re-earn the attention it already had.

Key point
Research from Gartner's B2B buyer studies found that roughly 30% of sales opportunities are lost to "no decision" — the prospect chooses neither a competitor nor the vendor, they simply stall. Momentum lost between discovery and proposal is one of the more controllable contributors to that outcome. (Gartner B2B Buyer Survey, via AM World Group)

A better approach

Shortening the gap without cutting corners usually comes down to structure, not effort:

  • Commit to a specific turnaround on the call. "You'll have this by Thursday" creates accountability that "soon" doesn't.
  • Separate the parts that change every time from the parts that don't. The buyer's specific problem and numbers change every deal. The overall structure, proof format, and pricing logic usually don't — so they shouldn't require rebuilding.
  • Pre-clear pricing ranges where possible. If every proposal needs a fresh approval cycle for pricing, that's the actual bottleneck — not the writing.
  • Draft key sections during the call, not after. Capturing the buyer's problem statement and numbers in near-final language while still on the call removes a full editing pass later.

Example

A boutique advisory firm used to average about a week between discovery and proposal delivery, mostly because the same two partners had to review every deck before it went out. After they split proposals into a fixed structural shell plus a shorter "what's specific to this deal" section — and set a 48-hour internal turnaround target — average delivery time dropped to two to three days. Close rate on proposals sent within 48 hours was measurably higher than on the ones that had slipped past a week, consistent with what buyer-attention research would predict.

Questions

Isn't a fast proposal a sign of a generic one? Only if speed comes from skipping the work of reflecting what the buyer actually said. Speed and specificity aren't in tension if the underlying structure is reusable.

What's a reasonable target turnaround? Within 24–48 hours for most professional services deals is achievable without rebuilding the deck from scratch each time, and it aligns with when buyer attention is still highest.

What if pricing genuinely requires more time to finalize? Send the proposal with the approach and scope confirmed, and flag that final pricing follows within a specific, short window — that's still faster than making the buyer wait for the whole document.