Pre-Call Planning: A 15-Minute Sales Call Plan

Pre-call planning is not a research contest. It is a short decision process that turns scattered account information into a useful sales conversation. In 15 minutes, a seller should be able to name the call's purpose, separate verified facts from plausible hypotheses, prepare questions that can disconfirm those hypotheses, and define a next step the buyer can reasonably accept.

A useful plan fits on one page. If it becomes a biography of the contact, a copy of the company website, or an AI-generated list of ten supposed pains, it has failed. The plan should improve judgment in the meeting, not create the illusion that the seller already knows the answer.

The one-page pre-call planning template

Field	Write this	Avoid this
Outcome	One decision or learning goal	"Close the deal"
Facts	Three to five sourced observations	Guesses stated as truth
Hypotheses	Two or three possible implications	A single fixed diagnosis
Questions	Four prompts that test the hypotheses	A generic interrogation script
Proof	One relevant example or benchmark	An unverified customer claim
Next step	One concrete action with an owner	"Let's keep in touch"

This is narrower than sales account planning, which maps priorities, stakeholders, opportunities, and risks across a strategic relationship. It also comes before the live diagnostic work covered in our sales discovery questions. The pre-call plan prepares the conversation; it does not complete discovery in advance.

Why the plan starts with buyer knowledge

In an August 2026 episode of Sales Talk for CEOs, Becc Holland argues that founders often overlook the buyer knowledge they carry naturally. They understand the role, recognize the problem, and know which questions expose it. New sellers are frequently taught the product without receiving that same model of the buyer's work. Her practical recommendation is to keep learning about the buyer for 15 minutes a day so sellers can diagnose instead of merely present. Listen to the episode.

In a September 2026 episode of Higgle: The B2B Sales Club, Carlo Girasoli makes the meeting-level version of the same argument. He recommends researching the data, understanding the larger issue, and entering the meeting with a clear idea of the desired outcome. He also warns against handing the answer to AI: the seller still has to choose the right questions and interpret the evidence. Listen to the episode.

The 15-minute workflow below is our synthesis of those lessons. It is a timebox, not a claim that every meeting deserves exactly the same preparation. Use more time when the commercial risk, number of stakeholders, or decision complexity is higher.

The 15-minute sales call planning workflow

Minutes 0–2: choose the outcome

Finish this sentence: "At the end of this call, both sides should know whether…" A first discovery call might determine whether the current process creates a material problem. A follow-up might validate technical fit. An executive meeting might decide whether a wider buying group should be involved. Choose one outcome that can realistically happen in the scheduled time.

An outcome is not a private seller target. "Book a demo" describes what you want. "Decide whether visitor-level account signals could improve the team's prioritization" describes a question both sides can evaluate.

Minutes 2–6: collect a small set of facts

Use sources you can name and date. Useful facts include:

• the company segment, market, and stated offer;
• the contact's current role and remit;
• a dated hiring, product, funding, technology, or organizational change;
• approved CRM history from previous conversations;
• account-level product or website activity when consent and instrumentation support it.

Record the source beside each fact. A pricing-page visit may be an account signal. It does not prove that a named executive visited, that budget exists, or that a purchase is imminent. The source tells you what you may safely infer.

Minutes 6–9: turn facts into testable hypotheses

A hypothesis links an observation to a possible business consequence. Label it visibly as a hypothesis. For example: "The team is hiring three SDRs" is a fact when the jobs are public. "Managers may need a repeatable account-prioritization process before onboarding them" is a hypothesis.

Use three columns to keep the reasoning honest:

Observed fact	Possible implication	What would disconfirm it
Three SDR roles opened this month	Pipeline capacity is expanding	The roles replace departures
Account returned to the pricing page	A buying question may be active	The activity is internal or unrelated
CRM notes show slow lead routing	Ownership may block follow-up	The workflow changed after the last call

Minutes 9–12: prepare four questions

Prepare one question for each job:

1. Trigger: "What changed that made this conversation useful now?"
2. Current process: "How does the team decide which account a rep works next?"
3. Test: "I saw the SDR team is expanding. Is consistency during that growth actually a concern, or am I connecting unrelated events?"
4. Decision: "What would we need to learn today to justify a next step?"

The test question matters most. It gives the buyer an easy way to correct your interpretation. Preparation should make you more curious, not more certain.

Minutes 12–14: choose one proof point

Bring one example that matches the problem, company stage, and audience. State what the evidence can and cannot show. A customer story may show that a workflow was useful in one context; it does not promise the same result for this account. If no relevant, approved proof exists, bring a process diagram or a product example instead of inventing authority.

Minute 14–15: define the next step and stop

Write the smallest next step that follows from a positive conversation: a technical review with a named owner, a second meeting with one missing stakeholder, or a limited test using agreed success criteria. Give it an owner and a date only after the buyer agrees.

Then stop researching. More tabs rarely improve the call after the objective, facts, hypotheses, questions, proof, and next step are clear.

Example: preparing for a first Lead Scorer conversation

Imagine a 60-person B2B software company hiring its third SDR. Public job descriptions mention outbound account research, while the CRM note says inbound leads are routed manually. The plan might look like this:

• Outcome: determine whether account prioritization is a meaningful problem.
• Facts: three SDR roles, manual routing note, B2B mid-market focus.
• Hypothesis: more capacity could increase inconsistent research and response time.
• Disconfirming question: "Has routing already been fixed since our last exchange?"
• Proof: show how an account score preserves each signal and its source.
• Next step: test the model on 25 accounts with an agreed review criterion.

Notice what the plan does not say. It does not claim to know which employee visited a page, that the VP Sales is unhappy, or that the company has budget. Those are questions for the conversation, not facts for the CRM.

When to spend more than 15 minutes

Extend the timebox for:

• strategic accounts with several business units or regions;
• executive meetings where the cost of a weak premise is high;
• procurement, security, legal, renewal, or commercial negotiations;
• calls involving several stakeholders with different success criteria;
• situations where the data itself needs verification.

For those cases, start from the fuller account plan and create a one-page call brief from it. Do not make every seller rebuild the account history before every meeting.

How AI should assist pre-call planning

AI is useful for retrieval and compression. It can assemble recent approved CRM notes, identify missing fields, summarize a public company update, cluster account-level signals, or propose questions against a hypothesis. Each output should preserve its source and date.

Keep three decisions human: which outcome matters, which inference is plausible, and which thread to follow when the buyer answers. Use a lead scoring model to prioritize preparation, but do not let a score or generated brief pretend to know the buyer's internal situation.

The best pre-call plan does not predict the meeting. It helps the seller enter with enough context to ask a precise question, enough humility to hear a correction, and enough clarity to propose a useful next step.