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

The $500K Deal That Died at the Proposal Stage

Consider a real scenario that plays out weekly in B2B sales organizations. A rep loses a $500K ARR deal in Q1. The rep blames the proposal's pricing page, claiming the CFO balked at the number. The sales manager, frustrated, accepts this explanation and moves on. The rep loses the next deal, and the next, and the pattern continues.

But when you dig deeper with the diagnostic question, the real story emerges. The rep never confirmed budget. The prospect's CFO had a hard cap of $300K, which would have been discovered with a single question in the first discovery call. The rep only spoke to the VP of Sales, missing the CIO entirely—and the CIO required a SOC 2 Type II report that the vendor didn't have. The incumbent competitor had already integrated the feature into their core product for free. And the rep didn't know the company required a 30-day proof of concept before any proposal could be evaluated.

The fix wasn't a better proposal. It was a complete re-education in qualification rigor. This scenario illustrates why the diagnostic question matters: it forces the rep to confront what they didn't know, rather than what they think went wrong. The proposal stage is where bad discovery dies, and the autopsy must start with the discovery process, not the document.

Why the Proposal Stage Is Where Qualification Failures Surface

The proposal stage acts as a pressure test for everything that came before it. When a rep sends a proposal, they're making a public claim that they understand the prospect's problem, have the right solution, and can deliver value at the stated price. If any of those assumptions are wrong, the proposal stage is where the deal collapses.

The mechanism works like this: during discovery, a rep gathers information about the prospect's needs, budget, timeline, and decision process. This information forms the foundation of the proposal. If the foundation is incomplete or inaccurate, the proposal will reflect those gaps—often subtly at first, then catastrophically when the buying committee reviews it.

Consider what happens when a rep skips budget discovery. They write a proposal with a price that's either too high or too low. If it's too high, the economic buyer dismisses it immediately. If it's too low, the prospect questions the quality or assumes there's a catch. Either way, the proposal fails, and the rep blames pricing rather than their own failure to ask the budget question.

The same dynamic applies to buying committee alignment. A rep who only speaks to one or two stakeholders writes a proposal that addresses their concerns but misses the priorities of the other 9–14 decision-makers involved in a typical B2B purchase. The proposal looks good to the champion but fails to answer the objections of the technical evaluator, the legal team, or the CFO. The deal stalls, then dies.

This is why the diagnostic question is so powerful: it forces the rep to confront the specific gaps in their discovery process. The answer reveals whether they knew the budget, mapped the committee, understood the competition, and aligned with the procurement process. If they can't answer these questions, the proposal was doomed from the start.

The Numbers Behind Proposal-Stage Losses

The statistics around proposal-stage losses paint a clear picture of where the problem lies. B2B sales cycles now average 8–12 months, with 11–16 decision-makers involved in each deal according to Gartner's research on buying committees. This complexity means more opportunities for misalignment and more chances for a proposal to miss the mark.

Research from Forrester shows that deals with identified champions close at significantly higher rates—but only if the champion is actively coaching the rep on internal politics. A champion who isn't engaged is little better than no champion at all. This suggests that the quality of stakeholder relationships matters more than the quantity of contacts.

McKinsey's analysis of late-stage deal losses found that a significant portion of losses in recent years were due to unaddressed procurement requirements. These include data residency concerns, security certifications like SOC 2 Type II, and multi-year pricing locks. Reps who don't discover these requirements during the discovery phase are setting themselves up for failure at the proposal stage.

Gong Labs data on winning and losing deals reveals that top-performing reps spend significantly more time on competitive positioning in early calls. They ask about alternatives, probe on the incumbent solution, and understand what the prospect would do if they did nothing. Reps who skip these conversations are operating blind when they write their proposals.

The practical ranges to keep in mind: 60–75% of lost deals have at least one alternative the rep never identified during discovery. Only 20–40% of tenured sellers can accurately articulate the economic and emotional urgency of their lost deals. Reps who can name 5+ stakeholders and their specific objections have a 40–60% higher close rate at the proposal stage. These numbers suggest that proposal-stage losses are rarely about the proposal itself—they're about the discovery that never happened.

The Three Layers of Diagnostic Inquiry

When you're coaching a rep who consistently loses deals at the proposal stage, you need a structured approach to diagnosis. The three-layer framework provides that structure, moving from discovery gaps to competitive awareness to process alignment.

