> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluso.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# A meeting, end to end
> The full lifecycle on a real Tuesday. Prep at 9:55, meeting at 10, processed and follow-ups drafted by 10:47.
The savings on meetings come from two places: the half hour before that you usually spend scrambling, and the forty-five minutes after that you usually spend on notes, tasks, and follow-up emails. Fluso compresses both. The meeting itself is exactly the same length.
## A real Tuesday
It's 9:00 AM. You have a project review with the Acme team at 10. You haven't prepped.
The old version: scramble through emails, find the last meeting notes, check Slack for Acme threads, try to remember what was pending. You arrive at 10 feeling slightly behind. After the meeting: 20 minutes typing notes, 15 minutes creating tasks, 15 minutes writing the follow-up email, 10 minutes drafting the Slack update. Done by 11:45, ninety minutes after the meeting ended.
The Fluso version is below.
### 9:55 — Prep
> *"Prep me for the 10am Acme meeting."*
Fluso replies with a brief in about a minute.
Attendees: Sarah (VP Product), Mark (CTO), and your team — James and Lisa. Last meeting (April 18) ended on Phase 1 scope agreed, contract pending Legal. Since then: three emails from Sarah about pilot expansion, a Slack thread in #partnerships about Acme's Q3 timeline. Open items on the table: Legal review (overdue, your action), technical specs (Friday, James's). Likely topics: pilot expansion timeline, API rate limiting (their team's been asking in Slack), Q3 budget.
You walk in informed.
### 10:00 — Meeting
You focus on the conversation. Press record in Zoom.
### 10:45 — Process
> *"Process this meeting transcript."*
About a minute later, Fluso has produced the cleanup work for you.
Summary: team agreed to expand the pilot to 50 users. Timeline May 25, conditional on Legal review completing first.
Six tasks created with assignees and deadlines. A follow-up email draft to all attendees, ready to send. A Slack update draft for #partnerships, ready to post.
### 10:47 — Done
Approve the email and the Slack update. Tasks tracked. Everyone aligned. The 47 minutes after the meeting started have produced an hour and a half's worth of post-meeting work. You go to lunch.
## The numbers
| | Without Fluso | With Fluso |
| --------------- | ----------------- | ------------ |
| Prep | 30 min scrambling | 1 min asking |
| Meeting | 45 min | 45 min |
| Notes | 20 min | 0 min |
| Tasks | 15 min | 0 min |
| Follow-up email | 15 min | 1 min review |
| Slack update | 10 min | 1 min review |
| **Total** | **2h 15m** | **48m** |
About 85 minutes saved per meeting. Multiply by your weekly load.
## Variations
When you weren't in the meeting yourself:
> *"Process this meeting recording. I wasn't there. Catch me up on what was decided."*
Fluso skips the personalised follow-up draft and gives you a thorough briefing instead.
For recurring meetings:
> *"Process this 1:1 transcript and update Lisa's profile in my knowledge graph."*
Each meeting adds to the graph. Your context on each person and project gets richer over weeks.
For async-style recordings:
> *"Process this Loom and create tasks from the action items."*
Works for any video or audio source, not just live calls.
## When you have multiple meetings in a row
> *"Prep me for my next three meetings today."*
Fluso processes them in batch. You read all three briefs over coffee and walk into each one prepared.
## Setup notes
Calendar connected (see [Google Calendar](/integrations/google-calendar)). Gmail connected for email-derived context. Slack optional, but it's the integration that makes prep dramatically richer. Recording enabled in Zoom, Meet, or Teams.
Always inform participants if you're recording. Follow your organisation's policies on recording and transcription.
## Related
Meeting intelligence and the rest of the skills.
How meeting context feeds the knowledge graph.