The 10-Minute Pre-Call Research Routine for Busy Reps

If you want to know how to research a prospect before a call without losing your morning to it, the answer is a timed routine: two minutes on the company, three on the people, two on org context, two on triggers and timing, and one writing three talking points. That is the whole system. A pre-call research routine is a fixed sequence of sources you check in a fixed order, with a hard stop, so every call gets the same baseline of preparation no matter how slammed your calendar is. Below is the exact 10-minute version, with one real-feeling example carried through every step, plus a 60-second fallback for the days when even ten minutes is a fantasy.

Why is 10 minutes the right budget (not 45, not zero)?

Ten minutes is the right budget because it is long enough to find everything that changes how you open a call, and short enough that you will actually do it before every call. Forty-five minutes of research produces maybe two more usable facts than ten. Zero minutes produces a call that sounds like every other vendor’s call.

The data backs the discipline. In LinkedIn’s State of Sales research, 82% of top performers say they always research prospects before reaching out, compared with just 49% of everyone else. Consistency, not depth, is what separates them. Meanwhile, buyers report that 58% of their meetings with sellers provide no value, according to RAIN Group. Most of that gap is preparation, not product.

The routine below sits inside a broader system for sales call preparation, but it stands alone. The core principle: ruthless prioritization. You are not building a dossier. You are looking for three things you can say in the first five minutes that prove you did your homework.

Just as important is what you deliberately skip:

• The full 10-K. Unless you sell to the CFO, skim the one-paragraph business summary and move on.
• Press releases older than six months. Stale news makes you sound stale.
• The prospect’s entire LinkedIn history. You need their current role, tenure, and one recent signal. Not their 2014 job change.
• Glassdoor rabbit holes, podcast back catalogs, conference talks. Interesting, rarely actionable in a first call.

The 10-minute routine at a glance

Here is the full sequence in one table. Each block has a source, a hard time cap, and a specific extraction target, because “look at their website” is not a step, it is a way to lose eleven minutes.

Minutes	Source	What you’re extracting
0-2	Company site + one news search	What they sell, to whom, and one recent change
2-5	LinkedIn profiles of attendees	Role, tenure, one personal signal per person
5-7	LinkedIn company page + org clues	Team size, who your contact reports to, likely approvers
7-9	Funding, hiring, leadership news	The trigger that explains “why now”
9-10	Your notes	Three talking points, written down

For the rest of this post, we will run the routine on a single example: you have a 2 p.m. discovery call with Dana Okafor, VP of Operations at Meridian Freight, a 400-person logistics company, plus one unknown second attendee on the invite.

Minutes 0-2: the company in two searches

The first two minutes answer one question: what does this company do, and what changed recently? Open the homepage and read the hero section and the customer logos. Then run a single news search for the company name filtered to the last six months. That is it. Two searches, two minutes.

From Meridian Freight’s homepage you learn they do refrigerated freight for grocery chains, and the logo bar shows two big regional supermarket brands. The news search surfaces one item: they opened a third distribution hub in Reno four months ago.

That is already an opener: “I saw the Reno hub announcement. Expansion like that usually puts pressure on ops tooling. Is that part of why we’re talking?” Notice what you skipped: the leadership page, the careers page essay, the blog. If a fact does not change your first five minutes, it does not earn time in this block.

Minutes 2-5: the people on the invite

Minutes two through five go to the humans, because people buy, companies do not. For each attendee, you want exactly three things: current title and scope, tenure in the role, and one recent signal, a post, a job change, a shared connection. Cap yourself at 90 seconds per person.

Dana Okafor: VP of Operations, 14 months in role, previously a director at a larger 3PL. She posted three weeks ago about “the hidden cost of manual dock scheduling.” That post is gold; it tells you the pain in her own words.

The mystery second attendee resolves to Priya Shah, Senior Manager of IT. Her presence on a first call usually means security and integration questions will come early. Note it and move on. Do not read either person’s full activity feed. Tenure plus one signal is the extraction target; everything else is curiosity dressed up as diligence. If you want the exhaustive version of what is worth gathering, keep a full pre-call research checklist bookmarked for high-stakes calls, and resist using it for routine ones.

Minutes 5-7: org context and likely decision path

This block answers: who else will touch this decision? You are not building a complete org chart in two minutes. You are forming a hypothesis about the buying committee that you will test on the call itself.