Layer 1: The Discovery Autopsy

Start with the fundamentals. Ask the rep: "What specific budget range did the prospect confirm in writing before you wrote the proposal?" If the answer is "they said it wasn't a problem" or "we assumed," the deal was dead on arrival. Budget confirmation isn't a nice-to-have; it's the foundation of any viable proposal.

Next, ask: "Who on the buying committee did you speak with, and what did each person's 'win' look like?" If the rep can't name the economic buyer, technical evaluator, and champion, they're writing a proposal blind. Each stakeholder has different priorities, and a proposal that doesn't address them will fail.

Layer 2: The Competitive Landscape

Move to competitive awareness. Ask: "What is the incumbent doing that we aren't, and why did the prospect say they're considering them?" If the rep says "they didn't mention competitors," they didn't ask. The proposal stage is too late to learn that the buyer already has a solution that does 80% of what you offer.

This layer also includes the "do nothing" option. Many proposal-stage losses stem from the prospect deciding the pain isn't acute enough to justify change. A rep who doesn't understand this dynamic is building proposals for prospects who are shopping rather than buying.

Layer 3: The Buying Process Mismatch

Finally, examine process alignment. Ask: "What step in their procurement process comes after our proposal, and who owns that step?" If the rep says "I don't know," they've handed the deal to the legal and security teams without preparation.

This includes understanding the prospect's internal review timeline, their vendor evaluation criteria, and any compliance requirements that could derail the deal. A proposal that arrives after the committee has already met is just a formality, not a contender.

Trade-offs and Alternatives in the Diagnosis Approach

The diagnostic question approach has trade-offs that RevOps leaders should understand. On one hand, it's efficient—one question can reveal the root cause of a proposal-stage loss. On the other hand, it requires the rep to be honest about their own failures, which isn't always comfortable.

An alternative approach is to use deal review tools to surface gaps automatically. Tools like Gong and Clari can flag deals where budget isn't documented, where next steps are vague, or where win probability is declining. These tools provide objective data that can supplement the diagnostic conversation.

For example, Gong's deal risk features can flag proposals sent without documented next steps. You can ask the rep: "Gong says this deal had a 23% win probability. What did you see that the AI missed?" This shifts the conversation from blame to analysis, which can be more productive.

Clari's forecast category changes are another useful signal. A deal that moves from "Commit" to "Best Case" to "Omitted" in two weeks is a proposal-stage loss in the making. Asking the rep what signal they missed that Clari caught can reveal blind spots in their qualification process.

The trade-off is between speed and depth. The single diagnostic question is fast and can be used in any conversation. The tool-based approach is more thorough but requires access to the right technology and the discipline to review it regularly. Most RevOps teams benefit from using both approaches in combination.

The Pre-Proposal Audit Question That Prevents Losses

Beyond diagnosing losses after they happen, RevOps leaders should implement a pre-proposal audit that catches gaps before the proposal goes out. This shifts from reactive diagnosis to proactive prevention.

The key question to ask before any proposal is sent: "Before you write this proposal, did you explicitly ask each decision-maker, 'What would have to be true for you to choose us over doing nothing or a cheaper alternative?'—and if so, what did they say?"

This question reveals whether the rep is validating the deal's economic and emotional urgency versus just collecting feature requirements. Buyers have more internal tools and more external options than ever before. A rep who skips this question is likely building proposals for prospects who are shopping rather than buying.

The honest range of reps who can accurately answer this question is 20–40% of tenured sellers. The rest are guessing at motivation. If the rep can't recall specific, candid answers from multiple stakeholders, the real issue is that they never earned the trust required for honest feedback. That's a relationship-building gap, not a proposal-writing gap.

Implementing this audit as a standard part of the proposal process can prevent losses before they happen. It forces reps to validate their assumptions and gives RevOps leaders visibility into potential deal risks before the proposal is sent.

Common Pitfalls in Diagnosing Proposal-Stage Losses

Even with the right diagnostic question, RevOps leaders can fall into traps that undermine the coaching process. Understanding these pitfalls helps you avoid them.

Pitfall 1: Accepting the Rep's Surface-Level Explanation

When a rep says "the price was too high," it's tempting to accept that explanation and move on. But price is rarely the root cause—it's a symptom of a deeper issue. The rep didn't discover the budget, didn't understand the value perception, or didn't position the solution against alternatives. Push past the surface explanation to find the real gap.

