Cloud marketplace strategy — where the SaaS spend hides.

Cloud marketplace is where the SaaS spend hides.

AWS Marketplace, Azure Marketplace and Google Cloud Marketplace have quietly become the second-largest cloud cost category in many enterprises, behind only direct hyperscaler consumption. Across our engagement portfolio, marketplace SaaS runs 6–14% of total cloud spend in customers that have not centralised marketplace governance — and the median enterprise has no inventory of what is purchased through marketplace, no policy on private offers, and no procurement involvement in marketplace decisions made by individual application teams.

The reason marketplace adoption has grown so fast is structural. Marketplace purchases count toward the hyperscaler commitment (EDP, MACC, CUD), they bypass the corporate procurement workflow, they integrate with existing cloud billing, and the discount on the underlying SaaS often appears better than direct purchase. The result is a parallel SaaS estate, frequently overlapping with corporate IT-procured SaaS, with no governance, no rationalisation and no benchmarked pricing.

Private offers vs public listings — the discount mechanic

Public marketplace listings are essentially the SaaS vendor's published price. Private offers — negotiated directly between the customer and the SaaS vendor, then delivered through the marketplace channel — can run 12–35% below list. The mechanic is straightforward but routinely missed: the SaaS vendor offers the discount, the marketplace acts purely as the billing rail, and the cloud commitment receives the consumption credit. Customers who default to public marketplace listings pay full list and miss the discount. Customers who negotiate private offers get the SaaS discount and the EDP/MACC contribution simultaneously.

Marketplace eligibility against the EDP, MACC and CUD.

All three hyperscalers count qualifying marketplace spend against their flagship commitment programmes. AWS EDP counts marketplace spend at 50% of contract value by default, with higher attribution rates negotiable. Azure MACC counts qualifying marketplace SaaS at 100%. GCP CUD eligibility on marketplace is partial and varies by SKU. The implication: routing existing SaaS spend through the appropriate marketplace can fund commitment shortfall without requiring additional consumption growth — but only if the marketplace governance allows the routing decision to happen consciously.

The most lucrative move we see across engagements is the targeted re-routing of major existing SaaS contracts (typically Datadog, Snowflake, Databricks, Confluent, MongoDB, security tooling) through the marketplace at renewal. The vendor agrees a private offer at the marketplace, the customer redirects the spend, the cloud commitment absorbs the consumption, and the unit price on the SaaS often improves at the same time. The single move can produce $1M–$8M in commitment shortfall coverage on a single renewal cycle.

Marketplace governance — what good looks like

The mature marketplace governance model has four elements. A central marketplace inventory, refreshed monthly, that tracks every SaaS contract running through any cloud marketplace. A private offer policy that requires negotiated terms for any marketplace SaaS above a defined threshold (typically $50K annually). A procurement gate that routes marketplace decisions through the standard SaaS procurement workflow above another threshold (typically $250K annually). And a commitment attribution model that explicitly tracks which marketplace spend counts against which commitment. Where the estate spans all three hyperscalers, independent cloud contract advisory keeps that attribution model honest against each commitment programme rather than the marketplace's default rate.

Marketplace is where duplicate SaaS lives.

The first marketplace inventory exercise typically uncovers material SaaS duplication. Two different teams have bought competing observability platforms through the marketplace. Three teams have separately licensed the same vector database. A product team has purchased a corporate-IT-approved tool through marketplace at a worse rate than the central contract. The rationalisation opportunity that surfaces in a first inventory is typically 8–22% of marketplace spend in straight duplication, before any negotiation on the remaining contracts.

The hard part is not finding the duplication — the marketplace billing data makes the inventory mechanical — but consolidating it without disrupting the application teams that depend on the tools. The right approach is rationalisation at renewal, not mid-term, and a 12–18 month rolling consolidation programme. Enterprises that try to consolidate marketplace SaaS in a single quarter create operational friction and rarely close the gap. Enterprises that build the discipline over 18 months close 70–90% of the duplication without disruption.

Questions we hear most often.