90 Minutes in a Meeting. Zero Minutes Catching Up.
The Departure
You just walked out of a 90-minute client meeting. Your phone shows three missed emails, one calendar conflict, and a prospect asking for a proposal. Before this series, that's a lost evening. This week, your briefing file handled it. You built it in Dispatch #012. You added operational rules in #013. Now we deploy it in three places so your AI works while you're in the room, not after.
The Co-Pilot
Tool: Claude in Microsoft Word (beta), Wispr Flow (Android), Claude Cowork
The Use Case: Three layers that turn your briefing file from a static document into an always-on system with one for documents, one for mobile, and one that runs autonomously.
The Prompt:
Layer 1 -- The Document Layer (Claude in Word)
Claude now works inside Microsoft Word on Team and Enterprise plans. Here's the move:
Open Word. Activate Claude from the toolbar.
Paste your full briefing file into the chat panel as context.
Type this prompt:
"Using the briefing file above as your operating instructions, draft a follow-up proposal for [CLIENT NAME]. They expressed interest in [SERVICE/PRODUCT]. Keep it under 400 words. End with one specific, time-bound ask per my operational rules."
You get a client-specific proposal that sounds like you, formatted the way you specified, with a real close at the bottom. No editing down from 1,200 words. No stripping out "delighted" and "game-changing."
Layer 2 -- The Mobile Layer (Wispr Flow)
Wispr Flow is a voice-to-text app available on iPhone & Android. Use it the moment you leave the meeting room:
Open Wispr Flow and dictate your raw meeting notes. Don't organize. Just talk.
Copy the transcript into Claude (mobile app or browser).
Use this prompt:
"Here are my raw meeting notes. Using my briefing file rules, produce two outputs: (1) a CRM update in 3 bullet points, and (2) a follow-up email under 150 words with a specific next step and proposed date."
That's your post-meeting admin done before you reach the parking lot.
Layer 3 -- The Autonomous Layer (Claude Cowork)
Claude Cowork went public this week. It runs tasks in the background -- no tab open, no babysitting. This is where your briefing file becomes an operating system.
Open Claude Cowork from your Claude dashboard.
Upload your briefing file and assign this first task:
"Review the attached briefing file. Every Monday at 8 AM, draft a weekly priorities summary based on my Q2 goals in Section 4. Keep it under 100 words. Flag any item that requires a decision with [DECISION NEEDED] at the top."
Start with one recurring task. See what it produces. Tighten the rules based on the output. That's how you build trust with an autonomous agent -- one task at a time.
The Upgrade
Topic: Your Briefing File Is Now an Agent's Operating System
Box CEO Aaron Levie said it plainly this week: any software an AI agent can't operate will be replaced. He's calling it "headless SaaS" tools that work without a human clicking buttons. That sounds like enterprise talk. It's not. It's exactly what you just built. Your briefing file tells an AI agent how to write, what length to use, which words to avoid, and how to close. That's not a convenience document anymore. That's the operating logic for software that runs while you sleep. Meanwhile, OpenAI launched $100 and $200/month tiers this week. The tools are getting more powerful and more expensive. The competitive edge isn't which plan you're on; it's whether your AI knows how to work like you. That's what the briefing file does.
The Landing
Your task today: Pick one layer. Just one. If you have a Word license, try Layer 1 with a real client proposal. If you're on iPhone or Android, install Wispr Flow and dictate your next meeting notes into Claude. If you want the autonomous play, upload your briefing file to Claude Cowork and assign one weekly task. You built the file. You wrote the rules. Now put them to work.
Safe travels,
Marcellus