At a glance
-
Current AWS spend $104,942 /mo
-
Potential savings identified $20,108 /mo
-
Potential reduction 19%
-
Potential annualized savings $241,296
-
Projected monthly run rate $84,834 /mo
-
Opportunities 100+ across 6 workstreams
Where the money was going
The client's AWS run rate rose by about 20% over four quarters, from roughly $88K to $105K. The bigger issue was that no one could explain or control the increase. The assessment traced it to four causes:
- Surprise charges: Costs showed up only after usage.
- Monthly uncertainty: Next bill couldn't be predicted.
- Unclear attribution: Spend wasn't mapped to teams.
- Limited ownership: No one was accountable.
Without governance, every increase in usage turned into a higher bill.
How the engagement works
The assessment ran on our Save Now Pay Later model. The client didn't need a budget or pay upfront. We funded the assessment and the implementation too. Our fee comes only from savings that show up on the AWS bill. If the bill doesn't go down, there's no invoice.
The process has five stages:
- Assess
- Validate
- Approve
- Implement
- Measure
Save Now Pay Later
- No upfront cost
- No financial risk
- Fee only from realized savings
If there are no savings, there's no invoice.
What the assessment found
We reviewed spend project by project in both AWS accounts.
Production account
- Project-level optimizations: $9,864 /mo (28%)
- Commitment optimization: $4,455 /mo
- Cloud waste removal: $2,765 /mo
Total: $17,084 /mo
Non-production account
- Project-level optimizations: $2,889 /mo (33%)
- Cloud waste removal: $120 /mo
Total: $3,009 /mo
What happens next
The client now has a project-by-project view of spend and potential savings. The next step is validating and approving the changes. If all go ahead, the monthly run rate drops from about $105K to about $85K. The roughly $241K a year in savings, after our fee, stays with the client.
Continue reading