What is a commitment ramp?

A ramp is the schedule that sets how much you must spend in each year of a multi year cloud commitment. It can be flat across the term or rise year over year. The shape of the ramp determines when your obligation comes due relative to your real consumption.

Why is a seller drafted ramp risky?

Sellers tend to front load the ramp so larger commitments book sooner, often based on optimistic growth forecasts. If your consumption does not rise as fast as the ramp, you hit a higher obligation with spend that has not arrived and pay the shortfall.

How do I build a ramp that protects me?

Anchor the first step to spend you already incur, tie each increase to a milestone you control such as a migration going live, keep the steepest steps late, and model the final year obligation in absolute dollars against a flat growth case.

What happens if I miss a ramp step?

As of June 2026, an AWS EDP shortfall means you pay the gap between the committed step and actual spend, and Azure MACC unused commitment is generally lost with no rollover. A missed step usually converts directly into cash you owe or value you forfeit.

Should a ramp ever rise steeply?

Only when the growth funding it is contracted or already in motion, such as signed migrations with hard dates. A steep ramp built on a sales forecast is exposure. For flat or declining spend a rising ramp is almost always the wrong shape.

Can I shift unused commitment between ramp periods?

Sometimes, where the provider allows a true up window or carry mechanism. It is worth negotiating explicitly, because without it a timing slip in one period becomes permanent loss rather than a recoverable shift.

COMMITMENT STRUCTURING · BUYER SIDE

Building a ramp structure that protects you

GET A CONFIDENTIAL REVIEW →

PUBLISHED JUNE 16, 2026 · REVIEWED JUNE 16, 2026

Building a ramp structure that protects you is how a multi year commitment stops being a trap and starts being a tool. A ramp is the schedule that sets how much you are obligated to spend in each year of the term. Get it right and your obligation tracks your real growth. Get it wrong, or let the seller draft it, and the ramp front loads risk into years when your consumption has not caught up, manufacturing a shortfall you pay for.

Most buyers focus on the total commitment and ignore the ramp. The seller knows this. The shape of the curve inside the term is where the exposure lives, and it is almost always negotiable. Building a ramp structure that protects you starts with treating that curve as the main event, not a footnote.

Why building a ramp structure that protects you matters

A flat commitment splits the total evenly across the term. A ramp lets the yearly obligation start low and rise. The seller prefers a ramp that rises fast, because it books larger commitments sooner. You want a ramp that rises only as fast as your consumption can credibly follow. As of June 2026, AWS EDP shortfall is the buyer paying the gap between the committed step and actual spend in that period (source: AWS EDP program terms), so an aggressive ramp converts a forecast miss directly into cash you owe.

This is the same logic that governs how to size a cloud commitment correctly, applied across time rather than in a single number. Sizing sets the total. The ramp sets when each portion of that total comes due. A perfectly sized total with a badly shaped ramp can still bankrupt your savings in year two.

The traps inside a seller drafted ramp

Front loaded steps

The most common trap is a ramp that jumps in year one or year two before your migration or growth has landed. The seller justifies it with the forecast they helped you build. If the forecast slips, and forecasts usually slip, you hit the higher step with consumption that has not arrived and you fund the difference. Front loading benefits the provider because it books revenue sooner and locks you in deeper before you can reassess.

Compounding escalators

Some ramps escalate each year by a fixed percentage that compounds. A number that looks modest in year one becomes punishing by year three. Always model the absolute dollar obligation in the final year, not the percentage, so you see what you are really agreeing to. A ramp that escalates fifteen percent a year more than doubles the year one obligation by the end of a five year term.

No relief for timing slips

A ramp with no mechanism to shift unused commitment within the term is the harshest form. Where unused commitment cannot roll, as is generally the case for Azure MACC where unused commitment is lost (source: Microsoft MACC documentation, as of June 2026), a timing slip in one period is permanent loss. We cover this exposure in depth in our guidance on structuring commitments for flat or declining spend.

A ramp that outlives the workloads

A ramp that keeps rising into years four and five can outlive the very workloads it was meant to fund. If a migration is complete by year three and the estate stabilises, a ramp that keeps climbing commits you to growth that the business plan never contained. Match the shape of the ramp to the shape of the project, then flatten it once the project is done.

How to build a ramp that protects you

Anchor the year one step to spend you are already incurring, not to forecast growth.
Tie each upward step to a milestone you control, such as a migration wave going live, rather than to the calendar.
Model the final year obligation in absolute dollars and stress it against a flat growth case.
Negotiate a true up window or the ability to shift unused commitment within the term where the provider allows it.
Keep the steepest steps late, after the growth that funds them has been proven.
Flatten the curve once the funding project completes, rather than letting it climb on autopilot.

The principle is simple. The obligation should follow the consumption, never lead it. Phasing the commitment correctly is a discipline of its own, covered in how to phase a commitment over a term.

A worked illustration of a protective ramp

Consider a composite enterprise migrating a data centre over two years, expecting cloud spend to climb from four million to ten million annually. A seller drafted ramp might demand six million in year one, nine million in year two, and ten million thereafter, front loading obligation before the migration has moved most workloads. A protective ramp instead sets year one near the current four million, steps to seven million only after the first migration wave is confirmed live, and reaches ten million in year three once the estate is fully landed. Same destination, very different risk. The protective version never asks the buyer to pay for spend that has not yet arrived.

Ramps for high growth versus stable spend

A genuinely high growth business can support a rising ramp, but only when the growth is contracted or already in motion. The structuring approach differs enough that we treat it separately in structuring commitments for high growth. For a flat or declining business, a rising ramp is almost always wrong and a flat or even descending obligation is the protective shape.

In both cases, model the downside first. The seller will model the upside for you all day. Your job, and ours on your behalf, is to ask what the ramp does to you in the year your best case does not arrive. A ramp you can survive in your worst plausible year is a ramp you can sign.

How the ramp interacts with renewal timing

A protective ramp also sets up your next negotiation. As of June 2026, AWS EDP renewal leverage is greatest in the window six to nine months before expiry (source: AWS EDP program terms). If your ramp peaks right at expiry, you arrive at the renewal carrying the largest obligation you have ever held, which weakens your hand. Shape the ramp so the final year obligation is one you can comfortably sustain or step down from, then diarise the renewal window early so you reopen the deal from a position of strength rather than drifting into an automatic extension at the peak number.

Read the ramp and the term together, never separately. A ramp that looks reasonable inside a single year can be punishing across a three year lock, which is why we treat the multi year versus single year tradeoffs as part of the same decision. The shape of the curve and the length of the term are two halves of one structure.

The bottom line on building a ramp structure that protects you

The total commitment gets the attention, but the ramp decides the pain. Anchor early steps to real spend, tie increases to milestones you control, keep the steepest steps late, and never accept a curve that rises faster than your consumption can follow. For the full framework see our cloud commitment structuring and sizing guide. If a ramped proposal is in front of you, a commitment structuring and sizing service will rebuild the curve on your terms before signature.