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.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Show our Google Cloud CUD coverage by project for the last 90 days, and the uncovered Compute Engine baseline.
Compute Engine coverage: 48%. Uncovered steady baseline in europe-west1: about $9/hour over 90 days. A spend-based CUD at $7/hour would leave headroom for the migration planned in Q1.
FinOps decides on the commitment amount and term.
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
Uncovered steady Google Cloud spend persists for 90 days.
Costory investigates
01
Import CUD metadata
Costory reads Google Cloud Committed Use Discount metadata from BigQuery.
02
See coverage
Covered vs uncovered spend by project and team.
03
Find the baseline
Claude finds the steady hourly spend per service.
04
Propose options
Spend-based CUD scenarios for your team to review.
Where you see it
Claude
You decide
FinOps decides on the commitment amount and term.
Why it matters
Google Cloud CUDs come in several flavours and are hard to attribute. Teams either over-commit or leave easy savings on the table.
Who it’s for
FinOps leads, platform leads
Where it runs
Claude · Slack
What you get
What lands in front of your team
Attributed commitments
CUD benefits mapped to projects and teams.
Sized on data
Options based on your steady baseline.
Decision support
Your team makes the commitment call.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Review
Show our Google Cloud CUD coverage by project for the last 90 days, and the uncovered Compute Engine baseline.
FAQ
Questions about this playbook
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.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
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
Coverage drops, or the steady on-demand baseline grows.
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.
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 dbt model's cost jumps or a new expensive model appears.
BigQuery cost by dbt model, package and team
Label BigQuery jobs with dbt metadata and allocate processing and storage costs to models, packages and owners.
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