The Pre-Meeting Prep Checklist: 40 Items Top Reps Run Before Every Sales Call

Most call prep advice says “do your research” and stops. This is the actual system: 40 items in seven blocks, run in order, with a paragraph on each covering why it earns its place and how to do it fast. Skim the block headers if you know your gaps; read the items numbered 1-5 and 19-22 even if you skim everything else, because those are the blocks that decide calls.

TL;DR

• Seven blocks, run in order: objective (1-5), company context (6-12), attendee intel (13-18), landmines (19-22), objections (23-27), materials (28-33), tech (34-40).
• Start from the objective, not the research. Items 1-5 determine what research even matters.
• The most-skipped block is landmines (19-22): what NOT to bring up.
• Blocks 2-4 are now a two-minute AI job. Prep time should go to the thinking blocks.

Block 1: Define the call (items 1-5)

Everything else on this list serves these five answers. Reps who research first and think second end up knowing the company’s funding history and not knowing why they booked the meeting.

1. Write down the one thing you must learn

Every call has one question that matters more than the rest: is the pain real, who actually decides, why now. Name it before you research anything, because it determines what research is even relevant.

The test: if the call ran ten minutes instead of thirty, what would you refuse to leave without? That is your one thing.

Where to find it: Your CRM notes and the deal’s framework gaps (which MEDDIC letters are blank).

How it sounds live: If pressed for time, ask it straight: “Before we run out of time, the one thing I need to understand is how this decision gets made. Can we spend five minutes there?”

2. Decide the next step you will propose

Not ‘we’ll follow up.’ A specific, dated, owned next step: a technical review Thursday with their ops lead, a pilot scoped by Friday. You can adjust it live, but a call that ends without a proposed next step ends the deal’s momentum by default.

Write it as a sentence you could actually say. If it sounds presumptuous when spoken, soften the phrasing, not the specificity.

Where to find it: Your own pipeline playbook: what the next stage requires (technical review, pilot scope, exec intro).

How it sounds live: “Based on what we covered, the logical next step is a 30-minute technical review with your ops lead. Does Thursday work?”

3. Define what would disqualify this deal

The most profitable prep item on this list, and the least done. If they have two seats, no problem you solve, or a contract locked through 2028, what answer tells you to stop? Deciding this beforehand is the only defense against happy ears.

Disqualification is not failure; it is the 80/20 rule doing its job. An hour returned from a dead deal is an hour for a live one.

Where to find it: Your ICP definition and closed-lost analysis: the patterns that never close.

How it sounds live: Expect to ask, not face: “If the answer to [X] is no, this probably isn’t a fit. Can I ask it anyway?” Buyers respect a rep willing to disqualify.

4. List the questions that must get asked

Three to five, written, in priority order, so that if the buyer talks for twenty minutes (a good problem), the essentials still land. Pull from your framework’s gaps: which MEDDIC letters are still blank on this deal?

Our discovery questions guide has the menu; pick for this buyer, don’t recite.

Where to find it: Your discovery question bank, filtered by this deal’s unknowns.

How it sounds live: Prioritize aloud: “I have three things I need to understand today: the pain, the process, and the timeline. Where do you want to start?”

5. Picture the day after

If the call goes perfectly, what happens tomorrow: who do they talk to internally, what do they need in hand, what will they be asked? Prepping for the buyer’s next 24 hours is how you show up with the thing their boss will want.

This one question generates most of your materials list (block 6) automatically.

Where to find it: Ask your champion directly, or infer from org structure: who reviews decisions like this.

How it sounds live: “After this call, who do you need to bring this to, and what will they ask you?” The answer is your materials list.

Block 2: Company context (items 6-12)

The goal is not knowing everything; it is knowing what changed recently and what it means for the conversation. This block plus blocks 3 and 4 is the part AI now does in two minutes; more on that at the end.

6. Pull the last 90 days of news

