Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask About Vendor AI Governance Committees
Transcript
- Lucas: So Luna, I'm seeing a new section appearing in enterprise RFPs lately — it's not about model rollback or data provenance, it's about who, inside the vendor, actually owns AI risk. Luna: You mean like a human committee? Not just a policy document? Lucas: Exactly. We've covered a lot of the 'what' — what data, what safeguards, what metrics. This is the 'who.' Buyers are now asking for the names, titles, and meeting cadence of your AI governance committee. They want to know it's not just a slide in a security deck. Luna: So instead of 'do you have an AI policy?' it's 'who's accountable and how often do they actually meet?' Lucas: Right. And it's showing up in the procurement portal as a mandatory field. I saw one RFP from a regional bank last week — they asked for the committee charter, the roster, and the minutes from the last two meetings. Luna: Minutes? That's a new level of transparency. Are they verifying that the committee actually does something? Lucas: That's the bet. They're not just checking a box anymore. They want evidence that AI decisions are being reviewed by a cross-functional group, not just the CTO or the head of data. Luna: So what does a credible committee actually look like in 2026? Is there a standard structure? Lucas: There's not a single standard, but the pattern is emerging: you need representation from legal, security, product, and — interestingly — customer success. Buyers love seeing customer success on that committee because it means the voice of the end user is at the table. Luna: Interesting. So it's not just an engineering review board. Lucas: No, and that's the shift. Engineering can say 'we can build it.' The committee's job is to say 'should we, and what does the contract say, and what could go wrong for the customer.' Luna: And buyers are smart to push for that, because a vendor's AI mishap can become the customer's regulatory nightmare. Lucas: Exactly. Let's talk about a specific case. There's a mid-market SaaS company I've been following — they sell document automation to financial services. They were in a six-figure deal with a credit union, and the credit union's procurement team sent back a security questionnaire that included a question they'd never seen before. Luna: What was the question? Lucas: 'Please describe your AI governance committee, including its charter, membership, and frequency of review.' That was it. No multiple choice. Luna: So they had to actually produce something. What did they do? Lucas: At first, they panicked. They had an AI ethics policy they'd written the previous year, but no standing committee. So they had to scramble to formalize one, and I'll be honest — they basically invented it on the spot. Luna: That's risky. But they turned it around somehow. Lucas: They did. They pulled together a group of five people: their general counsel, the VP of security, the head of product, the data science lead, and the VP of customer success. They wrote a charter in a week, held their first meeting, and sent over the minutes along with the charter. Luna: And the credit union bought it? Lucas: They did, but only because the vendor was honest about the fact that this was a newly formed committee. They didn't pretend it had been around for years. The credit union actually appreciated the transparency. Luna: So the key is to not fake it. Buyers can smell a retroactive committee from a mile away. Lucas: That's the thing — procurement teams are getting more sophisticated. They'll ask for the meeting minutes from the last two quarters. If you don't have them, you've lost credibility. Luna: So for a B2B SaaS founder listening right now — if you haven't set up your AI governance committee yet, what's your advice? Don't wait for the RFP? Lucas: Don't wait. It takes at least a couple of quarters of meeting minutes to look credible. Start small. You don't need ten people. You need the right five, a charter, and a quarterly cadence that's actually kept. Luna: And the charter should probably mention things like model risk, customer impact, and escalation paths. Lucas: Yes, and specifically tie it to your product roadmap. Buyers want to see that the committee reviews new AI features before they go to market, not just after a problem blows up. Luna: Let me play devil's advocate — does a committee actually slow things down? For a fast-moving startup, is it just bureaucracy? Lucas: It can be, if you make it a governance theater. But the best ones operate like a design review — they're a forcing function to think through edge cases before you ship. Luna: And for enterprise buyers, it's a signal of maturity. If you don't have one, they might wonder what else you're missing. Lucas: Exactly. And the interesting thing is, this is starting to move beyond regulated industries. I'm seeing questions about AI governance pop up in RFPs from manufacturing, logistics, even creative agencies. Luna: So it's becoming table stakes for any serious B2B deal. Lucas: Pretty much. And there's a nuance — some buyers are asking for a committee that includes an independent member. Like an external AI ethics advisor. That's still rare, but I think it's coming. Luna: Interesting. That would be a way to build even more trust, but it might be hard to staff. Lucas: For now, the practical thing is to have a real, functioning committee with clear ownership. And actually, this conversation reminds me of something we've been talking about on the show — the value of being genuinely prepared for these buyer demands. Luna: Yeah, we've seen so many vendors scramble when a new requirement shows up. Lucas: And if today was actually useful to you, the way these stays ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, it really does help us keep doing these deep dives. Lucas: And honestly, the fact that we can dig into something like AI governance committees and show you the actual mechanics — that's what we're here for. Luna: So back to that — you mentioned a mid-market company. What if you're a smaller vendor, say twenty employees? Is a formal committee even realistic? Lucas: You can do a lightweight version — three people, a monthly call, and a shared doc for decisions. The key is that it's documented and repeatable. Luna: So you don't need a chief AI officer. You need a group that actually meets. Lucas: Exactly. And one more thing — make sure your committee's charter is public or at least shareable with prospects. If it's buried in your internal wiki, it doesn't help you close deals. Luna: That's a great point. You should be able to hand over the charter as part of your security package. Lucas: Right. And remember, the committee isn't just for RFPs. It's for you. It catches problems early, and it makes your product better. But yes, it also helps you win deals. Luna: So the next time you see an RFP ask for your AI governance committee, you'll be ready. Lucas: And if you're not ready yet, start today. Because by 2027, this is going to be as standard as asking for your SOC 2 report.