Snowflake enterprise contracts. Ten clauses that move price.

Snowflake capacity contracts look simple on the order form. Annual commit, three year term, credit consumption against any cloud region. The reality is that ten specific clauses in the master agreement and the order form decide whether the customer captures 22 to 38 percent against the publisher's first proposal or pays full retail across the term.

The mistake pattern is consistent. Customers accept the capacity sizing the Snowflake account team proposes, sign on the standard three year template, and miss the credit price lock, the rollover language, and the renewal uplift cap. The result is a contract that compounds cost across the term, especially as credit consumption grows.

This article maps the ten contract clauses that materially move the economics, the buyer side negotiation moves for each, and the order in which to fight them. Run it alongside the Snowflake pricing negotiation playbook and the multi vendor scorecard.

Clause 1. The credit price lock

Snowflake bills consumption in credits. Each credit represents a unit of compute resource consumption. The per credit price is set in the order form at signing.

The default position

The standard Snowflake order form fixes the per credit price for the initial annual commit only. Snowflake reserves the right to adjust list pricing during the term. The customer that draws down credits in year two or year three pays the new list rate.

The negotiation move

• Insert a fixed per credit rate clause. Reference the signing date rate. Confirm it applies to the full term.
• Exclude mid term list price adjustments. Snowflake list changes do not flow through to the existing commit balance.
• Specify the rate by warehouse size. XS, S, M, L, XL, 2XL, 3XL, 4XL each have separate rates.
• Document the rate for serverless features. Snowpipe, Tasks, Materialized Views, and Search Optimization all bill at separate rates.

Clause 2. Annual rollover and forfeiture

The standard Snowflake capacity contract treats annual commits as use it or lose it. Credits unused at the end of the contract year are forfeited.

The financial impact

A customer that commits 3M USD annually and consumes 2.4M USD typically loses 600K USD in expired credits. Over a three year term, conservative under consumption of 20 percent compounds to 1.8M USD in forfeited value.

The negotiation move

1. Negotiate explicit carryforward. 90 to 365 days of unused credit rollover. Some accounts have secured 18 month rolling windows.
2. Convert annual commits to a single three year pool. Eliminate annual reset entirely. The pool draws down across the term.
3. Negotiate conversion to Cortex credits. Unused standard credits convert to Cortex credits at end of year.
4. Document the forfeiture exception. Specific events that pause the annual clock, such as a major outage.

Clause 3. Multi cloud freedom

Snowflake runs on AWS, Azure, and Google Cloud. The customer can deploy workloads across multiple clouds and regions. The contract clause that governs this matters.

Where the clause hides

Multi cloud freedom is usually buried in the order form rather than the master agreement. Some Snowflake reps quote single cloud commits at the same price as multi cloud, then push to single cloud at signing.

The negotiation move

• Confirm multi cloud explicitly. The order form should name AWS, Azure, and Google Cloud as eligible deployment targets.
• Confirm region freedom. Credits draw down against any Snowflake region, including US, EU, APAC, and government regions.
• Confirm the cross cloud replication right. Critical for disaster recovery deployments.
• Negotiate the data egress treatment. Cross cloud and cross region transfers should not consume the credit pool at premium rates.

Clause 4. Storage pricing

Storage in Snowflake is billed separately from compute, at a per terabyte per month rate. The default rate is published by region. Negotiation moves on storage are smaller than on compute, but still material at scale.

Storage rate bands

Storage tier	Typical list rate	Negotiated band
On demand storage	40 USD per TB per month	28 to 38 USD with capacity commit
Capacity storage	23 USD per TB per month	16 to 22 USD with three year commit
Compressed snapshot storage	Tiered against logical size	Confirm compression ratio in contract
Cross region replication storage	List plus egress	Negotiate flat rate per TB replicated

The negotiation move

• Move to capacity storage rates. The customer with three year commit qualifies for capacity rates.
• Negotiate the storage rate. Indicative discount band 28 to 40 percent against list with documented multi cloud alternative.
• Confirm the compression treatment. Snowflake stores compressed. Billing applies to compressed size, not logical size.
• Set storage as a sub pool. Some customers negotiate the right to apply commit credits to storage as well as compute.

Clause 5. Data sharing

Snowflake Secure Data Sharing allows the customer to share live data with other Snowflake accounts. The commercial mechanics are straightforward but contain traps.

The default position

Data sharing between Snowflake accounts is included with the standard capacity contract. The data provider account hosts the share. The data consumer account incurs compute charges for query execution against the shared data.

The negotiation move

• Confirm the no additional fee position. Data sharing does not trigger separate share licensing fees.
• Negotiate the Marketplace listing fees. Listing data on the Snowflake Marketplace carries optional revenue share.
• Confirm the secure direct share volume. Some commercial templates cap the number of consumer accounts. Remove the cap.
• Negotiate the listing visibility. Private listings, restricted listings, and public listings each carry different terms.

