Meeting Objection Brief
Write the pushback before you walk into the meeting
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.
The point is not to sound rehearsed.
The point is to walk into the room with the hard parts already thought through.
🧠 When to use this
Use this before a meeting where you need one of these:
Approval
Budget
Buy-in
A decision
A scope change
A yes from someone skeptical
Do not use it for every meeting. That turns it into homework.
Use it when the outcome matters.
What you need
You need two things:
ChatGPT/Claude
A Google Doc
That is it.
Your screen may look slightly different. ChatGPT moves the furniture constantly. Look for the feature name, not the exact location.
One more warning: ChatGPT does not know your coworkers. The named context you give it is what makes the output useful. Treat predicted objections as starting points, not truth.
Step by Step Guide
Step 1: Open a new ChatGPT chat
Paste this prompt.
I have a meeting coming up and I do not want to get caught off guard.
Meeting: [what the meeting is about]
My goal: [what I want approved, decided, changed, or agreed to]
People in the room:
- [Name / role]; usually cares about [budget, timeline, risk, sales impact, customer impact, workload, etc.]
- [Name / role]; usually cares about [same]
What I am worried about:
[the question, objection, or weak spot I hope does not come up]
Help me prep.
Give me:
1. The 3 objections most likely to come up.
2. Who is most likely to raise each one.
3. The real concern behind each objection.
4. A plain-English answer I can give without sounding defensive.
5. The one decision I should ask for before the meeting ends.
Be direct. Do not make this sound polished. I want useful prep, not talking points.Step 2: Run the second prompt
The first answer usually catches the obvious objections.
The second prompt is where the useful stuff shows up.
Paste this after ChatGPT answers:
Now be more skeptical.
What objection did you miss?
What would the toughest person in the room push hardest on?Do not skip this step.
The first pass gives you the clean version. The second pass gives you the thing that might actually happen in the room.
Step 3: Copy only the useful parts into Google Docs
Do not copy the entire ChatGPT answer.
That creates another wall of text you will never read again.
Copy only:
The likely objections
Who may raise each one
What they actually care about
Your plain-English answer
The weak spot
The question to ask in the room
The decision you want before the meeting ends
How to use the brief
Read it once, about 30 minutes before the meeting.
Do not read it during the meeting.
Do not use it as talking points.
If you recite the answers, you will sound rehearsed. The brief is there so you can listen better when someone pushes back.
The work happens before the meeting. The doc stays private.
Example
Here is the kind of input you might paste into ChatGPT:
Meeting: Budget review for a spring campaign
My goal: I want approval for a $25,000 paid media test.
People in the room:
- CFO: usually cares about budget, payback period, and whether the spend is tied to revenue
- Head of Sales: usually cares about lead quality and whether marketing is claiming credit for sales work
- Product Lead: usually cares about timeline and whether the campaign will create promises product cannot support
What I am worried about:
Sales may push back on attribution and say these leads would have come in anyway.The output will not be perfect. That is fine.
You are not asking ChatGPT to predict the future. You are using it to pressure-test your own ask before other people do.
The common mistake
The mistake is treating the brief like a script.
It is not a script.
It is a private prep doc.
You are not trying to win the meeting by sounding clever. You are trying to avoid being surprised by an objection you could have prepared for.
What to do before your next important meeting
Make one Meeting Objection Brief this week.
Pick a real meeting where you need a decision.
Run the two prompts. Copy the useful parts into the Google Doc. Read it once before the meeting.
You will know it worked when someone raises an objection and you are not answering it for the first time.
Was this useful enough to try before a real meeting?
I’m using these quick polls to decide what to make clearer, cut, or build next. One click helps me avoid guessing.