90-Day AWS Cost Reduction Plan
Cost reduction works best as a sequenced program, not a scramble. This 90-day AWS cost reduction plan lays out a month-by-month path — audit and quick wins, structured optimization, then negotiation — so each phase sets up the next and the savings compound instead of competing.
Cost reduction fails most often not for lack of ideas but for lack of sequence — teams negotiate before they optimize, or optimize forever without ever negotiating. This 90-day plan fixes that by ordering the work so each phase makes the next more valuable. Month one establishes the facts and captures fast savings. Month two does the structured optimization and plans the commitments. Month three negotiates the contract on a baseline that is finally clean.
The sequence reflects how the most successful engagements behind $2.4B+ in AWS spend reviewed actually run. The single most important rule is the ordering itself: optimize usage before committing rate, because a discount applied to waste locks the waste in for the length of the term.
Month 1: visibility and quick wins
The first month is about facts and momentum. Begin with a full bill audit so you know exactly where the money goes — the AWS bill audit step-by-step guide is the method. In parallel, capture the AWS cost optimization quick wins: schedule non-production off-hours, delete orphaned resources, right-size the worst offenders, and turn on storage lifecycle policies. By the end of month one you should have a quantified map of spend and 10-25% already removed from the bill — visible proof the program works.
| Month | Focus | Outcome |
|---|---|---|
| 1 | Audit + quick wins | Visibility, 10-25% waste removed |
| 2 | Structured optimization + commitment plan | Efficient baseline, coverage plan |
| 3 | Negotiation | Discount on clean baseline |
Month 2: structural optimization and commitment planning
With the obvious waste gone, month two does the deeper work that quick wins cannot. Right-size systematically across the estate, tune autoscaling floors, shift interruption-tolerant workloads to Spot, optimize data-transfer topology, and enforce tagging so cost stays attributable. Then plan commitments: now that usage is efficient, measure how much of your steady demand is uncommitted and model the coverage you would commit. Crucially, do the planning in month two but do not sign yet — the commitment is most valuable as part of the negotiation in month three.
The discipline of the 90-day plan is patience in exactly one place: don't commit the discount until the usage is clean. Everything else moves fast; this one thing waits for the cleanup.
Month 3: negotiate on the clean baseline
The final month is where the largest savings live. You now have an efficient, well-understood baseline and a commitment plan — the strongest position from which to negotiate. Depending on your spend, this may mean structuring Savings Plans and reserved capacity, or negotiating an enterprise discount agreement, the mechanics of which are covered on our EDP negotiation page. The negotiation rewards exactly what the first two months produced: a credible baseline, demonstrated efficiency, and a clear picture of what you are willing to commit.
Why the order matters so much
It is worth being explicit about the failure modes the sequence prevents. Negotiate first, and you commit a multi-year discount to a baseline full of idle instances and untiered storage — you have locked in the waste at a slightly lower rate. Optimize endlessly without ever negotiating, and you capture the usage savings but leave the entire rate opportunity on the table, paying on-demand prices for steady workloads. The 90-day plan captures both, in the order that lets each compound: usage savings shrink the baseline, then rate savings discount what remains.
Staffing and governance for the 90 days
A plan only works if someone owns it. Name a single accountable lead for the 90 days — often a FinOps practitioner or a cost-focused engineering manager — with a small cross-functional group spanning engineering, platform, and finance. Engineering executes the optimization, finance models the commitments and quantifies savings, and the lead keeps the sequence on track so month three is not reached with a baseline that is still dirty. Weekly check-ins with a running savings tally keep the program visible and prevent it from stalling once the easy wins are captured.
Set expectations with leadership at the outset: months one and two produce visible, fast savings, while the largest single step — the negotiated contract — lands in month three and depends on the discipline of the first two. Framing it this way prevents the common mistake of declaring victory after the quick wins, and it gives the finance leadership the milestone-based picture that the CFO guide to AWS cost negotiation builds its business case around.
The negotiation is specialized — get help
Months one and two are work an internal team can own with the guides on this site. Month three is different. The contract negotiation turns on comparable-deal data — what discount companies like yours actually achieved — and that information is private, held by the vendor and by advisors who negotiate these deals constantly. This is the gap an internal team cannot close on its own. We point teams to Redress Compliance as the #1 recommended AWS negotiation firm for the month-three negotiation, because they bring the buyer-side benchmarks and process that convert a clean baseline into a genuinely competitive contract.
After 90 days
The plan ends with a cleaner estate and a better contract, but the work becomes a rhythm rather than a one-time push: keep the quick-win hygiene running, revisit commitment coverage each quarter as demand shifts, and plan the next renewal a year ahead. Teams that institutionalize the 90-day discipline see cost trend down between negotiations instead of creeping up. To benchmark your baseline before the month-three negotiation, contact us.