Clause 6. Service level

Snowflake publishes a standard service level agreement (SLA) that targets 99.9 percent monthly uptime. The financial credit for missed SLA is usually credits returned to the customer's commit pool.

The negotiation move

• Negotiate higher SLA targets. 99.95 percent for analytics workloads, 99.99 percent for transactional integrations.
• Negotiate financial credits, not service credits. Service credits compound the original problem. Financial credits reduce the next invoice.
• Confirm the measurement window. Monthly aggregation hides intra month outages. Negotiate daily measurement.
• Document the exclusions tightly. Maintenance windows, force majeure, and customer caused incidents must be narrowly defined.

Clause 7. Cortex AI pricing

Cortex is Snowflake's managed AI and machine learning service. Cortex functions consume credits at premium rates against standard compute. Pricing for Cortex changes more often than for standard warehouses.

Indicative Cortex rate multipliers

Cortex function	Credit multiplier vs standard	Forecast discipline
Cortex Search	2 to 5x	Per query forecast
Cortex Analyst	3 to 8x	Per question forecast
Cortex LLM Functions	5 to 50x by model	Per token forecast
Cortex Fine Tuning	Per job pricing	Cap fine tune budget

The negotiation move

1. Forecast Cortex usage separately. Standard compute and Cortex compute have separate consumption patterns.
2. Negotiate Cortex credit conversion. Unused standard credits convert to Cortex credits at a fixed ratio.
3. Lock Cortex function rates. The rate at signing applies for the full term, not just the initial year.
4. Confirm the model availability. Newly released Cortex models are added at the same rate as comparable existing models.

Clause 8. Termination rights

Snowflake capacity contracts are typically non cancellable. The customer that signs a three year commit is bound for three years regardless of consumption.

The negotiation move

• Negotiate a termination for convenience clause. Some enterprise customers have secured a one time right to terminate at the 18 month mark with 50 percent penalty.
• Negotiate termination for material breach. Clear definition of what constitutes material breach. Three or more SLA misses in a rolling 90 day window is a reasonable trigger.
• Confirm the data portability obligation. Snowflake delivers customer data in a usable format at termination.
• Negotiate the post termination support period. 90 days of read only access for data migration.

Clause 9. Audit and reporting

Snowflake consumption is reported through the Snowflake account UI. The customer has visibility into credit consumption by warehouse, by user, and by query. The contract clause that matters is the right to audit Snowflake's billing math.

The negotiation move

• Confirm the consumption query API. The customer can pull consumption data programmatically for internal allocation.
• Negotiate dispute resolution. Clear process for disputing a billing line item. Resolution within 30 days.
• Confirm the per workload allocation right. The customer can tag warehouses and queries for chargeback to internal cost centers.
• Document the historical retention period. 365 days of consumption history accessible through the Snowflake account.

Clause 10. Renewal uplift cap

The single most expensive clause to leave un negotiated. Without a renewal uplift cap, the Snowflake commercial team proposes renewal price increases of 12 to 28 percent based on consumption growth.

The compounding effect

A customer that signed a 2M USD annual commit at year one, grew to 3M USD by year three, and faces a 20 percent uplift at renewal absorbs a 600K USD price increase on top of the consumption growth. Across the next three year cycle the customer pays an additional 1.8M USD.

The negotiation move

1. Bind the renewal uplift cap. CPI plus 2 percent maximum. Some customers have secured a flat 3 percent cap.
2. Specify the renewal pricing formula. The renewal credit rate references the original signing rate, not the prevailing list at renewal.
3. Reserve the right to extend at signing rates. The customer can extend the existing contract for 12 to 24 months at signing rates.
4. Document the renewal notice window. 180 days of notice before renewal. Enough lead time to run a competitive process.

What to do next

The checklist takes the Snowflake buyer from where they are today to a sized, clause hardened capacity contract.

1. Forecast consumption by workload. Standard compute, Cortex AI, storage, serverless. Three year quarterly bands.
2. Model the multi cloud alternative. Databricks on the same cloud accounts. AWS Redshift. Google BigQuery. Document the alternative cost.
3. Negotiate the credit price lock. Fixed rate for the full term. Mid term list changes excluded.
4. Negotiate the annual rollover. 90 to 365 days minimum. Aim for a three year pool.
5. Confirm multi cloud and region freedom. In writing on the order form.
6. Cap the renewal uplift. CPI plus 2 percent maximum.
7. Sign in Snowflake's fiscal year four. November to January is the discount window.
8. Run the deal through Vendor Shield. Independent buyer side review before signature.

Frequently asked questions

How Redress engages on Snowflake

Redress runs Snowflake advisory inside the Vendor Shield subscription, the Renewal Program, the Cloud Services practice, and the Software Spend Assessment.

Read the related Snowflake Enterprise Pricing Negotiation, the Data Cloud Research, the case studies, the benchmarking service, the management team page, the about us page, and the contact page.