There's a particular flavor of dread that arrives about ten minutes before a high-stakes meeting, when you realize you never actually thought through what you want out of it. I know it intimately. For years I walked into budget conversations and stakeholder pitches with a warm, vague sense of my position and walked out having delivered approximately none of it, then spent the rest of the afternoon rehearsing the sharp, confident things I should have said. The meeting was over. The rehearsal was just self-flagellation with extra steps.
Five minutes and a brief
Now there's a non-negotiable five-minute block before anything that matters. I open the Meeting-Prep Brief — Walk In Knowing Your Ask, Their Objections, and Your Opening Line prompt and fill in the basics: meeting type ('Budget review with the CFO'), the attendees and what they actually care about, my goal ('approval for two Q4 hires'), the relevant context, and the constraints I'm working against ('CFO is laser-focused on margin, and we're already over headcount plan'). Claude Sonnet 4.6 returns a half-page brief in about thirty seconds — fast enough that I genuinely have no excuse to skip it, which is the only reason I actually do it.
- The OBJECTIVE line forces me to define what success looks like before I walk in — deceptively simple, weirdly clarifying
- The LIKELY OBJECTIONS have been right about 80 percent of the time, so I'm rarely caught flat-footed
- I've started using the OPENING LINE nearly verbatim — it sets intent without sounding combative
- The DO NOT RAISE list has steered me clear of two or three landmines I'd have wandered straight into
The meeting that converted me for good
The one that truly sold me was a hard conversation with a vendor who'd been quietly underperforming for a full quarter. I walked in knowing my exact ask, the two objections they'd raise, and — crucially — the one topic I would not bring up unless they did. That last bit was the brief's idea, and it was right. The whole conversation was clean, direct, and resolved in 25 minutes. The old me would have danced around the discomfort for an hour, brought up three tangential grievances out of nervousness, and left having renegotiated nothing — just two professionals who'd successfully spent an hour avoiding the one thing that mattered.
Why Sonnet, and the honest limitation
I picked Claude Sonnet 4.6 for this deliberately. The hard part of meeting prep isn't listing topics — anyone can do that — it's the nuance: knowing the difference between firm and aggressive, anticipating what a margin-obsessed CFO actually fears, framing an ask so it sounds like a shared win rather than a demand you're hoping they'll grant. That's relationship-aware reasoning, and it's where Sonnet shines while staying fast enough for a five-minute pre-meeting window. The honest limitation: it's only as good as the context I give it. The one time I got a generic, useless brief, it was entirely my fault — I'd written 'meeting with the team' instead of who, why, and what was actually at stake. Specific in, specific out, every single time.
The 'attendees' field is the secret weapon
The input I almost skipped at first — attendees and their likely priorities — turned out to be the one that makes the whole brief sing. When I bother to write 'CFO, cares about margin and cash runway; VP Eng, secretly wants the headcount but won't fight for it; my manager, supportive but conflict-averse,' the LIKELY OBJECTIONS section stops being generic and starts predicting the actual room. It anticipated that the VP Eng would stay quiet and that I'd need to give him an easy way to voice support without sticking his neck out — which is precisely what happened, and I had a line ready. The model can't read the room for you, but if you describe the room, it'll war-game it surprisingly well.
I've also started using the brief as a post-meeting checklist. After the conversation, I glance back at YOUR ASK and DO NOT RAISE and ask myself: did I actually make the ask, and did I keep off the landmines? More than once the answer to the first one was 'no, I chickened out,' which is a useful and humbling thing to learn about yourself in writing. Naming the ask in advance makes ducking it feel like a deliberate choice rather than an accident, and that alone has made me ask for more things out loud.
The compounding benefit is reputational. People have started noticing that I'm consistently clear and prepared, and they treat me accordingly — I get the decision in the room more often, simply because I'm the one who walked in knowing exactly what decision I was asking for. When a meeting produces a follow-up I have to decline, I hand the situation straight to my Say No Professionally prompt and let it draft the language. Grab the Meeting-Prep Brief — Walk In Knowing Your Ask, Their Objections, and Your Opening Line prompt on Prompt Dock before your next meeting that matters, and notice how differently you walk in — and how differently the room responds.