A weekly optimization shortlist posted to each team's channel
Every Monday, each team gets three optimization candidates for its own services, with evidence, in its Slack channel.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
# finops
Costory
APP
This week's candidates for Payments: 1) RDS read replica at 9% CPU (€780/mo). 2) Unattached volumes from the old ledger service (€140/mo). 3) Staging cluster up on weekends (€610/mo).
Each team picks what to ship.
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
Every Monday.
Costory investigates
01
Scope by team
Team scopes define what each list covers.
02
Generate candidates
Claude reviews usage, cost and recent changes.
03
Post weekly
The shortlist goes to the team channel.
04
Track outcomes
Shipped items are logged as events.
Where you see it
Slack · #team-payments
You decide
Each team picks what to ship.
Why it matters
Recommendations die in dashboards. A short, owned, weekly list keeps optimization moving without a FinOps meeting.
Who it’s for
Engineering managers, platform leads
Where it runs
Claude · Slack
What you get
What lands in front of your team
Owned list
Three items per team, every week.
Evidence
Usage and cost attached.
Tracked
Outcomes logged as events.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Set up
Every Monday, post three optimization candidates for the Payments team to #team-payments with evidence.
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
A service runs well below its capacity for 30 days.
Rightsizing recommendations grounded in real usage
The agent compares what you pay for compute with what services actually use in CloudWatch or Datadog, then recommends instance sizes to the owning team, with the deploy history attached.
See the playbook
Costory notices
Idle capacity in a node pool stays above your threshold.
Find over-requested Kubernetes workloads and right-size requests
Measure the gap between requested and available CPU and memory, convert it to cost, and get request changes per deployment.
See the playbook
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
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