How to Use AI to Prepare for a Sales Meeting

What AI is good at in meeting prep

Preparing for a sales meeting is mostly reading and writing: going through what the prospect asked for, what was said last time, and what their company has announced, then turning it into a few lines you can hold in your head. That is the work AI assistants do well.

What they do not do well is know things you have not given them. A general-purpose assistant has no view of your CRM, your email thread, or the conversation your SDR had last Tuesday. Asked about a mid-sized company it knows little about, it may fill the gap with something plausible and wrong: an invented executive, an outdated product line, a merger that never happened.

So the rule for meeting prep is simple. You supply the facts; the AI does the shaping. The better your inputs, the less there is to check.

This post is a practical routine for one person preparing for one meeting. For the wider picture of how scheduling tools use AI, and what to ask a vendor, see our guide to AI meeting scheduling assistants.

Gather the inputs first

Before opening an assistant, collect:

• Their request, in their words. The booking form answer, the email that asked for the meeting, or the note from whoever booked it. "Wants to talk about integrations" is a summary. "We keep losing meetings when two reps book the same room" is the request.
• History with the account. The last few emails, the CRM notes, any open support tickets, and what was agreed in previous meetings. If the meeting was booked by someone else, a colleague or an AI sales agent, the handoff note is the most important input you have.
• Who is attending. Names and roles from the invitation. If you do not know a role, say so rather than letting the assistant guess.
• Public material you have read. Their website's product pages, a recent press release, an annual report if they publish one. Paste the relevant passage rather than asking the assistant what it knows.
• What you want from the meeting. One sentence: the next step you hope to agree.

Ten minutes of gathering saves twenty minutes of correcting.

Research the account, then check it

Many assistants can now search the web. That is useful for a first pass (what the company does, recent announcements, how they describe themselves) but it is also where most prep errors come from.

• Ask for sources, and open them. If a claim matters enough to mention in the meeting, read the page it came from.
• Check dates. A search result about a product launch, a reorganisation, or a new chief executive may be two years old. Old news delivered confidently is worse than no news.
• Never let it fill in people. Job titles, reporting lines, and who makes the decision are exactly what an assistant will guess at. Use what the attendees told you, their own public profiles, or your CRM.
• Separate fact from inference. Ask the assistant to mark which points are stated in the material and which are its own conclusions. "They are probably consolidating vendors" is a hypothesis to test with a question, not a fact to open with.

A useful prompt shape:

Using only the material below, summarise what this company does, what has changed for them in the last year, and anything relevant to [your product area]. Mark each point as "stated" or "inferred", and list anything you could not find rather than guessing.

Turn it into a five-minute brief

The output you actually want is a brief you can read in the five minutes before the call. Long research notes are rarely read. A good brief fits on one screen:

1. Why this meeting matters to them, in two sentences and in their terms.
2. Who is attending: names, roles, and what each probably cares about.
3. What happened before: previous conversations, commitments, and anything still open.
4. The three questions they are most likely to ask, and what you need ready for each.
5. Five questions to ask them.
6. Sensitive ground: a complaint, a lost deal, a competitor they mentioned.
7. The next step to aim for.

Our free AI meeting prompt builder writes a prompt for a brief like this. Choose "Pre-meeting briefing", fill in the details, and paste the result into the assistant you already use. The prompt tells the assistant to ask before guessing and not to invent facts about either company. What you type into the builder is sent to us when you copy the prompt, so leave out anything confidential there too.

Prepare for their questions

Most meeting prep is spent on what you will say. The meetings that go well are usually the ones where the seller was ready for what the buyer would ask.

Ways to use an assistant here:

• Predict the questions. Give it the request and the attendee roles, and ask what a [finance lead / IT architect / operations manager] would want to know before agreeing to a next step.
• Rehearse objections. Ask it to play a sceptical buyer and push back on your answers. It is not a real customer, but it is a patient sparring partner, and it will find the weak spots in a vague answer.
• Sharpen discovery questions. Paste your list and ask which ones the prospect has already answered in the material you supplied. Asking those again is how a meeting starts badly.
• Prepare plain explanations. If a technical topic is likely, ask for a two-sentence explanation at the level of the person attending, then check it with someone who knows the subject.

Draft the agenda and the next step

An agenda sent in advance tells the other side the meeting was prepared for them. Ask the assistant to fit it to the time you have, to start with their priorities rather than your presentation, and to leave the last five minutes for agreeing next steps and owners. The prompt builder has an agenda option for this. To start from a template instead, the meeting agenda builder builds a timed agenda without AI.

Then decide the next step you will propose before you go in, and write it down: a technical review with a named specialist, a pilot scoping call, a meeting with their finance lead. Meetings that end with "let's keep in touch" are a common leak in sales meeting conversion, and a specific proposal is the fix.

What to keep out of an AI assistant

Check your company's rules before you paste anything. As a starting point:

• Use the tools your company has approved. A business account may be set up not to keep or train on what you enter; a personal account may be set up differently. Check the settings rather than assuming.
• Leave out what you would not forward. Pricing and discount approvals, contract terms, anything under a non-disclosure agreement, and other customers' details.
• Be careful with personal data. Notes about individuals, such as their opinions or their position in internal politics, are personal data in many places. Keep it to what you need.
• Do not paste credentials or internal links. Shared-drive links, admin pages, and access tokens do not belong in a prompt.

If you are unsure whether something is allowed, leave it out and add it to the brief yourself afterwards.

A 20-minute AI prep routine

For a typical first or second meeting, adjusted to taste:

• Five minutes: gather. Their request, the history, the attendees, one or two pieces of public material, and your goal.
• Five minutes: research. Ask for a sourced summary, open the sources for anything you will mention, and drop anything you cannot confirm.
• Five minutes: brief. Generate the one-screen brief and rewrite the parts that do not sound right.
• Five minutes: questions and agenda. Likely questions, your discovery questions, the agenda, and the next step you will propose.

Then close the assistant and read the brief once more as yourself. The AI drafted it; you are the one walking into the meeting. Afterwards, the same discipline applies to AI meeting follow-up.

CallShark is being built to keep what an attendee asked for, who they are meeting, and what happened last time attached to each booking, so preparation starts from a complete record. The product is temporarily down.