The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/Sales/B2B SaaS Talks with Fexingo
B2B SaaS Talks with Fexingo artwork

Why Enterprise Buyers Now Require a Vendor Carbon Footprint Audit

B2B SaaS Talks with Fexingo · 2026-06-28 · 7 min

0:00--:--

Key moments - from our scoring

Substance score

63 / 100

Five dimensions, 20 points each

Insight Density14 / 20
Originality12 / 20
Guest Caliber11 / 20
Specificity & Evidence16 / 20
Conversational Craft10 / 20

The enterprise procurement landscape has undergone a fundamental shift: carbon footprint audits are no longer optional nice-to-haves but contractual deal requirements. JPMorgan, Microsoft, and over 60% of new software RFPs from large European banks now mandate vendor carbon audit clauses, typically requiring Scope 1, 2, and 3 emissions data verified against the Greenhouse Gas Protocol. This trend stems from SEC climate disclosure rules finalized in March 2026, which require public companies to disclose emissions and create downstream demand for vendor data. A concrete case study illustrates the impact: a mid-market CRM company with $50M ARR faced a three-month deal stall on a $15M contract until they hired Watershed for a verified audit, costing approximately $200k. Winners in this space include emissions-tracking platforms like Watershed (which raised a Series C at $2B+ valuation) and Persefoni, particularly popular with financial services firms aligning with the Partnership for Carbon Accounting Financials. For vendors, the message is clear: startups lacking carbon reporting capability face competitive disadvantage, as 78% of enterprise buyers have walked away from deals over vendor sustainability misalignment. The challenge lies in Scope 3 (supply chain) emissions - cloud hosting, employee travel, and device procurement - which most mid-market companies initially lack visibility into.

Key takeaways

  • →JPMorgan, Microsoft, and 60%+ of enterprise RFPs now require vendor carbon footprint audits as mandatory contract clauses, making this a deal-killer requirement rather than a nice-to-have.
  • →Vendors must track and report Scope 1, 2, and 3 emissions using the Greenhouse Gas Protocol framework, with third-party verification from firms like DNV or SGS becoming the gold standard for credibility.
  • →A mid-market CRM vendor spent $200k and faced a three-month deal delay to obtain a verified carbon audit via Watershed when losing a $15M contract was the alternative.
  • →Emissions-tracking platforms like Watershed and Persefoni are capturing significant value as vendors scramble to comply, with Watershed reaching a $2B+ Series C valuation.
  • →Vendors should immediately pull cloud provider emissions data from AWS, Azure, or GCP dashboards and map employee travel and device procurement to establish a baseline, as sustainability practices now influence 78% of enterprise buyer decisions.

Guests

Luna

Topics in this episode

Scope 1, 2, and 3 emissionsGreenhouse Gas ProtocolWatershedPersefoniJPMorgan procurement requirementsMicrosoft supplier agreementsPartnership for Carbon Accounting FinancialsSEC climate disclosure rules (finalized March 2026)AWS carbon footprint dashboardDNV and SGS third-party verification

Questions this episode answers

What emissions data must vendors now include in enterprise software contracts?

Vendors must provide Scope 1, 2, and 3 emissions data verified against the Greenhouse Gas Protocol. Scope 1 and 2 (direct operations and purchased energy) are required, and Scope 3 (supply chain, employee travel, device procurement) is increasingly mandatory, with third-party verification from firms like DNV or SGS becoming the standard.

Why are enterprise buyers suddenly requiring carbon audits from software vendors?

SEC climate disclosure rules finalized in March 2026 require publicly traded companies to disclose Scope 1 and 2 emissions, and Scope 3 if material. Procurement teams need vendor emissions data to complete their own regulatory disclosures, turning vendor carbon audits into a data-collection requirement.

How much does it cost a mid-market SaaS company to obtain a verified carbon audit?

A mid-market CRM company with $50M ARR paid approximately $200k to hire a consultant and implement Watershed for a verified audit when facing a three-month deal stall on a $15M contract.

