Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How a Rep Won by Asking the Buyer to Write a Case Study
Transcript
- Lucas: You know that moment in a long sales cycle when everything is lined up—except the final signature? The buyer says they're ready, but they just won't close. Luna: Yeah, that's the zone where deals go to die. We've covered a lot of tactics for breaking the logjam. What's this one? Lucas: This episode is about a rep named Jamie at a B2B analytics platform called Insightlytics. Jamie had a six-figure deal with a manufacturing firm's VP of Sales. The VP was enthusiastic, but kept pushing the close date out. Luna: Classic. So what did Jamie do differently? Lucas: Jamie asked the VP to write a case study. Not after the deal—before. She said, 'If we move forward, I'd love to feature your team's results. Could we draft a one-page overview of what success looks like for you, and get your sign-off on it before we finalize the contract?' Luna: Whoa. That's a big ask. What did the VP say? Lucas: He hesitated at first, but Jamie reframed it: 'This isn't extra work—it's your roadmap. We're aligning on outcomes before we even start.' He agreed. They spent thirty minutes outlining the expected efficiency gains and cost savings. The VP even got his team to verify the numbers. Luna: And then he signed? Lucas: Within a week. The case study commitment acted as a psychological anchor. Once the buyer publicly put their name on projected results, backing out meant losing face—and more importantly, losing the work they'd already invested. Luna: It's the classic 'commitment and consistency' principle from Robert Cialdini. People want to behave in ways consistent with their past actions. If they've already written down success metrics, signing the contract feels like the logical next step. Lucas: Exactly. Jamie didn't just ask for the case study—she asked for the buyer's specific numbers and timeline. She made it concrete. The VP committed to 'a 20 percent reduction in reporting time within six months.' That's measurable. Luna: But isn't there a risk? What if the buyer feels pressured? Or what if the results don't materialize and the case study becomes a liability? Lucas: Those are fair concerns. Jamie knew the product well enough to be confident in the outcomes. And she framed it as a best-case scenario—'Here's what top customers achieve'—not a guarantee. The key is to make it a collaborative vision, not a promise. Luna: Okay, so this tactic seems most powerful in solutions where the ROI is clear and the product has a track record. What about commoditized deals or low-margin sales? Lucas: Probably overkill. If you're selling a $500 software subscription, asking for a case study feels like too much friction. But for enterprise deals over $50,000, the buyer is already investing time in due diligence. Asking for an hour to draft a case study is a small additional ask that signals seriousness. Luna: And it weeds out tire-kickers. A buyer who won't invest thirty minutes to describe success probably isn't going to be a great customer anyway. Lucas: Exactly. Jamie also offered to write the first draft to reduce the buyer's effort. That made the ask feel generous—'Let me do the heavy lifting.' The VP just reviewed and approved. Luna: So the rep becomes a partner, not just a vendor. That's a relationship builder. Lucas: Right. And the case study itself becomes a selling tool for the next prospect. Jamie got permission to use the VP's name and company logo right away. That social proof accelerated her next few deals. Luna: Any downsides? We've talked about pressure—what if the buyer's legal team objects to pre-signing a case study? Lucas: Good point. Jamie's approach was to call it a 'success outline' rather than a final case study. She framed it as an internal document to guide the implementation. The legal review came later, after the deal closed. But getting the buyer's personal buy-in on the vision was the real win. Luna: So the key is to make the ask feel low-risk and high-value. You're not asking for a binding testimonial, you're asking for a blueprint of success. Lucas: That's the nuance. The rep I studied also included a clause in the outline that said 'subject to final results.' That took the liability off the buyer. The case study was about expected outcomes, not guaranteed ones. Luna: I like that. It's almost like a pre-commitment device. The buyer is saying, 'If we get these results, I'll be proud to share our story.' Lucas: Exactly. And once they've crafted that story, they're invested. It's the same psychology as asking the buyer to set the implementation date—you're getting them to act like the deal is already done. Luna: If today was actually useful to you, the way these stay ad-free is listener support. Buy me a coffee dot com slash fexingo. That's all. Lucas: Yeah, it's a small way to keep these conversations going. We don't run ads, and listener support truly makes it possible. Let's get back to the tactic. Luna: So the case study approach—does it work better with early adopters or with skeptical buyers? Lucas: Interestingly, it works with both. Early adopters are happy to be featured. Skeptical buyers? The act of writing down what success looks like forces them to articulate why they're even considering the purchase. That clarity often resolves their doubts. Luna: That makes sense. You're basically asking them to justify the decision to themselves. Lucas: Yes. One more thing: Jamie timed the ask right after a positive demo, when the buyer was most excited. She didn't spring it on a cold call. Context matters. Luna: Timing. Always. So to summarize: Ask the buyer to co-create a case study outline before the close. Keep it low-pressure, focus on their vision, and make it easy to say yes. Lucas: Exactly. It builds commitment, shortens the sales cycle, and gives you a powerful reference asset. If you try it, let us know how it goes.