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.

Structure discovery into two distinct conversations for maximum effect. The first meeting should focus exclusively on uncovering the customer's blocked goals (demand), without mentioning a product. Use the second meeting to validate if a high-level solution sketch (supply) gets ripped out of your hands.

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.

Customers use the same words and grammar as you, but the meanings are often different. This creates a dangerous illusion of understanding, leading you to build the wrong product. You must actively translate their language, which is a mix of demand, supply, and noise.

Go beyond simple customization and build proposals using the customer's own words and lingo from discovery calls. Reflecting their exact language back to them proves you listened and understood their unique pain. This makes them feel heard and emotionally connects them to the solution, creating urgency.

When customers talk, trust their articulation of what they're trying to accomplish (demand) and why their current tools fail (supply problems). However, completely disregard their suggestions for what product or feature you should build (supply they want). That is your job to design, not theirs.

To create resonant content, move beyond guessing customer problems. Analyze transcripts of past sales calls with an AI tool to identify recurring pain points, common questions, and the exact language your audience uses to describe their challenges.

Since "blocked" demand is unobservable, you must ask questions that reveal it indirectly. Asking "If I spent $100M to build something for you, what problem would it solve?" forces customers to consider their most critical, unaddressed needs, bypassing their current behaviors and revealing latent demand.

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.