Anatolii Lavryk

Posted on Jun 10

The 5-Minute Pre-Call Routine: How Top SDRs Prep for Discovery

#ai #sales #marketing #agents

The Call Is Won or Lost Before It Starts

Most SDRs treat pre-call prep as optional - something to do if there is time, skipped entirely during a busy block session. That choice is visible on the call. The rep who opens with a generic pitch and stumbles when the prospect asks why they reached out specifically is the rep who did not prep. The rep who references something specific, earns the prospect’s attention in the first thirty seconds, and stays composed when the conversation goes off script - that rep spent five minutes before the call doing something the other rep did not.

The gap between a prepared rep and an unprepared one is not experience. It is process. Top SDRs do not prep better because they are more talented - they prep better because they have a repeatable routine that takes exactly five minutes and leaves them with three specific things to use on the call.

This guide gives you that routine. Five steps, timed, with a checklist for each. A pre-call planning template you can use immediately. And the AI shortcut that the best reps are increasingly using to compress each step without cutting corners.
“Sellers who use AI tools to prepare for calls are 3.7x more likely to hit quota than those who don’t.” - HubSpot State of Sales, 2026

Why Five Minutes - Not Fifteen, Not Thirty

Sales enablement managers consistently overestimate how much pre-call research reps will actually do. A thirty-minute prep requirement gets skipped entirely when a rep has twenty calls to make in a day. A five-minute routine gets done.

The second reason is diminishing returns. The information that moves a discovery call is almost always found in the first three to four minutes of research. Spending twenty minutes on the same prospect rarely surfaces anything materially more useful than what you found in the first five. The marginal value of additional research is low. The marginal value of another call in the day is high.

Five minutes, done consistently across every call in the day, outperforms twenty minutes done on some calls and zero on others. Consistency beats thoroughness at volume.

Prep Time	Information Found	Rep Compliance Rate	Net Value
0 minutes	None - generic pitch, no personalisation	100% (it requires nothing)	Low - prospect hears a template
5 minutes	Trigger, pain signal, relevant proof point	High - sustainable at volume	High - targeted, specific, earns attention
15 minutes	Deeper context, more company background	Medium - gets skipped in busy sessions	Moderate - marginal improvement over 5 min
30+ minutes	Deep research, but often unused on the call	Low - unsustainable at scale	Low net — effort exceeds return

The 5-Minute Pre-Call Routine: Step by Step

Each step has a hard time limit. The discipline of the routine is keeping each step within its window - not letting step one expand into ten minutes of LinkedIn browsing. Set a timer if you need to.

0:00-1:00 (60 seconds)

Step 1: Find the One Trigger

What to do: Scan for one recent, verifiable event that explains why you are calling this specific person today. Not their job title. Not that they fit your ICP. A trigger: something that happened recently that creates a natural reason to reach out. Check LinkedIn activity, the company’s news page, recent funding announcements, new job postings, or a leadership change.

The output: One sentence: ‘I’m calling because [specific trigger] happened at [company], which usually means [relevant implication for them].’

Example: The company posted three SDR Manager roles last week. That suggests they are scaling the sales team fast, which usually means ramp time and consistency are on somebody’s priority list right now.

AI shortcut: A real-time AI copilot configured with intent data signals can surface trigger events automatically before the call - job postings, funding rounds, leadership changes - so the rep spends 30 seconds confirming the trigger rather than searching for it.

STEP 1 CHECKLIST
- One specific trigger identified (funding, hiring, product launch, leadership change, competitor
    win/loss, recent content they published)
- Trigger is verifiable - not an assumption, a fact
- One-sentence 'reason for calling today' drafted

Step 2: Form One Pain Hypothesis

What to do: Based on the trigger, the prospect’s role, and your ICP knowledge, form a single hypothesis about the most likely pain they are feeling right now. This is not research - it is inference. You are not trying to be certain; you are trying to have a specific starting point that you can test in the first two minutes of the call. A specific wrong hypothesis is more useful than a vague right one, because it creates a conversation.

The output: One sentence: ‘My hypothesis is that [specific person] is probably dealing with [specific pain] because [the trigger I found].’

Example: A VP of Sales at a company hiring three SDR managers is probably dealing with ramp time new hires taking too long to produce, or wide variance between what different managers are coaching. That is the hypothesis. The call will test it.

AI shortcut: If you have called this company before or spoken to someone at this account, a real-time AI copilot with call history indexed can surface the pain signals from past conversations in seconds - so the hypothesis is not inference but informed by what was already said.

STEP 2 CHECKLIST

One specific pain hypothesis formed - not ‘they might have problems with sales’ but ’they are probably dealing with X because $\mathrm{Y}^{\prime}$
Hypothesis is connected to the trigger from Step 1
Discovery question drafted to test the hypothesis in the first 90 seconds of the call

2:00-3:00 (60 seconds)

Step 3: Load One Relevant Proof Point

