A buyer joins a call and says, “We’re trying to understand why expense approvals keep getting stuck.” You have a polished demo ready. You also don’t yet know what “stuck” means. If you start clicking through every feature, you may spend the first ten minutes answering a question nobody asked.
Now imagine a different opening: the buyer has already described the approval problem and asked to see how your product handles it. Another long round of discovery could feel like a detour. The first minute is a chance to agree on which conversation you’re having.
Start discovery with a real moment
When the problem is still fuzzy, ask for an event rather than a verdict. “Walk me through the last time an approval got stuck” gives the buyer somewhere concrete to begin. Who submitted it? What happened next? Where did they notice the delay?
Follow their account before reaching for a list of prepared questions. If they mention that a manager was away, ask how the team found out. If they say the receipt was missing, ask what the employee had to do next. A specific story can reveal the work around the delay as well as the delay itself.
Leave room for an unexciting answer. Perhaps the delay happens twice a year and the team is comfortable with it. Discovery is useful when it helps both sides decide what matters, including what doesn’t need fixing.

Make a demonstration specific
If the buyer came to see a solution, acknowledge what you know and ask permission to show the relevant part: “You said the handoff is where things stall. Can I show you that step first?” Then demonstrate that step, slowly enough that they can compare it with their own process.
Pause for a question that invites comparison: “How would that fit with the way approvals work today?” A buyer may point out a policy, an exception or another person who needs to be involved. That is more useful than treating a nod as agreement. You can return to the broader product once you know what they want to see next.
A demonstration isn’t a promise that every edge case is solved. If you don’t know whether a particular approval rule is supported, say so and agree how you’ll check. Keep the unanswered question in your follow-up.
Choose the opening together
Sometimes the invitation is vague: “We’d love to learn more.” A brief choice can save both sides from guessing. “Would it be more useful to walk through what’s happening today, or should I show you the approval flow and we can react to it?” Listen to the answer, then confirm how much time you have.
There may be several people on the call who want different things. One person may own the process, another may have requested a demo, and a third may be checking technical requirements. Ask whose perspective is missing and make a small plan: ten minutes on the current workflow, a focused demonstration, then questions. Adjust it if someone raises a more urgent need.
What brought the buyer to the call?
“Our approvals keep getting stuck.”
- You
- “Take me back to the last one. When did you first notice it hadn’t moved?”
- Buyer
- “On payday. The manager who usually signs was on leave.”
- You
- “How did you find out who could sign in their place?”
“Can you show us how a backup approver works?”
- You
- “Let’s take that same expense report. Which part do you want to see from the backup’s side?”
- Buyer
- “How they know there’s something waiting for them.”
- You
- “Let’s start with what they see when they sign in.”
Notice when it’s time to switch
Discovery and pitching aren’t separate boxes that must fill an entire meeting. A buyer’s example may make a short demonstration useful; a demonstration may expose an assumption worth exploring. Name the transition: “That sounds different from what I imagined. Could we step back and map that handoff?”
Before the call ends, reflect back the problem in the buyer’s words, check whether you have it right, and agree on a next step. If that step is another conversation rather than a sale, that’s still a clear outcome. The aim is to leave with a shared understanding, not just a completed slide deck.