Your launch plan is right for about a week.
Then engineering slips, legal changes the copy on a call, and the board still says everything’s on track. Flo reads the launch sync, the Slack channel, and the email thread, and proposes the fix — with the sentence someone said. You confirm. The plan stays true without you chasing five teams.
01 / 03
It reads the sync, not a status form.
Decisions on a launch get made out loud — on the weekly call, in the channel, in a reply-all. Flo reads those. Nobody files an update.
Launch sync · Transcript
Tue 10:04
Priya (Eng)
0:42
“Checkout is going to slip a week. We’ll be ready the 26th, not the 19th.”
Marcus (Legal)
3:15
“Drop ‘guaranteed’ from the announcement copy. We can’t say that.”
Flo is reading · no form to fill
02 / 03
Every change shows who said it.
When the date moves, the board shows the moment on the call where it moved. That’s what you send when someone asks “who decided that?”
Checkout · Launch date
Sep 19
Sep 26
Launch sync
Tue · 0:42 · Priya (Eng)
“Checkout is going to slip a week. We’ll be ready the 26th, not the 19th.”
Open moment in recording
03 / 03
Nothing moves without you.
Flo proposes. You confirm or reject. It never writes to Slack, never sends anything, never changes the plan on its own.
Flo proposes
Waiting for you
Update announcement copy: remove “guaranteed”
From Marcus (Legal), launch sync · 3:15
Confirm
Reject
Never writes to Slack
Never sends anything
Never edits on its own
Flo doesn’t replace the launch sync. It reads it.
Flo reads from
GitHub
Slack
Google Meet
Notion