Why Enterprise Deals Stall
You had a great first meeting. The prospect was engaged, asked smart questions, and said "this looks really promising." They asked for a proposal. You sent it. And then... silence.
Two weeks later, a polite email: "We have decided to pause this initiative for now. We will revisit next quarter."
What happened? In almost every case, the answer is the same: the discovery was incomplete.
You pitched a solution before you fully understood the problem. You addressed the symptoms they described without uncovering the root cause. You solved the problem they told you about without discovering the problem they did not know how to articulate.
Enterprise sales is not about having the best product or the best pitch. It is about asking the best questions. The company that understands the buyer's world most deeply is the company that wins the deal.
The Discovery Framework
This 12-question framework is adapted from the Confident Conversions methodology and refined through hundreds of B2B tech sales conversations. The questions are organized into four phases, each building on the previous one.
Phase 1: Situation (Questions 1-3)
The goal of Phase 1 is to understand the prospect's current world — before you try to change it.
Question 1: "Can you walk me through how your team currently handles [the process your product addresses]?"
This is an open-ended question that lets the prospect describe their reality in their own words. Resist the urge to jump in with "our product does that better." Just listen.
What to listen for:
- Manual steps that could be automated
- Handoffs between teams (every handoff is a potential failure point)
- Tools being used (especially spreadsheets — spreadsheets mean the real tool does not exist yet)
- Workarounds (workarounds reveal where the current solution fails)
Question 2: "How many people are involved in this process, and how much of their time does it take?"
This question starts to quantify the pain. You need numbers — not because you will use them in your pitch right now, but because they will form the foundation of your ROI case later.
What to listen for:
- Total hours spent per week/month
- Seniority of people involved (senior people's time is more expensive)
- Frequency of the process (daily, weekly, monthly)
Question 3: "What tools or systems are you using today for this?"
This reveals the competitive landscape — not just direct competitors, but also the "do nothing" and "do it manually" alternatives that you are really competing against.
What to listen for:
- Existing vendors (potential displacement opportunity)
- Internal tools (hard to displace because of sunk cost bias)
- Excel/manual processes (easier to displace but need clear ROI)
- Integration requirements (what needs to connect to what)
Phase 2: Pain (Questions 4-6)
Phase 2 digs into the consequences of the current situation. This is where you uncover the real pain — not the surface-level complaints, but the business impact.
Question 4: "What happens when this process breaks down or goes wrong?"
Every process fails sometimes. The consequences of failure reveal the true urgency of the problem.
What to listen for:
- Revenue impact ("we lose deals when X happens")
- Customer impact ("customers complain when Y is delayed")
- Compliance risk ("we got flagged in our last audit because of Z")
- Team impact ("people are burning out because of the workload")
Question 5: "If you could wave a magic wand and fix one thing about this process, what would it be?"
This question bypasses politics and practicality. It reveals the single biggest pain point — the one thing that matters most to this specific buyer.
What to listen for:
- The first thing they say (it is usually the real answer)
- Emotional language ("I am so frustrated by..." "It drives me crazy that...")
- Specificity (the more specific, the more real the pain)
Question 6: "What is this costing you — in time, money, or missed opportunities?"
This is the money question, literally. If they can quantify the cost, you have a painkiller opportunity. If they cannot, you may have a vitamin.
What to listen for:
- Hard costs (salary hours, vendor fees, penalties)
- Soft costs (employee turnover, morale, customer satisfaction)
- Opportunity costs (what could they be doing instead?)
- Growth constraints (is this limiting their ability to scale?)
Phase 3: Impact (Questions 7-9)
Phase 3 connects the pain to business outcomes. This is where you build the case for change — not change to YOUR product specifically, but change from the status quo.
Question 7: "If this problem were solved, what would that mean for your team and your business?"
This is a future-state question. It gets the prospect to paint a picture of life after the problem is solved. The more vivid this picture, the more motivated they will be to change.
What to listen for:
- Business outcomes ("we could handle 3x the volume without hiring")
- Team outcomes ("my engineers could focus on building, not maintaining")
- Personal outcomes ("I would stop getting calls at 2am about failed processes")
- Strategic outcomes ("we could enter new markets")
Question 8: "Who else in the organization would benefit if this were fixed?"
This question serves two purposes: it reveals additional stakeholders (important for enterprise deals) and it broadens the impact narrative.
What to listen for:
- Other departments affected
- Executive sponsors who care about the outcome
- End users who would benefit
- Customers who would see improvement
Question 9: "What has prevented you from solving this before now?"
This is a critical question. The answer reveals the real obstacles — which are usually not technical.
Common answers (and what they mean):
- "Budget" = The pain is not urgent enough to fund, or you need a stronger ROI case
- "Other priorities" = This is a vitamin, not a painkiller (or the painkiller framing has not landed)
- "We tried before and it failed" = Buying is high risk. You need to reduce perceived risk.
- "We did not know a solution existed" = Good news. But validate that the pain is real, not just theoretical.
- "Internal politics" = You need a champion who can navigate the organization
Phase 4: Decision (Questions 10-12)
Phase 4 is about the buying process. You need to understand how decisions get made so you can navigate the process.
Question 10: "If you decided this was worth pursuing, what would the decision-making process look like?"
This question maps the buying process. Enterprise deals are not won by convincing one person. They are won by navigating a process involving multiple stakeholders with different concerns.
What to listen for:
- Who makes the final decision
- Who influences the decision
- What approvals are required (budget, legal, security, IT)
- Typical timeline for decisions of this size
Question 11: "What criteria will you use to evaluate potential solutions?"
This is where you learn what matters. If you do not ask, you will guess — and you will probably guess wrong.
What to listen for:
- Technical criteria (integrations, security, performance)
- Business criteria (ROI, time-to-value, risk)
- Political criteria (executive preference, existing vendor relationships)
- Deal-breakers (hard requirements that disqualify vendors)
Question 12: "Is there anything that would make this a no — regardless of how good the solution is?"
This is the bravest question in the framework. It asks the prospect to tell you why they might NOT buy. Most salespeople are afraid to ask it. But it is the most valuable question because it surfaces objections early — when you can still address them.
What to listen for:
- Budget constraints ("we cannot spend more than €X")
- Timing constraints ("we cannot start until Q3")
- Political constraints ("our CEO just invested in a competing vendor")
- Risk constraints ("we will not be the first customer for an unproven product")
Using the Framework in Practice
Before the Call
Research the prospect. Understand their industry, their company size, their recent news. Look at their LinkedIn for the person you are meeting. Customize questions 1-3 based on what you already know.
During the Call
Follow the phases in order, but let the conversation flow naturally. If the prospect jumps to Phase 3 (Impact) on their own, go with it. You can circle back to Phase 1 later.
Take detailed notes. Not summaries — verbatim quotes. The prospect's exact words are your most powerful selling tool later.
After the Call
Within 24 hours, send a summary email:
- "Here is what I heard about your current situation: [Phase 1 summary]"
- "The main challenge seems to be: [Phase 2 summary]"
- "The impact of solving this would be: [Phase 3 summary]"
- "The next step we discussed is: [Phase 4 summary]"
This email accomplishes three things: it confirms your understanding (reducing miscommunication), it demonstrates that you listened (building trust), and it creates a written record that the prospect can forward to other stakeholders (expanding your influence in the deal).
The Most Common Discovery Mistakes
Mistake 1: Pitching during discovery. Discovery is for understanding, not selling. If you catch yourself describing your product, stop. Say "I will share more about how we might help, but first I want to make sure I fully understand your situation."
Mistake 2: Asking only closed questions. "Do you have this problem?" generates a yes/no. "Tell me about how you handle this" generates a story. Stories contain the details you need.
Mistake 3: Skipping Phase 2 (Pain). Many salespeople go from "here is the situation" directly to "here is our solution." Without Phase 2, you do not know if the pain is urgent enough to motivate action.
Mistake 4: Not asking Question 12. If you do not surface objections during discovery, they will surface during negotiation — when you have no time to address them.
How Hyperion Consulting Trains Sales Teams
At Hyperion Consulting, we train B2B tech sales teams on discovery frameworks that close enterprise deals faster. Our workshops combine the 12-question framework with live practice, role-playing, and real deal coaching.
Ready to improve your team's discovery skills? Book a free consultation to discuss sales training and coaching.
