Practice · X.

Google Cloud. EDP, CUD and Workspace.

The GCP enterprise commitment design, the Committed Use Discount and Resource-based Commitment mix, the Workspace renewal and seat reconciliation, the Gemini for Workspace and Vertex AI commitments, the BigQuery edition pricing, and the Marketplace commitment counting. Google Cloud contracts close on a workload-by-workload commitment design and a Workspace seat reconciliation, not on the headline discount percentage. Independent buyer-side advisory across compute, BigQuery, Vertex AI, Workspace and the wider GCP estate.

Speak with a Senior Advisor Engagement models

Where the practice intervenes

Six points on the Google Cloud commercial cycle.

Pre-renewal

Estate reconstruction

Nine months before the EDP or Workspace anchor, the Google Cloud estate is reconstructed across GCP compute, GKE, Cloud Storage, BigQuery editions, Vertex AI, Workspace, Marketplace and the partner channel. Project hierarchy, CUD and resource-commitment burn-down, Workspace seat usage and forecast workload growth are mapped. The position paper governs the renewal commercial conversation.

Commitment

ii.

EDP and CUD design

GCP enterprise commitment is sized against documented workload growth at project and business-unit level. CUD mix across spend-based, resource-based, flexible and one-year and three-year terms is tuned. Multi-year ramp, overrun protection, underrun forgiveness, partial-year credit treatment and the closing-year cliff are negotiated.

Workspace

iii.

Seat and edition reconciliation

Workspace seat populations are reconciled against active usage. Frontline, Business Starter, Business Standard, Business Plus, Enterprise Standard and Enterprise Plus edition mix is tuned against documented use. Storage allocation, Vault scope, and edition swap rights at the renewal anchor are documented.

BigQuery

iv.

Edition and slot design

BigQuery Standard, Enterprise and Enterprise Plus editions, autoscaling slots, baseline slot commitment and storage tier mix are designed against documented workload at project level. Edition swap rights at term boundary and slot consumption controls are documented.

Gemini / Vertex

AI commitment scope

Gemini for Workspace seat commitment, Vertex AI model serving, training pipeline cost and the AI agent commitments are sized against documented use cases at functional-population level. Pilot scope, expansion criteria, dollarised business case and exit-to-on-demand terms are documented before the AI commitment is approved.

Multi-year

vi.

Closing contract terms

The renewal closes against a multi-year commitment with documented discount tiers, overrun protection, underrun forgiveness, contraction rights, edition swap rights and the renewal anchor terms. The closing contract is reviewed clause by clause. The senior advisor sits opposite the publisher's account team for the full negotiation.

Named senior advisor

The senior advisor named on the engagement letter leads every Google Cloud conversation. No leverage model, no rotation of junior consultants, no anonymous correspondence with the publisher. The advisor signs every position document.

II.

Counter-signed positions

Every written counter-position to Google Cloud is signed by the senior advisor and counter-signed by a second partner before transmission. Two named signatures on every position document for the full five-year retention period.

III.

Independent on every clause

Admodum holds no commercial relationship with Google. No reseller margin, no partner status, no Marketplace seller relationship. We do not work both sides.

IV.

Commitment is a risk, not a discount

Every CUD and EDP commitment is modelled against documented workload growth, overrun protection and underrun forgiveness. The commitment risk is documented at signature and reviewed quarterly through the term.

Five-year retention

Every position paper, counter-position, and closing memorandum is retained inside the firm for five years from engagement close. The buyer can request source workings at any point.

VI.

Reset the baseline every cycle

Every Google Cloud commitment renewal closes with a written baseline reset. The closing position, the contractual amendments accepted, and the live obligations carried forward are tied into the next renewal preparation cycle through the Renewal Programme.

Operating principles

How the practice is run.

Commitment is risk.

EDP and CUD commitments lock workload to instance family, region and term. The commitment is modelled against documented workload growth at project and business-unit level, with overrun protection and underrun forgiveness in the closing contract.

Workspace by edition mix.

Workspace edition mix is tuned against documented use at functional-population level. Frontline, Business and Enterprise tiers carry different entitlement needs. The right edition mix is documented per population with swap rights at the anchor.

BigQuery by workload.

BigQuery edition, slot commitment and storage tier are designed at project level against documented query workload. Edition swap rights and slot consumption controls are documented at signature.

AI with a documented exit.

Gemini and Vertex AI commitments are approved against a documented business case at functional-population level, with documented expansion criteria and exit-to-on-demand terms.

Questions

Asked before engagement.

How should we size a Google Cloud EDP?

On three reads: trailing-twelve-month consumption, the documented migration plan, and an independent FinOps forecast. Google's proposed ramp reflects the account team's narrative; the buyer's ramp should reflect signed procurement only.

Which CUD type should we use?

Stable workloads on known machine types take Compute CUDs (deepest discount, narrowest applicability); variable compute takes Spend-Based CUDs; service-specific commitments take Resource-Based CUDs. The mix is then sized against the EDP floor.

How do we rationalise Workspace seats?

Map the trailing active-user evidence onto the tier mix actually consumed. Tier over-stretch, inactive seats and suspended accounts are the three recurring findings, and the renewal window is the reset point.

How are engagements priced?

Three frameworks: fixed fee for scoped deliverables, contingency tied to verified savings, and an annual retainer for continuous coverage across every vendor. The model is agreed on the first call, which is always complimentary, and independence is warranted in writing on every engagement letter.