Before an executive meeting, your team gets one page and the executive gets a different one. Here's what goes on each, and how to run the half hour itself.
An executive brief is the one page your team prepares before meeting a key account's executive. It names the decision you need, what would make you lose, the customer's problem and why now, the KPIs at stake, the question in each attendee's head, who leads which part, and a value map for your focus areas. The executive gets a different page: a short pre-read attached to the invite.
Placeholder answer
Short, practical frameworks for executive messaging, business cases, multithreading, and sales enablement.
Executive meetings are high stakes. I mean, you haven't really sold enterprise if you've never sweat through your shirt before an exec-level meeting. It's a rite of passage. And I've screwed up my fair share of those precious few minutes, much to the chagrin of past champions.
So before every key-account meeting with an executive, write one page for your side of the table, send the executive a different page, and then use your page to run the half hour itself. Here's each piece.
Eight blocks, on one page, for your team:
1. Meeting objectives. Three sentences:
We need to enable [ next best buying behavior ] to keep our deal on track.
If we see [ evidence ] by the end of the meeting, the conversation was successful.
We also need to ensure [ key contact ] feels [ emotion ] after, based on [ context ].
2. Threats and alternatives. Finish the template's sentence: if we lose this deal, and they don't invest in us, it'll be because... It might be a competitor, an in-house build their CTO is exploring, or a competing priority.
3. The customer's problem statement. "Despite trying [ failed solution ], the customer still can't [ desired outcome ] because of [ problem ], which is costing them [ cost of problem ]."
4. Why now. "[ Executive ] is pushing to reach [ strategic goal ], and sponsored a project labeled [ internal language ] to support this. Their goal is to reach [ project milestone ] by [ compelling event ]."
5. Customer impact. The one or two executive KPIs the meeting is really about, with the current measure and the target by a date.
6. The attendees, and the question in each head. For every person from their side, write the #1 question they're privately asking, like "How is this going to be any different than the last / failed time?"
7. Roles. The AE opens with the intro and agenda, the AE and your champion frame the context together, the discussion runs between the AE, your own executive, and the champion, and the AE closes on next steps.
8. A value map for your focus areas. For the one or two areas you'll steer the discussion toward, map the problem, its root cause, the impact, what's required, your differentiator, and the outcome. Here's the example in my template, from selling to sales teams:
Underneath all eight sits the narrative you've built with your champion, compressed into a few sentences the executive can hear, retain, and repeat (the 4-sentence soundbite is how I'd build it). I learned that kind of compression early in my career, by the way, building valuation models that turned thousands of pages of legal documents into one line: "Your wireless technology is worth $4.00 per unit." That one line was the result of three months of work, lots of takeout, and a hundred Excel tabs.
Never the brief, since it's full of your team's honest read on the deal, including how you might lose it. The executive gets a pre-read instead, and the best one is your 1-page business case.
An executive assistant taught me this one. She was helping me set up a conversation with an SVP at a top-five insurance company (we landed a multiyear deal, which I attribute to her in large part). Here's how it works:
Executives are sharp. They think clearly and process information far faster than the pace of a typical sales conversation. Which is why a pre-read, with no homework expected, lets you both drive toward what's most important. But not every executive will be a fan, so ask their assistant or your champion first.
Now, find the executive whisperer. A small handful of people hold a no-questions-asked level of trust with any executive, and if they nod "yes" during your meeting, the executive gets the confidence to push forward. If you don't get the nod, well, get ready for an uphill battle. If that person isn't already your champion, meet them ahead of time and ask: "What area of this project gives you the most concern? If it were to go off the rails, why do you think that would be?" Then address those concerns before you're all in the room together.
Keep your prepared material to about 25% of the meeting time (that's seven minutes on a 30-minute call), because executive meetings always go off-agenda. Executives have strong opinions about where they'd like the conversation to go, and they're used to running it. So leave room, and plan the half hour in five pieces:
Executive meetings usually kick off a new round of internal communication, starting with that referral. Keep the executive posted while asking almost nothing of them:
[Executive], no reply needed here, just keeping you in the loop. We also have Y planned for next week and will update you after. We're continuing to make good progress on X.
By the way, this is also a good question for the end of the meeting itself: "How would you like us to keep you updated?"
And remember whose house this is. You're a short-term guest, while your champion lives with that executive long after you've left. So your main goal in all of this is to create more internal standing for them, and you'll know you did if your champion tells you afterward they're grateful you were part of the conversation. Like bringing John Legend to a wedding to sing to the bride and groom.
Less than it looks, because most of the brief carries over from work you've already done. The problem statement and the why-now line come from your business case, and the people come from your account plan. What's new is the question in each attendee's head and who leads which part, and those are the two things nobody can improvise once the meeting starts.