Funding, acquisitions, leadership changes, product launches, expansions, layoffs, earnings commentary. Organize by recency; the newest event is usually your opener and your urgency case.

A 90-day window is deliberate: older news is context, newer news is a reason you called this week.

Where to find it: Google News on the company name, their press page, Crunchbase for funding; or one deep-research run pulls all of it.

How it sounds live: “Congrats on the Series B. Usually that means pipeline targets just doubled. Has that hit your team yet?”

7. Read the careers page before the press page

Hiring tells you strategy before the announcement does. Five SDR openings means pipeline pressure; three RevOps roles means tooling consolidation is coming; a hiring freeze changes your whole cost framing.

Note the specific roles and locations; ‘I saw you’re hiring eight sellers in Austin’ is research, ‘I see you’re growing’ is filler.

Where to find it: Their careers page, LinkedIn jobs tab, hiring announcements.

How it sounds live: “I saw you’re hiring eight sellers in Austin. New reps ramping is exactly when [problem] gets expensive. Who owns that today?”

8. Size the company honestly

Headcount, growth trajectory, revenue band if public. Not for trivia: your pricing story, proof points, and rollout pitch all change between a 50-person team and a 5,000-person org, and using the wrong one reads as not having looked.

Where to find it: LinkedIn company page for headcount and growth %, filings for revenue if public, funding databases if private.

How it sounds live: Expect: “We’re only 60 people, is this built for us?” Your sizing research decides whether your answer is honest.

9. Map their competitive position

Who is beating them and who they are beating. A challenger fighting an incumbent buys differently (speed, edge) than a leader defending share (risk, scale). One search on their category plus reading their own positioning page usually suffices.

Where to find it: Their homepage vs competitors’ (G2 category pages show the field), analyst coverage if enterprise.

How it sounds live: “Most teams in your category are chasing [leader] on [dimension]. Is that the fight you’re in, or is it different from inside?”

10. Check the tech stack you’d touch

What do they run in your category and adjacent to it? Integration questions come up in the first call more often than pricing does, and ‘does it work with our stack’ answered instantly is credibility banked.

Stack data also times the deal: knowing their current contract’s typical cycle tells you whether this is a now-conversation or a renewal-window conversation.

Where to find it: Job postings mention stack; company case studies name vendors.

How it sounds live: Expect: “Does this work with our HubSpot instance?” Answering in one sentence, with the integration named, is credibility banked.

11. Find the fiscal calendar

Budget cycles decide timing objections before you hear them. A public company’s fiscal year is in every filing; a private one’s often shows in when they post finance roles. Pitching a Q4 spend in their Q1 is self-inflicted.

Where to find it: Public companies: any filing. Private: when they post finance/accounting roles, or simply ask.

How it sounds live: “When does your fiscal year close? I want to time this so budget exists rather than pitching into a freeze.”

12. Read what the CEO keeps repeating

Earnings calls, all-hands recaps, founder posts: the phrase leadership repeats is the company’s actual priority, and your pitch either connects to it or competes with it. Quote it back and you are speaking the language their boss uses.

Where to find it: Earnings call transcripts (public), founder’s LinkedIn posts, company all-hands recaps in blog form.

How it sounds live: “Your CEO mentioned [priority] three times last quarter. Does your team carry a piece of that number?”

Block 3: Attendee intel (items 13-18)

Companies do not take meetings; people do. Every item here is about the specific humans on the invite.

13. Learn to say their name

Two seconds on pronunciation (LinkedIn name audio, a company video) signals more care than a paragraph of flattery. Getting it wrong in second one is recoverable but expensive.

Where to find it: LinkedIn name-pronunciation audio, any conference video, or their team page video.

How it sounds live: Nothing to say; everything not to get wrong in the first second.

14. Map role, tenure, and trajectory

How long in this seat, and where before? A six-month VP is building their case and wants wins; a six-year VP is protecting what works and wants risk removed. Same title, opposite pitches.

