Pre-Call Planning That Ends in One Decision per Call

Most pre-call plans end where they should begin. The rep opens the template, fills in the company size, the contact's title and tenure, a line of recent news, three discovery questions and two objections, and then makes the call. Twenty minutes of research, and not one sentence of it says whether the call should happen, what to lead with, or what would have made the rep put the phone down and move to the next name.

That is the quiet failure of pre-call planning as it is usually taught. The guides are not wrong about what to look up. They are wrong about what the looking up is for. Research that produces facts is homework. Research that produces a decision is planning. Almost every template on the first page of results produces the first and calls it the second.

Why pre-call plans produce facts and not decisions

Read the top-ranking guides and the steps are the same. Yesware's pre-call planning guide lists six: research the prospect and company, define call objectives, prepare questions, identify talking points, anticipate objections, plan next steps. CloudTalk's template walks the same path: research, objectives, a tailored opening, discovery questions, objections, CRM history. Both are competent. Neither has a box for the question that matters most before any call: should this call happen at all, and if so, why today?

The call is treated as fixed. The plan exists to make a fixed call go better. For a strategic AE working ten accounts a quarter that is fine. The calls are already chosen, and what remains is execution. For a rep or an SDR holding two hundred names, the choice of which calls to make is most of the job, and a template that assumes the call skips the decision the rep most needs help with.

There is a second reason the facts never become decisions: the plan has no standard for what counts as a reason to call. "Company grew headcount 20% last year" is a fact. Whether it is a reason depends entirely on what you sell. For a payroll vendor it might be the whole case. For a procurement platform it says nothing. Templates written for every seller cannot carry that standard, so the rep writes the fact down and the decision stays in their head, which is to say it does not get made. The same funding round reads six different ways depending on the product, and a plan that does not know the product cannot read it at all.

The cost is time the rep does not have. Salesforce's fifth State of Sales report, a survey of more than 7,700 sales professionals in 38 countries, found reps spend 28% of their week actually selling, with the rest going to deal management, data entry and other tasks (Salesforce, 2023). Pre-call research that does not change a decision is part of the other 72%. It feels like selling and counts as admin.

The reason test: the one standard a call plan needs

A name is worth calling when you can say three things about it: what changed, where you saw it, and when it happened. That is the reason test. If one of the three is missing, you do not have a reason yet. You have a name on a list.

• What changed. A fact about the account that was not true six months ago and that maps to a problem your product solves. A new VP of Operations. A job post for a role your product makes unnecessary. A system migration announced on an earnings call. Not a static attribute: industry, size and location are fit, not reason.
• Where you saw it. A source you could paste into the first email. A careers page, a press release, a filing, a LinkedIn post by a named person. If you cannot name the source, you cannot defend the opener when the buyer asks "where did you hear that?"
• When it happened. A date. Reasons age. A leadership change from last month is a reason; one from two years ago is background.

The test is deliberately strict, because the buyer is strict. LinkedIn's State of Sales research, surveying 750 buyers and 750 sellers in the United States and Canada, found that 48% of buyers will not buy from sellers who give them misleading information, and that only 21% of buyers prefer a cold call as a way to be contacted (LinkedIn, 2022). A call that opens on a sourced, dated change is the version of a cold call a buyer can tolerate. A call that opens on a guess dressed as research is the version that costs you the account.

Run the test on your own list before reading further. Take the ten names you plan to call tomorrow. For each, write what changed, where, and when. Expect to lose a good share of the names at step one. That is not a failure of the list. It is the plan doing its job before the call instead of during it.

One decision per call: pitch, not yet, or skip

A pre-call plan that has passed through the reason test can end in exactly one of three decisions. Forcing the choice is the whole method.

Decision	What it means	The evidence that justifies it	What happens next
Pitch	Call this week, lead with this product, open on this fact.	A dated, sourced change that maps to a problem you solve, at an account that fits.	The call plan gets written: opener, two questions, one objection.
Not yet	Fit is real, the reason is not here yet.	The account matches the profile but nothing has changed recently, or the change is too old to open on.	Note what would turn it into a pitch, set a re-check date, move on.
Skip	Stop spending time here.	No fit, or a change that points away from you: they just signed a competitor on a three-year term, or the team your product serves was cut.	Record the reason so nobody re-researches the account next quarter.

Two of the three decisions end without a call, and that is the point. A planning method that can only say "pitch" is a script, not a plan. "Not yet" is the decision reps are worst at making on their own, because the account looks right and the pipeline is thin, so the call happens anyway, opens on nothing, and the account gets burned for a reason that would have arrived in two months. "Skip" is the cheapest decision in sales, and the one most templates make impossible to record.

The call plan: one page, five fields, one of them the decision

Here is the plan that replaces the six-step template. It is shorter because it does not need to be longer. Everything a call plan usually contains either feeds the decision or follows from it.

