PERSONAL PRODUCTIVITY

Weekly Meeting-Cost Digest for Team Leads

Every Monday it tallies the prior week's meetings per team, prices them by attendee load.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionPull prior week's eventsGoogle CalendarGoogle Calendar
  • ActionPrice and aggregate by teamPostgreSQLPostgres
  • LogicRank series and pick trim candidate
  • OutputEmail each lead a cost digestGmailGmail

What it does

This is the retrospective companion to per-invite pricing. On a weekly schedule it pulls the past seven days of calendar events, prices each by attendee rates and duration, groups the spend by team and by recurring series, then emails each team lead a digest: total meeting spend, the five priciest series, and which one looks most trimmable based on size and frequency.

When to use it

Use it when you want managers to see patterns rather than one-off prices. Surfacing the same 12-person weekly standup costing thousands per month is what actually changes behavior.

How it works

  1. 1A weekly schedule fires Monday morning.
  2. 2The prior week's events are pulled from Google Calendar.
  3. 3Attendee emails are priced against the Postgres rate table and aggregated per team and per recurring series.
  4. 4Logic ranks series by total cost and picks a trim candidate (large, frequent, low-attendance-required).
  5. 5Each lead receives a Gmail digest with their ranked breakdown and the suggested cut.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect GmailRead, draft, send, label.
  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.