Salesforce Net Zero Cloud: Edition Pricing Explained

Net Zero Cloud (rebranded as Agentforce Net Zero) is Salesforce’s ESG and carbon-accounting product, and it breaks from the familiar per-seat CRM pricing pattern in a specific way: it’s sold as a flat per-organization annual edition fee that bundles a fixed number of CRM licenses, rather than charging per user. Salesforce doesn’t publish this as a line-item public rate card the way it does for standard Sales Cloud editions, so the specific figures reported by third-party sources should be treated as illustrative rather than a quoted price for any given org.

How the edition-tier model works

• Flat per-org annual fee, not per-seat. Reported pricing describes two editions — a lower Starter tier bundling a small number of CRM licenses, and a higher Growth tier bundling more — each sold as a single annual org-level fee rather than a per-user rate.
• The bundled license count is a ceiling, not a floor. Once an organization needs more users accessing Net Zero Cloud than the edition’s bundled license count covers, additional licenses are purchased on top of the base edition fee — at that point the pricing starts behaving more like conventional per-seat licensing layered onto a fixed base.
• Add-ons are priced separately. Beyond the base edition, additional ESG data modules and integrations are commonly sold as separate add-ons rather than bundled into either tier.
• The edition jump is a step function, not a gradual scale. Because pricing is tiered by edition rather than metered by usage, an organization that outgrows the Starter tier’s bundled license count faces a full jump to the next edition’s price point, not a proportional increase.

Why this mechanic is genuinely different from most Salesforce clouds

Most Salesforce industry clouds and add-ons layer a per-user premium on top of standard Sales or Service Cloud licensing. Net Zero Cloud’s edition-based, bundled-license structure means the initial per-org fee can look attractive for an organization within the bundled license count — but it also means the pricing conversation is about which edition tier fits the reporting team’s size, not about optimizing individual seats the way a per-user product would allow.

Net Zero Cloud vs. a narrower custom build

	Salesforce Net Zero Cloud	Custom-built ESG data layer
Pricing	Flat per-org edition fee, bundled license count	Flat monthly fee, no license-count ceiling
Growing past the bundle	Additional per-seat licenses, or a full edition-tier jump	Unchanged
Best fit	Organizations needing Salesforce’s native ESG data model and reporting	Specific carbon-tracking or reporting workflows synced from existing data sources

Where the fix actually lives

For a sustainability or compliance team whose reporting needs are narrower than the full ESG data model Net Zero Cloud provides, a custom-built reporting and data-collection layer — synced to existing operational and utility data via API — can carry that workflow on a flat monthly fee, independent of a bundled license count or edition-tier jump. See Salesforce Nonprofit Cloud’s licensing ceiling for a similar industry-edition mechanic, and how to reduce CRM and industry-cloud licensing costs for the broader pattern.

Frequently asked questions

Does Salesforce publish an official Net Zero Cloud price list?

Not as a detailed public rate card in the way some SaaS vendors do — reported edition pricing circulates from third-party sources and partner materials, so treat any specific figure as illustrative rather than confirmed for your org’s negotiated contract.

What happens once we exceed the bundled license count?

Additional users typically require purchasing incremental licenses on top of the base edition fee, and growing significantly past the lower edition’s intended scale usually means evaluating the next edition tier up rather than a small incremental charge.

Is a custom build a replacement for Net Zero Cloud’s native ESG data model?

Not for organizations that need Salesforce’s built-in emissions-factor libraries and native reporting structure — the opportunity is narrower: teams whose actual need is a specific data-collection or reporting workflow that doesn’t require the full platform.