Where to find it: LinkedIn profile: current tenure and the two roles before it.

How it sounds live: A 6-month VP: “What did you inherit, and what’s the first thing you want to put your name on?” A 6-year VP: “What’s working that you refuse to let a new tool break?”

15. Work out what they are measured on

Every buyer has a number, and your product either moves it or is a distraction. If you cannot infer it from the role, asking is a great discovery question; guessing wrong in your pitch is not.

This is the item that turns feature talk into outcome talk automatically: features map to your product, measurements map to them.

Where to find it: Role norms (VPs carry pipeline coverage, RevOps carries data quality), their job posting if recent, or ask.

How it sounds live: “Let me check an assumption: you’re measured on sourced pipeline, not just closed revenue, right?” Wrong guesses in the pitch are expensive; this question is free.

16. Read what they have written

Their last three LinkedIn posts, a podcast appearance, a conference bio. Their own words beat your assumptions about tone, priorities, and vocabulary, and referencing them honestly is the strongest personalization there is.

Where to find it: Their LinkedIn activity tab, podcast appearances, conference bios.

How it sounds live: “You wrote last month that [claim]. Does that hold for [your category] too?” Referencing their words honestly is the strongest opener available.

17. Guess the champion and the skeptic

On multi-attendee calls, someone wanted this meeting and someone got dragged. Form a hypothesis from roles and behavior, test it early: the champion needs ammunition, the skeptic needs their objection heard first, and addressing each with the other’s script loses both.

Where to find it: Who booked the meeting (usually the champion), title mix, who spoke first in scheduling emails.

How it sounds live: Give the champion ammunition: “What would make you look right for bringing us in?” Give the skeptic the floor: “You look unconvinced, what am I missing?”

18. Notice who is missing

The invite list tells you where the deal actually is. No economic buyer at a late-stage call, or ops missing from a demo they would live in, is a signal to address (‘should we include X next time?’) rather than a detail to shrug at.

Where to find it: Compare the invite list against how this company’s deals usually decide (your CRM history with similar logos).

How it sounds live: “For a decision like this, most teams loop in [role] around now. Should we include yours next time?”

Block 4: Landmines (items 19-22)

The block everyone skips, and the one that saves calls. Five minutes of what-not-to-say research prevents the moment that makes everyone stare at their shoes.

19. Check for layoffs and reorgs

Congratulating growth that ended two months ago, or pitching expansion tooling to a team that just cut 15%, is instantly disqualifying. If there were layoffs, your framing shifts to efficiency and consolidation, and your tone drops a register.

Where to find it: News search + LinkedIn (departure posts cluster), layoffs trackers for tech.

How it sounds live: If there were cuts, open lower: “I know the last quarter was rough. I’ll keep this focused on doing more with the team you have.”

20. Scan for bad press and public failures

A security incident, a bungled launch, a viral complaint thread. You do not have to mention it; you have to not walk into it. If your product touches the sore spot, decide beforehand whether to name it carefully or route around it.

Where to find it: News search on company + ‘breach/lawsuit/recall’, their category’s trade press.

How it sounds live: Nothing to say unprompted. Decide beforehand: if THEY raise it, acknowledge briefly and move; never pretend you didn’t know.

21. Find the failed attempt in your category

If they tried a tool like yours and it died, your pitch lands on scar tissue. Better to surface it yourself: ‘lots of teams tried X in 2024 and got burned; what happened here?’ turns the landmine into your best discovery question.

Where to find it: Ask your champion pre-call, check their stack history, or listen for scar tissue in early answers.

How it sounds live: “A lot of teams tried [category] in 2024 and got burned. What happened here?” The landmine becomes your best discovery question.

22. Check your own company’s history with them

The CRM knows about the lost deal from 2024, the support escalation, the rep who ghosted them. Walking in unaware of your own history is the least forgivable version of unprepared, and it takes ninety seconds to check.

