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.
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
A commitment purchase shifts billed cost between teams.
Costory investigates
01
Understand the issue
Savings Plan discount sharing moves billed cost between accounts.
02
Use contracted cost
A stable, usage-driven metric for team reporting.
03
Keep billed cost for finance
Invoices still reconcile on billed cost.
04
Explain to teams
Claude explains which metric each persona should use.
Where you see it
Claude
You decide
FinOps confirms which metric each report uses.
Why it matters
With discount sharing, a team's billed cost can drop or jump without any change in usage. Trust in showback disappears.
Who it’s for
FinOps leads, platform teams, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
Stable showback
Team numbers follow usage.
The right metric per persona
Contracted for teams, billed for finance.
Fewer disputes
No more 'why did my cost drop?'.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Compare
Compare billed and contracted cost for the Search team over the last 6 months. Where do they diverge, and why?
FAQ
Questions about this playbook
When are month-end numbers final?
Costory refreshes month n-1 until the 10th of month n, then freezes it so close numbers stay stable.
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
Month n-1 freezes on the 10th.
Month-end close: allocated cloud costs ready for finance
Use Costory's frozen month-end numbers, allocated to cost centers, as the cloud input to your close.
See the playbook
Costory notices
A new team or report is set up.
Show the right cost metric to each persona
Finance, engineering and leadership each get the cost metric that fits their decisions: billed, contracted or unit cost.
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