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.

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'.

Use a ruthlessly simple, repeatable process for zero-to-one sales: 1) Craft a 'pull hypothesis,' 2) Schedule five conversations, 3) Execute the conversations to discover demand, not to sell, and 4) Analyze the results to refine your hypothesis for the next sprint. This forces focus and rapid iteration.

Sales teams often treat discovery as a prerequisite to their demo, blindly searching for any 'problem' to pitch to. This wastes up to 90% of the call because they aren't listening for the customer's true, top-priority need, leading to sales *despite* the call, not because of it.

Founders often rush discovery to save time for a long demo. This is backward. When you precisely understand a customer's 'pull' (their top blocked priority), your pitch becomes hyper-relevant and can be delivered in 90 seconds, making the entire sales process more efficient.

Structure customer validation across two meetings. The first is framed as a request for help to validate an idea, building rapport without sales pressure. The second presents the honed solution based on their feedback, creating a natural and easier transition into a sales conversation with a trusted partner.

Shift the first meeting's goal from gathering information ("discovery") to providing tangible value ("consultation"). Prospects agree to meetings when they expect to learn something useful for their role or company, just as patients expect insights from a doctor.