Where to find it: Your own CRM: search the domain, not just the contact.

How it sounds live: Expect: “We actually looked at you two years ago.” Being ready with “I know, and two things have changed since” beats visible surprise.

Block 5: Objection prep (items 23-27)

23. Prepare for this profile’s top three objections

Not all hundred, the three this persona actually raises: CFOs lead with price, ops leads with migration pain, IT with security. Write one honest response each. Our objections field guide sorts them by bucket so this takes five minutes.

Where to find it: Your objections field guide filtered by persona; your team’s call transcripts for what this profile actually says.

How it sounds live: CFO: “What does this cost, all-in?” Ops: “What breaks during migration?” IT: “Where does our data live?” One rehearsed honest answer each.

24. Ready your competitor story

If they name the incumbent or a rival, you need a comparison that respects the competitor and still wins: what you do differently, for whom, with proof. Trash talk loses even when it is accurate.

Where to find it: G2 comparison pages, your battle cards, win/loss notes against that competitor.

How it sounds live: Expect: “How are you different from [incumbent]?” Respect them, then differentiate: “They’re strong at X. Teams pick us when Y matters more.”

25. Decide your pricing posture

Price comes up early more often than not. Decide beforehand: do you give a range, anchor to value first, or defer with a reason? The worst version is improvising evasion, which reads as either hiding something or not knowing your own product.

Where to find it: Your pricing page and your own discounting authority; decide the posture, not just the number.

How it sounds live: Expect: “Ballpark cost?” in minute five. Decide now whether you range (“teams your size land between X and Y”) or anchor to value first.

26. Load one proof point that matches them

The reference that is their size, their industry, their stack. One close-match story beats five famous logos, and ‘a 200-person fintech like you’ does more than your biggest brand name.

Where to find it: Your case-study library filtered by size + industry; ask CS which reference is freshest.

How it sounds live: “A 200-person fintech, basically your shape, saw [number] in [timeline]. Want me to intro you to them?”

27. Rehearse the hard sixty seconds

The opening and the toughest expected objection: say both aloud once, or run them against an AI playing the skeptic (the roleplay setup). Rehearsed reps sound calm; calm reads as competence.

Where to find it: An AI roleplay session, or a colleague with five minutes.

How it sounds live: Have Claude play the skeptical CFO: “Push back on price twice and question our size once.” Two rounds and the real call feels slower.

Block 6: Materials and follow-through (items 28-33)

28. Have the case study ready to send, not summarize

Sharing the actual asset in the call (‘sending it to you now’) converts interest at its peak instead of promising it into the follow-up void.

Where to find it: Your content library; have the file open, not bookmarked.

How it sounds live: “Rather than describe it, I’m sending it to you right now.” Interest converts at its peak, not in the follow-up.

29. Pre-load the ROI math

Reasonable assumptions for their size, editable live with their real numbers. A calculation the buyer co-edits becomes their argument, not yours; that is the whole trick of the internal sale.

Where to find it: Your ROI template plus their numbers from items 8 and 15.

How it sounds live: “Let’s plug in your real numbers.” A calculation the buyer co-edits becomes their internal argument, not your claim.

30. Draft the follow-up email before the call

Eighty percent of it is predictable: recap structure, the promised asset, the proposed next step. Drafting it beforehand means it sends within an hour of the call ending, while the meeting is still warm on their calendar.

Where to find it: Your last five follow-up emails; the structure repeats.

How it sounds live: Send within the hour: recap in their words, the promised asset, the dated next step. Speed here is remembered.

31. Open the CRM record and actually read it

Every prior touch, note, and email thread. Asking a question the record already answers tells the buyer your company forgets them between meetings.

Where to find it: The CRM record: every note, thread, and prior touch on the account.

How it sounds live: Never ask what the record answers. “Last March you told our team X, is that still true?” shows the company remembers them.

32. Identify which fields you must fill

