10 Ways to Look Smart in Every Meeting (Using Claude)

Each tactic below is a Claude prompt you use before, during or after a meeting. Most take under 2 minutes. By week 2, people start saying "you always come prepared."

The power move

Save the four prompts you use most (I’d pick 1, 5, 7 and 10) as Claude Projects, one each, by pasting them into Set project instructions. Then prep is one click instead of one paste.

The night before, or 30 minutes before

Walk in knowing every attendee’s role, recent moves and what they care about. Most people show up cold. You’ll show up like you’ve been thinking about this meeting for a week.

Pre-research every attendee

I have a meeting [tomorrow / today at X time]. Pull research on every external attendee using web search. For each person, give me: 1. WHO THEY ARE Title, company, tenure, background. LinkedIn-level summary. 2. WHAT THEY'RE WORKING ON Current strategic priorities, recent public moves, quotes from the last 6 months. What are they being measured on right now? 3. WHAT THEY LIKELY CARE ABOUT Based on their role and what their company is doing, what KPIs / themes / outcomes matter most to them this quarter? 4. WHAT'S CHANGED RECENTLY Promotions, layoffs around them, public successes, controversies, departures, organizational shifts in the last 60 days. 5. THEIR COMMUNICATION STYLE Direct or diplomatic? Data-driven or vision-driven? Fast or deliberate? Match their style based on their public talks, podcasts, written content. 6. THE ONE QUESTION TO ASK A specific question tied to something they recently said or shipped, that signals I've done my homework without being a suck-up. 7. THE 3 THINGS NOT TO SAY Topics, framings, or names to avoid based on their public sensitivities or recent moves. If the attendee is low-profile and you can't find much, say so. Don't make anything up. If something's uncertain, flag it: "Based on [source], it appears X. Worth confirming." Here are the attendees: [List names + companies + roles]

Right after the meeting

Granola takes notes from your computer’s audio, so no bot joins the call. You stay present and clean notes show up after. Then the prompt below turns them into action items and follow-ups.

Set it up in 2 minutes

Download Granola (Mac, Windows, iPhone or Android) and allow microphone access. Open it before a meeting and it captures the audio without joining the call. The free plan keeps the last 30 days of notes (pricing). Then in Claude, open Customize (called Plugins on newer accounts), go to Connectors and add Granola, so Claude can read your notes directly (how it works). Full transcripts through the connector need a paid Granola plan, so on the free plan Claude reads your notes from the last 30 days, or you paste the transcript in.

Use Granola for live notes

Use the Granola connector to pull my notes from [meeting name, or "my last meeting"]. If the connector isn't on, I'll paste the notes or transcript below instead. Turn it into 4 outputs: 1. DECISIONS LOG Every decision made: - What was decided - Who decided - The reasoning - Any conditions or dependencies 2. ACTION ITEMS BY OWNER A table grouped by person: | Owner | Task (specific, not "follow up") | Deadline | Priority | Notes For ambiguous items, FLAG them: "Tom said 'I'll handle it' but didn't commit to a date." 3. FOLLOW-UP EMAILS Draft a personalized email for each attendee with ONLY their action items + a 3-bullet recap. Show me the drafts. Don't send anything. 4. WHAT'S OPEN Anything that came up but didn't get resolved: - The question - Why it matters - Who should pick it up - Suggested next step Skip filler, small talk, and obvious transcription errors. If a meeting was unproductive, say so. Don't invent value. Notes or transcript (only if pasting): [paste here]

30 minutes before

Walk in with 3 sharp, specific questions. You only ask one. Everyone remembers it, and they remember you as the person who thinks like a leader.

Pre-build devil’s advocate questions

I have a meeting on [topic / project / proposal]. Generate 3 sharp devil's advocate questions I can ask, not generic, not gotcha, but the kind of question that makes the room stop and think. For each question: THE QUESTION Specific to this topic, this team, this context. WHY IT MATTERS The deeper concern under the question. What surfacing this exposes. WHO IT WILL LAND HARDEST WITH The person in the room most likely to feel it, either because it threatens their position OR because they've been quietly thinking the same thing. THE LIKELY RESPONSE What the room will say back. Help me anticipate. HOW TO ASK IT WITHOUT BEING A JERK The exact phrasing: respectful, curious, not aggressive. ("I'd love to pressure-test this with one question..." not "Yeah but what about...") End with: which of the 3 is the most pivotal: the question that, if answered honestly, changes the direction of the meeting. RULES - Don't generate generic "have we considered..." questions. Be specific to my context. - The questions should sound like they came from someone with strong intuition, not from a checklist. Context for the meeting: [Topic, decision being made, people in the room, my position]

Before any pitch

Know every counter-argument before you walk in. When someone objects, you’ve heard it already and you have the answer ready. Turn the effort up to high for this one if your Claude plan gives you the option.

Steelman the opposition

