The rep had done plenty of research.
He knew the company had opened a second office, hired a new operations leader, and changed its home-page headline. He had the prospect's LinkedIn profile open beside two press releases and a page of product notes.
Then the call began.
The buyer spent the first five minutes repeating what she had explained the previous week: the current process was slow, finance needed a number, and the regional manager had not agreed to a pilot.
The rep had prepared for the company. He had not prepared for the deal.
That is an easy mistake to make because research feels productive. There is always another tab to open. A useful sales call plan is smaller. It gives the rep enough context to avoid going backward and one clear idea of what should be different when the meeting ends.
Start with the last conversation
HubSpot defines pre-call planning as researching the prospect, understanding the business context, and developing a tailored approach before the conversation. That is sensible for a first meeting. On a second or fifth meeting, the best source is usually the account's own history.
Read the most recent notes before searching the web.
Look for:
- the problem the buyer described in their own words;
- what they have already tried;
- the result or date they care about;
- people involved in the decision;
- concerns, unanswered questions, and promised follow-ups;
- the last next step both sides accepted.
If the CRM says only "great call, follow up next week", the rep has to reconstruct the deal from memory, email, and calendar invites. That is a CRM problem, but it becomes a call problem a few minutes later. The buyer hears an old question and wonders whether anyone listened.
Write the current state in one sentence:
Northstar wants regional managers using one visit-note workflow before its October rollout. Finance needs a credible time-saving estimate, and the West Coast manager has not joined the evaluation.
That sentence is more useful than a page of company facts. It names the desired change, the timing, and the open risk. If you cannot write it after reading the record, you have found the first thing the call needs to clarify.
Minute 1 to 3: decide why this call exists
"Run the demo" is an activity. "Find out whether the sales director will sponsor a three-rep pilot" is a call objective.
Choose one movement that would make the opportunity clearer. It may advance the deal, expose a reason to slow it down, or show that it should leave the pipeline. All three outcomes are useful.
For a first call, the objective might be:
- confirm that the problem is current and costly enough to address;
- understand why the buyer agreed to speak now;
- learn how the current process works and where it fails.
For a follow-up:
- resolve the concern that stopped the last meeting;
- confirm who owns the internal decision;
- agree on the evidence needed before a pilot.
For a demo:
- let the buyer test two workflows tied to the problem they described;
- learn what is missing for their users;
- agree on the evaluation step after the demo.
Do not write five equal objectives. When everything matters, the rep defaults to covering material. Pick the decision or piece of evidence that deserves the meeting.
Minute 3 to 5: write three questions, not a script
LinkedIn's discovery-call guide recommends preparing guiding questions and asking the buyer to add to the agenda. The questions should come from what is still unknown, rather than from a generic list.
Three good questions are usually enough to steer a scheduled call. Each should have a reason behind it.
| What you need to learn | Prepared question | Useful follow-up |
|---|---|---|
| Whether the problem has priority | "What has changed since we last spoke?" | "How has that affected the October date?" |
| Whether the buyer has internal support | "Who else will have to be comfortable with this workflow?" | "What will they want to see before they support a pilot?" |
| Whether the next step has a real test | "If three reps tried this for two weeks, what would tell you it worked?" | "Where could we get that baseline today?" |
The follow-up matters because the first answer is often a label. "Finance is concerned" tells you who is concerned, but not why. A short second question can uncover whether the issue is budget, procurement, proof, or something else.
Keep the questions visible, then stop looking at them once the conversation develops. They are prompts, not a route the buyer must follow.
Minute 5 to 7: prepare for one likely concern
Review the last call for hesitation. If this is the first conversation, use the role, company, and meeting source to make a modest prediction.
A finance leader may ask how the saving will be measured. An operations leader may care about rollout effort. A sales manager may worry that reps will ignore another process. None of those assumptions should be presented as facts. They tell you what to have ready.
Bring one piece of proof that fits the concern:
- a relevant customer example you are allowed to share;
- a short view of the exact workflow;
- a sample calculation with assumptions shown;
- an implementation outline;
- a direct answer from security or product.
One good example beats six backup slides. If the concern never appears, leave the proof alone. Preparation should make the rep more responsive, not more determined to use every asset.
Minute 7 to 8: set a plain agenda
The agenda should tell the buyer what the meeting is for and leave room for correction.
I thought we could spend a few minutes on what has changed since last week, look at the rep workflow you asked about, and then decide whether a small pilot is worth defining. What would you add?
This is close to the advice in LinkedIn's guide: set an agenda, share it, and ask for the prospect's input. The final question is important. A buyer who says "I also need to cover data retention" has just improved the meeting.
Avoid an agenda that reads like an internal sales process:
Introductions, discovery, presentation, objections, next steps.
Those headings tell the buyer how the seller has organized the hour. They do not explain what the buyer will get from it.
Minute 8 to 9: decide what a useful next step is
Do not wait until the final two minutes to invent the ask.
Write the smallest sensible commitment that could follow from a good conversation. It might be a technical review, an introduction, a dated pilot plan, access to baseline data, or a clear decision not to continue.
Make the step specific enough to schedule:
Priya and Marco will review the workflow with us on Thursday at 10:00. We will send the two-page security summary beforehand.
"Circle back in a few weeks" is not a next step. It is an agreement to remember each other later.
The proposed step is not a trap. The buyer may change it. Planning it in advance prevents the call from ending with a vague promise because everyone ran out of time.
Minute 9 to 10: close the tabs
Salesforce's pre-call checklist allocates time to the CRM, external research, a call plan, and a final minute to settle before speaking. The exact split can change. The final minute should stay.
Close anything you do not need during the call. Keep the account record, your short plan, and the meeting window. Check the names of the people joining. Put the phone away.
Then read four lines:
- Current deal state.
- Call objective.
- Three questions.
- Proposed next step.
The rep should enter the meeting ready to listen, not still consuming information.
A one-page pre-call planning template
Copy this into your CRM, notes app, or account workspace.
| Field | What to write |
|---|---|
| Why are we meeting? | The buyer's reason for accepting this call |
| Current state | Desired change, timing, and main open risk in one sentence |
| Last agreed facts | Important points already confirmed |
| Call objective | The one decision, commitment, or fact that should become clearer |
| Three questions | Questions tied to important unknowns |
| Likely concern | One concern worth preparing for |
| Relevant proof | One example, answer, or asset that fits that concern |
| Proposed next step | A specific action, owner, and date |
| Buyer agenda item | Leave blank until you ask what they want to add |
This plan should fit on one screen. If it becomes a document that takes twenty minutes to read, it will not survive a busy week.
Do different calls need different plans?
The structure stays the same, but the source material changes.
First sales call
Use the meeting source, CRM activity, the person's role, and a small amount of company research. Do not pretend to know the buyer's priorities because you read a press release. Turn the research into questions.
A good objective is to understand the current process, the reason for looking now, and whether another conversation would be useful.
Follow-up call
Begin with the previous conversation and open commitments. Check what your team promised, what the buyer promised, and what changed between meetings.
The useful question is often "What happened since we last spoke?" rather than a fresh discovery script.
Product demo
Review the buyer's language and choose the two or three product moments that answer it. Decide what feedback you need and how the buyer will evaluate fit.
The plan should make the demo shorter. A tour of every feature is usually evidence that discovery did not reach the person running it.
Late-stage or commercial call
Review the decision process, agreed value, unresolved risk, and people who have not yet participated. Bring exact answers on scope, security, implementation, or terms.
The goal may be a signature, but the call objective should name the decision still standing in its way.
Managers should review the plan, not add homework
A manager can improve call preparation with four questions:
- Context: What do we already know from the buyer?
- Objective: What has to become clearer on this call?
- Question: Which question will help us learn it?
- Next step: What would make sense if the answer is positive?
This is a short coaching conversation. It should not produce another internal form that the rep completes for inspection and ignores during the meeting.
After the call, compare the plan with what happened. Which assumption was wrong? Which question opened the conversation? What new stakeholder, concern, or commitment belongs in the CRM?
That review is how call planning improves. It also leaves better context for the next person who prepares, whether that is the same rep, a solutions consultant, or a customer-success manager.
Preparation gets easier when the CRM contains the conversation
The ten-minute plan depends on notes that carry more than an activity date.
The CRM should preserve the buyer's goals, language, constraints, stakeholders, objections, commitments, and unanswered questions. Tasks should show who owes what and when. A new rep should be able to understand why the next meeting exists without interviewing the last rep.
When that context is captured after each conversation, preparation becomes a decision-making exercise. The rep spends less time hunting through recordings and email threads and more time deciding what deserves the next call.
Before the meeting, answer one question:
What should be clearer, different, or agreed when this call ends?
Everything else in the plan should help the rep get there.
Quick answers
What is pre-call planning in sales?
Pre-call planning is the short preparation a sales rep does before a conversation. It combines relevant account context, the current deal state, a clear call objective, prepared questions, likely concerns, useful proof, and a proposed next step.
How long should sales call preparation take?
For an established opportunity with clean notes, ten minutes is often enough. A complex first meeting, technical review, or executive presentation may need more. The plan itself should still remain short enough to use during the call.
What should I research before a first sales call?
Check the CRM activity, how the meeting was booked, the contact's role, the company website, and recent company news that may affect the conversation. Use the findings to shape questions rather than treating public information as proof of the buyer's priorities.
What is a good objective for a sales call?
A good objective names what should become clearer or what commitment would move the deal forward. "Confirm whether the sales director will sponsor a three-rep pilot" is more useful than "show the product".
Should I write a sales call script?
Write the opening, three important questions, and the proposed next step if that helps you prepare. Avoid scripting the buyer's side of the conversation. A call plan should support listening and follow-up questions.
Research note: This guide draws on current pre-call planning guidance from HubSpot, LinkedIn Sales Solutions, and Salesforce. LogicNotes added the ten-minute sequence, deal-state sentence, three-question table, one-page template, and manager review prompts.
Make the last call useful before the next one starts.
LogicNotes turns sales conversations into structured CRM context and follow-up tasks, so reps can prepare from what the buyer actually said instead of rebuilding the deal from memory.
See LogicNotes for teams