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.

The discovery phase of a sales call isn't a generic interrogation or a prelude to a demo. Its only goal is to understand the customer's PULL: their specific Project, its Urgency, the other Options they've considered, and the Limitations of those options. Only then can you effectively position your product.

Instead of asking a long list of generic questions, identify the single trigger event or struggle common to your best customers. The entire discovery process then becomes asking prospects if they have that specific "pull." If not, they are disqualified, saving immense time and preventing wasted demos.

Standard discovery questions about 'pain points' are too broad. Instead, focus on concrete 'projects on their to-do list.' This reveals their immediate priorities, existing attempts, and the specific 'pull' that will drive a purchase, allowing you to align your solution perfectly.

To gauge a deal's urgency and qualify it, ask where the problem sits on their priority list. This forces them to state its importance out loud. It's psychologically difficult for someone to deprioritize something after they have verbally committed that it is a top priority.

In sales discovery, if you find yourself thinking 'that's useful,' you're likely gathering irrelevant context like team structure or company history. Truly useful information is identifying the customer's top blocked priority ('pull'), not accumulating interesting but unactionable facts.

Propose a link between your solution and a major company initiative. Even if your hypothesis is wrong, the prospect's correction will guide you directly to their most pressing business objective, which is more valuable than their polite agreement.

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.

Instead of asking about generic pain points, use the 'Pull' framework (Project, Unavoidable, Looking, Lacking) during discovery. The goal is to uncover the customer's single most important, blocked priority, which is the only thing they will act on.