PERSONAL PRODUCTIVITY

Recurring Meeting ROI Review and Cancel List

Monthly, it analyzes the last 90 days of recurring meetings, scores each by frequency, attendee count, and total person-hours burned.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly review schedule fires
  • ActionPull 90 days of recurring events from Google CalendarGoogle CalendarGoogle Calendar
  • LogicGroup by series and compute person-hour cost
  • LogicRank and flag cancel/consolidate candidates
  • OutputWrite ranked cancel list to NotionNotionNotion

What it does

Audits standing recurring meetings over a rolling quarter, multiplies each meeting's duration by its attendee count to estimate true person-hour cost, and produces a ranked list of the most expensive recurrences worth cancelling or merging.

When to use it

Use it during operational reviews when recurring meetings have quietly multiplied and nobody can say which ones still earn their slot. Great for chiefs of staff and ops leads running a calendar cleanup.

How it works

  1. 1A monthly schedule starts the review.
  2. 2It pulls 90 days of recurring events and their attendee lists from Google Calendar.
  3. 3A logic step groups events by recurring series and computes total person-hours, cadence, and last-meaningful-change signals.
  4. 4It ranks series by cost and flags low-attendance or rubber-stamp recurrences as cancel/consolidate candidates.
  5. 5It writes the ranked table with recommendations into a Notion page for the leadership review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  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.