Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask Vendors About Their Subcontractors
Transcript
- Lucas: So Luna, I was reading through a stack of recent enterprise RFPs last week, and there's a question that's showing up more and more that I don't think we've talked about on the show. It's not about the vendor itself, it's about the vendor's vendors. Who your subcontractors are, where they're located, what they do with your data. Luna: Interesting. So they're asking about your suppliers, essentially. Is that new? Lucas: It's not brand new, but the depth and the frequency has really ramped up this year. I'm seeing questions like, list all third-party subprocessors, their geographic locations, their security certifications, and even their financial stability. Some RFPs are asking for a full subcontractor register as part of the initial bid. Luna: That's a lot. I mean, we've always had vendors ask about our own security posture, but now they're wanting to know about the security posture of our cloud provider, our payment processor, even our email marketing platform. Lucas: Exactly. And there's a reason for this. It's about what's called fourth-party risk. You're the third party in the chain—the buyer is the first party, you're the third party to their second party, and your subcontractors are the fourth party. And enterprises have realized that a lot of the big breaches we've seen in the last few years haven't come through the primary vendor. They've come through a subcontractor who had access to data or systems. Luna: So they're basically saying, we don't trust you to vet your own suppliers, we're going to do it ourselves. Lucas: Right. And it's not just about trust. There's also a regulatory angle. Data protection laws like GDPR and the new state privacy laws in the US impute liability up and down the chain. If your subcontractor mishandles data, you're on the hook, and your buyer is on the hook too. So they want to see that you have the same kind of oversight over your vendors that they are expected to have over you. Luna: That makes sense. So what does this look like in practice? I mean, we're not talking about just listing names on a spreadsheet, right? Lucas: No, it's much more involved than that. I saw one RFP that asked for a complete map of all data flows from the vendor to each subcontractor, including what data types are transferred, the purpose, the legal basis, and the safeguards in place. Another one asked for the vendor's process for conducting due diligence on new subcontractors, and how often they review their existing ones. Luna: Wow. So you can't just say, we use AWS and we trust them. They want to know exactly what data AWS sees, where it's stored, and what happens if AWS has a subprocess of their own that's in a different country. Lucas: Exactly. And that's the thing that really caught my eye. One RFP I saw had a specific question about cloud subprocessors, and it asked for the names of any subprocessors that AWS or Azure or Google Cloud might use to provide services to the vendor. Now, if you know anything about the major cloud providers, they have hundreds of subprocessors. There's no way a SaaS vendor can list them all. But the buyer is asking anyway because they want to see if the vendor has actually thought about this and has a process for getting that information from their cloud provider. Luna: So it's more about the vendor's awareness and management of their own supply chain than having a perfect answer. Lucas: Right. And that's where a lot of vendors are falling short. I talked to a founder whose company lost a deal just last month. The RFP had a question about subcontractors in high-risk jurisdictions, and their cloud provider had a data center in a country that the buyer flagged as high-risk. The vendor didn't even know that was the case. They had to go back to their cloud provider to get that information, and by that time, the buyer had already moved on to a competitor who had a more transparent supply chain. Luna: Ouch. So being prepared for these questions is becoming a differentiator. And I guess it's not just about losing deals, it's also about the risk of getting weeded out early in the process. Lucas: Exactly. And that's why we're doing this episode. It's a trend that any B2B SaaS company needs to take seriously. And I know we've talked a lot about what buyers are asking for in RFPs, but this one feels like a turning point. It's a shift from evaluating the vendor as an island to evaluating the vendor as part of a larger ecosystem. Luna: And you know, I think this is a good moment to mention something about our own show. We deliberately don't run ads on these episodes. We want to keep these conversations focused on what's useful for you, whether you're building or running a B2B SaaS company. If you appreciate that, and you want to support us, there's a link at buy me a coffee dot com slash fexingo. It's not required, but it does help us keep doing what we're doing. Lucas: Yeah, and we really do appreciate that. But let's get back to the subcontractor question. So how should a SaaS vendor start preparing for this? I think the first step is to create a subcontractor register. Just a simple spreadsheet that lists every third-party service that touches your product or your data, including cloud providers, payment processors, analytics tools, even your customer support platform. Luna: And then for each one, you'd want to note what they do, what data they see, where they're located, and what certifications they have. Lucas: Right. And you also need to know their subprocessors. That's the hard part. Some vendors will publish that information, like Twilio does. Others are less transparent. But you can ask them. And you should, because if your buyer asks you, you need to be able to answer. Luna: So it's about building those relationships with your own vendors, almost like you're a mini procurement department. Lucas: Exactly. And then when you get an RFP, you can respond quickly and confidently. You can show that you've already done the due diligence. That's a huge signal to the buyer that you're low-risk. Luna: And what about contractually? Should vendors be putting flow-down clauses in their contracts with subcontractors? Lucas: Absolutely. Flow-down clauses are essential. They ensure that the same data protection and security requirements that you have with your buyer are passed down to your subcontractors. So if your buyer requires you to notify them within 24 hours of a breach, your subcontractor needs to have the same obligation to you. That way, you can meet your obligations to your buyer without having to hunt down information after the fact. Luna: And I imagine that also helps with the financial stability question. I've seen RFPs asking about the financial health of subcontractors, which seems like a pretty deep ask. Lucas: It is, but it's logical. If your payment processor goes bankrupt, that could disrupt your service and, by extension, your buyer's operations. So they want to know that you've considered the financial stability of your critical suppliers. You might not be able to get their financial statements, but you can ask for their latest reports or at least have a conversation about their business continuity plans. Luna: So it's really about being transparent and proactive. The vendors that are going to win are the ones that treat their supply chain as seriously as their own product. Lucas: And that's the shift. It's a mindset change. And I think it's one that's here to stay. As enterprises get more sophisticated about managing their own risk, they're going to demand the same from their vendors. And it's not just about RFPs. I've seen some enterprises now requiring vendors to provide a full subcontractor audit as part of their annual review process, not just at the initial sale. Luna: So if you're a SaaS founder, this is something you should be thinking about now, even if you're not seeing it in every RFP yet. Because the first time a big enterprise asks you for this, you don't want to be caught off guard. Lucas: Exactly. And to that point, I'd say start with the register, then map your critical subcontractors, and then work on getting flow-down clauses in place. It's a process, but it's doable. And the vendors that do it are going to stand out in a crowded market. Luna: I think that's a great practical takeaway. So, Lucas, what's the one thing you'd want listeners to remember from this episode? Lucas: That enterprise buyers are no longer just evaluating you. They're evaluating your entire ecosystem. So your subcontractor strategy is now part of your sales strategy. If you can show that you have visibility and control over your own supply chain, you're going to have a serious edge. Luna: And that's a wrap for today. Thanks for listening, and we'll catch you in the next episode.