Home / Case Studies / Snowflake Capacity Restructure
SnowflakeRetailCapacity CommitSnowpark

Snowflake capacity commit right-sized, with rollover rights.

A global retail group was negotiating a three-year Snowflake capacity commit with an opening proposal that priced credit consumption against a peak-season demand model and a Snowpark add-on stitched onto the master agreement at a higher list rate. Twelve weeks later, the commit was restructured for $3.4M of measurable saving, with rollover rights for under-consumed credits and the Snowpark add-on locked at master-discount parity.

Data analytics dashboard on screen
$3.4M
Three-year saving
24%
Reduction vs. opening commit
12 wk
Kick-off to signature
100%
Rollover rights
The contract going in

Peak-season sizing, credit drift, Snowpark on the side.

The retailer's prior Snowflake commit had been sized against a single peak-season month and projected forward as a constant. Credit consumption had run materially below commit for two consecutive quarters. A Snowpark adoption decision had been made outside the commit, with the add-on priced at list with a separate uplift schedule.

  • Annual credit commit running 22% above twelve-month rolling consumption.
  • Two warehouses sized for peak season but used at flat baseline for ten months of the year.
  • Snowpark added inside the term at list, outside the master discount.
  • Renewal cycle overlapping with a data platform consolidation initiative.
Snowflake's opening position

Larger commit, peak-season sizing, separate Snowpark uplift.

The Snowflake account team proposed a commit increase of approximately 18%, sized against the prior peak-season month plus growth, with Snowpark held outside the master discount and a separate annual uplift schedule. Rollover for under-consumed credits was not in the opening draft.

What we flagged

Capacity commits sized to peak demand systematically overshoot. Without rollover, every under-consumed credit is a transfer to the vendor. The conversation has to be about consumption curve, rollover and SKU parity, not headline commit size.

The work

Twelve weeks. Four workstreams.

1. Consumption-curve modelling

We pulled twelve months of credit consumption and rebuilt the forecast against actual usage curves rather than peak-season extrapolation. The output: a defensible commit shape that tracked baseline demand and isolated peak-season as a separate flex pool.

2. Rollover rights

Negotiated 100% rollover for under-consumed credits inside the term, removing the structural transfer that uncapped commits create when consumption tracks below forecast.

3. Snowpark parity

Brought Snowpark inside the master discount at SKU parity rather than as a separately-priced add-on with its own uplift schedule.

4. Commercial position

We drafted the position paper. The retailer's CTO sponsored it and the data platform lead presented it. Our team ran the three follow-up sessions across commercial, technical and finance reviews.

Lesson

The Snowflake commit conversation looks like a price negotiation. The leverage sits in rollover terms and add-on SKU parity. Get those two right and the headline commit number follows.

The contract going out

Baseline commit, peak flex pool, Snowpark at parity.

The signed commit sized against baseline consumption with a separate peak-season flex pool, included full rollover rights for under-consumed credits, and brought Snowpark inside the master discount at SKU parity.

$3.4M
Saved
Versus the opening Snowflake proposal, measured over the three-year term.
100%
Credit rollover
Under-consumed credits carried forward inside the term without expiry.
Parity
Snowpark add-on
Locked at master-discount unit price for the term, no separate uplift schedule.
“The rollover term changed the economics. Once that was in, the commit size stopped being a fight, because under-consumption no longer carried the same penalty. The Snowpark parity was the second-best outcome.”
Director of Data Platform · Retail · Anonymised by client request
Related resources

More on Snowflake commit strategy.

White paper

Snowflake Credit Optimization

How to shape a Snowflake capacity commit when peak-season sizing, rollover and add-on SKUs all sit on the same table.
Vendor practice

Snowflake Negotiation Practice

How we advise on capacity commits, credit rollover, Snowpark adoption and master-discount parity.
Service

Cloud Contract Advisory

Independent representation for data platform commits that determine three to five years of platform spend.
← Back to all case studies

Renewing a Snowflake capacity commit?

Tell us the commit shape, the consumption curve and the renewal date. We will respond within one business day with the lead and the most relevant precedent.

Contact Us →Snowflake practice