HR & RECRUITING

Weekly Contractor Spend Variance Review Agent

Every Monday, an agent reconciles last week's logged contractor hours in BigQuery against planned budgets, investigates each variance.

CategoryHR & Recruiting
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday-morning schedule
  • ActionQuery last week's actuals + plan from BigQueryGoogle BigQueryBigQuery
  • LogicIsolate engagements outside tolerance band
  • LogicAttribute likely cause per variance
  • OutputPublish variance review to dated Notion pageNotionNotion

What it does

An agent pulls the prior week's contractor hours and budgets, identifies every engagement where actual spend diverged materially from plan, and reasons about the likely cause of each variance (scope creep, ramp, idle time). It writes a narrative review with a recommended action per engagement to Notion, going beyond a raw numeric report.

When to use it

Use it for a recurring Monday operations review when you want explained variances and concrete next steps, not just a dashboard, and a durable record finance can read.

How it works

  1. 1A Monday-morning schedule starts the run.
  2. 2The agent queries BigQuery for last week's actual hours and the corresponding planned budgets per engagement.
  3. 3It computes variance and isolates engagements outside the tolerance band.
  4. 4For each, the agent reasons over recent timesheet notes and history to attribute a likely cause.
  5. 5It drafts a per-engagement variance narrative with a recommended action.
  6. 6It publishes the full review to a dated Notion page and links it for the operations channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.