Measure the impact of every optimization you ship
Log each optimization as an event and compare cost before and after, so the team can show what each change saved.
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
An optimization is logged as shipped.
Costory investigates
01
Log the change
Create an event from chat, the API or CI/CD when the optimization ships.
02
Compare periods
Cost before and after on the affected scope.
03
Normalize
Use unit costs so traffic growth doesn't hide the gain.
04
Share the win
Post the result to the team's channel.
Where you see it
Claude
You decide
The team reviews the measured impact two weeks later.
Why it matters
Teams ship optimizations but can't show the result. Without proof, cost work loses priority to features.
Who it’s for
Engineering managers, platform leads, CTOs
Where it runs
Claude · Slack
What you get
What lands in front of your team
Proof of impact
Before and after for each change, in euros.
Honest unit costs
Gains measured per unit, not just totals.
Momentum
Wins visible to the whole team.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Measure
What changed in search-indexer cost per 1,000 documents in the 2 weeks after the c7g migration?
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 deploy is followed by a cost change on the same service.
Cost impact of every deploy, from GitHub events
Capture deploys, PR merges and releases from GitHub or your CI/CD pipeline, and see which ones changed cost.
See the playbook
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
Monthly, or when a unit cost drifts beyond your threshold.
Track cost per customer, per request or per active user
Combine allocated cloud cost with your business and usage metrics to build unit costs that leadership can track over time.
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