CC BrainFlow on the threads where work happens. It digests what was decided, promised, shipped, and slipped — then answers by email or in chat when you ask for the week. Below is the template it follows, so you know exactly what you'll send.
1. CC or forward your threads
Add BrainFlow to the threads where work actually happens — client emails, vendor negotiations, internal decisions. It works with any email client; you don’t change how anyone writes.
2. BrainFlow digests
It extracts what was decided, promised, shipped, and slipped — every point linked to the source email, so nothing is a recollection.
3. Ask by email or chatbot
When Friday comes, ask “what’s the week?” in the thread or in chat. BrainFlow answers in Progress / Plans / Problems format — you review and send.
Progress, Plans, Problems — one sourced line per project. Prefer to assemble it by hand this week? Copy this; it's the exact format. Then let BrainFlow fill it for you next Friday.
Subject: [Company] Weekly — Week of [date] TL;DR - One sentence on the week. If someone reads nothing else, they read this. PROGRESS - [Project A]: Shipped [thing]. Metric moved: [X → Y]. - [Project B]: Hit [milestone] on [date]. - Unblocked: [what was stuck, and what fixed it]. PLANS - [Project A]: Ship [next thing] by [date]. Owner: [name]. - [Project B]: Decide [topic] by [date] — deciding with [who]. PROBLEMS - [Risk]: [What's wrong] → [plan] → [help needed, if any]. - [Slippage]: [What slipped] → [new date] → [who has been told]. NUMBERS - Revenue / usage / churn: [X] ([↑ / ↓] vs last week) ASKS - [Specific thing you need from the reader] — by [date].
The format is only half the battle. For the full playbook — audience tailoring, red flags, and the failure modes that kill weekly updates — read the deep-dive on writing weekly updates CEOs actually read.
Write TL;DR first, last
Draft the rest of the update, then write the TL;DR to summarize it. If you can’t compress the week into one sentence, you don’t have a clear picture of it yet — that’s a signal in itself.
One line per project, always
The multi-paragraph project update is where readers drop off. One line, one fact, one number. If a project needs a essay, that’s a meeting — not a status line.
Put problems in the same format as wins
Founders hide bad news in vague language, and readers learn to skim past it. Write problems with the same structure as progress — what’s wrong, the plan, what you need — and they get the same attention.
The template is the easy part. The hard part is Friday afternoon: opening fifteen threads, asking three people what actually shipped, trying to remember what the client agreed to on Tuesday, and reconciling three different versions of the same decision.
That assembly work is why updates arrive late, read like self-reports, and quietly rot into copy nobody trusts. It was never a formatting problem. It's an information-gathering problem — and it's the part BrainFlow removes.
Ask for the week, get the week
BrainFlow sits in CC of the threads where work happens and keeps a sourced record of what was decided, promised, shipped, and slipped. When Friday comes, ask in the thread or in chat — the update comes back in this template, every line linked to the email it came from.
The template stays. The Friday scavenger hunt goes.
Free for 7 days · No setup · Cancel anytime
Start your trial and CC BrainFlow on this week's threads. On Friday, ask it for the week — by email or in chat — and send the update after a five-minute review instead of a three-hour hunt.
Free for 7 days · No setup · Cancel anytime