Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask About Vendor Team Turnover
Transcript
- Lucas: So Luna, I stumbled on something this week that really caught my eye. A Fortune 500 company's latest RFP for a CRM platform had a section I have never seen before in a software procurement document. Luna: Okay, now you have my attention. What was it? Did they ask for your social media passwords? Lucas: Ha, not quite. But they did ask for something almost as personal. They wanted the vendor to disclose their team turnover rate over the past two years, broken down by role — sales, implementation, support — and to name the single point of contact for the entire contract term. Luna: Wait, they want you to guarantee a specific person stays on the account? That's a big ask. Lucas: Exactly. And it's not just this one RFP. I've seen this trend building over the last few quarters. Enterprise buyers are burned out from vendors who sell with a dream team and then hand you off to whoever is left after the contract is signed. Luna: I've been on the receiving end of that. We signed a marketing automation platform two years ago, and the implementation lead who sold us on the whole thing left three weeks before go-live. The replacement had never even seen our use case. Lucas: And what happened? Did the rollout survive? Luna: Barely. We delayed by two months, the budget went up, and the relationship with the vendor was tense for the first year. We ended up switching at renewal, partly because we couldn't trust the team to stay. Lucas: That's exactly the pain point these RFPs are targeting. Buyers are realizing that software is only as good as the people who implement and support it. And after the great reshuffling of the last few years, talent instability is a huge red flag. Luna: So how are vendors supposed to answer that question? If you're honest about your attrition, you might scare them off. If you fudge it, you're lying in an RFP, which is a legal minefield. Lucas: Right, and that's the tricky part. But the smart vendors I've seen are actually turning this into a strength. They're not just giving a raw number; they're showing structure. Like, here's our retention rate, here's how we cross-train our team, and here's our escalation path if someone does leave. Luna: So it's less about promising nobody will leave, and more about proving you have a system that survives turnover. Lucas: Exactly. And that's a much more credible promise. Because let's be honest, nobody can guarantee a person stays. But you can guarantee that the project won't fall apart if they go. Luna: Let's talk about the actual question in that RFP. What exactly did they ask for? Give me the specifics. Lucas: It was a table with three columns. Role type, annual turnover rate for the last two years, and the number of people in that role who have left in the last twelve months. And then a separate section asking for the name and tenure of the proposed account lead. Luna: So they want the raw data, not just a narrative. That's a big shift from the typical 'tell us about your team' question. Lucas: Yes. And it forces vendors to actually track this stuff. Many SaaS companies have no idea what their team turnover is beyond a vague HR stat. But now, if you want to play in the enterprise space, you need to know it by team and by role. Luna: I bet a lot of sales teams are going to be scrambling to get that data from HR, especially if they've never had to report it. Lucas: And that's the thing. This is becoming a due diligence item, just like security questionnaires. We've seen those evolve from a checkbox to a full audit. I think team stability is heading the same way. Luna: So what's the downside for vendors if they don't take this seriously? Besides losing the deal, I mean. Lucas: Well, there's a reputational risk. If a vendor's turnover is high, and they try to hide it, buyers talk. And in the SaaS community, word spreads fast. You could get a reputation for being a great product but a revolving door. Luna: And the flip side, if you have low turnover, it's a great differentiator. You can say, 'Look, our implementation leads stay an average of four years, and here's the proof.' Lucas: Exactly. I've seen a mid-market vendor win a deal against a much bigger competitor, largely because they could show a stable team and the big player couldn't. The buyer literally said, 'We know you'll still be here next year.' Luna: That's a powerful message. So for our listeners who are on the vendor side, what should they be doing right now to prepare for these questions? Lucas: First, talk to your HR team and get the data. If you don't have it already, start tracking it by role and by quarter. Second, build a clear key-person retention plan, not just for the sales cycle, but for the entire contract term. Luna: And third? I'm guessing it's not just about the data, but also about the story you tell around it. Lucas: Right. You need to be able to explain why your turnover is what it is. If it's high, what are you doing about it? If it's low, what's your secret? Buyers want to see that you're thinking about this as a business risk, not just an HR metric. Luna: I also think there's a negotiation angle here. If a buyer asks for a key-person clause, what's the typical ask? Is it just that the named person stays for a certain period, or is there more to it? Lucas: It varies. Some buyers want the named person to stay for the first year, with a financial penalty if they leave. Others want a consent clause, meaning the vendor can't replace the lead without buyer approval. And some want a knowledge transfer plan in place upfront. Luna: So it's not just about retention, it's about having a plan for the inevitable. That sounds reasonable. Lucas: And as a vendor, you should be open to these clauses, but you also want to be careful not to promise something you can't deliver. If you agree to a financial penalty for turnover, make sure you're not setting yourself up for a hit for reasons outside your control, like a layoff due to market conditions. Luna: Good point. The last few years have shown that even the best companies have had to make tough calls. Buyers understand that, but they want to see that you're being transparent about it. Lucas: Exactly. And that's where trust comes in. If you're upfront about a layoff that affected your team, and you show how you handled it, that can actually build more trust than pretending it never happened. Luna: So, what's the bottom line for enterprise software buyers? Should team turnover be a dealbreaker, or just a data point among many? Lucas: I'd say it's a major data point, but not necessarily a dealbreaker on its own. You need to look at the whole picture. A vendor with slightly above-average turnover, but a rock-solid implementation methodology, might be a better bet than a vendor with perfect retention but a chaotic process. Luna: Right. It's about risk, not just statistics. And I think we're going to see this trend expand to other areas, like asking about the tenure of the executive sponsor or the support team. Lucas: Absolutely. And for our listeners, if you're on the vendor side, this is your heads-up. Get your data in order, because these questions are only going to get more common and more detailed. Luna: And if you're on the buyer side, don't be afraid to ask for this. It's a legitimate question, and you deserve to know who you're going to be working with for the next three to five years. Lucas: Speaking of working with people for years, you know what would make our team even more stable? If the listeners who enjoy these episodes decided to buy us a coffee. It genuinely helps keep this show running and ad-free. Luna: Yeah, it's a small way to support what we do, and we appreciate every single one of you who has already done it. Lucas: If today's episode was worth a coffee to you, the link is buy me a coffee dot com slash fexingo. That's it. No pressure, just a simple way to keep us going. Luna: And now, back to the topic. I want to circle back to something you said earlier about vendors using this as a differentiator. Do you have any examples of a company that's really nailing this? Lucas: There's a smaller CRM vendor called VantageBase, not a giant, but they've built their whole pitch around team stability. They publish their average tenure for implementation leads, and they offer a guarantee that if your lead leaves in the first year, you get a discount on your next renewal. Luna: That's bold. I bet that gives buyers a lot of confidence. Do you think more vendors will follow suit? Lucas: I think the ones who want to win enterprise deals will have to. It's becoming table stakes, just like SOC 2 compliance was a decade ago. If you don't have it, you're going to be at a disadvantage. Luna: So, if I'm a vendor listening right now, what's the one thing I should do this week to prepare for this trend? Lucas: Go to your HR department and ask for your team turnover data for the last two years, broken down by role. Just the act of doing that will put you ahead of half your competitors. Luna: And if you're a buyer, what's your advice? How do you evaluate the answers you get? Lucas: Look for consistency. If a vendor says they have low turnover, but their LinkedIn shows a new set of people every six months, that's a red flag. And don't just look at the numbers; ask for references from clients who worked with the same team for more than two years. Luna: That's a practical tip. I think we've covered a lot today. To wrap up, I'd say team turnover is officially on the enterprise checklist. Lucas: Yeah, and it's a smart addition. Software is a team sport, and buyers are finally asking the right questions about who's going to be on their side of the field.