Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Buyers Now Demand a Vendor Carbon Disclosure Mandate
Transcript
- Lucas: So we’re about halfway through 2026, and there’s a new clause showing up in enterprise SaaS contracts that a lot of vendors still aren’t ready for. It’s the carbon disclosure mandate. Luna: I’ve seen this pop up in a few RFPs lately. The buyer basically says, 'Show us your emissions data — Scope 1, 2, and 3 — or we’re not signing.' Lucas: Exactly. And this isn’t just a nice to have for a few green-minded companies. We’re talking about major procurement organizations — automotive OEMs in Germany, big US banks, European telecoms. They’re inserting a contractual obligation for the vendor to report carbon data annually, in a specific format, often tied to an ESG scorecard that can trigger penalties. Luna: What triggered this? Was it regulatory pressure, or did buyers just decide they wanted it? Lucas: It’s a combination. On the regulatory side, the EU’s Corporate Sustainability Reporting Directive, CSRD, is phasing in. Companies that fall under it have to report their full value chain emissions. And since software vendors are part of that value chain, the buyer needs your data to comply with their own reporting obligation. On the voluntary side, a lot of these buyers have made net-zero pledges, and procurement is where they operationalize that commitment. Luna: So if you’re a SaaS vendor selling to a European auto manufacturer right now, you probably need to be ready to answer some pretty specific questions. Lucas: Yes. And we have a concrete example. I talked to the CEO of a mid-market analytics platform — about 200 employees, fifty million in ARR. They were finalizing a deal with a German automotive supplier. Seven figures, multi-year. Everything was agreed on price, scope, SLAs. Then the supplier’s sustainability officer asked for their carbon footprint data. Specifically, they wanted Scope 1, 2, and 3 broken out by category, verified by a third party, and mapped to the GHG Protocol. Luna: And they didn’t have it. Lucas: They had some rough numbers from their cloud provider — AWS’s carbon calculator — but nothing formal. No third-party verification. No Scope 3 data beyond that. The supplier put the deal on hold. It eventually closed, but only after the CEO spent three months and about forty thousand dollars getting a proper carbon audit done and building a reporting process. Luna: Forty grand and three months of executive time. That’s not trivial for a fifty-million-dollar company. Lucas: It’s a real cost of sale now. And the thing is, this isn’t an isolated case. I’ve heard from half a dozen SaaS founders this year who’ve lost deals outright because they couldn’t produce the data. The buyer just moves on to a vendor who can. Luna: So what exactly does a typical carbon disclosure mandate look like in a SaaS contract? Walk me through the clauses. Lucas: Broadly, there are three layers. First, there’s the reporting obligation itself. The vendor agrees to provide an annual carbon footprint report covering Scope 1 — direct emissions from owned sources like company vehicles or on-site generators — Scope 2, which is purchased energy, and Scope 3, which is everything else in the value chain. For a software company, Scope 3 is usually the biggest chunk: cloud hosting, employee commuting, business travel, hardware lifecycle. Luna: And that’s where it gets tricky, because cloud providers like AWS, Azure, and GCP do give you some data, but it’s not always granular enough for a third-party audit. Lucas: Right. And the mandate often specifies a methodology — usually the Greenhouse Gas Protocol. Some buyers will accept a reasonable estimate for Scope 3, but others want it broken down by category. The second layer is verification. More and more contracts require the data to be audited by an independent firm. That’s where the cost goes up. Third, there’s the performance linkage. Some buyers tie carbon disclosure to a sustainability scorecard that affects pricing. If the vendor fails to report on time or the data shows significant increases, there could be a penalty — like a discount on the contract or a holdback on future renewals. Luna: So it’s not just a report. There’s teeth. Lucas: There can be. Not every buyer does that yet, but the trend is toward making it a gating item. And the interesting thing is that this is showing up even in deals with US buyers who aren’t under CSRD. A lot of large US corporates have their own net-zero targets, and they’re applying similar standards across their supply chain. Luna: What about the smaller vendors? If you’re a ten-person SaaS company selling to a mid-market buyer, are you expected to do all this too? Lucas: The mandates tend to scale with deal size. A fifty-thousand-dollar contract probably won’t trigger the full disclosure requirement. But once you get above a quarter million annually, buyers start asking. And for enterprise deals — seven figures and up — it’s becoming standard. The challenge is that the smaller vendor may not have the resources. They might not even know what their cloud emissions are. But the buyer’s procurement team doesn’t always have a carve-out for small vendors. Luna: That creates a real barrier to entry. If you’re a bootstrapped startup trying to sell to a Fortune 500, you could be excluded before you even get to talk about your product. Lucas: Exactly. And that’s why we’re seeing a new mini-industry of carbon accounting tools aimed specifically at software companies. There’s providers like Watershed, Persefoni, Sinai — they help you calculate and report your footprint. Some even integrate directly with your AWS or Azure billing to automate the Scope 3 calculation. The cost is coming down. But it’s still an incremental expense that a lot of founders hadn’t budgeted for. Luna: And it’s not just cloud. What about on-premise software? If you’re selling a product that runs on the customer’s own servers, how do you account for that? Lucas: That’s a gray area. Typically, the buyer would attribute the energy use of running the software to their own Scope 2, not the vendor’s. But some buyers are asking vendors to provide an estimate of the software’s energy intensity — essentially, a power profile per transaction or per user. That’s even harder to calculate, and I think we’ll see more of that in the next couple of years. Luna: How are the big SaaS companies — Salesforce, Workday, ServiceNow — handling this? Lucas: They’ve been ahead of it. Salesforce has been publishing a carbon footprint report for years, and they have a whole sustainability cloud product. Workday and ServiceNow both have dedicated ESG reporting teams. For them, complying with a carbon disclosure mandate is just a matter of sending the right PDF. The pressure is really on the second-tier vendors — the fifty-million to five-hundred-million ARR companies that don’t have a sustainability function yet. Luna: So what’s the practical advice for a founder listening right now? If they haven’t started, where do they begin? Lucas: First, get a handle on Scope 1 and 2. That’s the easiest. Look at your utility bills, your company vehicles if you have any. Scope 3 is harder, but start with your cloud provider’s carbon calculator. That gives you a baseline. Then decide whether you need a third-party tool or if you can manage with spreadsheets for now. The key is to have something before the RFP hits your inbox. Luna: And be ready to talk about it in the sales cycle. If you wait until the sustainability officer asks, you’re already behind. Lucas: Right. And if you can get a third-party verification, even just a limited assurance engagement, it makes a huge difference. The buyer sees that as a signal that you take it seriously. Luna: One thing I’m curious about: are we seeing any pushback? Any vendors saying this is beyond the scope of a software contract? Lucas: Some, but not much. The pushback usually comes from smaller vendors who feel it’s disproportionate to the deal size. But I’ve also heard of a few larger vendors who’ve tried to push back on the verification requirement — saying it’s too expensive or that the methodology isn’t mature enough. And in some cases, buyers have accepted a self-declaration for the first year with a commitment to get verified by year two. So there is some flexibility, but it’s shrinking. Luna: It feels like this is going to become table stakes pretty quickly. Maybe within the next eighteen months. Lucas: I think so. Especially as the CSRD deadlines hit and more companies have to report their full value chain. By the end of 2027, if you’re selling enterprise software to a European company, or to any large multinational, you will almost certainly need to provide carbon data. And even if you’re selling to mid-market in the US, you’ll start seeing the question on RFPs. Luna: It’s another layer of procurement complexity. But it’s also an opportunity for vendors that get ahead of it to differentiate. Lucas: Absolutely. If you can show up to the first meeting with a verified carbon report and a process for annual updates, you’ve effectively cleared a gate that your competitors are still stuck at. Luna: And these conversations we’re having — where operators and builders get practical about what’s actually changing in the market — that’s exactly why we keep doing this show ad-free. If you find value in it, and you want to help keep it that way, you can support us at buy me a coffee dot com slash fexingo. No pressure, just if it’s useful to you. Lucas: Yeah, we deliberately don’t run ads. It keeps the conversation clean. And every bit of listener support makes that possible. So, thank you to anyone who’s contributed. Luna: Alright. Let’s get back to the carbon mandate. One thing we haven’t touched on is the data quality issue. How do buyers verify that the vendor’s numbers are accurate? Lucas: That’s the million-dollar question. Right now, most buyers rely on the third-party verification. But there’s a growing push for standardization. The Carbon Disclosure Project, CDP, has a questionnaire format, and some buyers are asking vendors to submit through that platform. Others are developing their own proprietary scoring systems. But there’s no single standard yet. It’s a bit like the early days of SOC 2 — every buyer wanted something slightly different. Luna: So vendors could end up having to report in multiple formats. That increases the burden. Lucas: It does. But I think over time, the market will converge on a few accepted frameworks — probably the GHG Protocol plus the CDP questionnaire. That’s what most of the large buyers are pointing to. And if you build your reporting process around those, you’ll be covered for the majority of requests. Luna: Let’s talk about the cloud provider angle again. If you’re on AWS, you get the customer carbon footprint tool. But I’ve heard that the data can be lagged and not very granular. Is that a problem? Lucas: It can be. AWS’s tool gives you monthly data with about a two-month lag. Azure’s is similar. For a buyer that wants annual data, that’s usually fine. But if they want quarterly or real-time, you’re stuck. Also, the tool only covers the cloud usage itself — not the embodied carbon of the hardware, which is part of Scope 3. Some buyers are starting to ask for that too. The cloud providers are improving, but it’s not perfect. Luna: So vendors might need to supplement with their own calculations. Lucas: Exactly. And that’s where the third-party carbon accounting tools come in. They can pull the cloud data and add factors for embodied carbon, plus handle the other Scope 3 categories like employee commuting and business travel. Luna: It sounds like for any SaaS company serious about enterprise sales, investing in carbon accounting is no longer optional. It’s a cost of doing business. Lucas: I think that’s the right framing. And the sooner you treat it that way, the less painful it will be. The companies that started three years ago are now reaping the benefits in deal velocity. Luna: Last question: do you see this expanding to other areas? Like water usage, waste, biodiversity? Lucas: Eventually, yes. But carbon is the priority right now. It’s the metric that’s most mature, most regulated, and most tied to net-zero commitments. Once companies have carbon dialed in, they’ll likely move to other environmental metrics. But for the next couple of years, focus on carbon. That’s where the contractual pressure is. Luna: Good advice. Let’s leave it there for today. Lucas: Next time, we’ll look at another emerging procurement clause — the vendor AI model card requirement. That one’s picking up steam fast.