Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask About Vendor Succession Planning
Transcript
- Lucas: So Luna, you remember the whole wave of RFPs asking about AI governance, data portability, all that stuff? Well, there's a new one that's quietly showing up in enterprise procurement docs, and it's a bit more human. Luna: More human how? Are they asking about office culture now? Lucas: Close, but not quite. They're asking about succession planning. Specifically, what happens to the product and the customer's data if a key person at the vendor — a founder, a chief technology officer, the lead architect — suddenly leaves. Luna: Interesting. So procurement is basically saying, 'We're not just buying software, we're buying the team that keeps it alive.' Lucas: Exactly. And it makes sense. I was looking at a recent survey from Gartner — I think it was from earlier this year — that said something like 60 percent of enterprise buyers now consider key-person risk as a formal part of their vendor due diligence. That's up from basically nothing five years ago. Luna: Wow, so it's a real shift. But how do you even verify something like that? I mean, you can't force a founder to stay. Lucas: Right, you can't. So what they're asking for is documentation. They want to see a formal succession plan, a defined knowledge transfer process, and in some cases, they want board-level oversight of talent retention. I even saw an RFP that required the vendor to name a designated successor for each critical role. Luna: That's pretty intense. So if you're a SaaS startup with a rockstar CTO, you better have someone in the wings ready to take over. Lucas: Exactly. And that's a real challenge for a lot of smaller vendors. I mean, you're asking a 20-person company to have a bench of qualified successors? That's tough. Luna: But it makes sense from the buyer's perspective. I mean, if you're betting your whole operations on a piece of software, you want to know it's not going to fall apart if the genius behind it takes a job at Google. Lucas: And that actually happened — a friend of mine at a mid-size company told me about a deal that fell through last year. The vendor's CTO left to join a big tech firm, and the enterprise customer, who was mid rfp, just... bailed. They didn't even ask for a revised proposal. They just walked. Luna: Ouch. So that's a cautionary tale for vendors. But what can a vendor actually do about it? Lucas: Well, that's what I want to dig into today. Because there are concrete steps you can take, even if you're a small team. And it's not just about paperwork — it's about actually building resilience. Luna: Alright, let's hear it. What's the first thing a vendor should do? Lucas: The first thing is to identify your key-person risk. Who are the two or three people whose departure would materially hurt the product roadmap or the customer relationship? And be honest — it's not always the founder. Sometimes it's the lead data engineer who's been there since day one and knows every quirk of the system. Luna: Right, so you need to know your own vulnerabilities before you can address them. Lucas: And in the RFP response, you don't just list names. You describe the plan. You talk about how you document knowledge — is it in a wiki, is it in the code comments, is there a regular process for cross-training? And you mention what happens if someone does leave. Is there a transition period? How do you ensure continuity? Luna: So it's like a mini business continuity plan, but focused on people. Lucas: Exactly. And some vendors go a step further. They actually offer what's called a key-person insurance policy, where the enterprise is a beneficiary. So if the CTO gets hit by a bus, the customer gets a payout to help cover the cost of migrating to another vendor. Luna: Wow, that's a bold move. But I can see how that would be a differentiator in a crowded market. Lucas: Definitely. But let's be real — not every vendor can afford that, especially early-stage ones. So what else can you do? Luna: I guess you could emphasize your hiring pipeline. Show that you have a strong team, not just one star. Lucas: Right. And that's where the conversation gets interesting. Because this whole trend is forcing SaaS vendors to think about their talent strategy as a sales tool, not just an HR function. Luna: That's a shift. But it makes sense — investors have always cared about key-person risk, so why shouldn't customers? Lucas: Exactly. And if the buyer is going to ask, you might as well have the answer ready. So let's get into a practical checklist that vendors can use to prepare for these new RFP questions. Luna: Before you do, I just want to say — if you're finding these episodes useful, you know, for what you're building or running, the way we keep this ad-free is through listener support. You can buy us a coffee at buy me a coffee dot com slash fexingo. It genuinely helps. Lucas: Yeah, that's right. Every little bit keeps the lights on and helps us dig into topics like this. Appreciate anyone who does that. Luna: So, Lucas, you were about to give us that checklist. Lucas: Right, the checklist. So first, document the knowledge. Make sure that critical knowledge isn't just in someone's head. Use design docs, runbooks, even recorded walkthroughs. If someone leaves, the knowledge stays. Luna: And then what? Lucas: Second, cross-train your team. Don't let one person be the single point of failure. Have at least two people who understand each critical system or client relationship. Luna: That's easier said than done for a small team, but it's the right goal. Lucas: Absolutely. And third, have a written succession plan for each key role. It doesn't have to be long — maybe two pages — but it should outline who steps in, what the transition looks like, and how you'll communicate with customers. Luna: That sounds like something you could build in an afternoon. Lucas: You'd be surprised how many vendors don't have it. But the ones that do are winning deals. I've talked to a couple of sales reps who told me that having a solid succession plan in their response was the thing that tipped the scale in their favor. Luna: So it's not just a checkbox — it's a differentiator. Lucas: Exactly. And one more thing I'd add to the checklist: consider offering key-person insurance if you're at a stage where it's feasible. It shows that you're serious about continuity, and it gives the buyer peace of mind. Luna: And if you can't afford that, at least be transparent about your risks and your mitigation plans. Honesty goes a long way in procurement. Lucas: That's the thing. These RFPs aren't about finding the perfect vendor — they're about finding the one that's least likely to blow up. And showing you've thought about succession is a huge signal. Luna: So, what's the broader trend here? Is this just a fad, or is it here to stay? Lucas: I think it's here to stay, honestly. Because the pandemic and the great resignation taught enterprise buyers that talent is volatile. And with SaaS being so critical to operations, they can't afford to ignore that risk. I wouldn't be surprised if in three years, every major RFP has a section on succession planning. Luna: So it's like the SOC 2 of the people world. Lucas: Ha, exactly. And just like SOC 2, the vendors that get ahead of it early will have a competitive advantage. So if you're a SaaS vendor, start working on this now, before it's in your next RFP. Luna: Great advice. And for our listeners, if you want to see a sample succession plan or a template for an RFP response, we'll put some links in the show notes. Lucas: Sounds good. Thanks for listening, everyone. We'll catch you next time.