Pitfall 2: Focusing on the Proposal Document

It's natural to review the proposal itself for issues—formatting, pricing structure, value proposition. But the proposal is a reflection of the discovery process. A poorly formatted proposal might lose a deal, but a well-formatted proposal won't save a deal that was built on faulty assumptions. Focus on the discovery, not the document.

Pitfall 3: Treating Every Loss the Same

Not all proposal-stage losses have the same root cause. One deal might fail due to budget misalignment, another due to missing stakeholders, a third due to competitive pressure. Using the diagnostic question to identify the specific gap for each deal is more effective than applying a generic fix to all losses.

Pitfall 4: Ignoring the Champion's Role

A champion who isn't actively coaching the rep on internal politics is little better than no champion at all. If the rep can't describe what the champion is doing to advance the deal internally, the champion isn't effective. This is a relationship quality issue, not a quantity issue.

Pitfall 5: Skipping the Feedback Loop

Diagnosis without action is just analysis. After identifying the gap, create a specific coaching action, roleplay the discovery conversation, and review the next deal's discovery call for improvement. Measure the proposal-stage win rate over 90 days to see if the coaching is working.

The Competitive Landscape Calibration Question

Another powerful diagnostic question focuses on competitive awareness. Ask the rep: "Name the three alternatives each of your lost prospects seriously evaluated—including the option to build internally or do nothing—and rank them by how often each beat you. What did those alternatives offer that you didn't?"

This forces the rep to admit whether they even knew what they were competing against. Many proposal-stage losses stem from reps assuming they're competing against a named competitor when they're actually losing to:

• An internal AI tool that the prospect's IT team built for free
• A cheaper, less-feature-rich SaaS that integrates with their existing stack
• The status quo, because the pain wasn't acute enough to justify change

If the rep can't name three alternatives with specific reasoning, they're operating with blind spots. The honest range is that 60–75% of lost deals have at least one alternative the rep never identified during discovery. This is a competitive intelligence failure, not a proposal failure.

The fix involves training reps to ask about alternatives in every discovery call. Questions like "What else are you considering?" and "What would you do if you didn't choose a solution like ours?" surface competitive information early. Reps should also research the prospect's industry and likely alternatives before the first meeting.

The Buying Committee Pulse Question

The third diagnostic question focuses on stakeholder mapping. Ask the rep: "For the last deal you lost after sending the proposal, can you name every person who would have to sign off—including their title, their primary concern, and whether they ever spoke to you directly?"

This question diagnoses whether the rep mapped the full buying committee or only the champion. The average B2B purchase involves 11–16 stakeholders, many of whom never meet with sales reps. If the rep only spoke to 2–3 people, they built a proposal that only addresses a fraction of the concerns.

The real issue is often that the rep didn't earn access to the full committee, or they relied on a champion to "sell internally" without equipping them with the right materials. Reps who can answer this question with 5+ named stakeholders and their specific objections have a 40–60% higher close rate at the proposal stage.

Those who can't are losing because they never understood who was actually deciding—and what those invisible decision-makers cared about. This is an access and stakeholder strategy problem, not a proposal content problem.

The fix involves teaching reps to ask for access to the full committee early in the sales process. Questions like "Who else will be involved in this decision?" and "Can you introduce me to the technical evaluator?" expand the rep's access. Reps should also create stakeholder maps that track each person's concerns, influence level, and engagement status.

The Feedback Loop for Continuous Improvement

The diagnostic question is only valuable if it leads to action. RevOps leaders should implement a structured feedback loop that turns diagnosis into improvement.

The loop starts with the proposal loss. The rep answers the diagnostic questions, identifying the specific gap in their discovery process. This gap becomes the focus of a coaching action, typically a roleplay of the discovery conversation with an emphasis on the missed area.

The rep then runs a new discovery with the next prospect, applying the coaching. The RevOps leader reviews the discovery call recording—using tools like Gong—to verify the gap is closed. This review should focus on whether the rep asked the right questions, documented the answers, and adjusted their approach based on what they learned.

After 90 days, measure the proposal-stage win rate to see if the coaching is working. If the win rate improves, standardize the new behavior in the sales playbook. If it doesn't improve, escalate to enablement for retraining.

