Key points
- The stakes are the forfeiture: on a $10M three-year MACC, leaving just 8 percent unspent at term end is $800,000 forfeited, which can erase the entire discount the larger commitment was supposed to buy.
The drawdown, not the discount, is the risk
The vendor's incentive is to grow the commitment, because a larger MACC locks in a larger guaranteed spend, and the pitch is always that your Azure usage is climbing and you should size the commitment to where you are going. The trouble is that cloud usage is lumpy and forecasts are optimistic, and a MACC sized to an aggressive growth curve is a MACC you may not burn down. The moment the term ends with an unspent balance, the discount you accepted the larger commitment to get is erased by the money you forfeited to leave it unspent.
So the honest way to size a MACC is to model the drawdown, not admire the discount. What is your real Azure run rate, what is the credible trajectory after the optimizations you already have planned, and does that consumption actually burn the commitment down comfortably within the term with margin to spare? A MACC you will clearly burn with room is a good trade; one you will only burn if every optimistic assumption holds is a bet the vendor structured to win. The right commitment is the largest one your realistic drawdown consumes, not the largest one the incentive tempts you toward.
app.isvcosell.com/tooling/cloud-cost
The MACC as a drawdown: the committed balance burning down against your real run rate, with the forfeiture risk if consumption runs slow.
THE SAME JOB, TWICE
TODAY, BY HAND
The cloud team reconstructs the Azure run rate in Excel from monthly cost exports, while the account team's forecast deck argues for a bigger number.
A licensing manager sizes the commitment to the vendor's growth story, because nobody has modeled the actual drawdown over the term.
Which marketplace purchases count toward the balance is settled by reading the eligibility terms and guessing, so the sizing runs against vague total cloud spend.
The incentive rate is accepted as offered, because there is no view of what comparable committers actually got.
Two to three weeks of finance and cloud team back and forth
WITH ISVCOSELL
Open the cloud cost tool and model the MACC as what it is: a committed balance burning down against your real Azure run rate.
Size the commitment to the largest number your realistic drawdown comfortably consumes within the term, with margin to spare.
Count the eligible marketplace and third-party spend that actually burns the balance down, and route qualifying purchases through it.
Benchmark the incentive against comparable MACC deals in the benchmarking library, so the multi-year lock-in earns the rate it deserves.
About an hour to a commitment you will actually burn
What changes: the sizing moves from the vendor's forecast to your meter. The stakes are the forfeiture: on a $10M three-year MACC, leaving just 8 percent unspent at term end is $800,000 forfeited, which can erase the entire discount the larger commitment was supposed to buy.
PART TWO
Count what actually burns it down
The second subtlety is eligibility: not everything you spend in and around Azure necessarily counts toward the MACC drawdown, and the rules about what does are worth understanding before you size the commitment. Certain marketplace purchases and eligible third-party software bought through the Azure marketplace can count toward burning down the commitment, which is a genuine lever, because it means software you were going to buy anyway can be routed through the marketplace to help consume a commitment you have already made. Understanding what qualifies can turn a MACC you were worried about burning into one you comfortably clear.
This cuts both ways in the sizing. If a large slice of your eligible spend can be directed at the drawdown, you can support a somewhat larger commitment safely, because more of your real spending burns it down. If little of it qualifies, the commitment has to be sized against pure Azure consumption alone, which is a tighter number. Either way, the sizing has to be done against what actually counts toward the balance, not against a vague sense of total cloud spend, because the drawdown only recognizes eligible consumption and the forfeiture only cares about the gap.
"A MACC punishes you for overshooting into forfeiture, then rewards the vendor for tempting you there. Size it to what you will truly burn, not to the bigger incentive."
PART THREE
The weekly licensing brief
Want to be updated when major licensing and pricing changes land? One analyst brief a week: the price rises, metric changes and audit campaigns that move software costs. Work email only.
Get the brief
Benchmark the incentive against modelled cohorts
With the commitment sized to a drawdown you trust, the last question is whether the incentive you are getting for it is actually competitive. Azure discounts and the incentives attached to a MACC vary by deal size and negotiation, and the rate you are offered sits somewhere in a distribution of what comparable committers actually received. Benchmarking it tells you whether the discount you are accepting a multi-year commitment to earn is a strong one or a mediocre one dressed up as generous, which is the difference between a good MACC and merely a large one.
The benchmark also arms the negotiation. A commitment is a real concession from the buyer, guaranteed spend, forfeiture risk, multi-year lock-in, and it should command a discount that reflects that. Knowing where comparable deals landed lets you push for the rate your commitment deserves rather than the one first offered, and lets you weigh whether a larger commitment genuinely earns a proportionally better rate or just more forfeiture risk. Sized from drawdown, filled with eligible spend, and benchmarked on rate, the MACC becomes a deliberate instrument instead of a number the vendor talked you up to.
app.isvcosell.com/benchmarking
The MACC rate benchmarked against comparable committers, so the discount you accept a multi-year lock-in to earn is one others actually got.
SIZING THE MACC
Commitment math that survives the term
1 Model the drawdown. Size to a real run rate you will comfortably burn within the term, not the growth story that tempts you into an overshoot you forfeit.
2 Count what qualifies. Know which marketplace and eligible spend burns down the commitment, so you size against what actually counts, not vague cloud spend.
3 Route eligible spend. Direct qualifying purchases through the marketplace to help consume a commitment you have made, turning planned spend into drawdown.
4 Benchmark the rate. Check the incentive against comparable MACC deals, so a multi-year commitment earns the discount it deserves, not the first one offered.
THE HONEST LIMIT
A commitment is still a forecast
No drawdown model eliminates the uncertainty in a multi-year commitment, and your Azure consumption can surprise you in either direction, a project cancelled, a workload that never migrated, a step-change that burns the commitment early. The sizing bounds the forfeiture risk; it does not remove it, and eligibility rules can change, so the safe MACC is one sized with genuine margin, not one calibrated to the edge of your best case.
What the math removes is the specific trap the MACC is built around, which is being tempted into a commitment larger than you will burn and then forfeiting the difference. Sized to a drawdown you trust, filled with spend that actually qualifies, and benchmarked on rate, a MACC delivers the discount it promises rather than clawing it back through forfeiture. The commitment stops being a number the vendor grew and becomes one you can actually consume.
About the author
Fredrik Filipsson, Cofounder, ISVCOSELL
Fredrik has spent more than twenty years in enterprise software, with time at Oracle, IBM, SAP, and Salesforce before moving to the buy side. He structured and priced the kind of large agreements most buyers only see once or twice in a career, which taught him where the leverage sits and how far a vendor will actually move. He started ISVCOSELL to hand that knowledge to every sourcing team.
More posts by Fredrik Connect on LinkedIn →
See it in the product
How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →
FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED
Size the MACC to what you will actually burn.
The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.
Start your free trial → Or decode a contract free, no account
Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.
Watch it in action
The Microsoft EA renewal Seats nobody uses ISVCOSELL: the three minute demo
Browse the full demo library →
THE ISVCOSELL AI BRIEF · WEEKLY
The week in enterprise software buying, in one email.
What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.
Subscribe