Automated CoreWeave Weekly Cost Reports
Every Monday, WebRun opens the CoreWeave cloud console, reads last week's usage and spend broken down by project, instance type, and storage, appends the week to a running Airtable table, and publishes a Notion page showing which teams spent what and how each one moved against the week before.
How do I report CoreWeave GPU spend per team each week?
WebRun opens the CoreWeave console every Monday and reads last week's usage and spend by project, instance type, and storage. It appends the week to an Airtable history and publishes a Notion cost review showing each team's spend and its change, so GPU cost is reviewed weekly rather than at invoice time.
- Every team sees its own GPU spend every Monday
- Week over week movement is visible before the invoice arrives
- A full spend history builds up in Airtable without anyone exporting it
Built for ML platform teams · engineering managers · FinOps analysts · AI startups
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cloud.coreweave.comin a real browser with your saved login - no setup, no API keys. -
1
CoreWeave - read last week's usage and spend
coreweave.com
WebRun opens CoreWeave to read last week's usage and spend. - Sign in to the CoreWeave cloud console
- Open the billing and usage view for the week just ended
- Record spend by project or namespace
- Break each project down by instance type and by storage
- Note any project that appeared for the first time this week
Done when Last week's spend is captured for every project.
-
2
Airtable - append the week to the running table
airtable.com
WebRun opens Airtable to append the week to the running table. - Open your cloud cost table in Airtable
- Append one row per project for the week just ended
- Store the week ending date, the project, the instance spend, and the storage spend
- Calculate the change against the same project last week
- Leave earlier weeks untouched so the history stays intact
Done when The week is appended to Airtable with week over week change.
-
3
Notion - publish the cost review page
notion.so
WebRun opens Notion to publish the cost review page. - Create this week's cost review page in your engineering Notion space
- Show total spend, then a table of spend per project with the change beside it
- Call out the three biggest movers up and down
- Name any project that appeared for the first time
- Link back to the Airtable table for the full history
Done when The cost review page is published and ready for the Monday meeting.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Can it shut down or resize anything to save money?
No. WebRun only reads the CoreWeave console. Stopping an instance, resizing a cluster, or deleting storage stays a human decision made inside your own account.
Is the Notion page internal only?
Yes. It is written to your own Notion space and shared with whoever already has access. WebRun never publishes it publicly and never sends it outside your workspace.
What if a project is new this week?
It is called out by name on the Notion page. A first appearance has no prior week to compare against, so WebRun flags it rather than showing a misleading change figure.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.