Sales Process
Most discovery calls are status checks in disguise. Here are the 8 questions that separate real discovery from a pleasant conversation that leads nowhere — plus a comparison table and call scorecard for rep coaching.

You need all 8 answered before a deal can move past Stage 1. No exceptions.
Discovery is the most undervalued part of the B2B sales process. Founders and reps rush it because they want to get to the pitch — the part that feels like selling. But the pitch without discovery is guesswork. You're presenting solutions to problems you've assumed, not confirmed. The result is demos that feel good but don't move forward, proposals that get "we need to think about it," and deals that stall because there was never a real urgency or decision process behind them.
The 8 questions above are not a script — they're the information you need to have before you can honestly call a deal "qualified." When these answers live in the CRM as required fields, your pipeline becomes a reflection of reality rather than a record of optimism. And when discovery findings inform your proposals and demos, close rates increase because you're solving the buyer's actual problem instead of showcasing your product's best features. For a complete picture of how discovery fits into your sales motion, read the sales playbook guide →
Both feel like a productive meeting. Only one actually qualifies the deal.
I'm Louie Bernstein — I have 50 years in business experience, including 22 as a bootstrapped founder. My Fractional Sales Leadership business has been helping founders since 2017.
I shadow calls in the first 30 days of every engagement. The most common observation: reps are spending 40% of a discovery call on product features before they've confirmed that a real problem exists. The fix is a documented discovery framework that reps use consistently. When discovery answers become required CRM fields, deal quality improves immediately because reps can't advance phantom opportunities.
Book 45 minutes; run it in 30 if you get what you need. The trap most reps fall into is booking 30 minutes and using 20 of them on a product demo because they ran out of discovery time. Discovery must come first. Product comes after you've confirmed that a real problem exists, that the buyer has urgency, and that the buying team and budget are real. If you can't cover the 8 questions in a 30-minute call, you're covering too much ground per question — keep answers focused.
Both are qualification frameworks, not conversation scripts. BANT (Budget, Authority, Need, Timeline) covers the minimum. MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is more thorough and better suited to complex B2B deals. Neither framework tells you what questions to ask — they tell you what information you need to leave the call with. The 8 questions above are a practical implementation of the MEDDIC elements in a natural conversation flow.
Acknowledge the question and redirect: "I want to make sure any number I give you actually fits what you're trying to do — can I ask a few questions first so we're not wasting each other's time?" Most reasonable buyers accept this. If a prospect refuses to engage in discovery and only wants pricing, that's useful information: they're either in early evaluation mode (not ready to buy) or they're using you as a competitive benchmark for a deal they've already decided on.
Every answer from the 8 questions goes into the CRM as a required field before a deal can advance past Stage 1. "Trigger event," "economic buyer name and title," "cost of inaction," "decision process," and "timeline" should all be required text fields — not checkboxes. Checkboxes allow reps to mark things done without actually having the information. Text fields require the rep to write what they heard, which forces the conversation to happen and creates accountability to the data.
In 30 minutes I can review your current discovery process, identify the questions that are missing or being skipped, and build a qualification scorecard your team can use starting this week.