PERSONAL PRODUCTIVITY
Meeting Cost Estimator with Pre-Send Trim Nudge
When an organizer creates a calendar invite, it prices the meeting from each attendee's loaded hourly rate and headcount.
How it runs
The automated pipeline, trigger to output.
- TriggerNew calendar event createdGoogle Calendar
- ActionLook up attendee rates in PostgresPostgres
- LogicCompute cost and flag if over threshold
- ActionDM organizer the cost + trim nudgeSlack
- OutputLog estimate to Postgres for trendsPostgres
What it does
Every new Google Calendar event gets an instant price tag. The workflow multiplies each attendee's loaded hourly rate (pulled from a Postgres rate table) by the meeting duration, sums it across the invite list, and sends the organizer a Slack DM with the total cost and the three most expensive attendees. The goal is a gut-check moment before the meeting becomes routine.
When to use it
Run this when recurring "sync" culture is quietly eating budget and you want organizers to feel the cost at the moment of creation, not in a quarterly report. Best for orgs that already track role-based rates.
How it works
- 1A new event is created on a watched Google Calendar.
- 2Attendee emails are looked up against a Postgres `employee_rates` table to fetch loaded hourly rates.
- 3Logic computes cost = sum(rate x duration) and flags meetings over a configured threshold.
- 4For flagged meetings, a Slack DM goes to the organizer with the total, the top-cost attendees, and a one-line nudge to trim optional guests.
- 5The estimate and decision are written back to Postgres for trend reporting.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