Which companies are winning in the carbon emissions tracking space?

Watershed and Persefoni are the leading platforms, with Watershed raising a Series C at a $2B+ valuation. Persefoni is particularly popular with financial services firms aligning with the Partnership for Carbon Accounting Financials.

What percentage of enterprise buyers consider vendor sustainability practices when making purchase decisions?

According to a Salesforce survey, 78% of enterprise buyers have walked away from deals because the vendor's sustainability practices did not align with their own.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

14 / 20

The episode delivers concrete, actionable insights about an emerging procurement requirement that most B2B operators likely haven't encountered yet. The CloudSales case study ($15M deal stalled, $200k remediation cost) and specific numbers (60% of European bank RFPs, 78% of enterprise buyers walked away over sustainability misalignment) ground the discussion. However, the conversation lacks depth on *how* to actually implement carbon accounting beyond surface-level advice ('pull your AWS dashboard'), and repeats some points (carbon audit becoming standard, trust signal) without fresh elaboration.

There's a mid-market CRM company I'll call CloudSales - about 500 employees, maybe 50 million in annual recurring revenue. They were in the final stage of a 15-million-dollar deal with a Fortune 500 financial services firm.
according to a survey by Salesforce, 78 percent of enterprise buyers say they've walked away from a deal because the vendor's sustainability practices didn't align with their own

Originality

12 / 20

The premise - carbon audits as a hard procurement requirement - is genuinely fresh and underexplored in most B2B podcasts. However, the framing relies heavily on established narratives (ESG compliance, SEC rules, trust signals) and the analytical angle is largely descriptive rather than contrarian or first-principles. The episode identifies the trend clearly but doesn't challenge assumptions (e.g., whether Scope 3 measurement is even feasible at scale, or whether this genuinely drives buyer behavior or is theater).

Buried on page fourteen is a clause that would have been unthinkable three years ago: a mandatory vendor carbon footprint audit.
there's no universal accreditation body yet for carbon audits. So buyers are having to decide what counts as 'verified.'

Guest Caliber

11 / 20

Lucas appears to be a podcast host rather than a practitioner with direct operating experience in procurement or SaaS revenue. While he references conversations with 'a procurement officer at a large European bank' and cites specific companies and survey data, there's no indication he has built, bought, or managed a SaaS business through enterprise sales cycles himself. Luna's role is similarly unclear - likely a co-host rather than a subject-matter expert. Both are journalists/commentators rather than operators with skin in the game.

I talked to a procurement officer at a large European bank last week
I've heard of a few cases where a vendor outright refused

Specificity & Evidence

16 / 20

The episode is exceptionally strong on named examples and numbers. JPMorgan, Microsoft, Watershed, Persefoni, DNV, SGS, Salesforce survey (78%), CloudSales ($15M deal, $200K cost, 500 employees, $50M ARR), European bank (60% of RFPs), SEC rules (March 2026), and GHG Protocol are all specific and concrete. The only weakness is vagueness around vendor resistance ('some pushback') and lack of detail on how exactly the $200K was spent or what the Watershed implementation timeline was.

There's a mid-market CRM company I'll call CloudSales - about 500 employees, maybe 50 million in annual recurring revenue. They were in the final stage of a 15-million-dollar deal with a Fortune 500 financial services firm.
The whole process cost them around 200 grand

Conversational Craft

10 / 20

The conversation flows naturally and is well-structured, but lacks the friction and rigor of strong interviewing. Luna asks mostly softball follow-ups ('Ouch. Did they have the data?' 'And did they eventually close?') without pushing back on claims or exploring contradictions. There's minimal challenging of the narrative - e.g., no question about whether this is genuine buyer demand or supply-side hype, whether smaller vendors are truly disadvantaged, or whether offset credibility concerns undermine the whole framework. The discussion reads as aligned rather than interrogative.

So we're talking Scope 1, 2, and 3 emissions data as a contract requirement?
That sounds like a recipe for confusion. Are we seeing any pushback from vendors?

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

