Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why RFPs Now Ask About Vendor M&A Plans
Transcript
- Lucas: So, Luna, I have been digging through procurement documents from a mid-market SaaS vendor, and I keep seeing a clause that wasn't there even two years ago. The enterprise buyer is now asking for the vendor's mergers and acquisitions roadmap. Not just their product roadmap, but literally, what is your M&A strategy over the next three years? Luna: That feels like asking a vendor to reveal their poker hand. How do you even respond to that without giving away confidential deal talks? Lucas: Right, and that's exactly the tension. But it's becoming a standard part of the enterprise RFP, especially for software that sits on critical infrastructure. Buyers are scared of a scenario where they sign a five-year deal, the vendor gets acquired, and the new parent company decides to kill the product or change the data handling. Luna: So they're trying to de-risk the acquisition scenario before it happens. Lucas: Exactly. And I've seen a specific case that illustrates this perfectly. A Fortune 500 financial services company sent an RFP to a data integration platform. Buried on page 47, they asked for three things. First, the vendor's M&A history for the last ten years, including any acquisitions or divestitures. Second, whether the vendor is currently in active acquisition talks, and if so, with whom. Third, a detailed change of control clause that would apply if the vendor were acquired. Luna: Whoa. Asking about active talks is a landmine. There's no way a private vendor can answer that truthfully without breaching confidentiality. Lucas: And that's where the smart vendors get creative. They can't disclose active discussions, but they can share their historical M&A activity, their ownership structure, and their stance on acquisitions in general. They can also point to their existing change of control provisions, which are often the real safety net. Luna: So the change of control clause is the key. What does that typically look like in a SaaS contract? Lucas: Well, the buyer wants to ensure that if the vendor is acquired, their contract remains valid, their data stays protected, and they have an exit ramp if things go south. I've seen clauses that trigger a Service Level Agreement review, require sixty days notice of any change in control, or give the buyer the right to terminate without penalty if the acquirer is a direct competitor. Luna: And this is a shift from the past. Five years ago, most buyers never even thought about the vendor's M&A plan. They just checked the box on financial viability and moved on. Lucas: Right. And now, with the wave of consolidation in the SaaS space, buyers have been burned. They've signed long-term deals, only to have the product roadmap change overnight after an acquisition. So they're getting more sophisticated. They're asking about IP ownership, data residency, and even the vendor's integration plans post-acquisition. Luna: How do you see vendors responding? Are they being transparent or just giving boilerplate? Lucas: The best ones are using it as a trust signal. They're saying, 'We're not planning to be acquired, but here's our M&A philosophy, here's our data governance framework, and here's how we've handled past acquisitions.' That transparency resonates with the procurement team. The worst ones are dodging the question entirely, which raises red flags. Luna: So if you're a vendor and you get this RFP, what's your practical advice? Do you actually have to reveal active talks? Lucas: The honest answer is no. But you have to frame it carefully. You can say, 'We evaluate strategic opportunities on an ongoing basis, but we have nothing material to disclose at this time.' That's a standard securities law phrase, even for private companies. And then you pivot to your change of control protections. Luna: And the buyer's side? How do they verify all this? Lucas: This is where third-party risk assessments come in. Many enterprise procurement teams now hire outside firms to run what's called a 'vendor M&A risk audit.' They look at the vendor's ownership structure, their debt covenants, even their key personnel's employment agreements. They're trying to spot whether an acquisition is likely and what that would mean for the buyer. Luna: It's almost like a background check on the company's future intentions. Lucas: Exactly. And it's not just about the acquisition itself. It's about the ripple effects. If the acquiring company has a different data residency policy, or a different AI governance framework, that impacts your compliance. So buyers want to know, 'What happens to my data if you get bought by a company based in another jurisdiction?' Luna: That's a real concern, especially with GDPR and data sovereignty laws. Lucas: Right. And that's why I think we're going to see more RFPs asking for a 'data control plan' in the event of a change in control. It's not just about the contract; it's about the operational reality. Luna: You know, it's interesting. This whole trend feels like a maturity marker for the SaaS industry. Buyers are treating software vendors like strategic partners, not just tools. Lucas: Absolutely. And speaking of partnerships, I want to take a quick moment to mention something that's been on my mind. You know, this show is completely listener-supported, no ads. And we're able to make this many episodes every day because a small group of listeners chips in through Buy Me a Coffee. It's honestly the thing that keeps the lights on. Luna: Yeah, and we're incredibly grateful. If you find these conversations useful, that's a way to make sure they keep coming. Lucas: So, if you're so inclined, you can support us at buy me a coffee dot com slash fexingo. And now, back to the topic. We were talking about how buyers are asking about M&A plans, and I think the next frontier is the 'acquisition response plan'. Luna: What's that exactly? Lucas: It's a document that outlines what the vendor would do if an acquisition happens. It includes a communication plan for customers, a data migration strategy, and a timeline for any product changes. We're seeing early adopters in the fintech space require this. Luna: That's really forward-looking. It's like a prenuptial agreement for your software vendor. Lucas: Ha, that's a great analogy. And just like a prenup, it forces both parties to think about the 'what ifs' before they become a problem. The vendors who embrace this as a trust-building exercise will win more deals, while the ones who bury their heads in the sand will lose out. Luna: So, what's your takeaway for our listeners who are either building or buying enterprise software? Lucas: For buyers, ask the hard questions now. For vendors, don't be afraid of the M&A question. Use it as an opportunity to showcase your stability and your commitment to your customers. The more transparent you are, the more trust you build, and that's worth its weight in gold in enterprise sales. Luna: Well said. And I think the next time we see an RFP, we'll both know exactly what to look for. Lucas: Exactly. And I'd love to hear from our listeners. Have you seen this clause in your own RFPs? Let us know in the comments.