1. The decision. Pitch, not yet, or skip. Written first, revised last. If you cannot fill this field, the research is not done.
2. The one fact. What changed, where you saw it, when. One sentence, one source, one date. Not three facts. The second and third facts weaken the opener, because they dilute the reason the buyer should keep listening.
3. The product. Which of your products or solutions the fact points to. At a single-product company this field is trivial. At a company selling four product lines into one customer base it is the field that decides whether the call makes sense, and the one that generic templates cannot hold.
4. The contact. Who at the account owns the problem the change created, and whether this person is still there. Nothing kills a well-researched call like opening on a reorg to someone who left in it.
5. The opener and two questions. The first sentence, built on the fact. Two questions that test whether the change created the problem you think it did. Objections, next steps and talking points live in your playbook, not in the per-call plan, because they do not change per account.

Notice what is missing: company overview, industry trends, tech stack, mission statement. If a fact in those sections would change the decision, it belongs in field two. If it would not, it is reading, and reading is what the other 72% is made of.

A worked example: three accounts, three decisions

Say you sell a workforce scheduling product to multi-site operators: retail chains, clinic groups, logistics depots. Three accounts come off the list.

Account one: pitch

A regional clinic group posted four "Practice Manager" openings in the last three weeks on its own careers page, each listing "staff rota management across sites" in the duties. The change: they are hiring the people who do by hand the thing you automate, at four sites at once. Source: the careers page, with the posting dates. The decision is pitch, the product is scheduling, the contact is the Director of Operations the postings report to, and the opener is the four postings. Two questions: how is the rota built across sites today, and what happens when one site is short?

Account two: not yet

A logistics operator with sixty depots, a perfect fit on paper. The most recent public change is a CFO appointment fourteen months ago. Nothing since: no hiring in operations roles, no expansion news, no system announcements. Fit is strong, reason is absent. Decision: not yet. Note: watch for depot openings or operations hiring. Re-check in eight weeks. The temptation is to call anyway because the account is big. The plan says no, and the plan is right, because "I noticed you are a large logistics operator" is not a reason anyone has ever taken a meeting for.

Account three: skip

A retail chain that announced, in a trade press interview six weeks ago, a group-wide rollout of a competitor's workforce platform on a multi-year contract. That is a change, it is dated and sourced, and it points away from you. Decision: skip, with the reason and the date recorded so the account does not resurface on next quarter's list as "untouched."

Three accounts, one call. The two that did not become calls took five minutes each to settle, and both left a note that saves the next rep the same five minutes. The one that became a call has an opener the buyer cannot wave away, because the rep is describing the buyer's own careers page back to them. This is what the pre-call research checklist is for when it is ordered by what changes the call: it feeds this decision, it does not replace it.

Running the method on two hundred names, not three

The honest objection to everything above is scale. Three accounts is an afternoon. Two hundred is the list a BDR is handed on Monday, and the reason test, run by hand at five to fifteen minutes per account, is twenty to fifty hours of work before the first call. Nobody does that, so the method quietly degrades to "call the ones with the most employees."

There are two ways out. The first is to run the test on a sample. Take twenty accounts, run the reason test by hand, and count how many land in each decision. If fifteen are "not yet" and three are "skip", the list is the problem and no call plan fixes it. If eight are "pitch", you have a week of good calls and a template for what a pitch-grade reason looks like at your company, which you can then teach. This costs a day, and it is the best day a new SDR can spend.

The second is to have the research done against what you sell before the list reaches the rep. This is where PitchSmart sits. It reads every lead on a list against the products you have described to it and returns a plan per lead: pitch, not yet, or skip, the product to lead with, the dated change behind the decision with its source, which contact to approach and whether they are still in the role, and an opener built on the strongest verified fact. The decision and the fact arrive together, because the research was done with the decision as its purpose. The five fields above come filled in, and what the rep still owns is the call, and the judgement to override a "not yet" when they know something the public record does not.

Either way the standard is the same. Every call gets a decision, every decision gets one fact, every fact gets a source and a date. Hold research to that standard and the qualification questions you ask on the call get sharper too, because you already know which problem the change created and are only confirming it.

The version you can run tomorrow

• Take tomorrow's call list. For each name, write the decision first: pitch, not yet, or skip. If you cannot, write "unknown" and count the unknowns. That count is your real planning gap.
• For each "pitch", write one fact: what changed, where, when. Delete every other research note from the plan. Make the call with the fact as the first sentence.
• For each "not yet", write what would change the decision and a re-check date. Do not call.
• For each "skip", write the reason in the CRM where the next person will see it.
• At the end of the week, count which decisions turned into meetings. If "pitch" calls with a dated, sourced fact book at a different rate from calls made on fit alone, you have your argument for applying the test to the whole list.

Pre-call planning was never about knowing more before the call. It is about deciding, before the call, whether the call is the right use of the next twenty minutes, and being able to say why in one sentence the buyer would recognise. The guides give you the research. The decision is the part they leave out, and it is the only part that was ever going to change the number.