Prep for a meeting by pasting in the agenda

The core move is five minutes and a paste. No Granola, no terminal, no meeting history.

What you'll have when you're done

A fast prep method you can run on anything that triggered the meeting: an agenda, a contract redline, a deck, an email thread. You paste it into a plain chat window, ask two or three targeted questions, and walk in knowing the real decision, what the other side will push for, and which questions to ask. Five minutes of pasting beats thirty minutes of skimming, and the model works only from what you paste.

Walking in cold

I used to skim. Calendar reminder fires, I open the deck or the agenda, I scan it for thirty seconds, I close it and tell myself I'll think about it on the walk over. Then I'm in the room making up answers in real time, running slower than I should.

The honest version: I wasn't underprepared because I was busy. I was underprepared because skimming doesn't load context. It loads the feeling of context. There is a difference, and the meeting exposes it.

Five minutes of targeted prep changes the room. Not because you know more than the other side. Because you know what you need to know.

What you need first

• A Claude or ChatGPT account. If you haven't set one up, your first 30 minutes with Claude walks you through it. Plain chat, no terminal.
• Whatever triggered the meeting. Agenda, email thread, deck, contract redline, SOW, brief. If nothing was sent, paste the calendar invite and any context you have.
• Five to ten minutes. Night before or right before. Either works.

That is it.

Step by step

The core move

Open a plain chat window. Paste the material. Run two or three questions before you close the tab.

The model works only from what you paste. It does not know your history with this person, the unspoken politics, or anything someone decided in a hallway conversation. What you give it is everything it has to work with. So the better the paste, the better the prep.

If the agenda is thin, paste the email thread that set up the meeting. If the deck arrived with no context, paste both. If you have a one-paragraph description of what the meeting is actually about, paste that too. The more you give it, the better the questions it can help you answer.

Six prep questions worth asking

These are ready to paste. Use two or three, not all six at once.

• "What is the real decision this meeting needs to reach?"
• "What are the three things I should know before I walk in?"
• "What questions should I be ready to answer?"
• "What is the other side likely to push for, and what is my counter?"
• "Draft three sharp questions I should ask."
• "What is missing from this agenda that should be discussed?"

The third and fourth are the ones most CEOs skip. Knowing what you will be asked is at least as valuable as knowing what you want to say. The fourth is where the real prep lives: understanding the other side's position before you sit down.

If you want to summarize a long document first and then run these questions, that works well too. Two prompts: one to surface the key content, one to build the prep.

Prep by meeting type

Different meetings need a different lead question. Paste the agenda and use the one that fits:

Sales or customer call: "What objections is this buyer likely to raise, and how should I address each?"

Vendor negotiation: "What leverage does the vendor have, what is my realistic walkaway, and which terms deserve the closest scrutiny?"

Board or investor: "What numbers will they ask for that are not in this deck, and what are the three hardest questions I should have answers ready for?"

Team or 1:1: "What is likely being left unsaid, and what should I listen for rather than push?"

Interview (hiring or candidate): "Based on this role and my background, what are the five likely questions, and what follow-up questions should I ask?"

Each of these takes thirty seconds to run. None of them require a terminal, a plugin, or anything beyond a browser tab.

The five-minute protocol

Night before or ten minutes prior:

1. Open a new chat.
2. Paste the agenda, email thread, or deck.
3. If useful, add a short paragraph of background: who this person is, where the relationship stands, what you are trying to accomplish. This is context the model cannot infer from the document alone. Give it the context it lacks and the prep gets sharper. (More on this in how to give AI the context it needs to help you.)
4. Run two or three questions from the list above.
5. Jot the answers. One page or a few bullets. That is your brief.

Practitioners who use this pattern, across sales and ops roles, report that the "paste the agenda, ask for objections plus talking points plus questions to ask" sequence is the part they run every time. Not a full thirty-minute prep session. Three questions from a paste.

How you'll know it's working

You stop improvising. You arrive with a position, not a posture. The first time you see a question coming before it gets asked, that is the workflow paying off.

You ask better questions. The model drafts questions you would not have thought to ask cold. One of them lands, and the meeting goes somewhere more useful than it would have.

You close the pre-meeting skim loop. You used to open the deck and scan it. Now you open the deck, paste it, ask two questions, and close the tab knowing what you need. The scan goes from passive to active in three minutes.

When it breaks

A few honest limits:

It only knows what you paste. The model has no access to prior conversations with this person, the political history in the room, or anything not in the document. If those things matter, you have to supply them. Add a paragraph: "Background: I've been working with this vendor for two years, we had a pricing dispute in Q3, and the relationship is currently cordial but transactional." Now the prep is accurate to your situation. Without that paragraph, the model is working from the document alone.

Verify anything it asserts as fact. If it cites a number from the deck, confirm the number against the original. If it summarizes a timeline, check the source. The model summarizes; you verify before you carry the figure into the room. How to verify AI output covers this in full.

It prepares you for the room. It does not attend for you. The prep surfaces what is knowable from the material. The dynamic in the room, the thing someone says on the way in, the question nobody sent in the agenda: that is still yours to read. The prep lowers the cost of reading the room by handling the static part. The dynamic part is still your job.

Level up

This article covers plain chat prep: no terminal, no setup, no prior meeting history. Once you have run this pattern a dozen times, the natural next step is to pull from your actual history with the people in the meeting. That is a different workflow, one that reads your meeting records and builds a brief from what you last discussed, what each side owes the other, and what the outstanding items are.

That workflow is the pre-meeting brief. It requires Granola and Claude Code, and the setup takes about thirty minutes. The plain chat prep you did today is the on-ramp. The brief is where it goes once you want the prep to happen automatically, every meeting, without you thinking about it.

Start with the paste. The brief will make sense when you are ready for it.