Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Structure discovery calls by mapping problems across four levels: Situation (what they do), Operational Problem (champion's complaint), Executive Problem (VP's concern), and Business Impact (C-level metric). This framework provides a logical path for your questions, moving from tactical to strategic issues.

Related Insights

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 generic discovery questions, present prospects with a framework of common problems (e.g., '15 GTM challenges'). This immediately turns the sales call into a collaborative working session, building credibility and accelerating the path to a deal.

Instead of asking broad questions like "What are your challenges?", present a menu of common problems: "Typically, frustrations are A, B, or C. Which is it for you?" This makes it easier for prospects to articulate their pain and guides them toward the specific problems your solution excels at solving.

Discovery has three levels: Situation (what they do), Operational Problem (a day-to-day annoyance for a champion), and Executive Problem (the business impact). Sales reps fail when they solve operational issues without connecting them to the executive-level "so what" that justifies a purchase.

The "Discovery Tree" maps problems in three layers: Situation (how they do it today), Operational Problem (daily annoyance), and Executive Problem (C-level risk, e.g., getting sued). Focusing only on operational issues leads to small deals; connecting them to executive-level risks is necessary to justify a large investment.

Move beyond just identifying a problem by asking for the specific story or "magic moment" the prospect realized it needed to be fixed. This uncovers the emotional context and visceral details of their pain, which is far more powerful for building a business case.

The bridge between a five-figure operational problem and a six-figure executive problem is often an emotional, painful story. Ask a "magic moment" question like, "When did you actually realize this was a problem?" to elicit the specific event or narrative that created the business impact and urgency.

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.

Avoid broad, open-ended questions like "tell me about your billing." Instead, provide two or three common problems your solution addresses and ask which resonates most. This keeps the conversation focused on your strengths and makes it easier for the prospect to provide a relevant answer.

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.