Cost per thousand active users with Amplitude
Correlate cloud cost with Amplitude active users and track cost per thousand MAU or WAU.
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, after Amplitude and billing refresh.
Context used
Remembered
Costory investigates
01
Connect Amplitude
Active users, new users, WAU and MAU are queried live, with no sync to BigQuery.
02
Pick the cost scope
Production spend, or a product's allocated cost.
03
Formula
Cost per 1,000 active users.
04
Share
Monthly trend in the exec report.
Where you see it
Claude
You decide
Product and engineering decide where to focus.
Why it matters
Consumer apps live and die by cost per user. Most teams only compute it once a year, by hand.
Who it’s for
Consumer app CTOs, product leaders, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
A live unit metric
No more yearly spreadsheet.
A product-level view
Per app or feature once allocated.
Exec-ready
One line in the monthly report.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
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
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
Costory notices
A release changes a service's cost per request.
Cost per API request with Datadog or CloudWatch metrics
Divide a service's allocated cost by its request volume from Datadog or CloudWatch, and track it release after release.
See the playbook
Costory notices
Quarter end, or before a board meeting.
A board and exec cost pack in minutes
Total spend trend, top drivers, budget progress, unit costs and month-over-month comparison in one executive view.
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