← All articles
Guide10 min readMarch 28, 2026

How to Prepare for Any Executive Meeting Using AI (a 10-Minute Workflow)

Real preparation — the kind that changes how a meeting goes — used to take hours. This workflow collapses it into 10 minutes using Claude.

Most executives don't walk into meetings underprepared because they're lazy. They walk in underprepared because real preparation — the kind that actually changes how a meeting goes — takes more time than they have. So they skim the deck on the way in and wing the rest.

AI doesn't fix that by doing the thinking for you. It fixes it by collapsing hours of prep into 10 minutes.

This guide uses Claude as the primary tool — it handles long context and nuanced professional scenarios particularly well — but the same workflow applies to ChatGPT, Gemini, or whichever AI assistant you already use. The prompts are written to work across all of them.

Executives around a boardroom table

The meeting outcome is often decided before anyone walks in the room

What This Workflow Covers

This is a repeatable system for any high-stakes meeting: a board update, a difficult client conversation, a quarterly business review, a stakeholder alignment session, or a 1:1 where the other person has an agenda you haven't fully mapped. If you have 10 minutes and something to paste into Claude, this works.

The 10-Minute Claude Prep Stack

Minutes 1–2: Context Dump

Don't start by asking Claude a question. Start by giving it everything — the agenda, any previous meeting notes, relevant emails, the deck you haven't had time to read. Paste it all in one go. Claude's context window is large enough to hold it. Your job in these two minutes is to be the fastest possible information courier, not an editor.

If you use Claude with Gmail connected, you can skip the copy-paste entirely — ask Claude to pull the last three emails from a contact and it will surface them directly. For everything else, a quick forward-and-paste takes under a minute.

Minutes 3–4: Stakeholder Brief

Ask Claude to tell you who's in the room and what they actually care about — not their job titles, but their likely pressure points going into this specific meeting. A CFO in a budget review is in a different headspace than a CFO in a board presentation. Context changes everything, and Claude can surface that distinction if you give it enough to work with.

Minutes 5–6: Anticipate the Hard Questions

This is the step most people skip entirely and the one that changes meeting outcomes most. Ask Claude to generate the five most uncomfortable questions you could face, then draft concise answers to each. You won't need all five. But walking in having thought through the hardest version of the conversation is a different mental state than walking in hoping it doesn't come up.

Minutes 7–8: Your Opening and Your Ask

Every meeting needs two things from you: a clear opening that establishes context fast, and a clear ask — what you need to walk out having decided, agreed, or moved. Ask Claude to draft both. You'll edit them. But having a draft forces you to react rather than create from scratch under pressure.

Minutes 9–10: The Human Layer

Read everything Claude gave you. Edit what doesn't sound like you. Delete what's wrong. This is not optional — it's where your judgment goes back in. Claude compressed the time; you supply the accuracy and the read on the room.

Professional reviewing notes at a desk

The human layer is non-negotiable — Claude compresses time, you supply judgment

The Exact Prompts

Use these as starting points. Adjust the bracketed fields for your meeting.

Step 1 — Context dump

"I have a meeting in [X minutes/hours]. Here's everything I have:

[PASTE: agenda, recent emails with attendees, deck, previous meeting notes, any relevant background]

My role: [your title and company]
The other key people: [names, titles, companies]
My goal for this meeting: [the specific outcome you need — a decision, an approval, alignment on X]
My relationship with these people: [new contact / existing client / internal team / senior stakeholder]

Read this and confirm you have the key context. I'll follow up with specific questions."

Step 2 — Stakeholder brief

"Based on what I shared, give me a 3-bullet brief on each key person in the room.

For each person, cover:
— What they are likely optimising for in this specific meeting
— What would make this a win from their perspective
— What would make this a loss or a frustration for them

Key people to profile: [list names and titles]
Context that matters: [any politics, history, or tension worth factoring in]

Be specific to this situation. No generic stakeholder advice."

Step 3 — Hard questions

"Generate the 5 toughest questions I could face in this meeting — the ones I would least want to be asked.

For each question:
Write the hardest version of it, not a softened version.
Write a concise, direct answer I can give on the spot.
Flag if there's anything I should avoid saying or committing to.

