What Is Discovery Call?
A structured conversation where SEs uncover the prospect's current state, pain points, technical requirements, and decision criteria.
Discovery is the most important skill an SE can develop. A great discovery call surfaces the information that shapes everything downstream: demo customization, POC design, competitive positioning, and value quantification. A weak discovery call means you are guessing at what matters, and guessing loses deals.
Good discovery calls follow a structure without feeling scripted. You are mapping the prospect's current state (what they use today), desired state (what they want), pain points (what is not working), and decision criteria (how they will choose a vendor). Each answer informs the next question.
Why It Matters for SEs
SEs who skip discovery or treat it as a formality end up delivering generic demos that do not resonate. The prospect sits through features they do not need, misses the ones they do, and leaves thinking your product is "fine but not differentiated." That outcome is almost always a discovery failure, not a product failure.
Discovery also qualifies the deal. If the prospect's requirements fall outside your product's strengths, it is better to know that in the first call than after a 30-day POC. SEs who qualify out of bad-fit deals early protect their time and their team's resources.
How SEs Use This
Prepare 8 to 12 open-ended questions before the call. Prioritize questions that reveal technical architecture, current pain, and decision process. Take detailed notes. Share a summary with the AE after the call so you are aligned on what you learned and what to present in the custom demo.
Separate the initial discovery from technical discovery. The first call covers business context and high-level requirements. The technical deep-dive (integrations, data flows, security) happens in a follow-up with the right technical stakeholders. Trying to cover everything in one call overwhelms the prospect and misses depth on what matters.
Frequently Asked Questions
How long should a discovery call last?
Thirty to 45 minutes is the sweet spot for an initial discovery call. Long enough to cover key questions, short enough that the prospect stays engaged. A follow-up technical discovery call can go longer.
What questions should SEs ask on a discovery call?
Focus on current state (what tools and processes exist today), pain points (what is not working), desired outcomes (what success looks like), and decision criteria (timeline, budget, stakeholders, competing vendors).
Should the AE or SE lead the discovery call?
The AE typically opens and covers business context. The SE takes over for technical requirements. The best teams prep together before the call and debrief after. Avoid two people asking redundant questions.