Check the LinkedIn company page for headcount and the rough size of the relevant department. Search for Dana’s likely boss: at a 400-person company, a VP of Operations probably reports to a COO or directly to the CEO. Meridian has a COO, Marcus Lin, who joined eight months ago. New executive plus new hub equals someone with a mandate to fix things, which is very good news for you.

So the hypothesis: Dana is the champion, Marcus is the economic buyer, Priya owns technical sign-off. Write it down as a question to validate, not a fact. Getting this map right early is the difference between a deal that moves and one that dies in “let me check with my boss.” A proper stakeholder mapping approach takes this much further, but on a 10-minute budget, a three-name hypothesis is the deliverable.

Minutes 7-9: triggers, timing, and why now

Minutes seven through nine hunt for the trigger: the event that made this company take a meeting this month instead of last year. Triggers cluster into a few types: funding, leadership changes, expansion, hiring spikes, regulatory pressure, and public incidents. You usually only need to find one.

For Meridian, you already have two from earlier blocks: the Reno hub and the new COO. A 60-second scan of their open roles adds a third: they are hiring four dispatch coordinators, which suggests volume is outrunning their current process. You do not need a fourth.

Triggers matter because they convert your questions from generic to specific. “What are your priorities this year?” is a question anyone could ask. “You’re adding a third hub and four dispatchers at the same time. What breaks first if nothing changes?” is a question only a prepared rep can ask. RAIN Group’s buyer research finds that 96% of buyers say a seller’s focus on the value they can deliver influences their purchase decision; you cannot speak to value until you know why now.

Minutes 9-10: write your three talking points

The final minute converts research into something usable mid-call, because findings you cannot retrieve under pressure might as well not exist. Write exactly three lines, each one a fact plus the question it sets up. Keep them visible during the call.

For the Meridian call:

1. Reno hub, four months old. “Is the new hub what’s stressing the current scheduling process?”
2. Dana’s post on manual dock scheduling. “You wrote about hidden costs of manual scheduling. What prompted that?”
3. New COO, eight months in. “Is Marcus driving an ops overhaul, and how does this fit his priorities?”

Three is the limit. Five talking points means you will be reading notes instead of listening. One means a single thread that can dead-end. Three gives you an opener, a pain probe, and a decision-path probe, which is the skeleton of a good discovery call.

What should you do with 60 seconds, not 10 minutes?

When a call gets dropped on your calendar with no warning, run the 60-second version: one look at the company homepage hero, one look at the primary attendee’s LinkedIn headline and tenure, and one honest opening line. That is genuinely enough to avoid the worst outcome, which is opening with “so, tell me about Meridian.”

The 60-second hierarchy, in order, dropping from the bottom as time runs out:

1. What the company sells, in one sentence
2. Your contact’s title and tenure
3. One recent company event

And the honest opener works better than reps expect: “This came together quickly, so I did a fast pass on Meridian rather than my usual prep. Can I ask you to fill in the gaps?” Buyers forgive limited research. They do not forgive pretended research.

When the routine becomes automatic

After a few weeks, the 10-minute routine stops feeling like a checklist and starts feeling like instinct. The next bottleneck is volume: running it well at 9 a.m. is easy, running it well before your sixth call of the day is not. That is the problem we are building Almanac to solve. It assembles the same brief this routine produces by hand: who is on the call and their roles and tenure, recent company news, a map of the likely buying committee, how the prospect found you, with your own talk tracks preloaded, so the ten minutes you do spend goes to thinking rather than tab-switching. The routine teaches you what a good brief looks like; the tooling keeps the standard from slipping on busy days.

FAQ

How long should pre-call research take?

Ten minutes for a standard discovery or first call, with a hard stop. Reserve 30 to 45 minutes for late-stage calls with executives or multi-stakeholder demos where the stakes justify it. The biggest gains come from doing consistent light research on every call, not deep research on a few.

What is the single most important thing to research before a sales call?

The trigger: the recent event that explains why this company is taking meetings now. Funding, a new executive, an expansion, or a hiring spike will shape your questions more than any product or company fact. If you can only find one thing, find that.

Should I research every attendee on the call invite?

Yes, briefly. Ninety seconds per person gets you title, tenure, and one recent signal, which is enough to address each person credibly. An unexpected attendee’s role often predicts the call’s direction, like an IT manager signaling early security questions, so never skip the names you do not recognize.

What should I skip when researching a prospect?

Skip annual report deep dives, press releases older than six months, the prospect’s full LinkedIn history, and Glassdoor reviews. Apply one test to every source: could this fact change what I say in the first five minutes of the call? If not, close the tab.