Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Buyers Now Audit Software Supply Chains
Transcript
- Lucas: So you spend months building a relationship with a midmarket logistics company. They love your CRM tool. The demo goes perfectly. And then procurement sends over their vendor questionnaire, and buried on page 17 is a single request: 'Please provide a current Software Bill of Materials for all third-party and open-source components in your platform.' Luna: And you don't have one. Lucas: You don't have one. That deal—$2.3 million over three years—evaporated. I talked to the founder of that CRM startup last month. He said the hardest part was that he'd never even heard the term SBOM before that email. Luna: SBOM being Software Bill of Materials. For listeners who haven't encountered it yet, it's basically an ingredient list for your software. Lucas: Exactly. Every open-source library, every commercial SDK, every build-time dependency—all cataloged with version numbers, license types, and known vulnerabilities. The idea has been floating around security circles for a while, but it went mainstream after the SolarWinds hack in 2020. Luna: Right. Hackers compromised SolarWinds' build system and inserted a backdoor into their Orion software. Over 18,000 customers downloaded the poisoned update. Lucas: And the really scary part was that even customers who did their due diligence couldn't have caught it because they had no way to see what was inside the software. SolarWinds wasn't hiding anything—they just didn't have a machine-readable inventory of their own supply chain. Luna: So the SBOM is supposed to fix that gap. But it's still pretty rare in practice, isn't it? Lucas: It depends on the buyer. Among Fortune 500 companies, especially in financial services and healthcare, SBOM requests have gone from a nice to have to a gating item. I pulled some data from a procurement consultancy—they surveyed 150 enterprise procurement teams in Q2 2026, and 68 percent now require an SBOM at the RFP stage for any new SaaS deal over $500,000. Luna: That's up from what? Lucas: From about 22 percent in 2023. So it's tripled in three years. And the trigger wasn't just SolarWinds. Last year's XZ Utils backdoor attempt was a huge wake-up call for open-source supply chains. Luna: Remind me of that one—XZ Utils is a compression tool, right? Used everywhere in Linux? Lucas: Correct. Someone spent years cultivating trust as a maintainer, then pushed a backdoor into the library. It was caught before wide release, but it terrified enterprise security teams because the attacker had been so patient and the code was so deeply buried. Luna: It showed that even an innocuous library like a compression utility can become an attack vector. So now procurement wants to know every single component you're shipping. Lucas: And not just names and versions. They want to know the provenance—where each component originated, whether it came from a trusted registry, whether there are any known CVEs with a score above 7.0, and what the license obligations are. Luna: License obligations—that's a whole other layer. If your SaaS tool uses a copyleft license like AGPL, the enterprise buyer might have to disclose their own source code if they modify your tool. Their legal team will block that. Lucas: Exactly. So the SBOM becomes a cross-functional document—security cares about vulnerabilities, legal cares about licensing, procurement cares about compliance, and engineering cares about maintenance. One document serves four audiences. Luna: But for a small SaaS vendor, generating an SBOM sounds like a big engineering lift. How hard is it really? Lucas: It's easier than most founders think. If you're using package managers like npm, Maven, pip, or NuGet, there are tools that can generate a basic SBOM automatically. OWASP has a free tool called CycloneDX that works with most build pipelines. You can literally run a command and get a JSON file. Luna: So the technical barrier is low. The hard part is keeping it current. Lucas: That's the real challenge. An SBOM is only useful if it's updated every time you change a dependency, add a new library, or patch a vulnerability. If you generate one at launch and never touch it again, it's worse than useless—it gives buyers a false sense of security. Luna: And that's exactly what the more sophisticated enterprise buyers are starting to audit. They're not just asking for an SBOM—they're asking for the date it was last generated, and some are requiring it to be regenerated with every release. Lucas: I saw a procurement template from a major bank where they require the SBOM to be signed and timestamped by the CI/CD pipeline. They want proof that it's generated automatically, not a hand-crafted spreadsheet that someone might forget to update. Luna: That's a high bar for a 20-person SaaS company. Lucas: It is. But the alternative is getting filtered out of deals you could have won. The CRM startup I mentioned earlier—the one that lost the $2.3 million deal—they spent about three weeks building an automated SBOM pipeline after that rejection, and they've since closed two enterprise clients who specifically cited the SBOM as a differentiator. Luna: So it went from a deal-killer to a deal-maker. Lucas: Exactly. And that's the pattern I'm seeing across more and more verticals. The companies that treat supply-chain transparency as a product feature—not just a compliance chore—are pulling ahead. Luna: It also changes the conversation with procurement. Instead of defensive, you get to say, 'Here's exactly what's in our software, here's how we manage vulnerabilities, and here's the real-time evidence.' Lucas: Right. And if these conversations about procurement strategy and building trust with enterprise buyers are useful for what you're building or running, it's worth mentioning that this show stays independent thanks to listener support. If you get value from episodes like this, you can help keep them ad-free at buy me a coffee dot com slash fexingo. Luna: We don't run sponsors, so it really does make a difference. And we appreciate it. Lucas: Okay, back to the SBOM. One of the interesting developments I'm tracking is that some SaaS vendors are now offering a public SBOM API endpoint. So a prospective buyer can query the latest SBOM programmatically before they even send an RFP. Luna: That's a power move. It signals total transparency from the first touchpoint. Lucas: It is. And it aligns with what the most forward-thinking security teams are asking for. They don't want a PDF attached to an email—they want to integrate your SBOM into their own vulnerability management system and get alerts when something changes. Luna: So we're moving toward continuous compliance rather than point-in-time audits. Lucas: Exactly. And that has implications for how you price and package your product. If you can offer a 'supply-chain verified' tier with a real-time SBOM, you can justify a premium over competitors who only provide a static document. Luna: I wonder how far this goes. Could we reach a point where every commercial software purchase requires an SBOM by default, the way every food product requires an ingredient list? Lucas: I think we're heading that way. The Biden administration's 2021 executive order on cybersecurity already requires an SBOM for all software sold to the federal government. And once the government sets a standard, enterprise procurement tends to follow within a few years. Luna: So if you're a SaaS founder listening, and you don't have an SBOM yet, where do you start? Lucas: Start with a single tool like OWASP CycloneDX or SPDX. Generate an SBOM for your main application. Verify it against a known vulnerability database. Then automate the generation in your CI/CD pipeline. It's not a weekend project, but it's a two-week project. And it will come up in every enterprise deal from here on out. Luna: And if someone pushes back in procurement, you can point them to the executive order or the SolarWinds case and say, 'We take this seriously, and here's the proof.' Lucas: Exactly. The companies that wait until a deal falls through will scramble. The ones that do it now will use it to close deals faster. It's one of those rare compliance requirements that can actually become a competitive advantage. Luna: Alright, that's a good place to leave it for today. For B2B SaaS Talks with Fexingo, I'm Luna. Lucas: And I'm Lucas. We'll be back with another angle on enterprise procurement soon.