DATA OPS
Monthly BigQuery Cost Optimization Briefing for Leadership
An agent reviews the month's BigQuery spend by team label, identifies the costliest recurring queries and likely optimizations.
How it runs
The automated pipeline, trigger to output.
- TriggerFirst-of-month schedule
- ActionPull monthly cost by team with top queriesBigQuery
- ActionAgent drafts optimization briefing with savingsOpenAI
- ActionPost executive summary to leadership SlackSlack
- OutputEmail full briefing to finance and data leadsGmail
What it does
Goes beyond raw numbers: an agent pulls the month's cost-by-team data from BigQuery, reasons about which recurring queries are the worst offenders and why (full scans, no partitioning, redundant materializations), and writes a prioritized optimization briefing with estimated savings.
When to use it
When leadership wants the "so what" — not just who spent what, but where the money is being wasted and what to fix first. Use it for a monthly FinOps review that produces an action list, not just a chart.
How it works
- 1A scheduled trigger fires on the first of each month.
- 2A BigQuery action pulls the prior month's cost grouped by team label and the top recurring queries with their scan patterns.
- 3The agent analyzes the queries, ranks optimization opportunities, and drafts a briefing with estimated dollar savings per fix.
- 4A Slack action posts the executive summary to the leadership channel.
- 5A Gmail action emails the full briefing with the per-team appendix to the finance and data leads.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect GmailRead, draft, send, label.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.