Costs · Every plan
Liz
Liz’s job is to track what the company spends on AWS and AI providers, where it is heading against each budget, and what is paid for but unused.
On this page
What Liz does
- AWS spend by service and AWS’s savings recommendations
- The month-end forecast against each budget, and cost anomaliesPro
- AI and LLM spend by provider and modelStudio
- Paid GitHub and Copilot seats nobody usesStudio
- What moved on the AWS bill each month, and whyPro
- How long AWS credits last at the current burn, and the bill once they stopPro
- AWS’s savings recommendations over time: acted on, still open or goneStudio
- Savings Plans and reservation coverage, and when each commitment endsStudio
- What the company runs in AWS by service and region, and what costs money with no trafficPro
What you can ask
You ask Grant, and he brings in Liz for questions like these. On Free, he answers from Liz’s saved briefs.
- “Why did our AWS bill go up?”
- “Will we go over our AWS budget this month?”Pro
- “How much are we spending on OpenAI and Anthropic?”Studio
- “What am I running in AWS?”Pro
What you get
AWS’s month-end forecast is $4,180 against a $4,000 budget, 4.5% over (AWS’s estimate). EC2 and NAT gateway data processing drive most of this month’s spend. One cost anomaly: S3 requests up $210 since the 24th.
What Liz reads
- AWS costs
- AWS forecast and budgetsPro
- GitHub seatsStudio
- AI provider spendStudio
- AWS commitmentsStudio
- AWS running resourcesPro
- GitHub deliveryPro
- AWS changesStudio
When Liz works
At each scheduled check-in and when you ask Grant. On Free, only at the monthly check-in you start.
What Liz may do
Read-only: reads the approved sources and reports findings.
What Liz never does
- Call an estimate money saved
- Buy, cancel or change anything in the company’s accounts
- Call a quiet key or an idle seat proof of waste
- Read or list resources in a region the connection did not approve
- Present CloudTrail changes from part of a month as the whole month
