Meeting Follow-Up Coordinator
Help anyone who spends the day in meetings leave each one with the follow-up already done: who owes what by when, the recap drafted, and decisions written down where the team can find them.
Suggested integrations
Works for
Capabilities
- Action items from each meeting with an owner and a due date, added to Asana, Linear, or your task list.
- A follow-up email drafted for external meetings: what was agreed, next steps, and anything you promised to send.
- A record of what was decided, by whom, and when, so the same question is not argued twice.
What it can set up for you
Where it starts. In setup it asks what you need and builds only what you approve.
Meeting Recap Method
Skill
Turns a transcript or notes into actions, decisions, and a follow-up email.
After-Meeting Follow-Up
Workflow · When a meeting transcript is ready
Adds each meeting's action items as tasks and drafts the follow-up email.
Decision Log
App
Every decision with the meeting, the date, who made it, and what it replaced.
What to bring
- A connected meeting notetaker (Granola, Fathom, Fireflies, or Zoom), your email, and your task tool.
- Which meetings to follow up, who owns tasks by default, your recap voice, and where decisions are kept.
How setup works
- Add the specialist. It arrives with its role and starter memory, and nothing is built or connected yet.
- It asks what you want it to handle, which tools your team uses, how often, and where results should go.
- It proposes the workflows, apps, and skills that fit, builds the ones you approve, and tests them with you before anything runs on its own.
Scope
- It creates tasks and drafts. It never sends a follow-up, invites anyone, or shares a transcript outside the people who were in the meeting.
- An action item needs an owner who agreed to it in the transcript. Anything unclear is listed as a question, not assigned.
Example
Fictional input and an illustrative result.
Input
Fictional transcript, Example Co weekly sync, 2026-10-14. Dana: "I'll send the revised quote by Friday." Sam: "We'll go with the April launch, not March." Lee: "Someone should check the shipping costs." No one replied to Lee.
Output
Follow-up: Example Co weekly sync, 2026-10-14
Tasks
- Dana: send the revised quote, due Friday 2026-10-17.
Decided
- Launch moves to April (Sam), replacing March.
Open question
- Shipping costs: Lee raised it and no one took it. Assign an owner?
Follow-up email draft
Thanks for today. We agreed to launch in April, and Dana will send the revised quote by Friday.
The email was not sent.