lucas16luna16carbon14audit9data9deal7scope7emissions7procurement6software6vendor6vendors5buyers5footprint4enterprise4clause3

Episode notes

Episode 79 of B2B SaaS Talks unpacks the newest clause in enterprise software contracts: the vendor carbon footprint audit. Lucas and Luna trace how procurement teams at firms like Microsoft and JPMorgan are now demanding granular emissions data - Scope 1, 2, and 3 - as a deal-breaker. They walk through a real example: a $15 million CRM deal that stalled for three months because the vendor couldn't provide a verifiable carbon audit. The hosts explain why Scope 3 (supply chain emissions) is the hardest to measure and how startups like Watershed and Persefoni are cashing in on the compliance gap. They also discuss the SEC's new climate disclosure rules (finalized March 2026) and how they're accelerating this trend. If you're selling or buying enterprise software, this episode gives you the language and leverage to navigate the carbon audit clause - and why ignoring it could kill your next deal.

Full transcript

7 min

Transcribed and scored by The B2B Podcast Index.

Lucas: Luna, have you seen the new procurement checklist that JPMorgan sent to its software vendors last quarter? Luna: I haven't, but I'm guessing it's not just about uptime and SLAs anymore. Lucas: Exactly. Buried on page fourteen is a clause that would have been unthinkable three years ago: a mandatory vendor carbon footprint audit.

And it's not optional. You don't comply, you don't get the deal. Luna: So we're talking Scope 1, 2, and 3 emissions data as a contract requirement? Lucas: That's exactly it.

And the interesting part is that JPMorgan is not alone. Microsoft started including similar language in its supplier agreements back in 2023. But now it's spreading fast. I talked to a procurement officer at a large European bank last week, and she told me that over sixty percent of their new software RFPs now include a carbon audit request.

Luna: That's a huge shift. How are vendors actually measuring this? Especially Scope 3 - that's the supply chain emissions, which for a SaaS company could be everything from cloud hosting to employee laptops. Lucas: Right, and that's exactly where it gets messy.

Let me give you a concrete example. There's a mid-market CRM company I'll call CloudSales - about 500 employees, maybe 50 million in annual recurring revenue. They were in the final stage of a 15-million-dollar deal with a Fortune 500 financial services firm. The deal was basically done.

Then procurement drops this carbon audit requirement. Luna: Ouch. Did they have the data? Lucas: Not even close.

They had a rough number for their office electricity - Scope 1 and 2 - but Scope 3? Zero. They didn't know what their AWS hosting emissions were, let alone the carbon footprint of their sales team's flights or the devices they issued to employees. The deal stalled for three months while they scrambled to hire a consultant and implement a carbon accounting tool.

Luna: And did they eventually close? Lucas: They did, but only after they signed up with a platform called Watershed to get a verified audit. And they had to commit to annual reporting with a third-party auditor. The whole process cost them around 200 grand, which is a lot for a mid-market company.

But losing a 15-million-dollar deal would have been worse. Luna: So who are the winners here besides the climate? There's clearly a new compliance software category emerging. Lucas: Absolutely.

Companies like Watershed and Persefoni are the obvious ones. They've built platforms that help enterprises track and report emissions across their entire value chain. Watershed just raised a Series C at a valuation north of two billion. Persefoni is also doing well, especially with financial services firms that need to align with the Partnership for Carbon Accounting Financials.

Luna: And the SEC's new climate disclosure rules - they were finalized in March 2026, right? That's definitely accelerating this. Lucas: It's a huge catalyst. The SEC now requires publicly traded companies to disclose Scope 1 and 2 emissions, and for many, Scope 3 as well, if it's material.

That means if you're a public company buying software, you need your vendors' data to fill in your own disclosure. So procurement is becoming a data-collection function. Luna: So the vendor carbon audit isn't just a nice to have - it's becoming a prerequisite for doing business with any large enterprise. Lucas: Exactly.

