Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Enterprise Buyers Now Demand a Vendor Software Bill of Materials
Transcript
- Lucas: You know how every enterprise software deal now has that moment where procurement hands over a forty-page security questionnaire? Luna: Oh, I’ve seen those. Page seventeen is always the one that trips everyone up. Lucas: Right, and there’s a new line item showing up more and more often. It’s called an SBOM — software bill of materials. A full inventory of every open-source library, every third-party component, every dependency that your product is built on. Luna: So basically a list of ingredients for your software code. Lucas: Exactly. And it’s becoming a hard requirement in enterprise contracts — not just a nice to have. We’re talking Fortune 500 procurement teams that will not sign a deal unless the vendor provides an SBOM and updates it quarterly. Luna: When did this shift happen? I feel like five years ago nobody was asking for this. Lucas: The inflection point was definitely the SolarWinds attack in 2020. That was a supply chain compromise where attackers inserted malicious code into a legitimate software update. Suddenly every CISO realized they had no idea what was inside the tools they were buying. Luna: So the SBOM is supposed to close that visibility gap. Lucas: That’s the idea. And it got a further push after the Log4j crisis in 2021. Companies scrambled to find out if they were running that vulnerable logging library. If they’d had SBOMs, they could have pinpointed exposure in hours instead of weeks. Now we’re seeing the legal fallout — there were shareholder lawsuits in 2024 against vendors that couldn’t produce an SBOM after a breach. Luna: That’s a big stick. So for a B2B SaaS company selling into enterprise, what does producing an SBOM actually look like in practice? Lucas: It’s not trivial. Most modern SaaS products pull in hundreds of open-source packages. A typical Node.js application might have five hundred direct dependencies, and when you count transitive dependencies — libraries that your libraries rely on — it can be several thousand. Luna: And you need to list every single one. Lucas: In a standardized format. The two main ones are SPDX and CycloneDX. The National Telecommunications and Information Administration, or NTIA, has put out guidelines. So it’s not just a list — it has to be machine-readable, with version numbers, license types, and known vulnerabilities mapped to each component. Luna: That sounds like a full-time DevOps job for a startup. Lucas: It is, but there are tools that automate most of it. GitHub has dependency graphs, Snyk and Black Duck can generate SBOMs. The challenge is keeping it accurate — your SBOM has to reflect what’s actually in production, not what was in the build three months ago. Luna: What happens if a vendor can’t or won’t provide one? Are deals actually dying over this? Lucas: Yes. I’ve heard from sales leaders at mid-market SaaS companies that they lost three deals last year specifically because they couldn’t deliver an SBOM within the procurement timeline. The enterprise buyer goes to the next vendor who can. Luna: Interesting. So it’s becoming a competitive differentiator. But is there any standardization across industries? Or is every Fortune 500 asking for something slightly different? Lucas: That’s the messy part right now. Some companies use the NTIA minimum elements, others have their own custom fields. But there’s a push toward a universal standard. The Linux Foundation’s OpenSSF project is working on it, and the U.S. government has mandated SBOMs for federal software procurement under Executive Order 14028. That tends to trickle down to the private sector. Luna: So if you’re a startup founder listening, this is the moment to get ahead of it. Lucas: Absolutely. Start generating SBOMs now, even if no customer has asked yet. The tooling is cheap — often free for open-source projects. And when a large enterprise asks for it in the middle of a sales cycle, you’ll look prepared instead of scrambling. Luna: And it also reduces your own security risk. You find out you’re using a library with a critical vulnerability before a hacker does. Lucas: Right. So it’s defensive for you and reassuring for your buyer. I think within two years, an SBOM will be as standard as a SOC 2 report in enterprise software deals. Luna: Speaking of things that reduce risk for buyers and sellers alike — if you’re getting value from these conversations, especially if you’re building or running a SaaS business yourself, listener support is what keeps this show ad-free and independent. You can buy me a coffee at buy me a coffee dot com slash fexingo. No pressure, just a way to keep the insights flowing. Lucas: Yeah, it genuinely helps us keep digging into the shifts that actually matter for operators. And speaking of shifts, let’s talk about one more angle on the SBOM: how it’s changing the legal language in enterprise contracts. Luna: Oh, I bet the lawyers are loving this. Lucas: They are. We’re seeing indemnification clauses now tied to SBOM accuracy. If a vendor provides an SBOM that’s incomplete and a breach happens because of an undisclosed component, the vendor could be on the hook for damages. That’s a material shift from the old ‘as-is’ software licenses. Luna: So the SBOM becomes a legal document, not just a technical one. Lucas: Exactly. And it forces vendors to have better internal governance. You can’t just slap an SBOM together at the end of the quarter. You need continuous monitoring and updating. Some forward-thinking vendors are even putting SBOM API endpoints in their products so enterprise customers can check in real time. Luna: That’s a premium feature waiting to happen. Lucas: I think so. And it aligns with the broader trend of ‘shift left’ security — catching vulnerabilities earlier in the development cycle. The SBOM is the manifest of that philosophy. Luna: Alright, so the takeaway for our audience: if you’re selling enterprise software, start your SBOM practice yesterday. If you’re buying, start asking for it in every RFP. Lucas: And if you’re a developer, start learning the SPDX format. It’s not going away. The enterprise procurement machine has spoken, and it wants an ingredient list.