EDP contracts expire on the commitment anniversary. Start renewal preparation 9 months out. Issue competitive RFP 6 months out. Sign 60 days before expiration. Always file 60-day non-renewal notice regardless of intent, it preserves negotiating leverage at zero cost.
— amazon-web-services-aws-discount-negotiation
EA contracts have defined renewal anniversaries. Start preparation 9 to 12 months out. Issue competitive AWS RFP 6 months out. Sign 60 days before expiration. Always file 60-day non-renewal notice regardless of intent.
— microsoft-azure-discount-negotiation
GCP custom contracts have defined expiration dates. Start renewal preparation 9 months out. Issue competitive AWS or Azure RFP 6 months out. Sign 60 days before expiration. Always file 60-day non-renewal notice to preserve leverage.
— google-cloud-platform-gcp-discount-negotiation
Databricks enterprise agreements auto-renew unless the customer provides written notice typically 60 to 90 days before anniversary. Miss the window and you're locked into uplifted per-DBU pricing for the next term. Send a formal written notice of intent to evaluate non-renewal 120 days before anniversary as standard procurement hygiene.
— databricks-discount-negotiation
Renewal calendar horizons#
| Tier | Planning Horizon | Typical Vendors | Savings Capture |
|---|---|---|---|
| Tier 1 | 12-18 months | Oracle, Microsoft, SAP, Salesforce, ServiceNow, Workday, AWS, Google Cloud, Adobe, IBM | 100% of benchmark when started on time |
| Tier 2 | 6-9 months | Snowflake, Databricks, Datadog, Atlassian, Slack, GitHub, Box, Okta, CrowdStrike | 100% of benchmark at 9 months; 70% at 4 months |
| Tier 3 | 3-6 months | Long tail SaaS, single department tools, niche analytics | 100% at 5 months; 65% at 2 months |
| Cloud commits | 9-15 months | AWS EDP, Google Cloud CUD, Azure MACC | Drift period analysis requires 9+ months |
The Tier 1 layer also tracks cross product mechanics that do not exist on Tier 2 or Tier 3. Microsoft EA price protection clauses across the agreement term, SAP digital access document tier reconciliation, Salesforce ELA scope expansion, Oracle ULA exit certification windows, ServiceNow tiered subscription pack rebalancing, Workday subscription unit pricing tier movements, AWS EDP commitment cliff dates, and Google Cloud CUD overlap windows are all calendar entries on the Tier 1 layer that have no Tier 2 equivalent. See the renewal negotiation playbook for the framework that operates these mechanics, and the Tier 1 vendor strategy for the per vendor approach.
The Tier 2 layer covers 20 to 60 vendors that account for 15 to 28 percent of total spend. The calendar mechanics are lighter. Each row tracks renewal date, notice date, ACV, tier, owner, and status. The negotiation milestones run on a 6 to 9 month horizon. Snowflake credit commits, Databricks DBU pricing, Datadog product mix rebalancing, Atlassian server to cloud migration deadlines, Okta SKU rationalization, and Slack to Teams consolidation candidate analysis sit on the Tier 2 layer.
— software-renewal-calendar-template
What changes at renewal#
- On-demand list prices: AWS raises these 5 to 15% every 12 to 18 months. This flows through to RI and Savings Plan discounts if you're calculating from a new baseline.
- Data egress pricing: Historically unchanged, but monitor this.
- EDP commitment amounts: AWS will pressure you to increase your annual commit if your usage has grown, sometimes significantly.
Start negotiating 60 to 90 days before renewal. AWS will argue for higher EDP commits based on your trailing 12-month usage (sometimes using your peak month, not average). Counter with trailing 6-month average plus modest growth projections.
— amazon-web-services-aws-pricing
- List prices: Azure raises list prices 5 to 10% annually, effective in April/May (end of Microsoft's fiscal year in June)
- Data egress: Historically flat at $0.087/GB, but monitor for changes
- AMC commitment: Microsoft will push for +15 to 30% based on 12-month trailing usage
- Support pricing: Unified Support costs creep up as your consumption grows
If your usage has grown 25% year-over-year, Microsoft will demand a 25%+ increase in AMC. Counter with trailing 6-month average + modest growth (8 to 12%). You'll typically compromise at +15 to 20% vs. current commitment.
- Private Agreement pricing: If you have a multi-year Private Agreement with a price ceiling (e.g., "GCP spend will not exceed $500K/month"), that ceiling usually holds through the renewal.
- Support tiers and TAM allocation: Once negotiated, support coverage is sticky, Google doesn't reduce TAM hours unless you reduce overall spend by 20%+.
- Credit commitments: If Google committed $100K in Vertex AI credits, renewal should include a similar credit pool.
- Per-resource pricing within a Private Agreement: If your usage patterns have shifted (less Compute Engine, more BigQuery), you can often renegotiate per-resource prices at renewal.
- CUD coverage percentages: CUDs expire after 1 to 3 years. At renewal, you can choose to re-commit, shift to different resource types, or move to a custom pricing agreement.
- Multi-region vs single-region pricing: If you've consolidated workloads into fewer regions by renewal, you may negotiate region-specific volume discounts.
Some enterprises renew without formally renegotiating and discover list prices have increased (Google raises list prices 3 to 5% annually, particularly for new VM types). Always model your renewal cost as if you're starting fresh, this forces the conversation about your actual consumption and ensures you capture any new discount mechanisms.
— google-cloud-platform-gcp-pricing
Databricks renewals are influenced by the company's growth trajectory and commercial ambitions. The opening renewal proposal will reflect the maximum contractual escalation, plus expansion proposals for AI workloads (Mosaic AI, Vector Search) that may not be in the current agreement. The framing is "Data Intelligence Platform" investment, emphasizing AI capabilities and the platform's role in enterprise AI strategy rather than pure data engineering value.
Renewal discounts achievable with preparation: flat per-DBU pricing versus prior year (eliminating standard escalation) in exchange for expanded workload commitment or multi-year term; 5 to 10% per-DBU reduction with a documented Snowflake evaluation; or tiered pricing that reduces per-DBU costs for the highest-consumption workload types in exchange for a higher minimum commitment. The most common successful renewal structure is a multi-year platform commitment (3 years) that locks per-DBU pricing for the full term in exchange for an annual commitment step-up.
What Databricks will not concede at renewal: retroactive DBU credits for prior-year on-demand consumption above commitment, removal of the All-Purpose/Jobs distinction from pricing (they will not blend these to a single rate), or pricing that applies capacity commitment rates to cloud infrastructure costs (the cloud provider compute cost passes through separately and is not discounted by Databricks). Focus renewal negotiation on per-DBU rates for each workload type, commitment amounts, and multi-year term structure.