Latest / Sales Leadership with Fexingo: Quota Carriers, Sales Managers, and Revenue Teams / How Sales Reps Can Handle a Prospect Who Keeps Asking for More Demos
Transcript
- Lucas: So you've done a great demo. The prospect seemed engaged. They asked smart questions. And then they say, 'Can you show that again? Maybe include the finance team next time.' Or, 'Could you walk through the integration module one more time?' Luna: And you're thinking — didn't we just cover that? But you smile and book another demo. Lucas: Right. And then after that demo, they ask for another. Maybe with a different stakeholder. Suddenly you're three demos deep, no contract in sight, and you're starting to wonder if this prospect is ever going to buy. Luna: This is one of the most frustrating patterns in sales, especially for complex B2B deals. I've been there. I once had a prospect who asked for five demos over six weeks. Lucas: Five? And did they eventually close? Luna: They did, but only after I finally got them to admit they were comparing us against an incumbent vendor they'd used for a decade. The demos were a stall tactic while they built internal consensus. Lucas: That's the key insight. Repeated demo requests are rarely about needing more information. They're usually a symptom of something else — decision paralysis, hidden competition, or a lack of clear decision criteria. Luna: So how do you handle it without coming across as pushy or dismissive? Lucas: I use what I call the 'Demo Convergence' framework. It's a three-step process. First, you establish a demo boundary upfront. Second, you diagnose the real reason for the request. Third, you pivot to a different engagement model if needed. Luna: Let's unpack that. What does a demo boundary look like in practice? Lucas: Before the first demo, you set expectations. Something like: 'To make sure this demo is as productive as possible, I'd like to understand what specific outcomes you're looking to achieve. Then I'll structure the demo around those criteria. After that, we'll be well positioned to discuss next steps.' Luna: So you're framing the demo as a step toward a decision, not an infinite loop. Lucas: Exactly. And if they ask for a second demo, you don't just say yes. You pause and ask, 'What specifically do you feel is missing from what we showed last time? I want to make sure we address that, and also understand how this fits into your evaluation timeline.' Luna: That forces them to articulate the gap. Often they can't, which tells you the request isn't about information. Lucas: Right. If they say, 'I just want my CFO to see it,' then you can say, 'Great, let's schedule a call where we focus on the CFO's top three concerns. And after that, we should be able to move toward a proposal.' That sets a natural endpoint. Luna: What if the real issue is that they're comparing you to a competitor and using demos as a way to keep you engaged while they evaluate? Lucas: That's where the diagnosis step is critical. I'll ask directly but gently: 'Just to help me focus the next demo, could you share what other options you're considering? I want to make sure I highlight where we differ.' Most prospects will tell you — especially if you've built trust. Luna: And if they still won't commit to a timeline? Lucas: Then you pivot to a trial or proof of concept. Offer a limited engagement where they can use the product with a small team for, say, 30 days. That changes the dynamic from watching a demo to actually using the product. It's harder to stall when the software is in their hands. Luna: I've used that approach. It works because it shifts the burden of proof from you to the product. They either realize the value and buy, or they don't — and you've saved yourself from demo number six. Lucas: Exactly. And here's the thing — if today was actually useful to you, the way these episodes stay ad-free is through listener support. If you've gotten value from this conversation or any previous one, you can help keep it going at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to say 'this matters to me,' and it lets us keep focusing on practical stuff like this without any corporate sponsors. Lucas: Appreciate that. Now, let's talk about the committee demo — that's a special case of the repeated demo problem. Luna: Where you've got multiple stakeholders who each want their own walkthrough. Lucas: Right. One rep I know recently had a prospect with seven stakeholders across IT, finance, and operations. They wanted seven separate demos. He said, 'I'm happy to do that, but let's do it in one session where all decision makers are present. That way everyone hears the same information and we can address cross-functional questions together.' Luna: Did they agree? Lucas: They pushed back, saying it would be too hard to schedule. So he offered to do a 30-minute pre-call with each stakeholder to understand their specific needs, then a single two-hour deep-dive with everyone. That collapsed six demos into one. Luna: That's smart. You're respecting their need for individual attention but protecting your time. Lucas: And it's more effective, too. When the CFO hears the IT director ask a question about integration, they understand the full picture. Seven separate demos, each stakeholder only sees their slice. Luna: What about the prospect who keeps asking for 'one more thing' — a feature they didn't see, a report they want generated live? Lucas: That's often a sign that they're not ready to decide. They're collecting ammunition for internal debate. My advice: after the first demo, send a summary of what was shown and ask, 'Based on what you've seen, do you feel this addresses your top priorities?' If they say yes, move toward next steps. If they say no, ask what's missing. Luna: You're creating a natural checkpoint. Lucas: Exactly. And if they keep asking for more, you might need to have a direct conversation: 'I want to make sure we're a good fit for you. Based on everything we've shown, what concerns remain that would prevent you from moving forward?' That often surfaces the real objection. Luna: And sometimes the answer is, 'We're not sure we need this at all.' Which is better to know early. Lucas: Far better than after five demos. So the core takeaway: don't let the demo become a crutch. Set boundaries early, diagnose the real reason for repeat requests, and pivot to a trial or decision-focused conversation when appropriate. Luna: And remember, if they're asking for more demos, they're probably still interested — but you need to channel that interest into action. Lucas: Exactly. Good selling.