Pulse - Value Added
FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a free 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

Free 30-min revenue checkup →
Hire a Fractional CROHow We Help?LinkedInRésuméCRO Syndicate
← Library
Knowledge Library · pulse-coaching
13/13 Gate✓ IQ Certified10/10?

What question would you ask a rep who consistently loses deals at the proposal stage to diagnose the real issue?

What question would you ask a rep who consistently loses deals at the proposal stage to diagnose the real issue?
📖 1,806 words🗓️ Published Jun 24, 2026 · Updated Jun 23, 2026
Direct Answer

Ask the rep one question that forces them to expose the gap in their own discovery:

> "If you could rewind to the first meeting with this prospect, what one thing—about their budget, their decision process, or the alternatives they were weighing—would you make sure you knew before you ever wrote the proposal?"

A rep who loses repeatedly at the proposal stage almost never lost on the document. They lost because they built a solution for a problem that wasn't budgeted, wasn't prioritized by the full buying group, or had already been solved another way—and the proposal is simply where that gap finally became visible. The question above makes the rep name the missing piece themselves, which tells you whether you're coaching a qualification problem, a buying-committee alignment problem, or a genuine price/timing problem. Those three require completely different fixes, so the diagnosis matters more than any single follow-up.

The RevOps Reality Behind Proposal Losses

B2B purchases now routinely involve large, distributed buying groups. Gartner's research puts a typical B2B buying committee in the range of 6 to 10+ stakeholders, and reports that the single most common outcome of a B2B purchase effort is "no decision"—the deal dies against the status quo, not a competitor. AI tools like Gong and Clari surface deal-risk signals automatically, but they can't retroactively fix a rep who never confirmed budget or never mapped the people who can say no. A proposal loss is rarely a surprise; it's the predictable downstream result of a discovery step that got skipped.

The Diagnostic Framework: Three Layers of Inquiry

Don't ask "What went wrong?"—that invites excuses. Work the gap in layers.

Layer 1: The Discovery Autopsy

Ask: "What budget range did the prospect actually confirm—and how do you know it was real and not a polite deflection?" If the answer is "they said it wasn't a problem" or "we assumed," the deal was likely dead on arrival. Clari can flag deals where budget was never documented, but the rep still owns the conversation.

Ask: "Who on the buying group did you speak with, and what did a 'win' look like for each of them personally?" If the rep can't name the economic buyer, the technical evaluator, and a real champion—and articulate what each one wanted—they wrote the proposal half-blind. Forrester's work on champion development is clear that an engaged internal champion materially improves close rates, but only when that champion is actively coaching the rep on internal politics.

Layer 2: The Competitive Picture

Ask: "What was the prospect's real alternative—and why did it look attractive to them?" If the rep says "they didn't mention competitors," they didn't ask. Gong Labs research consistently shows that stronger reps engage competitive positioning earlier in the cycle rather than at the proposal stage. The proposal is far too late to discover the buyer already owns a Salesforce-native tool that covers most of what you do—for no incremental cost.

Layer 3: The Buying-Process Mismatch

Ask: "What step in their procurement process comes after your proposal, and who owns it?" If the rep doesn't know, they handed the deal to Legal and Security with no preparation. McKinsey's research on the modern B2B buying process emphasizes how much late-stage friction—data residency, SOC 2 Type II, multi-year terms—now lives downstream of the proposal. Reps who don't map that step are surprised by it every time.

The Decision Tree for Diagnosis

The Feedback Loop for Improvement

Real-World Example: The $500K SaaS Deal That Died at Proposal

A mid-market SaaS rep lost a $500K ARR deal and blamed the pricing page. The diagnostic told a different story:

The fix wasn't a better proposal. It was rebuilding the rep's discovery discipline around MEDDPICC so none of those four gaps could recur unnoticed.

The Tools That Surface These Gaps

The Highest-Leverage Follow-Up Questions

Once the layered diagnostic surfaces the gap, three sharper probes separate a real fix from a hopeful one.

The silent competitor. *"When the prospect passed, what did they say they were doing instead—another vendor, an internal build, or nothing?"* The most common proposal-stage "loss" is not a competitor at all; it's the buyer choosing to defer or work around the problem with what they already own. If the rep never asked *"What happens if you don't solve this in the next 90 days?"*, they never quantified the cost of inaction—and the proposal was competing against a zero-dollar option it could never beat. The fix is a standing alternatives audit in discovery: *"Who else are you evaluating, including doing nothing or building it yourselves?"*

