You cannot optimise an invisible bill
Platform cost arrives as one number, charged to one cost centre, caused by everyone. Nobody feels responsible for it because nobody can see their own share.
Making the number visible per team is the single cheapest intervention we know.
How to attribute without a project
Most warehouses already support this with tagging and separate compute resources. The work is organisational more than technical:
- One warehouse or resource per team, so usage is separable
- Query tagging for shared jobs, with the owning team in the tag
- A scheduled job that writes cost by team into a table like any other dataset
- A dashboard anyone can open, not a monthly PDF
The behaviour change comes first
At one client the biggest single saving landed in week one, before we changed any code. A team opened the dashboard, recognised a job they had forgotten, and switched it off.
People do not defend waste. They defend things they cannot see the cost of.
Then set budgets
Once teams can see their number, a monthly budget with an alert is reasonable rather than punitive. Alert before month end, so there is still time to act.
What not to do
Do not start with a chargeback model. Attributing cost is informative; billing teams internally turns a technical conversation into a political one and usually stalls the work entirely.
Owen Mbeki
Head of Platform & MLOps