DATA OPS

Weekly BigQuery Cost Attribution Report by Owner

Builds a weekly leaderboard of BigQuery spend grouped by query owner and dataset, writes the rollup to a Snowflake reporting table.

CategoryData Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday 8am schedule
  • ActionAggregate weekly cost by owner + datasetGoogle BigQueryBigQuery
  • LogicRank owners, compute share, flag WoW jumps
  • ActionWrite rollup to Snowflake reporting tableSnowflakeSnowflake
  • OutputPost owner leaderboard to SlackSlack

What it does

Produces the weekly accountability report finance and platform leads actually want: total BigQuery spend broken down by owner and dataset, week-over-week change, and each owner's share of the bill. It persists the rollup into a Snowflake table so chargeback and trend analysis live alongside the rest of your reporting, and drops a readable Slack summary so the numbers reach people without a SQL client.

When to use it

Use this for monthly chargeback prep, cost-review meetings, or any time leadership asks "who is driving our warehouse spend." It replaces the manual spreadsheet someone rebuilds every Monday.

How it works

  1. 1A Monday 8am schedule kicks off the report.
  2. 2BigQuery aggregates the trailing week's cost grouped by owner and dataset, with the prior week for deltas.
  3. 3A logic step ranks owners, computes share-of-spend, and flags week-over-week jumps.
  4. 4The rollup is written to a Snowflake reporting table for durable history.
  5. 5Slack receives the formatted owner leaderboard and top movers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SnowflakeWarehouses, queries, shares.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.