Catch SKU price changes and marketplace renewals
Provider events flag SKU price changes and marketplace renewals on the timeline, so unexplained increases get explained.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
# finops
Costory
APP
Yes: an AWS Marketplace renewal for the observability subscription posted on Oct 1 (+€4,200). No usage change in the same period. It's marked as a provider event on the monthly review dashboard.
Finance and FinOps decide whether to renegotiate or adjust.
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 SKU price change or marketplace renewal posts.
Costory investigates
01
Track provider events
SKU price changes and marketplace renewals are captured automatically.
02
Overlay
They appear on cost charts next to your own events.
03
Ask
Claude checks provider events first when cost moves without a deploy.
04
Report
Include price changes in the monthly review.
Where you see it
Claude
You decide
Finance and FinOps decide whether to renegotiate or adjust.
Why it matters
Sometimes nothing changed on your side: the price did. Without provider events, teams hunt for a deploy that doesn't exist.
Who it’s for
FinOps leads, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
Fewer mystery spikes
Price changes explained.
Visible renewals
No surprise marketplace charges.
Cleaner reviews
Your changes vs provider changes.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Check
Were there any SKU price changes or marketplace renewals that affected our bill in the last 60 days?
FAQ
Questions about this playbook
How fresh is the data?
Costory refreshes billing data every morning. Providers deliver billing exports with some delay, so a change usually shows up within a day or two.
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 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
Spend on a team, service or account deviates from its baseline.
Investigate a cost spike and find the deploy behind it
When spend moves, the agent finds the deploy, team and service behind it, checks incidents and provider events from the same window, and posts the likely cause.
See the playbook
Costory notices
The 11th of every month.
Automate the monthly cloud cost review
A monthly report with an executive summary, root causes and trends, generated from a Cost digest and delivered automatically.
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