The meeting prep most people skip

The meeting you're walking into unprepared is the one that matters most.

📡 The prep doc that changes how decisions land →
📡 How to fact-check AI work before it leaves your hands →
🛠️ One draft. Five platform-ready visuals. Ten minutes. →

⚡ OpenAI just stood up an implementation company →
⚡ Spotify now builds private podcasts from your calendar →
⚡ Claude Code ships multi-agent orchestration →
⚡ Gemini is already on your Chrome browser →

Jump to the one that matters to you ↓

After you vote, add one sentence on what would help you most — your comments shape what I test and write next.

Some meetings go fine until one person asks the question you should have seen coming.

Finance pushes on budget. Sales pushes on attribution. Product pushes on timeline. Leadership asks what happens if the plan does not work.

That is the meeting prep most people skip.

Before any meeting where I need a decision, I now make a private Google Doc called a Meeting Objection Brief.

It is not something you send around. It is not a script. It is a 10-minute prep doc that helps you write down the likely objections before you hear them live.

You paste four things into ChatGPT:

1. What the meeting is about
2. What decision you want
3. Who is in the room
4. What you are worried will go sideways

Then ChatGPT gives you the likely pushback, who may raise it, what they actually care about, and a plain-English answer you can give without sounding defensive.

⚠️ The useful part is the second prompt: “What objection did you miss?”

That is usually where the real meeting prep starts.

📄 I put the two prompts and the Google Docs template in the web version.

Remember when the news was about what happened, not how to feel about it? 1440's Daily Digest is bringing that back. Every morning, they sift through 100+ sources to deliver a concise, unbiased briefing — no pundits, no paywalls, no politics. Just the facts, all in five minutes. For free.

Read the newsletter trusted by 4.5 million fact-seekers.

Some AI drafts look polished until one person asks, “Where did that claim come from?”

That is a different kind of prep.

Before I send AI-assisted work, I now run a 10-minute Client Claim Check.

It catches the risky sentences before they become the sentence someone challenges later.

The check is simple:

Then you make the only decision that matters:

Use, Revise, or Cut.

⚠️ The useful part is not “AI reviews AI.”

The useful part is forcing every important claim to point back to a source before it goes out the door.

This is especially good for numbers, client-specific claims, competitor claims, “best practice” language, and recommendations.

📄 I put the prompt, the Google Sheet template, and a worked example in the web version.

Get the full Meeting Prep Pack (Client Claim Check + Meeting Objection Brief). Reply PREP and I'll send it directly.

Most people write a post, open Canva, and start guessing at layouts. Try this instead.

Paste your draft into ChatGPT and ask it to build the visual versions for you.

Copy this:

Then send this follow-up:

⚠️ Common mistake: asking for one design in five sizes. That produces five awkward crops, not five platform-ready visuals.

Done looks like this: one rough draft becomes a small set of usable visuals, then the matching caption, post copy, worksheet intro, and web header text.

Trust check: check the logo, tiny text, and every claim before publishing. AI is good at the first design pass. It is not your final proofreader.

✅ SIGNAL — OpenAI just hired 150 engineers to implement AI inside your company Large orgs have been stalling on AI because they don't have the internal engineering capacity to actually deploy it. That excuse is gone. OpenAI launched a separate implementation company — staffed on day one — and Tesco, Virgin Atlantic, and Supercell are already signed.

✅ SIGNAL — Spotify will make you a private podcast from your calendar, inbox, or class notes Describe what you want. An agent builds the audio and drops it in your Spotify library. No coding after setup. Free and Premium both qualify. Here's what it does.

✅ SIGNAL — Claude Code now runs multi-agent orchestration, outcome loops, and session memory — all live One lead model delegates to specialized sub-agents. You define the end goal. The system evaluates itself against a rubric until it hits it. Session memory surfaces durable improvements between runs. All three are live for paid Claude Code users.

🔇 NOISE — Google silently pushed a 4GB Gemini model to your Chrome browser You can't trigger it deliberately. In the EU it may get pulled before it's useful. EU regulators are already asking questions. Worth knowing, not worth acting on.

195 of you voted on AI-generated files. 35% haven’t tried it at all. 14% are already turning one file into several for real work.

The middle is where it gets useful. Half of you have tried it, and half of that half got burned.

That tracks with this week’s issue. The problem is not “AI can’t make files.” The problem is that most people ask for the file before they give AI the constraints.

A few replies that landed:

Kristin: “Since we know the subject matter, we know what hallucinations look like. Minor edits at the end and I’m done.”

That’s the actual unlock. Your subject matter expertise is the error detector. AI can draft the file, the meeting brief, or the visual set. You still know when it smells wrong.

Fares: “If the prompt has detail on output expectations, I’ll still double-check format and output.”

Right. The prompt is the spec. Vague in, vague out.

📨 Know someone who walks into budget meetings or sends AI-assisted reports? Forward this to them — the two prompts above are the kind of thing you wish someone had shown you sooner.