AWS Cost Optimization Plan
Your Cost and Usage Report read line by line into a ranked savings backlog — a dollar estimate, effort rating, and first step per item. Read-only access; your team executes it.
One hour with the engineer who does the work. Verbal advice, no obligation, no deck.
$5,000, fixed within the published cap
This is you if: one payer account · up to $50,000/month spend · about five accounts
Within the published cap — a single payer account, up to $50,000/month of AWS spend, about five accounts — the price is $5,000, fixed. Larger estates get a fixed quote on the consult. Five to seven days from read-only access to walkthrough. Half the fee is due on signature and schedules the work; the remainder on acceptance.
Where AWS bills actually leak
- The Cost and Usage Report line by line — what changed, when, and what owns each dollar of growth
- Idle, oversized, and legacy-generation resources with no workload justification
- Commitment coverage — Savings Plans and Reserved Instances sized to the post-cleanup floor, never before it
- Storage posture — snapshot sprawl, lifecycle-less S3 growth, gp2-to-gp3 and tiering opportunities
- Data-transfer paths — NAT gateway traffic, cross-AZ chatter, and egress that a VPC endpoint would eliminate
The mechanics
Read-only access to Cost Explorer, the CUR, and CloudWatch — no agents, no production access. One 30-minute kickoff and a 60-minute walkthrough are the only meetings.
Deliverables, not impressions
Five to seven days, start to walkthrough
-
1
Days 1–2 — access and history
Read-only access live; twelve months of CUR and Cost Explorer history pulled and normalized.
-
2
Days 3–5 — the backlog
Findings identified, verified against utilization data, dollar-estimated, and ranked.
-
3
Days 6–7 — report and walkthrough
Backlog and narrative delivered; 60-minute walkthrough; access revoked.
Book this one when
- The AWS bill jumped and nobody can explain exactly why
- Spend has grown quarter over quarter without an owner, and finance is asking engineering for answers
- You suspect meaningful waste but need dollar figures and a ranked list before anyone will fund the cleanup
Bill spike specifically? That scenario, end to end — and the sample backlog excerpt (PDF) shows exactly what this produces. When the backlog lands, your team executes it — or DevOps on Demand works it down month by month.
Frequently asked questions
Do you charge a percentage of savings?
No. We think gain-share pricing points the incentives the wrong way — a percentage of savings can reward finding waste slowly, and it charges you a cut of a cleanup your own team executes. The price is fixed; the backlog is yours; your team can execute all of it without us.
What if you don’t find enough to justify the fee?
The consult is where we tell you honestly whether the likely savings and decision value justify the fee. If the math favors the free AWS tools first, we will say so before you commit.
What access do you need?
Read-only: Cost and Usage Report, Cost Explorer, and CloudWatch. No production access, no agents, revocation is one action.
What if we’re bigger than the cap?
The cap is what the fixed $5,000 price honestly covers. Larger estates aren’t declined — they’re scoped on the consult and quoted as a fixed price before work starts.
Who executes the backlog?
Your team — that’s the default, and the backlog is written so you can, with the first step stated per item. If you’d rather have it worked down for you month by month, that’s DevOps on Demand — an option, never an obligation.
A ranked list beats a hunch
The price is published and the access is read-only. One free hour to confirm fit — larger estates get a written fixed quote within 48 hours — and a start date you can plan around.
Book the Free Consult