Open any pre-call research checklist and count the order of the steps. Company overview first, then recent news, then the person's LinkedIn, then the tech stack, then mutual connections. That order is not wrong so much as it is arbitrary. It is the order things are easy to find in, which is a fact about search engines, not a fact about the call.
A rep with ten minutes before a call does not need a complete picture of the account. They need the two or three facts that will make them say something different than they would have said with no research at all. Those are not the same set, and on most accounts they are a small fraction of it. The checklist below is ordered by that difference, and it ends with a list of the things to deliberately not look at.
The test that orders the list
Before you look anything up, fix the question you are answering: would this fact change a sentence I say on the call?
Not "is this interesting." Not "does this show I did my homework." Changes a sentence. If you cannot name the sentence it changes, the fact is trivia and it costs you a minute you do not have.
This test is stricter than it sounds, and it kills most of what a standard checklist collects. Knowing a company was founded in 2011 changes nothing you say. Knowing they announced a European expansion six weeks ago changes the discovery question you open with, because it tells you which of your problems just became theirs. Knowing the headcount is 340 changes nothing. Knowing they posted four roles in revenue operations this quarter changes who you ask to be in the room.
The test also explains why research often feels unrewarding. A rep who spends twenty minutes and arrives with eleven facts has usually arrived with one usable one and ten pieces of ballast. The twenty minutes felt productive because the finding rate was high. The call went the same way it would have gone at minute three.
The ten minutes, in order
Run these in sequence and stop when the clock runs out. The order matters more than the completeness, because the first two blocks carry most of the effect and the last one converts everything into something you will actually say.
| Minutes | What you are looking for | What it changes |
|---|---|---|
| 0 to 3 | The most recent public statement of a problem you solve | Your opening line and your first question |
| 3 to 5 | The change that put a clock on it | Whether you argue for this quarter or next year |
| 5 to 7 | What this person owns and is measured on | Which outcome you attach the product to |
| 7 to 8 | What they already bought next to what you sell | Whether you position as replacement, addition, or neither |
| 8 to 10 | Nothing. Write two sentences. | Whether any of the above survives contact |
Minutes 0 to 3: the last time they said the problem out loud
An earnings call transcript, a job posting, a conference talk, an engineering blog, a press release, a regulatory filing. You are looking for the company describing, in its own words, a problem that sits inside what you sell. That sentence is worth more than any number of inferred pains, because you can quote it back and the buyer cannot argue with it.
Job postings are the most underused of these. A posting is a company writing down what it cannot currently do, signed and dated, with a budget attached. A requisition for a revenue operations analyst whose first listed responsibility is consolidating reporting across three CRM instances tells you more than a funding announcement does. This is the raw material behind most buying signals in sales, and it is public.
Minutes 3 to 5: what put a clock on it
A problem without a deadline does not get bought. This block asks what changed recently that makes the problem urgent now: a new executive who owns the area, a renewal date on an incumbent contract, a merger that doubled the number of systems, a compliance date, a market they just entered, a target they publicly committed to.
Without this, your call is a conversation about a real problem the buyer will keep tolerating. With it, you have a reason the conversation is happening this quarter rather than being deferred to a budget cycle nobody has scheduled. It is the difference between a valid observation and a reason to act on it.
Minutes 5 to 7: the person, narrowly
Two minutes on the individual, and spend them on scope rather than biography. What do they own? What number are they measured on? Who do they report to, and who reports to them? A director of revenue enablement and a director of revenue operations will route the same pitch to completely different outcomes, and the title alone will not tell you which one you have.
Skip the personal content. Their marathon time, their alma mater, the photo from the company offsite. A reference to it in the first thirty seconds reads as either filler or surveillance, and neither one helps. Use the two minutes to get their scope right instead, which is what decides whether your qualification questions land on someone who can answer them.
Minutes 7 to 8: the adjacent purchase
One minute. What have they already bought that sits next to what you sell? A job posting that names a tool, a public integration page, a customer logo on a vendor's site, an engineer describing the stack in a talk.
This is the fastest minute in the checklist and it decides your whole frame. If they bought the category two years ago, you are arguing about a gap in what they have, which is a different call from arguing the category exists at all. If they bought an adjacent product from a vendor who also sells against you, you are in a displacement and should know that before you dial rather than at minute eleven.
Minutes 8 to 10: stop looking, start writing
The last two minutes are not research. Write two sentences by hand:
- The reason-for-the-call sentence. One sentence connecting the thing they said (block one) to the thing that changed (block two). If you cannot write it, your research failed and more of it will not help. Go into the call honest and ask instead.
- The question you most want answered. The single thing you do not know that would most change whether this is a deal. Usually it is about the deadline or about who else has to say yes.
Reps skip this step because it is the only part that feels like work. It is also the only part the buyer ever experiences. Everything in the first eight minutes exists to make these two sentences possible.
What to skip, and why
A checklist that only adds is not a checklist, it is a wish. These are the items that appear on most pre-call lists and should not survive a ten minute budget.
| Skip | Why |
|---|---|
| The About page and the founding story | Written by marketing, near identical across the sector, changes no sentence you say |
| Exact headcount and revenue | Sizes the deal, does not shape the call. You can get it from the call itself |
| The full annual report | Forty minutes for what the risk factors section gives you in four, if you need it at all |
| Personal social content | Reads as filler or as surveillance, and buyers can usually tell which |
| Funding news older than a year | The money is allocated. Opening with it announces that your research stopped two years ago |
| Competitor lists with no reason attached | Knowing who else is in the market is not knowing why this account would switch |
The last row is the general case. Most wasted pre-call research is a fact collected without a reason attached to it. The fix is not to collect less, it is to refuse to collect anything you cannot immediately connect to a sentence you will say.
Why the ten minutes keeps collapsing into two
Every rep knows they should prepare. Most do it for a couple of minutes at best, and the usual explanation is discipline. That explanation is wrong, and the numbers point somewhere else.
The seventh edition of Salesforce's State of Sales report, fielded across August and September 2025 with 4,050 sales professionals, found the average seller spends 40% of their time selling. The rest goes to deal management, data entry, internal meetings, and admin. Pre-call preparation is not competing against laziness. It is competing against a calendar already full of work that is mandatory and visible, on behalf of a task that is optional and invisible.
The second reason is that research has no natural stopping point. Every source suggests three more. A rep who starts at ten minutes with no stopping rule either runs to thirty or, having learned that lesson once, starts allotting two. The test at the top of this article is the stopping rule: when the next fact will not change a sentence, you are done, whether that took nine minutes or three.
What raises the stakes is that the call now lands later in the process than it used to. 6sense's B2B Buyer Experience Report, from a survey of 2,509 recent buyers, found that 69% of the purchase process happens before buyers engage with sellers, and that 81% have chosen a preferred vendor before the first sales conversation. That preferred vendor wins more than 80% of the time. You are not opening the evaluation. You are arriving at one already underway, usually with someone else in front, and the ten minutes decides whether you sound like a participant in it.
The same pressure shows up on the receiving end. Salesforce's State of Sales statistics page reports that 73% of B2B buyers actively avoid sellers who send irrelevant outreach. Avoidance is the default posture, and a first sentence that could only have been written for this company is the thing that interrupts it.
What the ten minutes looks like when the research is already done
Notice what blocks one through four actually are. They are not analysis. They are retrieval. The rep is hunting for four specific facts that already exist in public, and almost the entire ten minutes goes to the hunt rather than to the thinking. The thinking happens in the last two minutes, and it is the part that gets cut when the hunt overruns.
That is a workflow problem with a workflow answer: move the hunting off the rep's calendar. This is what PitchSmart is built to do. It reads each account on your list against what you actually sell, and returns the buying signals that say who needs which of your products now, each one with the source it came from attached. The rep opens the account and reads four findings with links, instead of opening six tabs and guessing which one holds the useful sentence.
The ten minutes does not disappear. It changes shape. Minutes zero to eight become two minutes of reading, and the two minutes of writing stay exactly where they were, which is the part of the preparation nobody should want automated. Teams that already run a formal account research process or that buy intent data are solving the same half of the problem from a different direction. The question to ask of any of them is whether the output is a fact with a source attached to it, or a score you cannot repeat back to a buyer.
The version you can run tomorrow
Print this. It fits on an index card.
- Set a ten minute timer. It is a budget, not a target.
- Find the most recent place this company described a problem you solve, in its own words. Job postings first.
- Find what changed recently that puts a clock on that problem.
- Establish what this specific person owns and is measured on. Two minutes, scope only, no biography.
- Check what they have already bought next to what you sell.
- Stop researching with two minutes left. Write the reason-for-the-call sentence and the one question you most want answered.
- If you cannot write the sentence, go in and ask. That is a real option and it beats a generic opening every time.
One test, five blocks, two sentences. The measure of whether it worked is not how much you learned about the account. It is whether the first thirty seconds of the call sounded like it could only have been said to this company.
