What Should AWS Cost? The Benchmarks That Survive an Exec Meeting (2026)

For a typical SaaS company, cloud runs at roughly 5 to 15 percent of revenue, with 8 to 10 percent as the working middle. Industry-wide, respondents to Flexera's 2026 survey self-estimate 29 percent of cloud spend as wasted, the first increase in five years. And 98 percent of FinOps teams now manage AI spend, up from 31 percent two years ago, which quietly rewrote every benchmark published before 2025. Those three numbers answer most of the are-we-normal questions an exec meeting produces. The rest of this article is about how each of them lies to you.

A benchmark is a conversation starter, not a verdict. Your board does not actually want to know whether you match an average assembled from 753 mostly larger organisations. They want to know whether your trajectory is defensible. Keep that distinction and the meeting stays calm.

The number finance asks for first is also the least standardised. Veteran operators on Quora put a compute-light SaaS at around 5 percent of revenue and the average at 8 to 10 percent. The gross margin arithmetic agrees with them: mature SaaS companies run 70 to 85 percent gross margin, which leaves 15 to 30 percent for all cost of revenue, and cloud is the largest single slice of that for most products.

The number moves more on accounting than on engineering. One operator on r/FPandA reports AWS at 1.7 percent of revenue, because only the portion of the bill that serves production workloads counts as COGS; the rest of their spend sits in R&D. Same company, double the number, different classifier. Revenue timing distorts it further: a company spending 30 percent of revenue on cloud ahead of a product launch can be healthier than one at 8 percent after a pricing collapse.

Flexera's 2026 State of the Cloud survey, 753 cloud decision-makers, puts self-estimated waste at 29 percent, and calls it the first increase in five years, attributing the reversal to surging AI workloads. Practitioner audits tell a compatible story: a cost auditor posting in r/devops reports finding 20 to 30 percent savings across more than 50 accounts. When a survey of estimates and a set of invoices agree this closely, the range is real.

Two caveats keep it honest. It is a self-estimate: it asks the people who own the waste to grade their own homework, and nobody audits themselves into bad news. And waste is three different numbers wearing one word: idle resources nobody deleted, commitments bought and under-used, and workloads running at the wrong price. Your exec deck should name which one it means.

AWS now ships its own benchmark. Cost efficiency, on the Cost Optimization Hub homepage, is calculated as one minus potential savings over total optimizable spend, rolling the last 30 days of spend against today's opportunities, and refreshing every 24 hours. As a trend line it is genuinely good: implement a recommendation and the score moves the next day, per account and per region.

As a grade it has three biases, all leaning the same way. The recommendations are AWS's, the savings are netted against discounts AWS sold you, and the optimizable-spend denominator covers the services AWS chooses to cover. A score that improves when you buy more commitments is partly a score of how much AWS you have agreed to keep buying. Watch the direction, not the number.

Sooner or later someone forwards the a16z argument: The Cost of Cloud, a Trillion Dollar Paradox, which estimated $100 billion of suppressed market value across 50 public software companies and held up Dropbox, whose S-1 claimed $75 million in savings from repatriating workloads while gross margin rose from 33 to 67 percent. The strongest counter, Corey Quinn's critique, points at the roughly $200 million of capex surrounding Dropbox's migration years, a workload uniquely suited to leaving, and the 34PB warehouse Dropbox later moved to AWS.

Notice what both sides share: precision, real numbers, and a motivated author. The a16z piece argues a thesis about market value; the critique argues one about hidden costs. In a deck, cite the motivation next to the number and you cannot be blindsided by either side. That habit has kept more than one of my presentations honest.

The deck that answers are-we-normal has five slides and no industry logo on any of them. One: spend trend, twelve months, with deploys and customer milestones marked on the line. Two: cloud as a percent of revenue against the 5 to 15 range, with our COGS split footnoted. Three: cost per customer, trend, not level. Four: waste found versus waste fixed, with the three definitions separated. Five: forecast, and the two decisions that move it.

Slide three is the one that ends arguments. A bill that grows 40 percent while customers grow 60 percent is not a cost problem, and cost per customer shows it in one line. A flat bill with a rising cost per customer is a margin problem wearing a calm face. No external benchmark can make either distinction; your own curve makes it instantly.

Industry averages are for opening the meeting: they establish that the question is legitimate and the ranges are known. They cannot govern one company, because they are assembled from companies with different revenue models, AI exposure and accounting choices. Your cost per customer trend, your coverage against your own stable baseline, your waste definitions held constant: those close it.

Upload your most recent AWS bill and we will score your Estimated Savings Rate and Commitment Lock-in Risk against the ranges in this article, and tell you which side of each benchmark you actually sit on.