Mastering the Discovery Call: The Foundation of Every Great SE Demo

Published May 26, 2025

Author: Sales Engineer Direct Founder

Great demos might get all the glory, but every great demo is built on an even better discovery call. For a Sales Engineer, the discovery call isn't a perfunctory box to check – it's often the moment where the deal is won or lost.

In fact, how you run the discovery will set the trajectory for the entire deal – it shapes how you'll present your solution, what objections are likely to arise later, and even how fast the deal advances. Experienced SEs treat discovery as the foundation of their sales strategy, investing as much skill and care here as in the demo itself.

Focus on the Real Pain

The first priority in a discovery call is to identify the real business pain points behind the prospect's requests. Prospects might come in asking for specific features or a quick demo, but an advanced Sales Engineer looks deeper: what core problem are they trying to solve?

No one buys software just because it's shiny and new – they buy it to fix a problem. So think of yourself like a doctor diagnosing an illness, rather than a rep pushing a prescription. Your job in discovery is to uncover the illness (the pain) before you prescribe the medicine (your product).

This often means reading between the lines. A prospect may say, "We're getting by with our current process," when in reality "getting by" is code for it's a nightmare but I don't want to admit it. It's on you to gently dig into those hints and find out what's really broken.

In fact, the best Sales Engineers often surface needs or challenges the customer hasn't even fully articulated yet. By homing in on the underlying pain – the wasted hours, lost revenue, frustrated end-users, or strategic risk – you set the stage for a far more compelling conversation.

Ask Layered, Open-Ended Questions

How do you uncover those deeper issues? By asking smart, open-ended questions – and then asking more follow-up questions that peel the onion further. A basic question like, "What's your biggest challenge right now?" is just a start.

When they answer, dig deeper: "What have you tried so far to fix that, and what's still not working?" or "If we could wave a magic wand and solve this tomorrow, what would success look like for you?" Each answer should prompt another "why" or "how" question, drilling down from surface symptoms to root causes.

These layered questions move the conversation beyond the obvious and into the real meat of the matter, often revealing unspoken desires or hidden opportunities. Crucially, you need to let the prospect talk freely – if you're doing most of the talking, something's off.

Make it a conversation, not an interrogation. The goal is to get the customer talking a lot about their world. Studies have shown that the most successful discovery calls tend to explore around three or four major problem areas and involve roughly 11–14 total questions in a natural back-and-forth – enough to be thorough without making the prospect feel grilled.

Top-performing SEs sprinkle their questions throughout the call, rather than reading down a checklist all at once. It should feel like a friendly game of tennis – question, answer, dig deeper, and so on – not a rigid Q&A session. When done right, the prospect will feel heard and engaged, not quizzed.

Pro Tip: End with Individual Priorities

As you build this dialogue, be both curious and methodical. One technique many great SEs use toward the end of discovery is to ask each stakeholder for their top priority in the upcoming demo. For example: "Before we wrap, I'd love to hear from each of you – what is the one thing you want to see the most in our demo? Let's go around the room."

By explicitly giving everyone a chance to speak up, you ensure no important insight or expectation is left unspoken. Maybe the IT lead cares most about integration, while the VP cares about reporting analytics. By gathering this info, you now know exactly what each person will be looking for when you demo.

Document Everything with Precision

Advanced discovery isn't casual chit-chat; it's a targeted exploration, and it produces a goldmine of information – provided you capture it. Take diligent notes on every key point the prospect makes. And don't just jot down the gist – write down the exact words and phrases they use for their pain points and goals.

If the prospect says, "Our team spends five hours a week merging spreadsheets and it's super frustrating," note that verbatim. Those exact words ("five hours a week," "super frustrating") are clues to what really matters to them. Later, when you replay those points – "You mentioned the team spends about five hours a week on manual spreadsheet work…" – they'll know you were listening.

Precise documentation also lets you quantify the pain, which can be incredibly powerful. For instance, if you learn that 10 sales reps each waste 5 hours a week on a broken process, that's 50 hours weekly. Do the math: that's ~2,600 hours a year, equivalent to perhaps $125k+ in productivity cost.

When you reflect that back ("This inefficiency is costing around $130,000 a year in lost time"), the problem becomes crystal clear and urgent. By writing everything down, you won't forget these nuggets, and you can strategize with your Account Executive later using hard data and exact quotes.

It also ensures that when you transition into the demo or proposal phase, nothing falls through the cracks. Great SEs often have a cheat sheet of the customer's own words and metrics in front of them during the demo – and it shows.

Reframe and Confirm the Problem

Part of your role in discovery is to synthesize what you've heard and play it back to the prospect in a way that brings clarity. After you've dug into their challenges, take a moment to summarize and reframe the problem to ensure you and the customer are on the same page.