Context for the hard questions: [any known risks, objections, gaps, or sensitive topics]

Don't protect me from the uncomfortable questions. I need to be ready for the real ones."

Step 4 — Opening and ask

"Draft two things for me:

1. A 2-sentence opening I can use to frame the meeting, set the right tone, and establish why we're here. Tone should be [confident and direct / collaborative / consultative].

2. A single clear ask — the one thing I need to walk out of this meeting having achieved.

My ask in plain language: [describe what you actually need]

Make both crisp enough that I can say them without reading from notes."

Step 5 — Sanity check

"Final check before I go in.

Based on everything you know about this meeting:
1. What is the one thing most likely to go wrong, and how should I handle it if it does?
2. What is the one thing I must not forget to say — the point that, if I leave without making it, the meeting will have failed?
3. Is there anything in the context I gave you that I might be underestimating or overlooking?

Be direct. I have [X minutes] left."

When This Works Best — and When It Doesn't

This workflow is strongest when you have material to feed Claude. A deck, a prior meeting summary, an email thread, a brief — anything that gives it context beyond the meeting title. The more specific the input, the sharper the output.

It's weakest in two situations. First, when you have zero context — no agenda, no history, no materials. Claude can only work with what you give it, and vague input produces vague output. Second, when the meeting is highly dynamic — a negotiation that could go in ten directions, or a conversation where the real agenda is unstated. Claude can help you prepare for probable scenarios, but it can't anticipate the one the other person is keeping to themselves.

One thing worth saying plainly: preparation doesn't guarantee outcomes. The meeting still depends on your presence, your read of the room, and your judgment in the moment. This workflow gets you to the table in better shape. What happens at the table is still on you.

VP presenting confidently in a client meeting

Preparation changes the version of yourself that walks into the room

What This Actually Looks Like in Practice

I had a quarterly business review with one of our largest clients last quarter. Ten minutes before the call, the old version of me would have skimmed the numbers, remembered there was a support issue I'd never fully resolved, and hoped it didn't come up.

Instead, I pasted the account history, the last QBR summary, and the client's recent support tickets into Claude. Four minutes later I had a stakeholder brief that flagged their procurement lead — who had joined three months ago — as an unknown variable with likely cost-reduction pressure. Eight minutes after that, I had five anticipated questions including the exact one about the support issue, with a drafted answer that acknowledged it directly and pivoted to what had changed.

I walked into that call with a 3-bullet brief, a clear opening line, and the confidence of someone who had already had the hard conversation once — in my head, with Claude's help. The meeting still required me. But I showed up as a different version of myself.

Try It Before Your Next Meeting

Take the prompts from this article into your next high-stakes meeting. The whole workflow takes 10 minutes. By the third time, it's second nature.

For board-specific prep — mapping room dynamics and stress-testing your narrative before a high-stakes board presentation — see How to Prepare for Board Meetings with AI.

Free guide + weekly newsletter

Get Started with AI in One Day — Free

Subscribe and get our free 15-page starter guide instantly. Then weekly AI workflows, honest tool takes, and strategies for senior professionals. No fluff. Unsubscribe any time.

No spam. Unsubscribe anytime.

Keep reading

Guide6 min read

The 10 AI Prompts Every Executive Should Know

From briefing synthesis to stakeholder communication — prompts that actually save hours every week.

Mar 5, 2026Read more →
Guide9 min read

How to Build an Executive Presentation with AI in 30 Minutes

Most AI presentation tools optimise for speed and aesthetics. This workflow builds narrative structure first — so your deck moves a decision, not just fills a room.

Mar 31, 2026Read more →
Guide14 min read

The Best AI Prompts for Executives: 15 You'll Actually Use

Most 'AI prompt' roundups were written for marketers or freelancers. These 15 were built for executives who run teams, manage stakeholders, and don't have time to debug a bad output.

Apr 5, 2026Read more →
Guide15 min read

The Executive's Complete Guide to AI in 2026: What to Use, How to Start, What to Skip

Most executives don't have a time problem. They have a preparation problem. This guide covers what AI can actually do for you, which tools are worth paying for, which workflows to automate first, and why most executives quit before they see results.

Apr 9, 2026Read more →