I'm walking into a meeting where I'll be advocating for [my position / my proposal / my recommendation]. Before I do, build me the strongest case AGAINST my position, the version a sharp critic in this room would actually argue. Use: - The assumptions I'm probably making without realizing - The data the decision-makers in this room likely care about more than I do - The political or strategic context my proposal might be ignoring - The opportunity cost (what we're NOT doing if we do this) - The implementation risk (where this falls apart in execution) - The track record (have similar moves failed before? has this team historically struggled with this kind of decision?) Then give me: 1. WHERE THE COUNTER-ARGUMENTS ARE WEAKEST Where I have a real opening to push back. Specific. 2. WHERE THEY'RE STRONGEST Where I need to concede or restructure. Specific. 3. THE QUESTION I CAN'T ANSWER The one someone in the room WILL ask. Tell me what it'll be and prep me for it. 4. THE 30-SECOND RESPONSE A short, calm, non-defensive response to the strongest objection. Plain language. RULES - Don't soften it. If my proposal is weak, say so. - Use specific evidence and reasoning, not vague concerns. Context: [My proposal, the room, the stakes]

Before exec meetings

Frame your point around what each person is measured on and you sound like you have the whole company’s strategy in your head. Most people only argue from their own side.

Know each attendee’s priorities

For each person in tomorrow's meeting, map them to the priorities they're being measured on this quarter / year. Use web search + their public statements + general knowledge of their role. For each attendee: NAME + ROLE WHAT THEY'RE ACCOUNTABLE FOR The 2-3 specific outcomes their boss is judging them on right now. Not vague ("growth"). Specific ("net retention," "Q3 ARR," "reducing customer churn below 8%"). WHAT KEEPS THEM UP AT NIGHT Their current biggest worry or risk, the thing they'd happily get help solving. HOW MY POINT CONNECTS TO THEIR PRIORITIES Specifically: why what I'm proposing helps them hit THEIR number, not just mine. Give me the framing in their language. WHAT NOT TO LEAD WITH The angle that won't land, the part of my point that's irrelevant to what they care about. THE ASK PHRASED FOR THIS PERSON The same ask, reworded specifically for what this person cares about. After all attendees, surface: WHO TO LEAD WITH The person whose priorities most align with mine, the natural ally to anchor the conversation around. WHO WILL PUSH BACK HARDEST The person whose priorities are most misaligned with mine, and the specific bridge that would matter to them. RULES - Be specific about KPIs. Don't write "they care about growth." Write "they're measured on net new ARR and their Q3 target is $4M." - If you don't know the actual KPIs, infer from their role + company stage and flag: "Based on their role at Stage X company, likely measured on..." Attendees: [List with companies + roles] My ask: [1-2 sentence summary of what I'm proposing]

Draft before, send 60 seconds after

Most people send the recap hours later, if at all. You’ll send yours a minute after you walk out, and whoever sends the recap shapes how everyone remembers the meeting.

Pre-write the recap email

