Pre-call planning is two jobs. Before the first call, research the account: why they’d buy now, who’s coming, and the next step you want. Before every call after it, recall the deal: what the buyer asked, what you promised, who they mentioned, and what’s changed. Let AI gather both. You pick the questions and the ask.
Most pre-call planning advice stops at the first call. It’s a list of research steps: read their site, check LinkedIn, look for news. That’s useful once. By call four, the buyer doesn’t care that you read their About page. They care whether you remember the question their CFO asked on call two.
How to prepare for a discovery call
The research job has three parts, and none of them is a fact sheet.
Why they’d buy now. Look for a reason this company has this problem this quarter: a new sales leader, a round of hiring, a funding announcement, a tool they just stopped using. One poster on r/sales put it well: “A LinkedIn profile is not a signal, it’s a fact sheet.” So when you ask AI for help, ask for the reason, not the facts, and read the source yourself before you mention it on the call.
Who’s coming. Everyone on the invite, their role, and what each of them gets out of the deal. If the invite has one name, plan to ask who else weighs in.
The ask. Write down the one next step this call has to get to, with a date. A call that ends with “let’s stay in touch” was prepped for the wrong goal. Our sales follow-up guide covers what to send after the call.
Then plan your questions. Gong’s 2017 analysis of 519,000 recorded discovery calls found that 11 to 14 questions correlated with the most success, that questions about the buyer’s business problems and goals did best, and that top sellers spread their questions through the call instead of front-loading them. That doesn’t mean 14 scripted questions. Prep three to five about their problem and let the rest come from their answers. SPIN selling is a good frame for what to ask.
Don’t recite your research back to them. As a post on r/sales put it, “There’s a difference between showing you looked and showing you understood.”
Pre-call planning for the second call and every call after
You’ve already done the research. What you need now is recall: everything that’s happened on the deal, in one place, before you dial in.
Pull these five things before every call after the first:
- The buyer’s open questions. What they asked that you said you’d come back to. If you walk in without the answer, it looks like you didn’t listen.
- What you promised and haven’t sent. The case study, the security doc, the pricing breakdown. Send it before the call, so you’re not apologizing for it on the call.
- Who they mentioned. When a buyer says “I’ll loop in our ops lead,” look that person up before you meet them. Multi-threading starts here.
- What changed since the last call. A reply that went cold, a meeting that moved, a new name on the email thread, a close date that slipped in the CRM.
- What you still need to confirm. The economic buyer, the decision process, the date it has to be live by. MEDDPICC is a useful checklist for what’s still missing.
The type of call decides which of these you lean on. Before an executive meeting, the open questions and the business case matter most. Before a competitive demo, bring what you know about the other vendor they’re looking at. When a new stakeholder joins, research them like it’s a first call, and bring the rest of the deal’s history too.
None of this lives on the web. It lives in your call notes, your email, and your CRM.
AI tools for sales call prep and account research
Every tool below preps something before a call. The difference is what each one reads.
| Tool | What it prepares before a call |
|---|---|
| Apollo | Pre-meeting insights from templates: the company’s priorities, the decision makers in the meeting, key company information, and objections from past meetings |
| Cirrus Insight | A research email each morning for every external meeting on your calendar |
| HubSpot Breeze Assistant | A call agenda: key information and suggested topics |
| Salesforce Agentforce | Account summaries, key priorities, and suggested next steps ahead of every meeting |
| Clay | Account Research Agents that keep research fields current across every account in a segment (open beta) |
| Gong | A meeting prep page with objectives, highlights from earlier conversations, and suggested questions. The summary appears once the account has prior calls or emails |
| Sybill | A pre-meeting brief: agenda, related tasks, qualification, the company, the participants, past interactions |
| Claude (sales plugin) | A prep sheet with account context, attendee research, and a suggested agenda, from its /call-prep skill |
| Arrows | A pre-call brief on every deal, from its calls, emails and CRM, with no prompt |
So pick by the calls you actually prep. A deal has one first call, and anything that reads the web covers it. Every call after that needs a tool that reads your call recordings and email threads, or call four gets a brief that reads like the one for call one.
Recall is the part we built Arrows for. Your best rep has a gameplan in their head for about 5 deals, and the other 15 get improvised. Arrows keeps one for every deal: a path to close, built from your team’s playbook and from what’s actually happening on that deal.
After every call, Arrows holds what was discussed and what needs to happen next. The pre-call brief is one of the actions in your team’s playbook. The brief for call four is ready before anyone asks for it, and it starts from calls one to three. When a new person shows up on a thread, Arrows researches them. A rep approves each piece before it goes out. See how Arrows works for AEs.