Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Buyers Now Demand a Supplier Code of Conduct
Transcript
- Lucas: So there's a new item showing up on enterprise procurement scorecards this year, and it's one that a lot of software vendors aren't ready for. It's the supplier code of conduct. Luna: Like a document saying we promise to be ethical? I've seen those in manufacturing and retail for years. But for software? Lucas: Exactly. Historically, codes of conduct were for hardware supply chains—sweatshop labor, conflict minerals, that world. But Gartner published a report in late 2025 showing that 68 percent of large enterprises now require a supplier code of conduct as part of software procurement. That's up from 42 percent in 2022. Luna: Sixty-eight percent is huge. What triggered the jump? Lucas: A couple of high-profile incidents. In 2023, a major cloud provider was found to have subcontractors in Southeast Asia running data-labeling operations with poor working conditions. The buyer—a European bank—caught flak in the press for not vetting its software vendors' supply chains. After that, procurement teams started treating software vendors like any other supplier. Luna: Right, because even if the code isn't enforceable, it forces the vendor to at least have a policy. But is it actually enforceable? Lucas: That's the tension. Most codes include clauses about labor rights, environmental standards, data ethics, and sub-contractor oversight. But enforcement is usually through an annual self-attestation or a third-party audit. The real teeth come when the buyer writes termination rights into the contract if the vendor breaches the code. Luna: Okay, so give me a real example of a deal that hinged on this. Lucas: There's a mid-market SaaS company called DataSync—they provide data integration tools. In early 2025, they were competing for a twelve million dollar contract with a Dutch multinational bank. The bank's procurement team sent DataSync a thirty-question supplier code of conduct questionnaire. DataSync had a generic one-pager that basically said 'we follow local laws.' That didn't cut it. Luna: What specifically was missing? Lucas: The bank wanted DataSync to certify that all subcontractors—including the cloud infrastructure providers they resell—also adhered to the code. DataSync didn't have any visibility into their own subcontractors' practices. They lost the deal to a competitor that had a detailed code covering the entire value chain. Luna: So the code has to extend beyond the vendor itself. That's a big lift for a smaller SaaS company. Lucas: It is. And it's becoming more detailed. I've seen codes that include specific greenhouse gas emission targets, diversity requirements for the vendor's board, and even clauses about not using AI in ways that violate human rights. Some buyers are requiring vendors to publish their code publicly on their website. Luna: If it's public, then NGOs and activists can scrutinize it. That raises the stakes. Lucas: Absolutely. And it's not just B2B buyers. Some government agencies in the EU now require suppliers to have a code of conduct aligned with the UN Guiding Principles on Business and Human Rights. That's a pretty specific standard. Luna: Let's talk about the AI angle. Are codes of conduct starting to address AI governance? Lucas: They are. I've seen codes that say the vendor will not use customer data to train generative AI models without explicit consent, or that the vendor will conduct bias testing on any AI features. Some codes even require the vendor to have an AI ethics board. That's moving beyond traditional social responsibility into product design. Luna: But isn't there a risk that these codes become a checkbox exercise? I mean, a vendor can write a nice code and still behave badly. Lucas: That's the critique. The real due diligence comes in the audit. Some buyers are asking for annual SOC 2 Type II reports plus a separate attestation that the vendor complied with its code. Others are doing spot audits of subcontractor facilities. But if the buyer doesn't follow up, it is just a piece of paper. Luna: So what should a SaaS vendor do right now if they don't have a code of conduct? Lucas: First, don't copy-paste a generic one from the internet. Procurement teams can spot boilerplate immediately. Second, map your entire supply chain—who are your subcontractors, cloud providers, data centers, even your payment processors. Third, set up a governance process for updating the code annually. And fourth, be prepared to answer questions during the RFP process. Luna: Honestly, if this episode saved you from losing a deal like DataSync did, that's the kind of value that makes a coffee worth buying. If today's episode was useful for what you're building or running, you can support the show at buy me a coffee dot com slash fexingo. Small gestures keep us independent. Lucas: Yeah, that's a good way to put it. And speaking of useful, there's another trend I'm watching: some buyers are starting to ask vendors to disclose their own suppliers' codes of conduct. It's like a cascading requirement. Luna: So the vendor has to vet its own vendors. That's a lot of paperwork. Lucas: It is, but it's also an opportunity. If you can show that your supply chain is clean, that can be a differentiator. For example, a vendor that uses only renewable energy powered data centers can highlight that in its code. That appeals to buyers with net-zero commitments. Luna: I want to go back to the DataSync example. Did they eventually create a proper code of conduct? Lucas: They did. After losing the bank deal, their CEO made it a priority. They hired a part-time compliance officer, drafted a code aligned with the UN Guiding Principles, and started requiring their own subcontractors to sign the same code. It took about six months, but they say it's helped them qualify for deals they wouldn't have been considered for before. Luna: Six months is fast. I would have guessed a year or more. Lucas: It helped that they already had a SOC 2 report and an AI governance framework in place from other deals. The code of conduct was the missing piece. A lot of vendors are in that same position—they have most of the components, just not the document that ties them together. Luna: Are there any industry standards emerging? Like a template that everyone uses? Lucas: The closest thing is the Software Alliance's code of conduct framework, which was released in early 2026. It's a modular template with sections on labor, environment, data ethics, and supply chain. But adoption is still early. I think within two years, most enterprise RFPs will include a code of conduct questionnaire as standard. Luna: So if you're a startup selling to large companies, you basically need to have this ready before you even start the sales process. Lucas: Exactly. Don't wait for a procurement team to ask. Have it on your website, include it in your security documentation, and train your sales team to talk about it. It's becoming table stakes. Luna: One more question: do you see any pushback from vendors? Like, is anyone arguing that this is overreach? Lucas: Some privately grumble that it's regulatory creep through contract law. But publicly, everyone is complying. The reputational risk of being seen as unwilling to commit to ethical practices is too high. And honestly, most of the requirements are things good vendors already do—they just didn't write them down. Luna: So the code of conduct is really just making implicit promises explicit. Lucas: That's exactly right. And in doing so, it creates a document that both parties can point to if something goes wrong. It's a risk-management tool as much as an ethics statement. Luna: Do you think we'll eventually see a standard code of conduct that all enterprise software vendors are expected to adopt, like a seal of approval? Lucas: I think that's where we're heading. Maybe an ISO standard or an industry-wide certification. But for now, it's still fragmented. Every buyer has their own version. The vendors that are most agile in adapting will have a clear edge. Luna: Interesting. Thanks, Lucas. That was a really practical look at a trend that's easy to overlook. Lucas: Thanks, Luna. It's one of those things that sneaks up on you, but once you see it, you can't unsee it.