My AWS Bill Grew 40%. Revenue Grew 20%. Here's the Math I Showed the Board.

A 40 percent increase on a $60,000 monthly bill looks like an emergency until you split it. The split took one afternoon of Cost Explorer work and found three buckets: $17,000 a month of new customer usage and one AI feature the product team had launched, $5,000 of fixable waste, and $2,000 of on-demand spend sitting outside commitment coverage. Revenue had grown 20 percent over the same year. The board had seen the 40 percent. It had never seen the split.

That is the whole method. Growth arrives bundled into one number, and the three buckets inside it have different owners, timelines and fixes. The customers belong to sales. The waste belongs to engineering. The commitment gap belongs to whoever buys the commitments. Present the bundle and you get an argument; present the buckets and you get a decision.

Of the $24,000 monthly increase, $17,000 traced directly to usage the business had approved: existing customers consuming more, new customers onboarding, and one AI feature whose inference costs arrived before its revenue did. None of it was waste. All of it was the product working.

The test is cost per customer. At the start of the year the bill was $60,000 across roughly 200 active customers: $300 each. At the end it was $84,000 across about 270: $311 each, up under 4 percent while the bill grew 40. That single line converts a scary aggregate into a defensible trend, and it is exactly what AWS calls a unit metric: spend paired with the demand driver that causes it.

AWS's guidance on unit metrics draws the line I showed the board: a rising unit cost is a sign that something needs to be investigated. Ours rose under 4 percent, which is growth, not drift. When cost per customer doubles, the story changes from sales success to architecture problem, and the response is completely different.

The waste bucket came to $5,000 a month: idle resources nobody had deleted, oversized instances running at low utilization, and storage that had never tiered. Real money, $84,000 a year, and all of it recoverable at zero risk.

Here is the part worth being honest about. The 29 percent waste figure from Flexera's 2026 survey, 753 cloud decision-makers, measures total spend: the stock you already run. Waste concentrates in the stock. A growth delta is mostly new, purposeful usage, so the fixable share of the increase is smaller: in the audits I run it lands nearer a fifth to a third of the delta. Apply 29 percent to the increase, as I have watched happen in boardrooms, and you promise savings that were never in the room.

The last $2,000 a month was on-demand spend that should have been covered. The commitment portfolio had been sized for the old baseline, and the growth had outrun it. This bucket is quiet because nothing breaks: it is just list price, month after month, for usage that deserved a discount.

The fix is sequencing, not shopping. AWS's advertised Savings Plans discount runs up to 72 percent, and you only realise anything like it on the workload you actually keep running. Commit before the cleanup and you convert removable waste into contractual waste. AWS's own target-coverage guidance says the same thing in politer language: set coverage that leaves room to rightsize instances and clean up idle resources before committing further, then buy incrementally against the stable residue.

One wrinkle from the AI feature: volatile inference is exactly the workload not to commit. The stable residue gets the commitment. The experimental workload stays on demand and gets watched.

The board slide is one line and two numbers. The line: +$24,000 a month, split 17 / 5 / 2, growth, waste, pricing. The two numbers: cost per customer $300 to $311, and addressable $7,000 a month with a 60-day plan attached. No industry averages, no service pie charts, nothing the board has to take on faith.

Raw bills create fear. Decomposed bills create decisions. The 40 percent headline invited the board to imagine the worst bucket was all of it. The split showed them the worst bucket was 8 percent, already priced, with a plan. That is the difference between a meeting about the CTO's competence and a meeting about the company's money.

The sequence that collected the $7,000: close the idle and rightsizing waste in the first two weeks, it is free and risk-free. Buy the commitment against the residue that survived, sized with target coverage rather than the recommender's default. Then install the ritual: a quarterly decomposition of the delta into the same three buckets, so the next growth surprise arrives pre-split.

Upload your most recent AWS bill and we will produce this exact split: Estimated Savings Rate for the waste, Commitment Lock-in Risk for the commitment gap, and the growth bucket separated out, before your board asks for it.