Prepare for a sales conversation with AI in 15 minutes
Create an evidence-based call brief, useful discovery questions, and a realistic next step without inventing facts about the buyer or automating unsolicited outreach.

Start here
AI-generated editorial image. Illustrative scene; not a photograph of our team or a client.
Good preparation helps you listen. It gives you enough context to ask a relevant question without pretending to know the buyer's priorities. Use AI to organize confirmed information, expose gaps, and rehearse a clear opening. Fifteen minutes is a useful planning limit, not a guarantee that every account can be researched responsibly in that time.
Minutes 1–4: gather the facts you actually have
Start with the meeting purpose, the buyer's stated role, approved CRM notes, relevant public company information, and the offer you can genuinely deliver. Use an approved workspace and remove unnecessary personal information. Keep the original source and date beside each fact so you can verify it quickly.
A company announcement may suggest a topic to ask about, but it does not establish a buying priority. A job title does not prove budget authority. If information is missing, mark it unknown. A short brief with honest gaps is more useful than a complete-looking profile built from inference.
Prompt to tryCreate a one-page call brief using only the supplied information. Separate confirmed facts, hypotheses to test, and unknowns. Cite the source or CRM note for each fact. Do not infer budget, authority, urgency, personality, or private circumstances. Finish with three questions that would most improve our understanding. Call purpose and sources: [paste].
Minutes 5–8: choose questions that reveal the work
Build questions around the buyer's process, desired outcome, current difficulty, and decision criteria. Ask how the work happens today before describing how your solution works. Avoid a checklist that forces the person through your sales framework regardless of what they say.
In a hypothetical conversation with a small manufacturer about CRM cleanup, you might ask where a qualified inquiry goes after the first reply, how ownership is assigned, and which handoff causes rework. Those questions invite observable detail. Asking whether they want more revenue is unlikely to reveal enough to design useful help.
What happens between the first inquiry and a confirmed next step?
Where does the team have to check or repeat information?
What would a worthwhile improvement look like in your own terms?
What would need to be true for changing this process to be worth the effort?
Minutes 9–11: prepare a short, honest opening
Use a simple opening that establishes the purpose, checks the agenda, and gives the buyer room to redirect. For the hypothetical manufacturer: “I would like to understand how inquiries move through your team, then see whether a focused cleanup would help. Is there something more important we should cover first?” Remove any claim that assumes a problem the buyer has not confirmed.
If the buyer already named a concern, reflect it accurately instead of embellishing it. You can be specific without being presumptuous. A strong opening makes a useful conversation possible; it does not need a dramatic statistic or an unverified observation about the company.
Prompt to tryReview this opening and discovery plan as a skeptical buyer. Highlight unsupported assumptions, leading questions, jargon, and places where I start pitching too early. Rewrite the opening in natural language and recommend four questions, with a reason for each. Keep the buyer free to disagree or redirect. Brief and draft: [paste].
Minutes 12–15: decide what a useful next step means
Prepare several appropriate outcomes: a focused follow-up, a request for a missing fact, an introduction to the right owner, or a clear decision that there is no fit. Do not make booking another meeting the only acceptable result. You need enough evidence to know whether further effort serves both sides.
If an objection appears, clarify it before answering. Salesforce's objection-handling guidance emphasizes checking your understanding and asking open questions. We do not have the bandwidth could mean timing, implementation effort, or a polite decline. Your preparation should help you ask, not select a convenient interpretation.
Keep the real conversation authoritative
During the call, follow the buyer's answers rather than reading the AI brief as a script. Afterward, separate what the person said from your interpretation. Verify names, dates, responsibilities, and commitments before updating the CRM or sending a recap. Never turn an exploratory comment into a purchase commitment.
Use the assistant to prepare a draft follow-up for your review, with only the agreed actions. Do not auto-send unsolicited messages. Compare the brief with what you learned: which assumptions were wrong, which question helped, and what should change for the next conversation?
Check before you use the result
Facts, hypotheses, and unknowns are clearly separated.
Questions invite explanation without presuming a problem.
The opening gives the buyer room to redirect.
CRM updates and follow-up commitments reflect the actual conversation.
One thing to try.
1. Prepare a brief for one upcoming conversation using only approved, traceable information. 2. Rehearse a thirty-second opening and select four discovery questions. 3. After the call, record one assumption you corrected and one genuinely agreed next step.
Put it into practice