Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / When Your Champion Leaves Mid-Sale
Transcript
- Lucas: So you're eight weeks into a six-figure enterprise deal. You've done the demos, you've answered the security questionnaire, you've gotten verbal buy-in from legal. Your champion — the VP who brought you in, who's been selling internally on your behalf — sends you a meeting invite titled 'quick check-in.' You join, and they tell you they're leaving the company. Luna: My stomach just dropped. That is the single most gutting moment in enterprise sales, I think. Lucas: It's brutal because you've done everything right up to that point. And it's also incredibly common. I looked at some data from a sales intelligence platform called Clari — they analyzed over 50,000 enterprise deals last year. Deals where the champion departed mid-cycle had a close rate roughly 40 percent lower than deals with a stable champion. Luna: Forty percent? That's not a small dent — that's basically a coin flip turning into a long shot. Lucas: Exactly. And the interesting thing is, the reason isn't usually that the new person hates your product. It's that the institutional knowledge leaves with the champion. They knew why they picked you, they knew how to navigate internal politics, they knew which objections to pre-bury. That's all gone. Luna: So the deal doesn't die because the product is bad — it dies because the context disappears. Lucas: Right. And that context is incredibly hard to transfer in a handoff meeting. So today I want to talk about a specific framework for insulating your deals against this — before it happens. Luna: Good. Because I've definitely been on the side where I just cross my fingers and hope my champion stays. That's not a strategy. Lucas: Let's start with a real example. I talked to a VP of Sales at a mid-market cybersecurity company — calls it his 'four hundred fifty thousand dollar lesson.' They had a deal with a regional bank. Their champion was the VP of Security. He was all in — he'd built a business case, he'd gotten preliminary budget approval. Then he got poached by a fintech startup. Luna: Oof. And the bank just went dark? Lucas: Worse. The new VP of Security came from a competitor's customer. First thing he did was put the entire vendor evaluation on hold. They eventually lost the deal — nine months of work, gone. The sales rep later admitted they had only ever met the champion and one other person in IT. They had no relationship with the CISO's boss, none with procurement, none with the end users in the SOC. Luna: So they built a house of cards. One person leaves, the whole thing collapses. Lucas: Exactly. So the first principle of insulating a deal is multi-threading — having relationships with at least three or four stakeholders beyond your champion. Not superficial ones — real relationships where you understand their priorities. Luna: How do you do that without making your champion feel like you're going around them? I've seen reps get paranoid about that. Lucas: It's a fair concern. The key is framing it as 'helping you build consensus.' You say to the champion: 'To make sure this goes smoothly through procurement and legal, it'd help to get early alignment with a couple of other stakeholders. Can you point me to the right people?' If you're seen as an ally in their internal sell, they'll welcome the multi-threading. Luna: So you're not going behind their back — you're extending their arm. Lucas: Exactly. Second principle: document the value in the champion's own words. Before they leave, get them to articulate why they chose you — on the record. A written business case, a video testimonial, even a Slack message you can reference later. Luna: Does that actually hold weight with a new stakeholder? Or do they just disregard it as 'the old guy's opinion'? Lucas: It depends on how you use it. If you just forward a PDF, yeah, it'll get ignored. But if you say to the new VP: 'Your predecessor left some really thoughtful documentation on why this project was a priority. Would it be helpful to walk through it together?' That signals respect for their autonomy while giving you a bridge back into the conversation. Luna: That's smart. It's not 'here's what you should think' — it's 'here's the context, what do you think?' Lucas: Right. Third principle — and this is the one most reps skip — create a 'deal artifact.' A one-pager that summarizes the problem, the solution, the business case, and the agreed next steps. Something that could survive the champion's departure. Luna: You mean like a memo of understanding? Lucas: Similar, but it's more about capturing the narrative. I've seen deals where the champion left, and the rep literally had a document that said: 'We agreed that reducing incident response time by 40 percent would justify the investment. Here's the data we both signed off on.' That document becomes a kind of institutional memory. Luna: It forces the new person to either accept that rationale or explicitly reject it. Which is harder to do. Lucas: Much harder. Because if they reject it, they need to explain why the 40 percent improvement isn't valuable. That's a tougher conversation for them than just saying 'I want to review other options.' Luna: So you're basically building a legal brief for your deal. Lucas: In a way. And you do it before you need it. The moment your champion tells you they're leaving, it's too late to start documenting. Luna: Right. Okay, so let's say the worst happens. Your champion leaves. What's the first move — do you email the new person immediately? Lucas: Not immediately. You need to let the dust settle. A day or two — no more than a week. Then reach out with a low-pressure message: 'I heard about the transition. I know you're getting up to speed. I put together a summary of our work so far — no ask attached. Happy to chat when it's useful.' Luna: No ask attached — I like that. It's the opposite of the typical 'let's get back on the calendar' panic email. Lucas: Exactly. Panic kills deals. The new person already feels pressure to prove they're in control. If you come across as desperate, they'll assume your product can't stand on its own. Luna: So you project confidence and patience. But what if the new person just ghosts you for weeks? Lucas: Then you escalate — carefully. Sometimes the right move is to go to the executive sponsor, if you have one. Say: 'I want to respect the new VP's time, but I also want to make sure we don't lose momentum on a project that had strong support.' The executive sponsor can nudge without you looking pushy. Luna: And if you don't have an executive sponsor? Lucas: That's a problem. It means you didn't multi-thread high enough. But at that point, you might need to accept that the deal has a low probability and focus your energy elsewhere. Not every deal is salvageable. Luna: That's cold — but realistic. You can't spend another six months chasing a ghost. Lucas: Right. And sometimes the best outcome is a clean loss that frees you up to win three deals elsewhere. I think the real lesson here is that champion dependency is a risk you can manage — but you have to start before the deal is in trouble. Luna: So multi-thread early, document the narrative, and create artifacts. That's a pretty actionable framework. Lucas: If today's episode was useful and you want to keep it ad-free, buy me a coffee dot com slash fexingo helps. Luna: Yeah, a few listeners chip in monthly — that's literally what keeps us going. And it means we can keep having these specific, no-fluff conversations. Lucas: Alright. So where does this leave us? I think the final takeaway is this: a champion is an accelerator, not a foundation. If your entire deal rests on one person, you haven't built a deal — you've built an introduction. Luna: That's a good line. I'm going to steal that for my next pipeline review. Lucas: Steal away. And next episode, I want to talk about the flip side — what happens when the champion isn't the problem, but procurement is. Luna: Oh, procurement. That's a whole other beast. Looking forward to it.