Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / Why Prospects Ghost You After the Demo
Transcript
- Lucas: You run what feels like the perfect demo. The prospect is engaged, asking smart questions, nodding along. And then — radio silence. No replies to follow-ups. The deal just evaporates. Luna: It's one of the most frustrating things in sales. And we've talked about ghosting after proposals, but this is different. This is after the demo, before anything's even been priced. Lucas: Right. And I want to look at a specific case that I think reveals why this happens — and it's not what most people assume. It's from a $2 million SaaS deal that a friend of mine was running earlier this year. Luna: Two million dollar deal. That's not a small thing to lose. What happened? Lucas: So this company sells compliance software to mid-market firms. The demo was with the VP of operations and the head of legal. My friend — let's call him Mark — spent ninety minutes walking through every feature. Every single one. He answered every question. He showed them exactly how the software would solve their biggest pain point around audit readiness. Luna: Sounds like a thorough demo. Where did it go wrong? Lucas: The prospect said, 'This is exactly what we need.' And then nothing. Mark waited a week, sent a follow-up. Nothing. Another week, another email. Crickets. He finally got the VP on the phone, and the VP said, 'We're going in a different direction.' No explanation. Luna: Ouch. So what was the real reason? Lucas: Mark later learned through a backchannel that the prospect had taken the demo — all that detail — and used it to build an internal specification. They handed it to their own IT team and decided to build the solution themselves. Luna: Oh, that's brutal. They essentially used him as a free consultant. Lucas: Exactly. And the thing is, Mark did exactly what a lot of sales training says to do: 'Be helpful. Give them everything they need to see the value.' But he gave them so much that they didn't need him anymore. Luna: So the lesson is don't be too helpful? That feels counterintuitive. Lucas: It's not about being unhelpful. It's about being strategic with information. There's a concept from negotiation called 'information asymmetry' — you want to maintain some advantage. If the prospect knows everything your product does and how it works, they can replicate it or shop it around. Luna: So what should Mark have done differently? Lucas: He should have focused the demo on outcomes, not mechanics. Instead of showing every feature, he should have shown just enough to prove the concept — and then tied the rest to the buying process. Like, 'This is how we handle audit trails. The full configuration depends on your specific workflows, which we'd map out during implementation.' That leaves them wanting more, not feeling like they've seen the whole movie. Luna: Yeah, because once they've seen the whole movie, they don't need to buy the ticket. Lucas: Right. And there's another layer here. By over-explaining, Mark also removed the mystery. People are more likely to buy when they still have questions. Curiosity is a powerful motivator in the sales process. When you answer every question, you kill the curiosity. Luna: That reminds me of something I read about how the best demos are actually conversational — they leave room for the prospect to ask the next question, rather than the salesperson preempting it. Lucas: Exactly. And that's hard for a lot of salespeople because we're trained to anticipate objections. But sometimes the best answer to a feature question is, 'That's a great question. Let me show you how it works in your specific scenario — can I ask you a few more questions about your current process first?' Luna: That also builds rapport. It shows you're not just a demo machine, you're actually trying to solve their problem. Lucas: Right. And it gives you control of the timeline. Mark's mistake was that he let the prospect set the agenda — they asked, he answered. He never directed the conversation toward next steps or commitment. Luna: So what should the demo actually accomplish? What's the goal? Lucas: The goal is not to show everything. The goal is to create enough belief that they want to move to the next stage — whether that's a trial, a proof of concept, or a proposal. You want them to say, 'I need to see how this works with our data' or 'Can we get a pilot?' Not, 'Great, thanks, we'll take it from here.' Luna: So the demo is a hook, not the whole story. Lucas: Exactly. And I think this is especially dangerous in SaaS because the product is so demo-able. You can show everything in an hour. But just because you can doesn't mean you should. Luna: It's like going on a first date and telling them your entire life story. No mystery, no reason for a second date. Lucas: Love that analogy. And the fix is simple: before the demo, plan what you will NOT show. Decide what stays for the proposal or the implementation phase. That's the discipline. Luna: I've also heard that some sales teams use a 'demo qualification' step — they won't even schedule a full demo until the prospect has agreed to certain criteria, like a timeline or budget. Lucas: That's smart. Because if they're not willing to commit to a next step before seeing the demo, you're already in a weak position. Mark didn't do that either. He jumped straight to the deep dive. Luna: So the ghosting wasn't really about the demo quality. It was about the demo structure. Lucas: And the information strategy. And I think this is actually a broader lesson for any kind of consultative sale. If you give away your intellectual property for free, you can't be surprised when people use it without paying. Luna: We see that a lot in our own world, too. People listen to these conversations and sometimes they get value without ever buying anything. And that's fine — that's part of why we do this. Lucas: Yeah, that's a good point. We deliberately don't run ads on these shows. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. No pressure, just if it's moved your work forward in some small way. Luna: And we mean that. It keeps the show ad-free and focused on the content. Lucas: So back to the demo — another thing Mark could have done is built in a 'next step' right inside the demo. Like, at the forty-five minute mark, say, 'Before I show you the reporting module, I'd love to schedule a follow-up with your IT team to walk through integration requirements. Does that make sense?' Luna: That gives them a reason to stay engaged and a commitment to move forward. Lucas: Right. And if they're not willing to do that, you've learned something important about their level of interest. Better to know that during the demo than after. Luna: So the demo should be a two-way gate. It's not just about them evaluating you, it's about you evaluating them. Lucas: Exactly. And I think the best salespeople treat it that way. They're not afraid to ask for a small commitment during the demo — a date for a technical call, an introduction to the economic buyer, access to a decision-maker. Luna: That also changes the dynamic. You're no longer just presenting; you're negotiating the path forward. Lucas: And that reduces the chance of ghosting, because the prospect has already agreed to a specific next step. It's harder to ignore a person you've already committed time to. Luna: What about the content of the demo itself? Should you always leave something out? Lucas: I'd say leave out the 'how' and focus on the 'what' and 'why'. Show them the outcome, not the machinery. If they ask about the machinery, give just enough to satisfy — but then pivot back to the outcome. Luna: So for Mark's compliance software, he could have shown a sample audit report and said, 'This is what your team will see. The way we populate it is based on your specific data sources, which we'll configure during onboarding.' Lucas: Perfect. That creates a need for the implementation service. It also builds the case for why they need you, not just the software. Luna: It's almost like you're selling a transformation, not a tool. Lucas: Exactly. And if you sell the transformation, the demo becomes a proof of concept for the vision, not a catalog of features. That's much harder to replicate internally. Luna: So the next time I run a demo, I'm going to plan what to hold back. Lucas: And plan what commitment you'll ask for. I'd say if you walk out of a demo without a clear next step, you've probably given away too much. Luna: Good rule of thumb. Thanks, Lucas. Lucas: Thanks, Luna. That's it for this one.