Prospect Research Cheat Sheet: What to Find Before You Dial
A role-by-role lookup table telling reps exactly what to research before a cold call, where to find it in under 90 seconds, and how to turn each finding into a specific opener. Includes a hard 4-minute research cap and named failure modes so reps stop over-preparing or winging it blind.
How to use it
Before each call block, pick the prospect's role from the lookup table, run only the listed checks in the order shown, and stop at four minutes regardless of what you still want to find. Use the opener templates the moment the call connects, then move into your pitch. Review the failure-mode flags at the bottom of the sheet if your dial rate or connect quality is consistently low.
What's inside
- Hard 4-minute research cap rule with the reasoning behind it
- Role-by-role lookup table covering five common prospect seniority levels
- Must-have vs nice-to-have data point classification for each role
- Named source for every data point with a realistic time estimate
- Word-for-word opener templates tied directly to each finding type
- Trigger event categories with a conversion note for each
- Two named failure modes: the over-researcher and the under-researcher
- A pre-dial checklist to run in the final 30 seconds before you ring
- When NOT to use this cheat sheet note for edge cases
The One Rule That Governs Everything
Cap pre-call research at 4 minutes per contact. Set a timer.
Not because research does not matter. Because beyond four minutes you are no longer preparing, you are procrastinating. The return on research time drops sharply after the first two minutes. The last two minutes exist only to catch a live trigger event or a glaring red flag. After four minutes, dial.
Two Failure Modes to Avoid
The over-researcher spends eight minutes per contact, builds a perfect dossier, and dials 40% fewer people than the target. Their calls are well-informed but rare. Pipeline suffers.
The under-researcher dials cold with a generic opener ("I wanted to reach out about your sales process…"), gets dismissed in ten seconds, and blames the list. Their volume is fine. Their connect rate is not.
This sheet solves both. You get enough to sound relevant in the first 30 seconds. You do not get a research rabbit hole.
Must-Have vs Nice-to-Have
Before the role table: every data point in this sheet is labelled M (must-have, find it every time) or N (nice-to-have, grab it if it surfaces in the first pass).
If you hit four minutes before you have finished the M items, dial anyway. An incomplete must-have list still beats a perfect nice-to-have list.
Role-by-Role Lookup Table
| Prospect Role | Must-Have (M) | Nice-to-Have (N) | Where to Find It | Time Budget |
|---|---|---|---|---|
| C-Suite / Owner | Recent public statement (earnings, press quote, LinkedIn post) | Board composition changes | LinkedIn activity tab, Google News ("[name] + [company]") | 90 sec |
| C-Suite / Owner | One strategic priority visible in the last 90 days | Acquisition or funding news | Company newsroom, LinkedIn company page | 60 sec |
| VP / Director | Their team's reported headcount or recent hires | Their tenure in role | LinkedIn "People" tab on company page, LinkedIn profile | 60 sec |
| VP / Director | A department-level initiative or job posting in their function | Awards or recognition | LinkedIn Jobs filtered by department, Google ("[company] + [function] + hiring") | 60 sec |
| Manager / Team Lead | A tool or system named on their profile or in job ads | Personal content they've published | LinkedIn profile skills section, job postings for their team | 45 sec |
| Manager / Team Lead | A pain point implied by their team's current vacancies | Recent career move | LinkedIn Jobs, LinkedIn profile | 45 sec |
| Individual Contributor (economic buyer unlikely) | Confirm they are not the buyer before spending further time | Their manager's name | LinkedIn, company website org chart | 30 sec |
| Procurement / Finance | Current vendor contracts visible (tech stack tools) | Budget cycle timing | BuiltWith, LinkedIn profile, Crunchbase | 60 sec |
Trigger Events: What to Look For and How to Use It
A trigger event is a recent change that creates a reason for your call to land now rather than in three months. You need one. If you cannot find one in 90 seconds, proceed without it and use a role-based hook instead.
| Trigger Event | Where to Find It | Time to Find | Opener Hook |
|---|---|---|---|
| New hire in a relevant role | LinkedIn "People" filtered by date joined | 30 sec | "I saw you've just brought on a [role], which typically means [relevant pain] becomes more pressing…" |
| Funding round announced | Crunchbase, TechCrunch, LinkedIn company page | 30 sec | "Congratulations on the Series B. Companies at that stage often find [specific challenge] starts to bite…" |
| Headcount growth (10%+ in 90 days) | LinkedIn company page, Crunchbase headcount graph | 45 sec | "Your team looks like it's grown significantly this quarter. That kind of growth usually creates [specific friction]…" |
| Leadership change (new CEO/VP) | LinkedIn, Google News | 30 sec | "You've recently had a new [title] come on board. New leaders usually review [relevant area] in the first 90 days…" |
| Technology change (dropped or added a tool) | BuiltWith, LinkedIn job ads listing required tools | 45 sec | "I noticed you're now running [tool]. A lot of teams that make that switch hit [specific issue] shortly after…" |
| Job posting for a role you help reduce/replace | LinkedIn Jobs, Indeed | 30 sec | "I spotted you're hiring a [role]. Sometimes that hire can be avoided entirely with [brief value point]…" |
| Recent press coverage (product launch, award) | Google News, company newsroom | 30 sec | "I read about your [launch/award]. The teams we work with at that stage usually have [relevant challenge] at the top of the list…" |
Pre-Dial 30-Second Checklist
Run this in the 30 seconds before you ring. Do not answer the phone or check email during this window.
- I know their title and what their function is responsible for
- I have one M-level data point confirmed
- I have a trigger event OR a role-based relevance hook ready
- I know the specific opener I am leading with (written or spoken aloud once)
- I know what I am asking for at the end of the call (meeting, next step, referral to right contact)
If you cannot tick the first three, you have under-prepared. Revisit the table above quickly. If your timer says four minutes, dial anyway and use a role-based hook.
Opener Templates by Finding Type
Copy these. Fill in the brackets. Do not improvise around them until you have used each one at least 20 times.
Trigger event (any): "Hi [name], it's [your name] at [company]. I'll be brief. I noticed [specific trigger event] and it made me think of a challenge that tends to come up at exactly this point for [role/function]. Worth 90 seconds to see if it's relevant?"
No trigger event, role-based hook: "Hi [name], it's [your name] at [company]. I work specifically with [role/function] teams at [company size/sector]. One thing that comes up almost universally at this stage is [specific, credible pain point]. Is that on your radar at all?"
Recent hire or headcount growth: "Hi [name], it's [your name] at [company]. I saw your [function] team has been growing. When teams scale that quickly, [specific problem] usually surfaces. I wanted to ask whether that's something you're already across, or whether it's worth a quick conversation."
Tech stack signal: "Hi [name], it's [your name] at [company]. I could see you're running [tool]. A lot of [function] teams using that setup find [specific friction point] becomes harder to manage past a certain scale. Is that something you're dealing with?"
When NOT to Use This Sheet
This sheet is built for cold and low-familiarity outreach. Do not use it for:
- Accounts you have already spoken to in the last 30 days. You should have notes. Use them instead.
- Inbound leads who have filled in a form. They have told you what matters. Read the form.
- Re-engagement of a lapsed opportunity. You need deal history, not prospect research.
- Warm introductions. The person who introduced you is your primary intel source. Call them first.
Quick-Reference: Sources by Time Cost
| Source | What It Gives You | Typical Time Cost |
|---|---|---|
| LinkedIn profile (activity tab) | Recent posts, career history, skills | 45-60 sec |
| LinkedIn company page (people tab) | Team size, recent hires, structure | 30-45 sec |
| LinkedIn Jobs | Open roles, implied pain, tech stack | 30-45 sec |
| Google News ("[name]" or "[company]") | Press coverage, quotes, announcements | 30 sec |
| Crunchbase | Funding, headcount trend, investors | 30-45 sec |
| BuiltWith | Current and historical tech stack | 20-30 sec |
| Company newsroom | Product launches, partnerships, hires | 30 sec |
Total if you run every source: roughly 5-6 minutes. You do not run every source. You run the ones the role table points you to, and you stop at four minutes.