What to do: Identify one piece of evidence - a customer story, a specific result, a case study, a stat that is relevant to the pain hypothesis you just formed. Not your general pitch deck. The specific proof point that would be most credible to this specific person in this specific situation. If the hypothesis is wrong, you may not use it. But having it loaded means you are ready if the hypothesis turns out to be right.

The output: One sentence you can say if the pain hypothesis is confirmed: ‘The reason I’m reaching out is that we’ve helped [similar company] with exactly that - they went from [before] to [after] in [timeframe].’

Example: If the VP of Sales confirms the ramp time pain: ‘That’s exactly what we helped Ventairy with their new reps went from months of learning to executing on day one, and they cut their training cost by over $4,700 per rep per year. Happy to show you how it works.’

AI shortcut: A RAG-powered AI copilot can surface the most relevant case study for this specific prospect’s industry, company size, or pain type from the company’s knowledge base - in the moment the pain is confirmed on the call, not before it. This removes the need to pre-select the right proof point and eliminates the risk of leading with the wrong one.

STEP 3 CHECKLIST

One specific case study or result identified - not a general value prop
Proof point is relevant to the pain hypothesis, not just the product category
Story follows the before/after/timeframe structure
Know the source - be ready to elaborate if the prospect asks for more

3:00-4:00 (60 seconds)

Step 4: Anticipate the Most Likely First Objection

What to do: Based on the prospect’s role, company stage, and any prior context you have, identify the single most likely objection you will hear in the first three minutes. Is this a company that probably has a current vendor? A budget cycle that makes timing difficult? A seniority level that makes the ‘not my decision’ deflection likely? Pick one and have your response mentally loaded.

The output: The objection in one phrase and your opening response in one sentence. Not a full reframe - just the first move. The rest of the objection handling will depend on what actually happens in the conversation.

Example: A VP of Sales at a 40-person company is likely to say either ‘we already have something for that’ (Gong, Chorus, a homegrown tool) or ‘budget’s tight right now.’ For the first: ‘Makes sense - can I ask what you’re using and what gap prompted you to look at anything else?’ For the second: ‘I hear that a lot. Is it a budget question or a priority question - those are actually different problems?’

AI shortcut: This is exactly the step that a real-time AI copilot handles live during the call - surfacing the right objection response the moment the prospect says the triggering phrase, even if it is phrased differently than expected. Pre-loading one objection manually is useful; having every objection covered automatically is the AI copilot’s job.

STEP 4 CHECKLIST

Most likely first objection identified based on role and context

Opening response to that objection drafted - not a full script, one sentence
Fallback identified: if the call takes a different direction entirely, what is the minimum outcome you are trying to achieve?

4:00-5:00 (60 seconds)

Step 5: Set Your Opener and Your One Ask

What to do: Finalise the first line you will say after ‘is now a good time?’ - the line that anchors the call to the trigger you found in Step 1 and opens the pain hypothesis from Step 2. Then confirm the single outcome you want from this specific call. Not the eventual deal - the next micro-yes. A booked follow-up. A confirmed name of the actual decision-maker. An agreed next step. Know what you are asking for before the call starts.

The output: Your opener in one sentence and your ask in one sentence. Write both down. Saying them aloud once before dialling takes twenty seconds and makes a measurable difference to how naturally they come out when the prospect answers.

Example: Opener: ‘I noticed you’ve posted three SDR manager roles this week - that usually means you’re scaling fast, and ramp time becomes a real cost. Is that on your radar at all?’ Ask: If the call goes well, the ask is a 20-minute demo next week - not a commitment to buy, not a full technical walkthrough. One small yes.

AI shortcut: If you are running back-to-back calls, an AI copilot that summarises the previous call automatically means your next call’s ‘any prior context’ step takes ten seconds rather than digging through CRM notes. The routine stays at five minutes even when you are on call twelve of the day.

STEP 5 CHECKLIST
- Opening line finalised - trigger + implied pain in one sentence
- Opening line said aloud at least once before dialling
- Minimum outcome for this call defined - what is the one ask?
- Know how you will transition from opener to discovery question

The Pre-Call Planning Template: Master Checklist

Print or save this template. Fill it in for every discovery call. The discipline of writing the answers - not just thinking them - is the difference between preparation that survives the first objection and preparation that
evaporates when the prospect surprises you.

PRE-CALL PLANNING TEMPLATE

PROSPECT: Name, title, company, LinkedIn URL
TRIGGER: One specific, verifiable event that happened recently at their company

TRIGGER SOURCE: LinkedIn / company news / job postings / funding / other

PAIN HYPOTHESIS: The most likely pain this person is feeling right now, based on the trigger and their role
DISCOVERY QUESTION: The one question to test the hypothesis in the first 90 seconds
PROOF POINT: One specific customer story relevant to the hypothesis - [Company], [before], [after], [timeframe]
MOST LIKELY OBJECTION: The first pushback I am likely to hear
OPENING RESPONSE TO THAT OBJECTION: One sentence - not a full reframe, just the first move
OPENER: First sentence after ‘is now a good time?’ - trigger + implied pain
THE ONE ASK: The minimum outcome that makes this call a success
PRIOR CONTEXT: Any previous calls, emails, or notes from this account in the CRM
COMPETITOR CONTEXT: Are they likely to have a current vendor? Who?

