Net Zero Cloud—Salesforce's sustainability and carbon accounting capability, evolved from the original Sustainability Cloud and now broadened to cover Scope 1, 2, and 3 emissions tracking, supplier engagement, energy and water management, waste tracking, and the regulatory reporting surface that overlays each of those—has matured into a commercial commitment large enough to warrant its own negotiation discipline. The product sits in the Industries portfolio, and its commercial structure borrows the same patterns we see across Financial Services Cloud and Health Cloud: a base subscription priced per user, several add-on capability bundles priced per user or per organization, and a consumption-priced data ingestion surface that scales with the breadth of supplier and asset data the customer chooses to track.
Three things have shifted the Net Zero Cloud commercial discussion since 2024. First, the regulatory environment has hardened. CSRD in the EU, California's SB 253 and SB 261, and the SEC climate disclosure framework have moved sustainability reporting from a voluntary disclosure into a regulated filing for a growing share of the customer base. Second, Salesforce has shifted Net Zero Cloud's positioning from a marketing-led ESG narrative into a compliance-led reporting capability, which has changed the persona buying the product and the urgency profile of the deal. Third, the consumption surface—particularly around supplier engagement and Scope 3 data ingestion—has expanded faster than the licensing surface, which means the commercial commitment increasingly behaves like a hybrid subscription-and-consumption contract.
What the Net Zero Cloud capability set actually includes
The capability surface spans five distinct categories. Core emissions accounting covers Scope 1 emissions from owned operations, Scope 2 emissions from purchased energy, and the foundational accounting capability that calculates emissions from activity data. Scope 3 supplier engagement covers the broader supply chain emissions surface, including supplier outreach workflows, supplier-reported emissions intake, and the supplier ESG questionnaire surface. Energy, water, and waste management covers the operational sustainability metrics beyond emissions, including water consumption tracking, waste stream tracking, and the operational efficiency reporting layer. Regulatory reporting covers the disclosure formats required by CSRD, the California climate framework, the SEC climate framework, and the various regional and industry-specific reporting regimes. Climate analytics and target-setting covers the science-based target tracking, scenario modeling, and the broader climate strategy analytics layer.
Each of these categories has a different commercial structure. The core emissions accounting capability is bundled into the base Net Zero Cloud subscription. The supplier engagement capability is priced as an add-on with both per-user and per-supplier scaling. The energy, water, and waste management capabilities are typically priced per-facility or per-asset. The regulatory reporting capability is priced per-deployment with regulatory-regime-specific scaling. The climate analytics capability is priced as an add-on with consumption-based scaling for the scenario modeling and predictive analytics dimensions.
| Capability | Pricing model | Typical scope driver |
|---|---|---|
| Core emissions accounting | Per-user, included in base | Sustainability team headcount |
| Supplier engagement | Per-user + per-supplier | Reportable supplier population |
| Energy & water management | Per-facility, per-asset | Operational footprint |
| Waste tracking | Per-facility | Operational footprint |
| Regulatory reporting | Per-deployment, per-regime | Regulatory exposure |
| Climate analytics | Per-user + consumption | Modeling workload |
The Scope 3 supplier engagement scope is where the bill explodes
The most material commercial surface in a Net Zero Cloud discussion is the Scope 3 supplier engagement scope. Scope 3 emissions—the supply chain emissions outside the customer's direct operational control—frequently constitute 70-90% of a customer's total emissions footprint, which has made the supplier engagement capability the centerpiece of most Net Zero Cloud deployments. The capability is priced with a per-user component for the customer's sustainability team and a per-supplier component for the supplier population that the customer engages through the platform.
The per-supplier scaling is the dimension where the commercial commitment most often runs ahead of the operational reality. A customer with a global supplier base of 8,000-15,000 vendors does not typically engage every supplier in the platform. Realistic supplier engagement scopes are concentrated in the regulated subset, the top-tier strategic suppliers, and the suppliers in carbon-intensive categories. Scoping the supplier engagement capability against the full global supplier base produces a commercial commitment 3-5x larger than the operational reality demands.
The disciplined approach is to scope the supplier engagement capability against the supplier population that the customer actually intends to engage in the first year of the deployment, with explicit expansion mechanics for years two and three. The expansion mechanics should specify the per-supplier pricing for the additional supplier populations, the volume thresholds at which the per-supplier pricing steps down, and the customer's right to scope down the supplier population if the actual engagement falls short of the original assumptions.
The regulatory reporting capability deserves separate negotiation attention
The regulatory reporting capability is priced per-deployment with regulatory-regime-specific scaling. The customer with CSRD exposure pays for the CSRD reporting capability. The customer with California climate framework exposure pays for the California reporting capability. The customer with SEC climate exposure pays for the SEC reporting capability. The customer with multiple regulatory exposures pays for each regime separately, with the regulatory-regime-specific scaling adding up to a substantial commercial commitment for customers with broad regulatory exposure.
The disciplined approach to the regulatory reporting capability is to scope each regulatory regime against the specific regulatory requirements the deployment actually supports, not against the maximum addressable regulatory surface. The negotiation should also secure the customer's rights to expand the regulatory regime coverage at pre-agreed pricing as regulatory exposure changes, and the customer's right to scope down the regulatory regime coverage if regulatory exposure narrows.
The four levers that move the price
1. Scope the supplier engagement against the engaged supplier population
The supplier engagement capability should be scoped against the supplier population the customer actually intends to engage in the first year, with explicit expansion mechanics for the subsequent years. The disciplined scoping captures the operational use case without the multiplicative licensing exposure that occurs when the supplier engagement capability is scoped against the full global supplier base. The right-sized scope is typically 20-40% of the full supplier base for first-year deployments.
2. Right-size the regulatory reporting capability against actual regulatory exposure
The regulatory reporting capability should be scoped against the specific regulatory regimes the deployment supports. A customer with European operations and CSRD exposure should license the CSRD reporting capability. A customer with California operations should license the California climate framework capability. The disciplined scoping prevents the regulatory-regime overcommitment that occurs when the customer licenses every available regulatory reporting capability without operational use.
3. Negotiate the per-facility and per-asset scaling explicitly
The energy, water, and waste management capabilities are priced per-facility or per-asset. The customer should negotiate the per-facility pricing explicitly, with volume thresholds at which the per-facility pricing steps down, and with the customer's right to scope down the facility count if operational footprint changes. The per-facility scaling is the dimension where the disciplined negotiation captures meaningful commercial outcomes for customers with broad operational footprints.
4. Coordinate with the broader Salesforce commercial commitment
The Net Zero Cloud commercial commitment should be coordinated with the broader Salesforce commitment. The bundled negotiation captures volume leverage and prevents the negotiation-leverage dilution that occurs when sustainability capabilities are licensed sequentially. The bundling is particularly important when Net Zero Cloud adoption is positioned as a strategic capability for the broader Salesforce deployment, and when the customer has parallel commitments across Sales Cloud, Service Cloud, Data Cloud, or the Industries portfolio.
The pitfalls that show up in the order form
Five patterns appear repeatedly in Net Zero Cloud order forms. First, the supplier engagement capability is scoped against the full global supplier base rather than against the engaged supplier population. Second, the regulatory reporting capability is licensed at maximum addressable regulatory scope rather than against the specific deployment exposure. Third, the per-facility and per-asset pricing is silent on volume thresholds, exposing the customer to discretionary repricing as operational footprint changes. Fourth, the renewal mechanics are silent on the supplier population and the regulatory regime coverage, exposing the customer to discretionary repricing at the renewal moment. Fifth, the order form does not specify the customer's rights to scope down the supplier population, the regulatory regime coverage, or the facility count if operational reality falls short of the original commercial assumptions.
What a well-negotiated Net Zero Cloud commitment looks like
A well-negotiated Net Zero Cloud commitment has seven features. The supplier engagement capability is scoped against the engaged supplier population, not against the full global supplier base. The regulatory reporting capability is scoped against the specific regulatory regimes the deployment supports, with explicit expansion mechanics for additional regimes. The per-facility and per-asset pricing has volume thresholds, with the per-facility pricing stepping down at pre-agreed thresholds. The renewal mechanics specify the supplier population, the regulatory regime coverage, and the facility count protections explicitly. The commitment is bundled into the broader Salesforce commercial discussion. The customer retains the right to scope down the supplier population, the regulatory regime coverage, or the facility count if operational reality falls short. And the order form specifies the Scope 3 data ingestion consumption pricing and the customer's protections against consumption overruns.
Benchmark outcomes by deployment scale
For a mid-market customer with 200-800 sustainability and operational users, 1,000-3,000 engaged suppliers, and 1-2 regulatory regime exposure, the median annual Net Zero Cloud commitment lands at $180,000-$420,000. Top-quartile outcomes—achieved through disciplined supplier engagement scoping and regulatory regime right-sizing—sit in the $140,000-$280,000 range. The bottom quartile lands at $380,000-$680,000 for equivalent deployments where the supplier engagement capability was scoped against the full global supplier base.
For a large-enterprise customer with broader operational footprint and multi-regime regulatory exposure, the median annual commitment lands at $1.2M-$3.4M. Top-quartile outcomes reach $780,000-$2.1M through disciplined scoping. The bottom quartile lands at $2.4M-$5.2M for equivalent operational footprint with undisciplined scoping.
The renewal data that wins
The single most valuable artifact for a Net Zero Cloud renewal is a scope-by-scope operational consumption report: which supplier populations have actually been engaged, which regulatory regimes have actually been reported, which facilities and assets have actually been tracked, and which capabilities have produced operational outcomes. The report establishes the operational baseline that supports the next renewal conversation and prevents the discretionary repricing that occurs when the customer arrives at renewal without operational data.
Where to begin
If your Net Zero Cloud deployment is in scoping, the most useful first step is a scope-by-scope operational plan. Document the specific supplier population, the regulatory regime exposure, and the facility footprint that the deployment will actually support in the first year, with expansion mechanics for the subsequent years. The plan establishes the disciplined scope and the foundation for the commercial commitment. If your Net Zero Cloud deployment is already in production, the most useful first step is a scope-by-scope consumption analysis that establishes the operational baseline for the next renewal conversation.
The strategic frame
The Net Zero Cloud commercial discussion is ultimately a strategic sustainability platform decision. The choice has long-term implications for the customer's sustainability reporting strategy, the regulatory compliance posture, and the cost trajectory of the broader Salesforce footprint. The commercial decision should be framed against the strategic question with explicit scope discipline and operational measurement. Customers who treat the Net Zero Cloud decision as a strategic platform decision—with disciplined scoping and measured operational outcomes—consistently outperform customers who treat it as a default sustainability capability bundled into the broader Salesforce footprint without scope-by-scope discipline.