Know the three CRM fields this call must populate (stage evidence, next step, new stakeholders) so capture happens during, not from memory on Friday. Better: let the transcript do it (the workflow).

Where to find it: Your CRM’s required fields per stage; know the three this call must fill.

How it sounds live: Post-call, the transcript can propose the update and you approve the diff; the workflow is in our Claude + CRM guide.

33. Prepare the leave-behind for the absent audience

Whatever you show will be forwarded to someone who was not in the room. Make sure the deck or one-pager argues your case without narration; the internal sale happens in your absence.

Where to find it: Whatever you plan to show, reviewed with one question: does it argue without me?

How it sounds live: Expect, silently: your deck being forwarded tonight to someone you never met. Write the annotations for them.

Block 7: The tech check (items 34-40)

34. Test video, audio, and network

Two minutes, every time, no exceptions. The rep debugging their microphone during minute one has spent their credibility before speaking.

Where to find it: Your own hardware, two minutes before.

How it sounds live: The rep debugging a mic in minute one has spent credibility before speaking.

35. Plan the recording ask

Decide whether you are recording, know the consent line, and say it comfortably. The transcript feeds your notes, your CRM update, and your post-call analysis; fumbling the ask costs all three.

Where to find it: Your recorder’s consent flow and your region’s rules.

How it sounds live: “I’d like to record so I’m not scribbling while you talk, and you’ll get the recap. OK?” Comfortable ask, near-universal yes.

36. Arrange the second monitor

Notes, CRM, and battle card on one screen; the buyer and shared content on the other. Reading from the same screen you present on is how reps end up sharing their notes.

Where to find it: Second screen: notes, CRM, battle card. Presenting screen: them and the content.

How it sounds live: No line; the alternative is sharing your notes with the room.

37. Curate your tabs

Open what you will share, close what you will not. The moment of screen-share honesty has ended deals; treat your browser like part of the deck.

Where to find it: Your browser, 60 seconds before.

How it sounds live: Close the other prospect’s tab. Screen-share honesty has ended deals.

38. Send the 24-hour confirmation

One line, their agenda, not yours: ‘Tomorrow at 2, we’ll dig into the pipeline-visibility problem you mentioned and I’ll bring the benchmark for your segment.’ This is the single highest-leverage no-show reducer that exists.

Where to find it: Your calendar tool’s reminder, but written by you, in their terms.

How it sounds live: “Tomorrow at 2: the pipeline-visibility problem you mentioned, plus the benchmark for your segment.” Highest-leverage no-show reducer that exists.

39. Re-check the calendar mechanics

Right time zone, working link, correct attendees. Boring, and the number-two cause of no-shows after ‘no reason to show up.’

Where to find it: The invite itself: time zone, link, attendees.

How it sounds live: Boring, and the number-two cause of no-shows after “no reason to show up.”

40. Take ninety seconds of silence

Before joining: what is the one thing (item 1), what is the proposed next step (item 2), what does this person care about (item 15). Reps who join settled run calls; reps who join mid-scramble attend them.

Where to find it: Nothing. Ninety seconds and a closed door.

How it sounds live: Join settled: the one thing, the next step, what this person cares about. Reps who join mid-scramble attend calls; settled reps run them.

The two-minute version of blocks 2-4

Items 6 through 22 used to be twenty minutes of tab-hopping per meeting, which is why nobody did them daily. They are now one research run: point an AI workflow at the account and attendee and get the news, hiring signals, background, and landmines in a single brief. Salesgear’s deep research does this per prospect across 100+ sources with verified contact data underneath; to run it in Claude instead, use the four-prompt chain in our role-by-role guide, or schedule it for every meeting on tomorrow’s calendar with Claude Cowork.

Automating the middle blocks is not about saving fifteen minutes. It is that the saved minutes move to items 1-5 and 23-27, the thinking blocks, and those are the ones that close.

Frequently asked questions