For example, you might say, "So, if I understand correctly, the core issue is that because your data isn't up to date and your team is stuck doing manual entries, they're losing precious selling time and even contacting customers with outdated info – which ultimately puts your revenue target at risk. Is that fair to say?"

In one swoop, you've taken a tactical pain ("manual data entry") and framed it as a strategic business problem ("risk to hitting revenue target"). That kind of reframing is incredibly powerful. The prospect will often respond with relief: "Exactly. That's our struggle."

In that moment, you've shown that you get it. You've articulated their pain even more clearly than they did. When you can capture a customer's problem better than they can describe it themselves, they will trust you implicitly. You've essentially put words to the pain they felt, and now you both are aligned on what needs solving.

This clarity is gold for both of you – it means you can now tackle the solution as partners. Don't rush past this step; confirming and reframing the problem ensures that you and the prospect agree on what really needs to be addressed. It also sets you up to knock the demo out of the park, because you're zeroed in on what matters most.

When It's Demo Time, Use What You Learned

At this point, a well-run discovery call has armed you with everything you need to deliver an effective, tailored demo. Think of discovery as loading the ammunition into your demo "weapon" – the insights and pain points you've gathered become the exact targets your demo will hit.

Instead of a generic feature tour, you'll show the specific capabilities that solve the exact pains the prospect described. Every click, every screen, every use-case you present should tie back to something you heard in discovery. The demo stops being about your product and becomes about their solution.

(This is exactly how we framed our approach in the Demo Guide – focus on the customer's needs and tell a story in their language.)

When a prospect sees their own problems being solved in real time, it's incredibly compelling. They nod along because you're replaying their story, not just showing off software. A discovery-driven demo also differentiates you from competitors who might still be giving canned demos. You're showing that you listened and you care about what they asked for. That builds trust and enthusiasm.

Often, prospects will say during your demo, "I'm so glad you showed this – this is exactly what we were looking for." That's when you know your discovery truly paid off.

Discovery Accelerates Deal Velocity

Moreover, great discovery doesn't just make for a targeted demo – it also makes objection handling and next steps much smoother. By the time you've done discovery, you should already know the likely objections or concerns. Maybe the prospect hinted at worries about integration complexity, or budget limitations, or user adoption challenges.

Because you took note of these, you can proactively address them either during the demo ("You mentioned your existing system is clunky – you'll see here how we integrate seamlessly, which should alleviate that concern") or in the discussion right after. You're essentially defusing objections before they fully surface, using the information the prospect themselves gave you.

And if an objection does come up, you're not caught off guard – you can say, "Right, you raised X earlier, and here's how we deal with it…" instead of scrambling. This not only makes you look on top of things, it gives the customer confidence that nothing will derail the process. By covering bases early, you avoid unpleasant surprises late in the game.

All of this leads to something every Sales Engineer and salesperson craves: deal velocity. A thorough discovery accelerates the deal in several ways. First, the prospect's team is bought in and enthusiastic because they feel understood – you've addressed their needs head-on, so there's less back-and-forth clarifying what they want.

Second, your demo and proposal hit the mark on the first try, avoiding long revision cycles. And third, stakeholders high up the chain get value sooner, because your champion can relay that "these folks really understand our situation." When the solution aligns perfectly with the identified pain and there's clear agreement on value, the whole sales process just moves faster. There's momentum instead of friction.

In the end, a great discovery call doesn't lengthen the sales cycle – it shortens it. It's not a delay before the "real selling" starts; it is where the real selling starts. By the time you're done, the prospect should be nodding not just about the problem, but about the path to the solution. And that makes everything that follows – the demo, the business case, the negotiations – fall into place more easily.

The Foundation of Sales Engineering Excellence

Mastering the discovery call is arguably one of the most important skills in a Sales Engineer's toolkit. It's what transforms you from a generic presenter into a trusted advisor. If you're an aspiring SE, you've likely heard us harp on the importance of listening and translating customer needs in our posts on how to become a Sales Engineer – and discovery is exactly where those abilities shine brightest.

And if you're already an experienced SE, sharpening your discovery techniques is a sure way to elevate your game from good to great. The beauty is that these advanced discovery strategies don't just help you on sales calls; they're also incredibly useful in other arenas.

For instance, if you're interviewing for an SE role, demonstrating that you know how to run a thoughtful discovery (instead of just jumping straight into a demo) can really set you apart – something we explore in our guide on common Sales Engineer interview mistakes.

The bottom line: nail the discovery call, and everything else in the sales process gets easier. Great discovery fuels great demos, smoother objection handling, and faster deals. It's the secret sauce to being not just a Sales Engineer who demos a product, but one who truly drives the sale forward.

Master Your Discovery Skills

Want to practice these discovery techniques? Join our community of Sales Engineers and connect with companies that value strategic thinking and customer-first approaches.

πŸŽ‰ FREE for sales engineers looking for a new job πŸŽ‰

Create Your Profile