FINANCE

Quarterly Vendor Price Creep Report

Each quarter it computes per-unit price changes by vendor from BigQuery, identifies vendors quietly raising rates.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly schedule starts the run
  • ActionPull per-unit price by vendor and periodGoogle BigQueryBigQuery
  • LogicCompute creep and filter over tolerance
  • ActionDraft ranked price-creep narrativeOpenAI
  • ActionPublish report to procurement workspaceCodaCoda
  • OutputPost top offenders to SlackSlack

What it does

This workflow detects silent rate increases. Each quarter it pulls per-unit pricing by vendor from BigQuery, compares it against prior periods to compute price creep, and publishes a ranked report in Coda highlighting vendors whose effective unit prices rose without a corresponding usage change.

When to use it

Use it when vendors raise prices in small increments that escape line-by-line review but compound over a year. It gives procurement an annual ammunition list of who quietly got more expensive and by how much.

How it works

  1. 1A quarterly schedule starts the run.
  2. 2BigQuery returns per-unit price by vendor for the current and prior comparison periods.
  3. 3A logic step computes price creep and filters to vendors whose unit price rose beyond a tolerance.
  4. 4OpenAI drafts the report narrative ranking the worst offenders with the percentage increase.
  5. 5Coda publishes the price-creep report to the procurement workspace.
  6. 6Slack posts the top offenders so the team sees them without opening the doc.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect CodaDocs, packs, automations.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.