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.
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
Monthly, or when a unit cost drifts beyond your threshold.
Costory investigates
01
Bring the denominator
Active users from Amplitude, orders from BigQuery, customers from a Google Sheet, or pushed custom metrics.
02
Write the formula
Formulas combine cost and metrics, for example cost / active users.
03
Track
Unit cost trends on a dashboard and in reports.
04
Alert
Alert when the unit cost drifts.
Where you see it
Claude
You decide
Leadership decides whether the drift needs action.
Why it matters
Total spend going up is fine if the business grows faster. Without unit costs, every increase looks like a problem.
Who it’s for
CTOs, finance, product leaders
Where it runs
Claude · Slack
What you get
What lands in front of your team
Growth-aware numbers
Spend in the context of the business.
Defensible increases
Show leadership the unit trend.
Drift alerts
Know when efficiency slips.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Build
Build a cost per 1,000 active users metric using Amplitude MAU and our production spend. Show the last 12 months.
FAQ
Questions about this playbook
Where do business metrics come from?
From Amplitude, BigQuery, Snowflake, Google Sheets, S3, Datadog, CloudWatch or metrics you push to Costory's API.
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 tenant's infrastructure cost grows faster than its plan.
Cost per tenant for multi-tenant SaaS
Allocate shared infrastructure to tenants using labels, namespaces or usage metrics, and track infrastructure cost per client.
See the playbook
Costory notices
Monthly, after Amplitude and billing refresh.
Cost per thousand active users with Amplitude
Correlate cloud cost with Amplitude active users and track cost per thousand MAU or WAU.
See the playbook
Costory notices
Monthly close, or when COGS share moves.
Cloud COGS and gross margin by product line
Allocate infrastructure to product lines and combine it with revenue from a sheet or warehouse table to track COGS and margin.
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