When a prospect gets bogged down in niche technical requirements, ask how they accomplish that task today. Often, they'll admit they don't have a solution, which reframes their "must-have" requirement into a "nice-to-have." This prevents you from getting sidetracked defending a non-critical feature.
Prospects often describe wants (e.g., "a more efficient system"), which are not true problems. Asking about the motivation behind their desire forces them to articulate the underlying pain that actually drives a purchase decision.
Instead of only showing your solution, ask the prospect to share their screen and walk through their current workflow. This "reverse demo" vividly exposes flaws in their system, making the need for your solution painfully obvious to everyone on the call, as evidenced by a crashing Excel file.
If a prospect is unresponsive to discovery questions, describe the specific priorities and blockers of similar customers. Framing case studies around their demand ('they were trying to do X but were blocked by Y') can prompt recognition and help the prospect articulate their own 'pull'.
When a prospect asks if your product does something, it’s a confession that their current process is failing. Instead of just answering "yes," use it as a discovery opportunity. Ask, "How do you currently do that today?" to uncover the underlying problem and tailor your demo to solve it directly.
Instead of asking broad, open-ended questions about pain, provide prospects with a multiple-choice list of the common problems you solve. This steers the conversation toward your solution's strengths and prevents wasting time on issues you can't address.
When a prospect gives one-word answers, repeatedly and politely ask "Can you give me an example of that?" or "Can you be more specific?" This simple loop forces them to move from vague statements to the concrete details needed to build a case for your solution.
Resist the instinct to explain what a feature is and does. Instead, first explain *why* it was built—the specific business problem it solves and why that's relevant to the prospect. This framing turns a feature walkthrough into a personalized 'test drive'.
Instead of reacting defensively when a customer mentions a competitor, use it to probe their underlying needs. Asking 'What do you like about it?' helps differentiate between a critical feature gap ('the steak') and a superficial want ('the sizzle'), keeping you focused on solving real problems.
To sell effectively, avoid leading with product features. Instead, ask diagnostic questions to uncover the buyer's specific problems and desired outcomes. Then, frame your solution using their own words, confirming that your product meets the exact needs they just articulated. This transforms a pitch into a collaborative solution.
When a prospect describes an operational pain, present two common, high-impact business consequences you've seen elsewhere. This frames the problem in executive terms and guides them toward revealing a more significant issue, rather than hoping they connect the dots themselves.