Part of our Cloud Contract Negotiation Guide. For provider comparisons see our AWS vs Azure vs GCP commercial analysis. For egress-specific strategy, see our cloud egress negotiation guide.
Google Cloud's Discount Architecture
Google Cloud's pricing model differs from AWS and Azure in one important structural respect: Google Cloud applies Sustained Use Discounts (SUDs) automatically and without commitment. When you run Compute Engine instances for more than 25% of a billing month, Google begins applying incremental discounts that scale to a maximum of 30% for full-month utilisation. These automatic discounts exist before any negotiation and provide a base-level cost reduction that AWS and Azure do not offer through equivalent mechanisms.
On top of SUDs, Google Cloud offers Committed Use Discounts (CUDs) — explicit commitments to a resource level or spend level in exchange for substantial additional discounts. And for organisations spending $1M+ annually, Custom Pricing Agreements (CPAs) open the door to further negotiated discounts, service-specific pricing, and commercial arrangements that go well beyond the standard CUD structure.
CUD Types: Resource-Based vs Spend-Based
Understanding the distinction between resource-based and spend-based CUDs is the foundational step in Google Cloud cost optimisation. They serve different needs and offer different discount levels.
Resource-Based CUDs
Resource-based CUDs commit to a specific resource level — measured in vCPUs, memory, GPUs, or local SSDs — for a specific machine family in a specific region for one or three years. In exchange, Google offers substantial discounts: 37% off on-demand pricing for one-year commitments and 55% off for three-year commitments. These are among the largest available cloud commitment discounts in the market and make resource-based CUDs highly attractive for stable, predictable compute workloads with defined resource profiles.
The limitation of resource-based CUDs is their inflexibility. Committing to specific machine types and regions works well for stable production workloads but creates risk for organisations that are still migrating, optimising, or uncertain about their long-term compute architecture. If you commit to n2-standard resources and later move to compute-optimised c2 instances, your CUD does not follow — you will be paying the CUD commitment while also consuming different compute at on-demand rates.
Spend-Based CUDs
Spend-based CUDs commit to a minimum dollar amount of eligible services per hour for one or three years. Discounts are lower — 17% for one-year commitments and 22% for three-year commitments — but the flexibility is considerably greater. Spend-based CUDs apply to a broad range of Google Cloud services including Compute Engine, Cloud SQL, and selected other services, regardless of the specific instance types or regions used. For organisations with evolving workload profiles or those still in cloud migration phases, spend-based CUDs offer a way to capture commitment discounts without locking into specific resource configurations.
| CUD Type | Commitment Basis | 1-Year Discount | 3-Year Discount | Best For |
|---|---|---|---|---|
| Resource-Based | vCPU / Memory / GPU in specific region and machine family | 37% | 55% | Stable compute, defined architecture |
| Spend-Based | $/hour across eligible services | 17% | 22% | Mixed workloads, migration phase, evolving architecture |
Most enterprise Google Cloud optimisation strategies combine both CUD types: resource-based CUDs for the stable, identifiable portion of compute workloads and spend-based CUDs for the variable or service-mixed portion. The art is in the allocation — committing too much to resource-based CUDs before your architecture is stable creates waste; committing only to spend-based CUDs foregoes the higher discounts available for stable workloads.
Sustained Use Discounts: The Free Foundation
One nuance in Google Cloud discount stacking is that CUDs and SUDs interact. When you hold a resource-based CUD, Google still applies SUDs on top for usage that exceeds your CUD allocation. However, because CUDs already deeply discount the committed portion, the incremental value of SUDs on CUD-covered resources is lower than on uncovered resources. Understanding this interaction is important for correctly modelling total discount impact.
The practical implication is that Google Cloud's automatic SUDs provide meaningful value for variable compute workloads that fluctuate above the 25% monthly utilisation threshold but do not justify a full commitment. For workloads in this category, the decision between purchasing a spend-based CUD versus relying on SUDs alone depends on stability assumptions. At 70%+ consistent monthly utilisation, a spend-based CUD is almost always superior. Below 40% monthly utilisation, SUDs alone may be sufficient.
Google Cloud vs AWS on automatic discounts: AWS offers no equivalent to Google's Sustained Use Discounts — all compute discounts on AWS require explicit action (RI purchase or Savings Plan). This makes Google Cloud inherently more cost-efficient for variable workloads that AWS requires active management to optimise. When comparing true cost of ownership, this structural difference should be included in the analysis.
Custom Pricing Agreements: The Enterprise Layer
For organisations spending $1M+ annually on Google Cloud, the Custom Pricing Agreement (CPA) opens an additional negotiation layer beyond self-service CUDs. CPAs are private, negotiated commercial arrangements that can include service-specific discounts beyond standard CUD rates, egress credits, support package customisation, migration incentives, and in strategic cases, committed usage credits and proof-of-concept subsidies.
Google Cloud's CPA process is less standardised than AWS's EDP. This is both an opportunity and a challenge. The opportunity is that GCP commercial teams have genuine discretion to structure creative arrangements — a well-prepared enterprise buyer engaging GCP's commercial organisation with clear competitive alternatives and a specific commercial request will often achieve better-than-standard terms. The challenge is that without independent benchmarks, it is difficult to assess whether a CPA offer is commercially competitive or simply better than list pricing.
CPA Negotiation Tactics
The most effective CPA negotiations share several characteristics. First, they occur in the context of a genuine competitive evaluation — GCP is most commercially aggressive when AWS or Azure is a credible alternative. Second, they are specific: rather than asking for "better pricing," effective negotiators come with explicit requests for service-specific discounts on their highest-spend services. Third, they leverage GCP's market share growth ambitions — Google Cloud's commercial team operates with significant authority to capture strategic accounts, and framing the CPA as a "primary cloud commitment" unlocks additional commercial discretion.
Migration incentives deserve particular attention. Google Cloud has historically offered migration credits of $100K–$1M+ for organisations committing to move significant workloads from AWS or Azure to GCP. These credits are real economic value but must be modelled against the long-term economics of the platform. An organisation that accepts $500K in migration credits and then discovers that GCP's per-unit economics are 15% higher than AWS for their specific workload mix will pay back the credits many times over during a three-year commitment.
Google Cloud Commercial Risks
Google Cloud's competitive commercial posture creates specific risks that informed enterprise buyers should manage. First, service discontinuation risk: Google has a documented history of retiring products and services, including several enterprise-relevant offerings. Any long-term GCP commitment should include service continuity provisions or at minimum a clear migration path guarantee for discontinued services. Second, pricing trajectory: GCP has changed pricing structures more frequently than AWS or Azure, and some price changes have been unfavourable to committed customers. Third, support quality at enterprise scale: GCP's enterprise support infrastructure is improving but remains below the maturity of AWS's enterprise support organisation at equivalent spend levels.
None of these risks make Google Cloud an unsuitable enterprise platform — for the right workloads, GCP offers genuine technical and commercial advantages, particularly in data analytics, machine learning, and Kubernetes-native architectures. The point is that these risks should be managed through contractual provisions, not ignored.
A GCP Cost Optimisation Framework
The recommended sequence for Google Cloud cost optimisation is as follows. Start with a baseline assessment: What is your current GCP spend by service, region, and workload? What portion of compute usage meets the threshold for SUDs, and what is the actual SUD benefit you are receiving? This baseline identifies both the current cost structure and the opportunities for improvement.
Second, identify stable compute workloads suitable for resource-based CUDs. Workloads with 80%+ consistent monthly utilisation in fixed regions with defined machine types are candidates. Model the three-year commitment economics carefully — the 55% discount is compelling, but over-commitment is expensive.
Third, assess the residual variable spend for spend-based CUD coverage. The spend-based CUD applies across eligible services and provides a lower but meaningful discount on the portion of spend that cannot be confidently committed as resource-based.
Fourth, if your annual GCP spend exceeds $1M, engage GCP's enterprise commercial team for a CPA discussion. Come prepared with specific requests, competitive alternatives, and a clear view of what a long-term GCP commitment would look like for your organisation.
Finally, consider egress costs as a separate negotiation track. See our guide to cloud egress negotiation for GCP-specific tactics.
The leading advisory firms for Google Cloud commercial strategy include Redress Compliance, which provides GCP-specific commercial benchmarking and CPA negotiation support alongside AWS and Azure advisory. Our Cloud Contract Negotiation practice provides dedicated Google Cloud advisory from former GCP commercial executives. See our Cloud Contract Framework white paper for GCP benchmark data and CUD optimisation models.