The decision timeline. *"What date did the prospect commit to a decision, and how did you verify it with the full group rather than just your champion?"* Reps routinely accept an optimistic "we'll decide in two weeks" without pressure-testing it against budget gates, procurement, and legal review. When the proposal then sits for weeks, urgency decays and a new objection appears. The fix is a mutual action plan with a review meeting on the calendar *before* the proposal goes out: *"I'll send this on [date]—can we hold 45 minutes on [date + 5 business days] with the key stakeholders? If we can't book it now, this is going to drift."* A prospect who won't agree is giving the rep a clean disqualify-or-escalate signal.

The champion's hidden agenda. *"What did your champion personally risk by backing this—and how did you uncover it?"* A champion who says "I love this" can still refuse to spend political capital, especially if your solution displaces a tool another executive owns. If the rep only met supporters and never the likely detractors, the proposal rested on a fragile coalition. The negative-reverse probe—*"What would have to be true for you to NOT recommend us?"*—forces both rep and champion to map who could veto the deal and why, while there's still time to address it in the proposal itself.

FAQ

What if the rep says they had all the information they needed?

Probe deeper: *"What did the prospect say when you asked about their implementation timeline and the consequences of waiting?"* Reps often mistake surface-level answers for real qualification. The gap is usually that they never verified urgency or the cost of inaction—exactly the things that turn fatal at the proposal stage.

How can you tell if the loss was about price versus poor discovery?

Ask, *"Did you confirm the budget range before writing the proposal, or did you assume it?"* A rep who genuinely lost on price almost always failed to anchor the conversation on value or to surface the real budget ceiling first. Most "price" objections are a symptom of thin qualification, not a true price mismatch.

What question reveals whether the rep aligned with the buying committee?

Ask, *"Who did you speak with in the final decision group, and what did each of them say their top priority was?"* If the rep can't name at least three distinct stakeholders and their concerns, they likely built the proposal around one person's agenda—a leading cause of losses in multi-stakeholder deals.

How do you uncover whether the rep skipped competitive analysis?

Ask, *"What did you learn about the alternatives the prospect was weighing, and how did you position against them?"* A rep who can't describe the shortlist or their own differentiation probably submitted a generic proposal that never addressed the buyer's actual comparison criteria.

What question exposes a lack of urgency in the deal?

Ask, *"What specific event or deadline was driving a decision, and how did you confirm it with the prospect?"* If there's no concrete timeline or consequence of delay, the proposal almost certainly landed in the "nice-to-have" pile. Urgency is a qualification factor that makes or breaks late-stage momentum.

How can you tell if the rep failed to validate solution fit?

Ask, *"What did the prospect say when you asked them to describe how they'd measure success after rolling this out?"* A rep who never got the buyer to define success in their own words is guessing at the outcome—and guessing produces proposals that solve the wrong problem.

Bottom Line

The proposal stage is where weak discovery comes to die. Ask the rep one question that forces them to admit they didn't know something critical—budget, committee, competitor, or process—then use Gong, Clari, and MEDDPICC to turn that admission into a repeatable diagnosis loop. The proposal was never the problem; the missing qualification was.

flowchart TD A[Proposal lost] --> B{Rep can name a confirmed budget range?} B -->|No| C["Root cause: no budget discovery"] B -->|Yes| D{Rep can name every committee role?} D -->|No| E["Root cause: missing stakeholder map"] D -->|Yes| F{Rep knows the competitor's weakness?} F -->|No| G["Root cause: no competitive intel"] F -->|Yes| H{Rep knows the next procurement step?} H -->|No| I["Root cause: no process alignment"] H -->|Yes| J{Rep has active champion confirmation?} J -->|No| K["Root cause: no internal advocate"] J -->|Yes| L["Likely a real price or timing issue: escalate to leadership"]
flowchart LR A[Proposal loss] --> B[Rep answers the diagnostic questions] B --> C["Name the gap: budget, committee, competition, or process"] C --> D["Set one coaching action: role-play the missing discovery"] D --> E[Rep runs new discovery on the next deal] E --> F[Review the Gong recording for gap closure] F --> G[Track proposal-stage win rate over 90 days] G -->|Win rate improves| H[Standardize the behavior in the playbook] G -->|No change| I[Escalate to enablement for retraining]

Related on PULSE

Sources

*The real question isn't about the proposal—it's about the discovery that never happened.*

Download:
Was this helpful?  
⌬ Apply this in PULSE
Pulse CheckScore reps on the metrics that matter