SPEC · cloud-cost-cleanup
Cloud Cost Cleanup
Your AWS bill crept past $3k a month and nobody is sure what half of it does. You do not need a DevOps hire. You need two weeks of cleanup.
Cloud bills grow by default. Every experiment, every "temporary" instance, every over-provisioned database sticks around until someone goes looking. I go looking. In about two weeks you get a smaller bill, a written record of what changed and why, and guardrails so it does not creep back.
Guarantee: if the savings I find, measured over 12 months, add up to less than my fee, the fee drops to match them. You will never pay more than the cleanup found.
What's included
- Full cost breakdown across all accounts you give me access to
- Identification and safe removal of unused resources (with your sign-off on every deletion)
- Rightsizing analysis for compute and databases, applied where approved
- Savings plan and reserved-capacity recommendations with the tradeoffs spelled out
- Budget alerts and anomaly detection wired up before I leave
- Written findings report: monthly spend before and after, fixes applied, fixes recommended
What's not included
Fixed prices only work with honest boundaries. Here is where this project ends:
- Application code changes or re-architecture (I will flag opportunities, not build them)
- Multi-cloud audits (AWS only for this package)
- Ongoing management. This is a project, not a retainer.
Deliverables
- Findings report with before/after monthly numbers
- List of every change made, with rollback notes
- Drift-prevention setup: budgets, alerts, tagging recommendations
See a specimen of the findings report you get
Timeline
About 2 weeks: a few days of read-only analysis, a review call where you approve changes, then execution and the report.
What I need from you
- AWS read access via a cross-account IAM role (I will send you a template; no shared credentials, ever)
- A 30 minute kickoff call and someone who can approve changes