A useful deal brief helps the rep enter the next conversation with a clear purpose. It brings together what the buyer has confirmed, what remains uncertain and what the team needs to learn next.
You can prepare that brief before a buyer meeting or use it in a manager's deal review. Start with the questions below, then keep only the information that changes how you will approach the conversation.
Name the purpose of the meeting
Write one sentence describing what the meeting should establish. It might be confirming the problem, understanding a review process or agreeing the next evaluation step.
Keep that purpose specific enough to check afterward. “Move the deal forward” leaves too much open. “Confirm who needs to review the proposed workflow and what evidence they need” gives the rep something concrete to ask.
The buyer may have a different priority. Prepare to check the meeting's purpose with them before working through your questions.
Separate confirmed facts from assumptions
Collect the commitments, questions and relevant account context from previous conversations. Record where each important detail came from and when it was last confirmed.
| Item | Confirmed information | Still to establish |
|---|---|---|
| Problem | What the buyer has said needs to improve | How they will judge a useful result |
| People | Who has participated so far | Who else reviews or approves the work |
| Process | Steps already discussed | Evidence needed at the next stage |
| Timing | Dates the buyer has confirmed | Dependencies that could change them |
| Next action | Existing commitments and owners | Any missing owner or unclear outcome |
Treat an empty cell as a question to investigate. Filling it with an assumption may make the brief look complete while leaving the rep unprepared.
Review what changed
Look for differences since the last conversation. A meeting may have moved, a new person may have joined, or a previously agreed action may still be open.
Each change is a reason to ask a question. It does not establish the buyer's intent on its own.
For an illustrative example, imagine an evaluation meeting was postponed and the rep has not heard from the person coordinating it. The brief could record both facts, then prepare a question about timing and ownership. It should not describe the deal as lost without further evidence.
Use past deals to prepare better questions
Ask the manager whether similar opportunities revealed a question the team should address earlier. The useful lesson might concern missing stakeholders, unclear success criteria or an evaluation step that took longer than expected.
Check whether that lesson fits this buyer. A pattern from a previous deal can suggest what to investigate, but it cannot replace the current buyer's answer.
Keep the review practical: what does the rep need to ask, what material will help, and which uncertainty matters most now?
Prepare the follow-up before the meeting
Create a short outline with space for the buyer's confirmed priorities, decisions, open questions and agreed next action. Leave the actual answers blank until the conversation happens.
Afterward, check the outline against your notes. Make the next action clear enough that both sides know who owns it and what it should produce. If no next action was agreed, record that accurately.
This makes the brief useful for the next conversation too. The account history becomes a record of what was established and what still needs attention.
Keep the checklist small enough to use
A rep should be able to find the meeting purpose, the most important unknown and the next question without reading a long account history. Keep supporting material available, but put the immediate work first.
Alfred for Sales is in development. I’m being built to help with deal preparation, follow-ups and coaching informed by your team's winning patterns. If these are areas your reps need help with, explore the planned Sales support or discuss your requirements.
Related reading: What does an AI Chief of Staff do?.