AWS Cloud Costs: Cut 35% Without Lowering Usage [2026]

Smart finance leaders get outmaneuvered on cloud because it's hard to negotiate something you don't understand. A CFO can open an AWS contract, see 20 different line items, and have no idea how each product and service works. The salesperson says it's a great deal, and without benchmark data there's no way to tell the difference. It's like trying to tell the mechanic how to fix your car when they're the expert.

One customer's cloud rep told them they were getting a 12% discount, which is a good discount. What the rep didn't explain was that some of their usage modules weren't being used, and some had been spun up by developers and never turned off. Obviously, vendors are never going to tell customers these details, because they expect the customer to be responsible for them. Finance is usually meant to pay for things and expects the technical stakeholders to understand what's being bought. Those stakeholders often don't have the interest or the responsibility for the money.

How Do Cloud Cost Reductions Drive EBITDA Margin Growth?

In the Varisource savings program, cloud averages 25 to 35% savings, against 15 to 25% for software and 20 to 30% for telecom. Cloud is also one of the areas where we can drive savings immediately. Most of our savings come from customers keeping the same vendor and the same service at a better price. Each saving is measured against a baseline set upfront, usually the previous spend or the previous quote, and we validate it with you before we claim it.

The 20% is simple arithmetic: at a 10% EBITDA margin, savings worth two points of revenue grow EBITDA by 20%. My rule of thumb is that tech spend should sit around 10 to 15% of revenue, and usually it's much higher, closer to 25%. You can run the math on your own ratio. At 25%, two points of revenue is an 8% cut in tech spend, and at 15% it's about 13%. Both are under what cloud and software average on their own.

How Do Cloud Service Providers Build Hidden Overcharges Into Usage Models?

In my 15 years on the vendor side, renewal work was about coming up with the statistics that justify the renewal. It was also about giving the customer enough comfort and confidence that they never went out to market. Every vendor is overcharging you and charging every customer different prices, because they can and because you would pay for it.

A headline discount like that 12% doesn't protect you, because a discount is only off whatever list price the vendor picked. In cloud, vendors also add modules, change the pricing model so the calculation is different, or raise the price on the same service. As usage grows, they oftentimes don't apply the right discounts at the SKU level. By the time anyone sees it, the cost has already been charged.

With one customer, Datadog, the monitoring vendor, added modules and features the customer never asked for and raised the price, calling it inflation and R&D. Because it's a usage product, the customer kept using it with no idea that a lot of their usage was being counted twice. It ended up closer to a 35% overcharge.

How Can CFOs Lower AWS Cloud Costs Without Reducing Resource Usage?

What CFOs get wrong about saving money is thinking it means reducing service or quality, and on a cloud bill that turns into asking engineering to use less. Ask a usage-based vendor for a better price without leverage and "use less" is exactly what they'll tell you, which kind of defeats the purpose of having a good solution. When Datadog refused one customer a discount and told them to simply use less, we helped them move to a faster alternative, and they saved about 50%.

Visibility is the first step, and AWS will even help with it. Its Compute Optimizer flags idle resources from your utilization metrics and refreshes its recommendations daily. Benchmarking is totally separate from visibility. It tells you whether each SKU is priced at what the market pays, and the vendor isn't incentivized to hand you that data. Our benchmarks come from three sources: anonymized spend across thousands of customers, distributor and wholesale pricing that shows vendor costs and margins, and like-for-like quotes from alternative vendors.

On the price itself, we push for better terms on the EDP or PPA, the enterprise discount or private pricing agreement you have with AWS or Azure. We also check that the right savings plans and reserved instances are in place. AWS's Savings Plans documentation puts the discount on eligible compute at up to 72%. In exchange, you commit to a set hourly usage for one or three years. Customers usually skip the three-year term because they want flexibility, so they stay on-demand or buy one-year. Through our savings program, we can get them three-year term discounts on month-to-month flexibility, usually on EC2 and other compute.

How Do AWS Sales Representative Revenue Goals Create Cloud Contract Negotiation Leverage?

Benchmark and leverage all depend on understanding what the other salesperson is looking for. That means knowing what the customer wants, what the vendor wants and where the leverage points are, and then the right price for each component. With one customer, we helped migrate a lot of their software spend into the AWS marketplace. Their spend with AWS went up, which satisfied the vendor's revenue goals. That gave us the leverage to bring their compute costs down by over 30%. If you have a committed-spend agreement with AWS, eligible Marketplace purchases can count toward your committed spend. That means software you already buy from other vendors may help you hit it.

Why Are Lead Time and CFO Mandates Critical for Cloud Contract Negotiations?

Leverage is information and competition, plus the time to use them, and a benchmark only covers the information. Vendor sales teams spend 90 days strategizing before a big renewal, while customers deal with it 30 days in advance, which is why customers always overpay. Most of the negotiations we've lost came down to time. Customers reached us with two weeks left on a vendor deeply integrated into their systems, and the vendor knew they weren't going to switch in two weeks.

Benchmarks also need someone with authority behind them. In the FinOps Foundation's 2026 survey, 78% of FinOps practices reported into the CTO or CIO organization and 8% into the CFO. The people managing cloud cost mostly sit on the technology side, while the bill lands on finance. I think the CFO has to put people and process in place to track renewals months ahead, and set the mandate that every spend dollar with a vendor has an ROI. A PE operating partner would ask you for the ROI on the who, what, when, why, how of every vendor. On a cloud contract with 20 line items, you can't answer that without a benchmark for each one.

I'd be glad to show you where your cloud spend sits against our benchmarks before your next AWS or Azure commitment comes up. All we need is your AP file, just vendor names and spend for the last 18 months, and we'll come back with a free savings estimate in about 48 hours.