Choreography: preparing the sales meeting
The choreography that turns 30 minutes of prepping for a sales call into 5, with AI building the pre-call briefing. The briefing is a hypothesis; running the conversation stays yours.
You have an important meeting tomorrow and barely any time left to prepare. You opened two tabs on the topic, skimmed them, and closed the laptop, because the afternoon turned into firefighting all day long. AI builds the briefing before the meeting: a summary of what's at stake, the likely points of resistance, the right questions to pull out what you still don't know, and the possible paths depending on how the conversation goes. But the briefing is a hypothesis, not a script: reading the room, sensing the other side's hesitation, and deciding the next step, that's still on you. Thirty minutes of digging becomes five minutes of reading, and you walk in prepared, not caught off guard.
Tomorrow you have the final interview with the candidate who could take over the sales team's leadership, and the area manager will be in the room too. You read half the résumé, took a quick look at their LinkedIn, and stopped, because you still have two more interviews today. AI builds the pre-interview briefing: the candidate profile summary, likely red flags for that kind of career path, the right behavioral questions to dig into real experience, and next steps depending on how the conversation goes. But reading the candidate on the spot, sensing a hesitation in an answer, deciding to dig deeper or move on, that stays only yours. AI democratizes the prep that used to only exist in a senior recruiter's head.
Tomorrow you have a discovery call with the customer who uses the product the most, to understand why they stopped engaging with the new feature. The head of product will attend. You opened the metrics dashboard, saw the retention drop, and stopped, because the sprint review ate up your afternoon. AI builds the pre-call briefing: the summary of that account's product behavior, likely hypotheses for that usage pattern, the right discovery questions to separate symptom from cause, and possible next steps for the roadmap. But running the conversation, hearing what the user says between the lines, and deciding which thread to pull, that stays yours. AI hands you the plan, you read the room.
Tomorrow you have the proposal meeting with the account that could double your quarter's pipeline, and the decision-maker who went silent for three weeks finally got back to you. You opened the CRM, reread half the history, and stopped, because this week's forecast still isn't closed. AI builds the pre-meeting briefing: the deal's stage summary, likely objections at this stage, the right questions to confirm budget and decision criteria, and possible routing paths. But running the negotiation, reading the decision-maker's tone, and deciding when to push forward or pull back, that stays only yours. AI prepares the ammunition, who fires it at the right moment is you.
Tomorrow you have a meeting with the logistics supplier that's been missing SLA for two months, and the operations director will attend. You opened the delay report, glanced at the numbers, and stopped, because the afternoon shift blew up again. AI builds the pre-meeting briefing: the supplier's performance history summary, likely excuses they'll bring, the right questions to separate a one-off problem from a process bottleneck, and possible next steps to renegotiate or replace. But running the conversation, noticing when they're stalling, and deciding on the move, that stays yours. AI democratizes the prep that used to only exist in a seasoned manager's head.
Tomorrow you have a meeting with the area that processed customer data outside policy, and legal will attend to assess LGPD risk. You opened the incident record, read the first paragraphs, and stopped, because internal audit still has three open fronts. AI builds the pre-meeting briefing: the summary of the deviation's context, likely risk points for that kind of processing, the right questions to map what actually happened, and possible remediation next steps. But running the conversation, sensing if the area is omitting something, and deciding how hard to push, that stays only yours. AI hands you the plan, reading the room stays yours.
Tomorrow you have the post-mortem for the incident that took down the production deploy on Friday, and the CTO will be in the room. You opened the logs, saw half the stack trace, and stopped, because two other tickets caught fire today. AI builds the pre-meeting briefing: the incident timeline summary, likely causes for that kind of architecture failure, the right questions to separate human error from a systemic problem, and possible next steps to shield the pipeline. But running the post-mortem without it turning into a witch hunt, reading the team's mood, and deciding the focus, that stays yours. AI prepares the plan, playing the game is you.
Tomorrow you have a research session with the user who abandoned the signup flow right in the middle, and the head of design will watch. You opened the journey recording, saw all the way to the error screen, and stopped, because you still have two more prototypes to review today. AI builds the pre-session briefing: the summary of that user's behavior in the flow, likely friction points for that profile, the right questions to get them to reveal where they actually got stuck, and possible next steps for the redesign. But running the interview, noticing when the user rationalizes instead of reporting, and deciding where to dig deeper, that stays only yours. AI democratizes the prep that used to only exist in an experienced researcher's head.
Tomorrow you have the committee meeting that decides whether the company enters a new market, and the CEO will be in the room. You opened three market reports, read half of one, and stopped, because the quarter's deck still isn't closed. AI builds the pre-meeting briefing: a summary of the scenarios already mapped, the likely objections for that kind of decision, the right questions to stress-test the weakest assumption, and the possible next steps depending on the committee's call. But running the discussion, reading the CEO's hesitation, and deciding when to push, that stays only yours. AI hands you the plan, defending the bet in the room is still on you.
How many times have you walked into a sales meeting hoping it would go well? The customer talks, you answer on the fly, the objection comes and you stumble because you hadn't thought about it beforehand. In the end, you didn't lose the sale from lack of talent. You lost it from lack of prep. And prep, you know, has always been a privilege for whoever had the time or was senior enough to carry the briefing in their head.
Think with me: a sales meeting is a game. And no good team enters a game without studying the opponent first. The coach builds the plan the night before, draws up the plays, anticipates what the other team will do. Except in the game itself, it's the player who decides the play, on the spot, reading the field. The plan doesn't play. But a player with no plan spends the whole game chasing the ball.
The core idea of this lesson. AI builds the pre-call briefing, it hands you the plan, anticipates objections, and gives you the right questions. But running the conversation, reading the room, and deciding on the spot stays only yours. AI democratizes the prep that used to only exist for the senior rep.
01The choreography has four pieces, and all fit into the briefing
Prepping for a call isn't a loose task, it's a choreography with pieces that fit together. AI builds all four at once, in a single one-page briefing, based on what you know about the account. The four pieces are: the account context summarized, likely objections for that profile with the answer ready, the right discovery questions, and possible next steps to close.
Notice the word "likely". It carries the whole lesson. AI doesn't guess what the client is going to say. It looks at the profile, the segment, the account's moment, and tells you what usually comes up in a conversation with people like that. It's an informed hypothesis, not a crystal ball. Keep this, because it comes back at the end of the lesson.
Four pieces, one page, five minutes. It's the plan the coach used to build the night before, except now it's ready before your coffee gets cold. Fair enough?
02The context and objections: AI anticipates what you would have discovered the hard way
Start with the context. You feed AI what you know about the account, the site, the company's LinkedIn, a recent news item, the name of whoever will be in the room, and ask for an executive summary: who this account is, what moment it's in, who decides, what likely hurts. What used to take you thirty minutes of digging, and still left gaps, now arrives organized in one read.
The piece that changes the game the most, though, is the objections one. AI looks at the profile and tells you: people in this segment tend to get stuck on price, or on implementation timeline, or on "we already have a vendor". And for every likely objection, it already hands you a way to respond. You won't get caught off guard anymore when the customer says "it's too expensive". You already thought about this yesterday, with a cool head, not in the panic of the room with the CEO staring at you.
Notice AI didn't sell anything for you. It gave you ammunition. The ready answer is a starting point, not a memorized line. Whoever chooses to use it, adapt it, or drop it altogether, is you, reading the customer's face on the spot.
03The discovery questions: what separates whoever sells from whoever pushes
Here lives the most underrated piece of the briefing. A bad salesperson walks in talking. A good salesperson walks in asking. The difference between the two is almost always the quality of the discovery questions, the ones that get the customer to reveal the real pain, the budget, the decision criteria, and who else needs to say yes.
AI builds that arsenal of questions calibrated to the account's profile. For a manufacturer complaining about margin, it suggests questions that pull the cost thread. For a newly arrived director, questions that explore what they want to prove in their first hundred days. Before, that repertoire was the senior salesperson's asset, ten years of experience distilled into knowing what to ask. AI democratizes this: the six-month rep walks into the call with the discovery script that used to only exist for the veteran.
Think of the bridge metaphor again. AI hands you the questions, the piers on each side. But you're the one who crosses, who chooses which one to ask first, who listens to the answer and decides the next move. The right question at the wrong moment isn't worth anything. Timing is yours. The economic frame is direct: AI cuts the cost of prep to almost zero, but the value of the conversation, what actually closes the deal, is still generated by you in the room.
04Next steps and the golden rule: the briefing is a hypothesis, not a script
The fourth piece is the open-ended finish. AI hands you the possible next steps: if the conversation goes well, propose a pilot; if it gets stuck on price, offer a smaller scope; if a hidden decision-maker shows up, schedule a second call. It's not a single path, they're routes. Because you don't control what the customer's going to do, you only control being ready for each fork.
And here comes the golden rule, so read it slowly: the briefing is a hypothesis, not a script. Everything in it is "likely", never "certain". The objection AI anticipated might not come. The pain it imagined might be a different one. Whoever walks into the room reading the briefing like a rigid script stops listening to the customer and starts pushing the plan down their throat. That's worse than having no plan at all.
Close the reasoning with a clean division of labor. AI built the briefing, anticipated the objections, built the questions, sketched the routes. You run the conversation, read the room, choose the move, and decide on the spot. Thirty minutes of prep become five, and you show up much stronger, not because AI sold anything, but because you walked into the game with the plan you didn't used to have time to make. This connects directly to lesson 2.1, on giving AI context, because a briefing is only good when you feed AI with what you know about the account. And it connects to N.vnd.3, on account research, which is the raw material that goes into this. Context goes in, briefing comes out, you play. Fair enough?
Do it now
Take your closest your real task: a meeting or sales call you have coming up in the next few days. Build the pre-call briefing in five minutes:
- Context: feed AI what you have about the account (site, LinkedIn, a news item, who'll be in the room) and ask for an executive summary: who the account is, what moment it's in, who decides, what likely hurts.
- Objections: ask for the three most likely objections for that profile, each with a response path. Read it with a cool head and adjust each response to your own style.
- Discovery: ask for five discovery questions calibrated for that account, the kind that get the customer to reveal pain, budget, and decision criteria.
- Next steps: ask for the possible routing paths, depending on whether the conversation goes well, stalls on price, or a hidden decision-maker shows up.
Before the call, reread the briefing once. In the room, use it as a map: listen to the customer first, and only then pull the piece from the briefing that fits. Afterward, time how long this took and compare it to your old prep time.
Practice
1. In the meeting-prep choreography, what part stays irreplaceable, even with AI building the briefing?
2. Why should the briefing be treated as a hypothesis, not a rigid script?
3. What's the gain AI brings to preparing a sales meeting?
For the board
On the lossyou do not lose the sale for lack of talent. You lose it for lack of preparation.
On what the AI anticipatesthe objections you were going to discover the hard way, inside the meeting, with no time to think.
On the golden rulethe brief is a hypothesis, not a script. Whoever reads a script in front of the client stops listening.
Thanks for the feedback. It helps sharpen the next lesson.