Pre-Call Prep for Discovery vs. Cold Calls: The Difference

The five-step routine above applies to both, but with a different emphasis depending on the type of call. Discovery calls - where you have already earned a meeting - warrant slightly more time on steps 2 and 3 because the prospect has already self-identified with a problem. Cold calls require more emphasis on step 5 because the opener is doing more work.

Step	Cold Call Emphasis	Discovery Call Emphasis
Step 1: Trigger	Critical - justifies why you’re calling uninvited	Useful context - you already have the meeting; trigger colours your hypothesis
Step 2: Pain hypothesis	Framed as a question to earn engagement	Framed as an assumption to test slightly bolder because they agreed to talk
Step 3: Proof point	Hold in reserve - only use if hypothesis is confirmed	Load it prominently - you likely have longer to use it
Step 4: First objection	Critical — cold calls hit objections in the first 30 seconds	Lower priority - discovery calls have more runway before the first wall
Step 5: Opener and ask	The opener carries most of the weight refine it carefully	The ask is the priority - what is the next step from this meeting?

The AI Shortcut: Turning Pre-Call Prep Into In-Call Confidence

The five-step routine above makes you better prepared than most of the reps making calls today. The honest limitation is that preparation only covers the scenarios you anticipated. Real discovery calls do not follow the prep notes.

The prospect says something unexpected. A competitor is mentioned you did not load. The pain they confirm is not the one you hypothesised - it is adjacent, and the proof point you loaded does not quite fit. The objection they raise is a variant you have not heard phrased this way before.

This is the gap between a prepared rep and a truly confident one - and it is where a real-time AI sales copilot picks up where the pre-call routine leaves off.

Past call summaries surfaced automatically. If you have spoken to anyone at this account before, a copilot with call history indexed shows you the relevant context in seconds - no CRM digging required. The ‘prior context’ field in your pre-call template is populated for you.
Objection responses available live. The objection you loaded in step 4 is the most likely one. The copilot covers every objection - recognising what the prospect means even when they phrase it differently than your pre-call notes anticipated.
Proof points retrieved on confirmation. When the prospect confirms the pain, the copilot surfaces the most relevant case study from the knowledge base in real time - so you do not have to choose the right proof point before you know which pain they actually have.
Competitive intel live. When a current vendor is mentioned, the relevant battlecard surfaces immediately from your company’s own documentation - not from memory.
MEDDIC qualifying questions prompted at the right moment. The copilot tracks which qualification elements have been covered and surfaces the right question when the conversation opens a natural window - without the rep having to track it consciously.

The pre-call routine makes you ready for the call you planned. The AI copilot makes you ready for the call that actually happens. Both together is what top performers consistently do.
“Instead of spending months learning, I can execute immediately and rely on Convinco where needed, at a lower cost.” - Ryan Holanda, Commercial Representative, Ventairy Full case study: convinco.co/blog/ventairy-case-study

5 Pre-Call Prep Mistakes That Kill Discovery Calls

Mistake	What It Looks Like	The Fix
Over-researching at the expense of calling volume	Thirty-minute prep sessions that leave the rep with too little time for dials	Hard time cap: five minutes, no exceptions. More research does not equal more success at this stage.
Generic trigger (‘I saw you work in sales’)	Opening a cold call with a trigger so vague it applies to everyone	The trigger must be specific and verifiable: a recent event, not a permanent fact about the company or role.
Loading too many proof points	Rep memorises four case studies and uses none of them fluently	One proof point, perfectly relevant, delivered naturally beats four proof points delivered awkwardly.
Prepping the pitch instead of the discovery	Rep rehearses the product demo instead of the hypothesis and questions	Pre-call prep is for the first five minutes of the call, not the close. The goal is to earn ten more minutes, not to pitch in sixty seconds.
Skipping prep on follow-up calls	Assuming familiarity with a prospect means prep is not needed	Follow-up calls need prep for what has changed since the last call: new stakeholders, moved timelines, competitive activity.

Conclusion: Five Minutes Is a Competitive Advantage

Most reps are not doing this. The SDR who runs a consistent five-minute routine before every discovery call is not competing against a field of equally prepared peers - they are competing against people who dialled cold.

The routine is not complicated. One trigger. One hypothesis. One proof point. One anticipated objection. One opener, said aloud before dialling. Written down so it survives the moment the prospect says something unexpected. That is the whole thing.

And when the call goes somewhere the pre-call notes did not cover - which it will, regularly - that is the moment a real-time AI copilot becomes the rep’s best teammate.

See how Convinco supports live discovery calls - covering the moments five minutes of prep cannot anticipate. Book a demo: https://tally.so/r/eqYkZk View pricing: convinco.co/pricing Download the assistant: convinco.co/download SDR ramp-up plan: convinco.co/blog

DEV Community