FINANCE

Monthly Unprofitable-Account Review Brief

On the first of the month, an agent reads the per-account cost-of-service and revenue data from BigQuery, identifies accounts whose cloud cost exceeds their revenue.

CategoryFinance
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule, first business day
  • ActionQuery per-account cost and revenueGoogle BigQueryBigQuery
  • LogicAgent isolates negative-margin accounts
  • LogicDraft narrative and recommended actions
  • ActionPublish brief to NotionNotionNotion
  • OutputPost summary to SlackSlack

What it does

Turns the per-account cost and revenue tables into a written monthly review. An agent ranks accounts by margin, flags the ones running at a loss, explains why each is underwater (heavy usage, low plan, free overage), and proposes concrete actions like a plan upgrade conversation or usage cap. The output is a ready-to-discuss brief, not a raw table.

When to use it

Use it for the monthly finance or revenue review when you need judgment and narrative on top of the numbers — deciding which loss-making accounts to renegotiate, migrate, or sunset.

How it works

  1. 1A monthly schedule trigger fires on the first business day.
  2. 2Query BigQuery for per-account cost-of-service and recognized revenue for the prior month.
  3. 3The agent computes margin per account and isolates the negative-margin set.
  4. 4It drafts a narrative for each flagged account with a root cause and recommended action.
  5. 5Publish the brief to a Notion page and post the summary with a link to Slack.

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
    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.