Savings Plans and Reserved Instances coverage review
The agent watches covered versus uncovered spend and utilization, and recommends where additional commitments could make sense as your steady baseline grows.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
Coverage drops, or the steady on-demand baseline grows.
Costory investigates
01
See coverage
The Savings Plan and CUD coverage template tracks covered vs uncovered spend, utilization and trend.
02
Track purchases
Provider events put Savings Plan and RI purchases on the timeline automatically.
03
Stable team costs
Contracted cost keeps team numbers stable when discounts are shared.
04
Claude proposes
Coverage scenarios based on your steady baseline; you decide what to buy.
Where you see it
Claude
You decide
FinOps and finance decide whether and how much to commit.
Why it matters
Commitment decisions are made once a year in a spreadsheet, while usage keeps moving. Under-coverage wastes money; over-commitment locks it in.
Who it’s for
FinOps leads, platform leads, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
Coverage at a glance
Covered, uncovered and utilization over time.
Scenarios, not guesses
Options sized on your steady baseline.
You stay in control
Costory does not buy commitments for you.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Review
What was our Savings Plan coverage and utilization by month over the last 6 months? Where is on-demand spend steady enough to commit?
Scenario
Propose a conservative and an aggressive Compute Savings Plan option based on our lowest steady hourly usage.
FAQ
Questions about this playbook
Does Costory purchase Savings Plans or Reserved Instances?
No. Costory shows coverage and helps you size options; purchases stay with your team.
Why do team costs change after a Savings Plan purchase?
Discount sharing moves billed cost between accounts. Contracted cost gives teams a stable, usage-driven view.
Does Costory guarantee savings?
No. The agent investigates and recommends with the evidence attached; your team decides what to change. Impact figures are estimates based on your own data.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
Uncovered steady Google Cloud spend persists for 90 days.
Committed Use Discount planning for Google Cloud
Import CUD metadata, see coverage per project and team, and size spend-based commitments on your steady baseline.
See the playbook
Costory notices
A commitment expires or a renewal posts.
Track Savings Plan and RI purchases, expirations and renewals
Provider events put commitment purchases, marketplace renewals and SKU price changes on the cost timeline, so nothing expires silently.
See the playbook
Costory notices
A commitment purchase shifts billed cost between teams.
Stable team costs with contracted cost
Give teams a usage-driven cost view that doesn't swing when Savings Plan discounts are shared across accounts.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud