Results
What the work looks like
In both of these engagements, the hard part was not finding the discount. It was committing to it while the business underneath was changing.
Software
Committing around a migration
A software company with a family of brands, running on AWS, was moving one of its largest workloads to new infrastructure. Committing to that workload too early meant paying for capacity it might not keep. Committing too late meant paying on‑demand rates in the meantime.
We split the estate in two. Anything in the two accounts running that workload, or tagged to it, was carved out and handled on its own track, apart from everything else. We then raised coverage on that workload in steps, as the company grew confident its infrastructure choices would stick.
| Measure | Before | After |
|---|---|---|
| Spend covered by commitments | 49% | 64% |
| Effective discount | 18.3% | 22.0% |
| Savings per month | $77,000 | $98,000 |
Software
Keeping the discount through a sunset
A software company ran its largest application on Azure. For most of the engagement we bought one‑year guaranteed commitments. Then the company decided to sunset that application.
We moved the focus to thirty‑day commitments. It kept getting a discount on that application, committing thirty days at a time, and the longer commitment underneath was ours to cover.
More than $375,000 saved over 17 months.
Send us one recent cloud invoice and we will tell you what we would do with it, in writing, at no charge. [email protected]