I read the account by hand.

What it costs

$1,000 flat, paid once. Or nothing up front and 20% of the savings, ninety days later. Your call, made before I start.

The 20% is measured, not claimed. We agree the baseline month before anything changes, then compare the same account ninety days on. The numbers come out of your Cost Explorer, not mine.

What the scan cannot see

The scanner reads resources. It finds the volume nobody detached and the box nobody turned off, and it is good at that. It cannot read how the system is put together.

• Whether your steady usage belongs on a Savings Plan or Reserved Instances at all, and for how long. Commit to the wrong one and you have locked the waste in for a year.
• What you are paying for high availability - Multi-AZ, standby replicas, spare capacity - and how much of it the downtime you can live with actually needs.
• Whether your instance families still fit the work, what moving to Graviton would save, and what the porting would cost you.
• Where your traffic crosses a boundary that bills - NAT gateways, cross-AZ traffic, egress - and whether it has to be laid out that way.
• Which resources the scanner flagged that are load-bearing anyway. A scanner cannot tell idle from standby. I can ask you.

What you get

A written plan: every change worth making, what it saves per month, what it costs you to make it, and what it risks if the assumption behind it is wrong. Ordered so you can stop reading when the numbers stop being worth your time. Then a call to go through it.

What I do not do

Touch your account. The access is read-only, the same as the scanner's. I tell you what to change and your engineers decide whether to change it.

Start a conversation

Tell me roughly what you run and what the bill is. I reply with whether the deep-dive is worth it for you, and I will say no when it is not.

analyze@awscost.fyi