Draft a recap email TEMPLATE I can fill in during the meeting and send 60 seconds after it ends. Build it for [meeting topic / decision being made]. Pre-fill what you can; leave bracketed placeholders for what I'll fill in live. EMAIL STRUCTURE To: [attendees] Subject: [Meeting topic]: recap and next steps Hey all, Quick recap from today's discussion on [topic]: WHAT WE DECIDED - [Decision 1]: [owner] - [Decision 2]: [owner] - [Decision 3]: [owner] WHAT'S OPEN - [Open question 1]: [who's owning the answer + by when] - [Open question 2]: [who's owning the answer + by when] NEXT STEPS - [Action 1]: [owner], by [deadline] - [Action 2]: [owner], by [deadline] - [Action 3]: [owner], by [deadline] NEXT SYNC [Date / time, or "as needed"] If I missed anything or got something wrong, please reply with corrections. Otherwise, treating these as the agreed-on takeaways. [My name] RULES - Default tone: confident, direct, no apology preamble. The person who writes the recap controls the narrative. - Make it scannable in 30 seconds. - Add a short "Pre-Meeting Notes" section in MY personal copy (not in the email) where I'll capture anything else worth remembering. Pre-fill everything you reasonably can based on the meeting topic. Leave the rest as bracketed placeholders. Meeting context: [Topic, attendees, key decisions on the table]

Before any big ask

Know the 3 most likely objections and your answer to each. The room sees you handle pushback calmly because you saw it coming.

Anticipate the 3 objections

I'm presenting [proposal / recommendation / ask] in a meeting. Predict the 3 most likely objections I'll face from this audience. Not generic concerns. The specific pushback this specific room is likely to raise. For each objection: 1. THE OBJECTION (in their voice) Phrase it the way the most likely critic would actually say it. Not "concerns about budget." The actual sentence: "I'm not convinced this gets us the ROI we need vs. just hiring two more reps." 2. WHO'S MOST LIKELY TO RAISE IT Name the role or person. Why them. 3. WHY IT'S A REAL OBJECTION What's true about their concern, the legitimate part you should acknowledge. 4. MY RESPONSE A 30-second response in plain language. Not defensive. Not over-explaining. Acknowledges the legit part, then lands my point. 5. THE CONCESSION I'M WILLING TO MAKE If they push hard, what could I offer to meet them halfway without abandoning the core? (Sometimes the best response is "you're right about X. Let me revise.") After all 3, surface: THE OBJECTION I'M MOST AT RISK FOR NOT HANDLING WELL The one I'd fumble if it caught me cold. Tell me how to prep. THE WILD CARD The 4th objection nobody usually predicts. What could come from left field? RULES - Specific over generic. Use the audience's real language. - Don't strawman. The objections should sound like things smart people would actually say. Context: [Proposal, audience, what's at stake]

5 minutes before

Most meetings drift. The person who remembers what the meeting was for, and gently brings the room back to it, ends up running it without anyone noticing.

Memorize the meeting goal

Read the meeting invite below. Distill the actual goal of this meeting into ONE sentence I can carry in my head. FORMAT GOAL: "By the end of this meeting, we will have [specific, measurable outcome]." If the invite is vague (and most are), surface: - What you can infer the host probably wants - What's MISSING from the invite that should be clarified before or during the meeting - A 1-line message I could send the host BEFORE the meeting to clarify (if useful) Then give me 3 short phrases I can use in the meeting if it's drifting: - A redirect ("To make sure we leave with a decision, can we focus on...") - A deferral ("That's worth its own discussion, want me to grab time separately?") - A close ("So to make sure I'm tracking, we've decided X, and the open question is Y, right?") After all that: - Tell me if the meeting goal is actually achievable in the time slot. If not, flag: "30 minutes isn't enough for this. Suggest expanding the agenda or trimming scope." RULES - Be honest. If the meeting has no clear goal, say so. Don't manufacture one. - Don't make me sound like a meeting cop. The redirects should be diplomatic. Meeting invite: [Paste the calendar invite]

10 minutes before

Know exactly what you want before you walk in. Most people leave wishing they’d asked for something. You won’t.

Pre-draft your asks

Help me crystallize my asks for this meeting. I'll tell you the context. You give me a tight, decisive set of asks, ranked by what I should fight hardest for. For each ask: 1. THE ASK (one sentence) Specific. Quantitative where possible. ("$50K added to Q3 marketing budget" not "more marketing investment.") 2. WHY IT MATTERS The outcome it unlocks, in language that ties to the priorities of the people in the room. 3. THE MINIMUM ACCEPTABLE VERSION The fall-back I'd take if I can't get the full ask. ("If I can't get $50K, I'd take $30K + headcount approval for next quarter.") 4. THE LIKELY OBJECTION + RESPONSE Why they'll push back, and how I respond. 5. WHAT I'LL DO IF I GET A "NO" The next step if the ask doesn't land. ("Schedule a 1:1 with [person] to escalate" / "Bring it back next quarter with X data" / "Move forward without the budget on a smaller scope") After all asks: RANK THEM Tell me which ask to lead with, which to negotiate on, and which to drop if the room is hostile. THE NUCLEAR OPTION The ask I'd love to make but probably shouldn't. Tell me when it WOULD be the right move (i.e., what condition in the room would make it worth pulling out). RULES - Be specific. "Approval for X" beats "support for X." - Don't pad with asks I don't actually want. Better to walk in with 1 strong ask than 5 weak ones. Context: [Meeting topic, audience, what I'm trying to accomplish]

Within 60 minutes

Most people send four paragraphs at the end of the day. You send 3 lines within the hour, with the decision, the owner and the deadline.

Send 3-line follow-ups in an hour

I just walked out of a meeting. Draft a 3-line follow-up email for each attendee I owe one to. The format: decision, owner, deadline. No fluff, no preamble. EMAIL TEMPLATE To: [Name] Subject: [Meeting topic]: quick recap Hey [Name], [Decision or alignment in 1 sentence.] [The owner of the next step + what they're doing.] [The deadline + how I'll follow up.] Anything else from your side? [My name] RULES 1. MAX 3 LINES of body content. Anything more goes in a doc, not an email. 2. The first line states what was DECIDED, not what was discussed. 3. Use specific names, deadlines, and outcomes, never vague phrases like "we'll circle back" or "TBD." 4. End with a single yes/no question that invites correction. No "let me know if there's anything else I can help with" energy. For each attendee, customize: - The decision line should highlight what THEY committed to (or what was decided that affects them most) - The deadline should be specific to their action item, not the meeting's general timeline After all drafts, give me: THE GROUP THREAD VERSION A single 3-line message I could send in a Slack channel or email thread that captures the meeting recap for everyone at once. WHAT TO DO IF I HEAR NOTHING BACK IN 48 HOURS A 1-line nudge I could send to anyone who hasn't responded. Meeting context: [Topic, who attended, what was decided, who owes what]

10 Ways To Look SmartIn Every Meeting

10 Ways To Look Smart
In Every Meeting