This feedback loop ensures that diagnosis leads to action, and action leads to measurable improvement. It also creates a culture of continuous learning, where proposal-stage losses are seen as opportunities for growth rather than failures to be hidden.

Related Questions

What question reveals if the rep skipped discovery entirely?

Ask: "What did you learn in the first meeting that made you confident this deal was real?" If they can't name a specific budget range, decision timeline, or pain point that the prospect explicitly owns, they likely wrote a proposal based on assumptions rather than validated needs.

How can you tell if the rep failed to map the buying committee?

Ask: "Who else did you speak with besides your main contact, and what did each person tell you about their priorities?" A rep who only talked to one person usually misses the hidden influencers or economic buyers who kill deals late.

What question exposes a mismatch between the solution and the prospect's actual priority?

Ask: "What was the prospect's #1 business objective when you first met, and how did your proposal directly tie to that goal?" If the rep can't connect their solution to a top-three priority, they built a solution for a problem that may not be urgent.

How do you check if the rep ever confirmed budget before writing?

Ask: "What exact budget range did the prospect share, and how did your proposal fit within it?" Reps who lose at the proposal stage often never asked about budget, assuming it would be fine.

What question uncovers whether the rep ignored competitive alternatives?

Ask: "What other options did the prospect say they were considering, and how did you position your proposal against them?" If the rep can't name at least two alternatives—including the "do nothing" option—they likely wrote a proposal in a vacuum.

FAQ

What question reveals if the rep skipped discovery entirely? Ask: "What did you learn in the first meeting that made you confident this deal was real?" If they can't name a specific budget range, decision timeline, or pain point that the prospect explicitly owns, they likely wrote a proposal based on assumptions rather than validated needs. Most reps who lose at the proposal stage never confirmed the problem was worth solving.

How can you tell if the rep failed to map the buying committee? Ask: "Who else did you speak with besides your main contact, and what did each person tell you about their priorities?" A rep who only talked to one person usually misses the hidden influencers or economic buyers who kill deals late. In committee-heavy environments, a proposal that doesn't address each stakeholder's criteria is dead on arrival.

What question exposes a mismatch between the solution and the prospect's actual priority? Ask: "What was the prospect's #1 business objective when you first met, and how did your proposal directly tie to that goal?" If the rep can't connect their solution to a top-three priority the prospect explicitly stated, they built a solution for a problem that may not be urgent. Most losses happen because the proposal solved a nice-to-have, not a must-have.

How do you check if the rep ever confirmed budget before writing? Ask: "What exact budget range did the prospect share, and how did your proposal fit within it?" Reps who lose at the proposal stage often never asked about budget, assuming it would be fine. Without a clear number, the proposal is either too expensive or too cheap, and either way it gets dismissed.

What question uncovers whether the rep ignored competitive alternatives? Ask: "What other options did the prospect say they were considering, and how did you position your proposal against them?" If the rep can't name at least two alternatives—including the "do nothing" option—they likely wrote a proposal in a vacuum. The real issue is often that the prospect already has a cheaper or simpler internal fix.

How can you tell if the rep lost control of the timeline? Ask: "What specific date did the prospect say they needed a decision by, and how did you ensure your proposal arrived before their internal review deadline?" Reps who lose at the proposal stage frequently deliver late or fail to align with the prospect's buying process. A proposal that lands after the committee already met is just a formality, not a contender.

Sources

• Gong Labs: The Anatomy of a Won Deal
• Gartner: B2B Buying Committees Now Average 11-16 Members
• Forrester: The ROI of Champion Development
• McKinsey: The New B2B Buying Process
• SaaStr: How to Fix Underperforming Sales Reps
• Clari: Deal Risk Signals in the Age of AI
• MEDDPICC Framework: Command of the Message

Related on PULSE

• [How can RevOps use AI in the funnel to identify stalled deals before the buying committee loses interest?](/knowledge/q16667)
• [What's the right way to coach a rep whose calls sound great but whose deals consistently slip?](/knowledge/q1110)
• [How do you coach a sales rep who's consistently missing quota?](/knowledge/q13971)
• [Which 2027 AI tools successfully automate proposal generation for complex buying groups?](/knowledge/q16534)
• [How Do I Get My AEs to Update the CRM Consistently?](/knowledge/q16024)
• [How is AI changing RFP and proposal automation in 2027?](/knowledge/q13049)