FINANCE

Budget Overrun Vendor Investigation Agent

On demand from a Slack command, an agent investigates which vendors drove a department over budget using BigQuery.

CategoryFinance
Enginepaperclip
Difficultyadvanced
Triggerchat
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack command names department and periodSlack
  • ActionQuery and decompose overrun by vendorGoogle BigQueryBigQuery
  • LogicRank contributors and form hypothesis
  • ActionDraft root-cause findings memoOpenAI
  • OutputStore memo in Coda and reply in SlackCodaCoda

What it does

This is an agent-driven investigation. A finance lead asks in Slack why a department went over budget, and the agent queries BigQuery to decompose the overrun by vendor, isolates the largest contributors, reasons about likely causes, and writes a findings memo to Coda. It answers the why, not just the how much.

When to use it

Use it when a month closes over budget and someone needs an answer fast. Instead of an analyst hand-pulling queries, the agent does the decomposition and drafts the memo, leaving a human to review and act.

How it works

  1. 1A Slack slash command names the department and period to investigate.
  2. 2The agent issues BigQuery queries to break the overrun down by vendor and line item.
  3. 3It reasons over the results to rank contributors and form a root-cause hypothesis.
  4. 4OpenAI helps draft a clear findings memo with the breakdown and recommended next steps.
  5. 5Coda stores the memo and the agent replies in Slack with a link and the headline finding.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect CodaDocs, packs, automations.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.