And the standard they're using is the Greenhouse Gas Protocol, which categorizes emissions into three scopes. But here's the kicker: there's no universal accreditation body yet for carbon audits. So buyers are having to decide what counts as 'verified.' Some accept a self-reported audit if it's done using a recognized methodology.

Others demand third-party assurance from firms like DNV or SGS. Luna: That sounds like a recipe for confusion. Are we seeing any pushback from vendors? Lucas: Some, but not much.

The vendors that resist are usually smaller ones who don't have the resources. But they're learning quickly that it's a deal-killer. I've heard of a few cases where a vendor outright refused, and the buyer just moved on. There's enough competition in most software categories that buyers can afford to be picky.

Luna: If today's episode was useful for what you're building or running, the way these conversations stay ad-free is listener support. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small way to keep the show going. Appreciate anyone who chips in.

Luna: So back to the carbon audit - what about startups that want to sell to enterprises? Should they start building this capability now? Lucas: Absolutely. If you're a B2B SaaS founder and you're not already collecting emissions data, you're at a competitive disadvantage.

Even if your current customers don't ask for it, the ones you'll want in two years will. And it's not just about compliance - it's also a signal. A company that can show a detailed, verified carbon footprint is saying, 'We're mature, we're transparent, we're ready for your scrutiny.' Luna: It's a trust signal, essentially.

And in enterprise sales, trust is everything. Lucas: Exactly. And here's one more number that stuck with me: according to a survey by Salesforce, 78 percent of enterprise buyers say they've walked away from a deal because the vendor's sustainability practices didn't align with their own. That's not a niche concern anymore - that's mainstream procurement.

Luna: So what's the one thing a vendor should do this week if they want to prepare? Lucas: Start with your cloud provider. If you're on AWS, Azure, or GCP, they all have carbon footprint dashboards. Pull that data.

Then map your employee travel and device procurement. You don't need a full-blown audit yet, but you need a baseline. Once you have a baseline, you can start talking to buyers who ask. Luna: And for buyers, what's the red flag to watch for?

Lucas: If a vendor says they're 'carbon neutral' but can't show you the underlying data, that's a red flag. Carbon neutrality claims are often based on offsets that may not be credible. What you want is a detailed inventory - Scope 1, 2, and 3 - with a clear methodology. The gold standard is third-party verification, but at minimum, they should be using a recognized framework like the GHG Protocol.

Luna: So it's about moving from marketing claims to actual data. That seems like a healthy trend. Lucas: It really is. And I think five years from now, a carbon audit clause will be as standard as a data security clause.

It's just part of doing enterprise software business.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • How Idempotency-Key Design Prevents Payment DisastersThe Developer Tools Podcast with Fexingo · features Luna98 / 100
  • How Kubernetes Topology Spread Constraints Create Scheduling HotspotsDevOps Daily with Fexingo · features Luna95 / 100
  • Why Pipeline Velocity Trumps Deal Size Every TimeThe Growth Operator with Fexingo · features Luna95 / 100
  • How B2B Brands Wreck Pipeline with Unsyncroned CRM DataThe Marketing Operator Podcast with Fexingo · features Luna92 / 100
  • Why Marketing Attribution Misses the Seasonality PatternMarketing Analytics with Fexingo · features Luna91 / 100
  • How to Sell Against a Competitor Already in the BuildingSales Leadership with Fexingo · features Luna85 / 100

More from B2B SaaS Talks with Fexingo

All episodes →
  • Enterprise Buyers Now Demand a Vendor Software Bill of Materials81 / 100
  • Enterprise Software Buyers Now Demand a Vendor Data Portability Guarantee82 / 100
  • Why Enterprise Software Deals Now Include a Vendor AI Model Explainability Mandate94 / 100
  • Enterprise Software Buyers Now Demand a Vendor AI Training Data Provenance Audit80 / 100
  • Why Enterprise Buyers Now Mandate a Vendor AI Bias Audit85 / 100
Explore the best B2B Sales podcasts →
All B2B SaaS Talks with Fexingo episodes →