How Atelier Nord handed its meeting minutes and client meetings to FlowOS.
The scope, the team, the setup and what changes, described without outcome figures.
Illustrative scenario: fictional companies and people
Fictional industrial SME
Pilot led by C. M., operations director
Teams, Outlook and FlowOS ERP
One team, use cases chosen together
“We wanted to leave meetings with minutes, not with one more task.”
The problem: meetings with no written follow-up.
At Atelier Nord, project meetings and client calls follow one another. Minutes arrive late, sometimes never, and sales meetings are prepared by digging through several tools for the customer history.
Leadership wanted neither one more tool nor to hand decisions to AI: they wanted the writing prepared, with the team staying in charge.
- Teams meetings, with transcription turned on
- Customer history scattered across several tools
- Follow-ups and meeting prep written by hand
- One requirement: nothing goes out without review
Why FlowOS.
Two reasons mattered:
- Traceability. Requests and sensitive reads are recorded in the audit log: who asked for what, when, with which agent.
- Drafts rather than sending. FlowOS prepares emails as drafts in Outlook; the employee is the one who sends.
“What convinced us is that nothing goes out on its own. The agent prepares, we review, we decide.”
Three use cases, real connections.
The pilot is deliberately narrow: three use cases, with the connections FlowOS uses today.
Goal set together: minutes reviewed and sent on the day of the meeting, and every client meeting prepared from the FlowOS ERP record.
The pilot steps.
Demo and scoping
A 30-minute demo on the team's documents, then a scoping workshop: chosen use cases, permissions and review rules.
Connections
Each employee connects their Microsoft account (email, calendar, meetings); the administrator grants the consent required for Teams transcripts. FlowOS ERP roles are defined.
Onboarding
Training for each team: writing a request, reviewing minutes, adjusting a draft.
Assisted use
The first minutes and meeting preps are reviewed with an AI engineer, then the instructions are adjusted.
Review
Review with leadership: use cases to extend, for example invoice reminders from FlowOS ERP.
What changes for the team.
Before
- Minutes written late, or not at all
- Customer history searched across several tools
- Follow-ups written one by one
- Little visibility into AI usage
After the pilot
- Minutes prepared from the transcript, reviewed the same day
- Client meetings prepared with the FlowOS ERP record
- Email drafts ready in Outlook, sent by the team
- AI insights: time saved and cost tracked by leadership
What we'd keep in mind.
Lessons from this scenario that apply to most pilots:
- Transcription starts during the meeting. Without a Teams or Zoom transcript, there are no automatic minutes: it's a habit to build.
- Permissions are decided first. FlowOS ERP roles determine what agents read: best to set them before the pilot.
- Review remains the rule. Deliverables are drafts: their quality also depends on the team's review.
What comes next.
Next step under consideration: reminders for overdue invoices from FlowOS ERP, and a weekly note posted by a scheduled task to the leadership Teams channel.
Rule kept: every new use case starts with a period of systematic review.