Pharma · Cold Call
Pharma Cold Call Script: Getting Thirty Seconds With Clinical Ops and Field Medical Leaders
You are calling someone who is looking at an enrollment curve where the actual line diverged from the forecast line four months ago. They know the number: sites activated, sites randomizing, sites sitting at zero. They also know that the burn didn't pause while the curve flattened, and that the fix currently on the table is a protocol amendment to loosen I/E criteria — which means re-consent, another IRB cycle, and a quarter gone. That is the emotional weather when their phone rings with your unknown number on it.
Which means a pharma cold call has a very short window and a very specific pass condition. A VP, Clinical Operations or an Executive Director, Clinical Development is not going to be charmed into a meeting, and they are not going to be argued into one. They will give you a meeting if, in the first thirty seconds, you say something so specific about randomizations per site per month, screen failure rate, or site activation cycle time that they think: this person has seen my study before. Everything else — SOC 2, Part 11, your reference logos — is for the second call.
Use this script the way it's built: one buyer title, one trigger, one problem, one ask. Do not lead with your company. Do not run discovery. And when they reflex-fire "our CRO owns recruitment" or "anything touching HCPs is a six-week MLR queue," recognise those as the two most common brush-offs in this industry and answer them once, calmly, then re-ask for the calendar hold.
The cold call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial (90 seconds, out loud)
Say each of these out loud before the phone rings. If you can't, you're not ready to dial. 1. **Who is this?** Not "clinical leader." *"Maria Ochoa, VP Clinical Operations, in seat fourteen months, owns the Phase III program in cardiorenal plus two Phase II assets."* A Director, Field Medical (MSL Team Lead) gets a completely different call than a Head of Patient Recruitment & Site Engagement. 2. **What's the trigger?** A ClinicalTrials.gov record where sites were added but the estimated primary completion date moved. A protocol amendment posted. A hiring req for a Senior CRA or a Patient Recruitment Manager. A PDUFA date inside twelve months. An earnings call where someone said "enrollment headwinds." If there's genuinely no trigger, the indication is the trigger: *"every sponsor running a heart failure trial with an eGFR cut-off is fighting the same screen failure problem."* 3. **The one problem.** Written down, one sentence. Not enrollment *and* site burden *and* retention. 4. **The ask.** "Twenty-five minutes, Thursday 8:15 or Friday 4." Have the follow-up email drafted in a window before you dial, so you can send the invite while they're still on the line.
- 2
The opener (0–8 seconds)
Name → honest frame → permission → pause. > "Maria — it's Dan Reyes at Corvale. We haven't spoken, this is a cold call. Can I have thirty seconds to say why I rang, and you can tell me to get lost?" Then **stop talking for two full seconds.** Don't fill it. The silence is the ask. Variants: - *Pattern interrupt:* "Maria — Dan Reyes, Corvale. You don't know me. Bad time?" - *Trigger-led:* "Maria, Dan Reyes at Corvale. You've got three Senior CRA reqs open and the estimated completion date on the ATLAS-3 record moved out two quarters — that's actually why I called. Got a minute?" Downward inflection on "thirty seconds." Slower than feels natural. Match their energy within one notch — if they answer flat and clipped, do not come in bright.
- 3
The reason: problem, not product (8–45 seconds)
Who else → what they're dealing with → the operational consequence → check-in question that offers an out. No product name. **For VP, Clinical Operations / Executive Director, Clinical Development:** > "We work with sponsor ops teams on enrollment rescue — mostly Phase II and III, mostly cardiometabolic and neuro. The pattern I keep hearing: you've got sixty percent of sites green-lit, and of the activated ones, better than half have randomized zero. So the blended randomizations per site per month is sitting under 0.4 against a forecast of one-point-something, and the only lever on the table is an amendment to loosen I/E — which costs you re-consent and another IRB cycle. Is that anywhere near your world, or have you got that curve back on track?" **For Head of Patient Recruitment & Site Engagement:** > "Everyone I talk to in your seat has the same problem — it's not referral volume, it's screen failure rate. You paid for a thousand referrals last study and thirty, forty percent failed on a washout or a lab value that was knowable before they ever sat in the chair, and the site absorbed the screening cost and stopped trusting the channel. Familiar, or did yours land better than that?" **For Director, Field Medical (MSL Team Lead) / VP, Medical Affairs:** > "I spend most of my time with field medical leads at mid-cap sponsors. The thing that comes up every time: your tier-one target list hasn't changed in two years but the door has closed. Scientific exchange at the big academic centers is booking six weeks out, and you're being asked to justify headcount against reach and frequency numbers that keep sliding. Is that your quarter, or is your access holding up?" **For Senior Director, Commercial Excellence / Launch Readiness:** > "I work with launch readiness leads, mostly first-in-class or first-launch orgs. The consistent pain is that you're building the field model against a PDUFA date you don't control and a label you haven't seen, so every asset gets built twice — once before the label, once after — and MLR cycle time is what actually sets your launch calendar, not the market. Sound like your build, or are you further along than that?"
- 4
Two questions maximum
You are not running discovery. Two narrow, factual questions, then close. Never "walk me through your process." Pick two: - "How many sites are activated versus contracted right now — roughly?" - "Is the CRO's site management group handling pre-screening, or is that on the sites themselves?" - "What's your screen failure rate running at on that protocol?" - "Is the amendment already drafted, or is that still a debate internally?" - "Is there a rescue line in the study budget, or does that money come out of a change order?" - "Is that on someone's plan this year, or is it just being lived with?" Listen for the **admission**: "honestly, it's a mess," "we're about six weeks behind," "we've been meaning to look at that." The second you hear it, stop asking and ask for the calendar.
- 5
The ask
Small, named length, say what it isn't, two options. > "Here's what I'd suggest. Twenty-five minutes — not a demo, no deck. I'll bring the site-level randomization data from two studies in your indication and you tell me whether the pattern matches yours. If it's not relevant you say so on the call and I'll leave you alone. I've got Thursday at 8:15 before your day starts, or Friday at 4. Which is less bad?" For field medical: > "Twenty minutes. I'll show you what access at four of the big IDNs actually looks like right now versus what your reach and frequency report says. If it's the same picture, fine, I'll disappear." The moment they say yes: **"Sending the invite now — can you confirm it landed before I let you go?"** Meetings calendared on the phone no-show dramatically less.
- 6
Gatekeeper / assistant screen
Short, calm, specific. Never cute, never imply a prior relationship. > "It's about site activation cycle time on the Phase III — Dan Reyes at Corvale. She won't know my name, this is a first call." If they ask you to email: "I'll do that, and I'd still rather not clog her inbox with something she didn't ask for. When does she usually have five minutes — early, or after four?"
- 7
Voicemail (under 20 seconds, no ask)
> "Maria, Dan Reyes at Corvale — you don't know me. Calling about randomization rate per site per month on cardiorenal Phase III programs; it's the thing we get pulled into most. I'll try you again Thursday morning. 415-555-0192." No pitch, no calendar link, no "looking forward to connecting." The voicemail's only job is that your name is familiar when you call back and when the email lands.
- 8
The soft no and the recycle
If they won't book, get one piece of intelligence and a dated reason to return. > "No problem. Last thing and I'll let you go — is this a timing thing or a not-a-priority thing? … Got it. When's the database lock on that study? … And the next protocol, does that start feasibility before or after topline? … Perfect. I'll come back to you the first week of October. I'll send one email so you've got my name and you can bin it." A call that ends with "database lock is late September, next protocol enrolls Q1, call me in October" is a good call. A call that ends with "send me an email" and nothing else is a polite hang-up.
- 9
Immediately after
- Invite sent on the call, or email within five minutes with a subject line referencing the call: "Our call just now — the zero-randomizing sites." - Log their exact words. If they said "the CRO keeps telling me it's a feasibility problem, not a recruitment problem," that sentence goes into the discovery call verbatim. - Log the disposition honestly. "Interested" is not a disposition. "Booked Thu 8:15 with VP ClinOps, bringing site-level randomization data, wants ops lead on the call" is.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Maria — it's Dan Reyes at Corvale. We haven't spoken, this is a cold call. Can I have thirty seconds to say why I rang, and you can tell me to get lost?
Buyer
I'm walking into something in four minutes. What is this?
Rep
Fair. Thirty seconds then. We work with sponsor clinical ops teams on enrollment rescue, mostly Phase II and III cardiorenal and neuro. The pattern I hear constantly: contracted site count looks fine, but of the activated sites, better than half have randomized zero, so the blended rate is sitting under half a patient per site per month against a forecast of one and change. And the only lever left on the table is an amendment to loosen I/E, which buys you re-consent and another IRB cycle. Is that anywhere near your world, or have you got that curve back?
Buyer
Where did you get my number? And how do you know anything about our enrollment?
Rep
Your number, a data provider — I look for sponsors with an active Phase III and a completion date that's moved, and you fit. Your enrollment, I don't know. I know the registry record for ATLAS-3 added eleven sites in Q1 and the estimated primary completion moved out two quarters. That combination usually means one thing. If I've read it wrong, tell me and I'll hang up.
Buyer
You've read it half right. But recruitment is in our CRO's scope of work. That's what we pay them for.
Rep
It usually is, and it's usually the line item they're behind on. Honest question — in the bid defense, what did they forecast for randomizations per site per month, and what's it actually running at?
Buyer
They forecast 1.2. We're at about 0.5, and their answer is that it's a feasibility problem, not a recruitment problem, and that we should amend the eGFR cut-off.
Rep
Which is the answer that costs you a quarter and doesn't fix the sites that are already green-lit and sitting at zero. So — is that amendment already drafted, or is it still an internal argument?
Buyer
It's drafted. Look, I'll save you time. We tried a recruitment vendor on the last program. They sent us volume, and our screen failure rate went to about forty percent. My sites were furious and I spent the money twice.
Rep
That's the right thing to be angry about — you paid per referral and absorbed the screening cost. Where did they fail: eligibility, washout, or lab values?
Buyer
Mostly labs and prior therapy. The pre-screen clearly wasn't built off our actual criteria.
Rep
Then that's the whole difference. We contract on randomized patients, not referrals, and the pre-screen is built line by line off your I/E, labs included. If we send you someone who screen-fails on a criterion we should have caught, we don't get paid for them. That's the version worth twenty-five minutes of your time — not mine.
Buyer
Even if that's true, anything that touches a patient or a physician goes into privacy review, IT security, vendor qualification and a GxP assessment before procurement opens a file. That's four months and I have to personally sponsor it. I'm not doing that this quarter.
Rep
Understood, and I'd rather you not put it in the queue yet. Two things. One, send me your vendor security questionnaire and DPA template and I'll return the completed pack — SOC 2, HIPAA and GDPR positions, Part 11 documentation — which starts that clock in parallel and costs you nothing. Two, most of what we do sits pre-consent and never touches a promotional asset, so the med-legal piece is often a two-page process description, not a campaign submission. Neither of those requires you to sponsor anything yet.
Buyer
I've got about six weeks until the DSMB interim. I genuinely don't have bandwidth to evaluate a vendor right now.
Rep
Then let's not evaluate a vendor. Twenty-five minutes, no demo, no deck — I bring site-level randomization data from two cardiorenal programs and we look at which site archetypes went to zero and why. If the pattern doesn't match ATLAS-3 you've lost twenty-five minutes and you'll know something about your own site list either way. Thursday at 8:15 before your day starts, or Friday at 4?
Buyer
Thursday. 8:15, and I mean 8:15 — I have a governance call at 8:45. And bring the ops lead question, not a pitch.
Rep
Thursday 8:15, twenty-five minutes hard stop. Sending the invite now — can you tell me it landed before I let you go? And if you want your CRO ops lead on it, add them; we work alongside CROs, we're not there to take a scalp.
Buyer
It's in. Send me the security pack too — I'll forward it to our vendor management group so it's not sitting on my desk.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Anything touching HCP engagement has to clear med-legal — that's months.” | Understood, and I'd rather you not put it in the queue yet. What I'd propose first is a scoping conversation with your MLR lead and privacy on the process only — no content, no promotional claim, nothing branded. Most of what we do sits pre-consent and never touches a promotional asset. If we can define what actually needs review, you're submitting a two-page process description instead of a full campaign, and I've seen that go through in one cycle. |
| “Our CRO owns recruitment. That's in their scope of work.” | It usually is, and it's usually the line item they're behind on. What's the actual randomization rate per site per month against what they forecast in the bid defense? If it's under, the change order to fix it costs you more than a parallel channel would. We're not replacing them — we work alongside the CRO, and we've been added as a sponsor-direct vendor on studies where the CRO welcomed it, because they were the ones taking the escalation calls. |
| “We tried a recruitment vendor on the last study. Half the referrals were screen failures.” | That's the right thing to be angry about — you paid for volume and absorbed the screening cost. What was the screen failure rate, and where did they fail: eligibility, washout, or lab values? We contract on randomized patients, not referrals, and we build the pre-screen off your actual I/E criteria. If we send you someone who screen-fails on a criterion we should have caught, that's on us. |
| “Sites won't adopt another platform. Our coordinators are drowning.” | Agreed, and if it needs a coordinator login it fails. The pre-screening happens on our side — the site receives a pre-qualified referral with the I/E boxes already checked and the consent conversation already teed up. Their workload goes down, not up. Ask any site you've got a good relationship with what they'd say to that. |
| “We're mid-trial readout — nobody signs anything new this quarter.” | Then this isn't a signature conversation. Your next protocol starts enrolling when — Q3? The sites you'll need are being selected right now, and feasibility takes ninety days regardless. Give me thirty minutes with your ops lead to map the site list for that study, so the day the readout clears you're not starting from a blank feasibility questionnaire. |
| “Privacy and IT security will take four months to clear you.” | They will if we start cold. Send me your vendor security questionnaire and DPA template now — we've got the completed pack, SOC 2, the HIPAA and GDPR positions and the Part 11 documentation ready to go. That work happens in parallel with your team deciding whether this is even worth doing. It costs you nothing to start the clock. |
| “This is a budget that was set last year. There's no line for it.” | Where does a month of trial delay get charged? Most groups I work with fund this out of the study budget as a rescue line, or out of the change-order money they'd otherwise send to the CRO. If your burn is several million a month and this pulls LPI in by six weeks, the funding conversation is a redirection, not a new ask. Who owns that study-level budget — you or clinical finance? |
| “Send me some information.” | Happy to, but the generic pack will get binned and we'll both have wasted the effort. Give me two things — how many sites are activated versus contracted, and whether the amendment is already drafted — and I'll send you the site-archetype breakdown from a program that looked like yours. Then you can decide whether Thursday is worth twenty-five minutes. |
Questions reps ask about this call
- What actually opens a pharma cold call to a VP of Clinical Operations?
Name, honest frame, permission, then a problem stated in their metrics. "It's a cold call, can I have thirty seconds" outperforms any softener because it collapses the suspicion loop — they stop trying to place you and start listening. Then spend those thirty seconds on randomizations per site per month, screen failure rate, or site activation cycle time. Avoid "how are you today," "did I catch you at a bad time," and any sentence that starts with what your company is.
- Should I pitch to Clinical Operations or Medical Affairs first?
Depends entirely on what you sell. If you touch patients, sites, or enrollment, the pain lives with VP Clinical Operations, Executive Director Clinical Development, or Head of Patient Recruitment & Site Engagement — and their problem statement is the enrollment curve. If you touch physicians, it's VP Medical Affairs or the Director, Field Medical running the MSL team, and their problem is access collapse and sliding reach and frequency. If you touch launch assets, it's Senior Director Commercial Excellence / Launch Readiness, whose real constraint is MLR cycle time. Never run one script across all three — the language doesn't transfer and they'll hear that instantly.
- How do I handle "our CRO owns that" on a cold call?
Answer once, with a number, then re-ask for the meeting. "It usually is, and it's usually the line item they're behind on — what did they forecast for randomizations per site per month in the bid defense, and what is it actually running at?" That question either produces an admission or ends the call honestly. Critically, position yourself alongside the CRO, not against it: sponsors don't want a vendor fight in the middle of a Phase III, and the CRO is often the party that welcomes the help because they're the ones taking escalation calls.
- Isn't it pointless to cold call pharma when everything goes through MLR, privacy and vendor qualification?
That's exactly why the ask has to be small. You're not asking them to sponsor a six-month internal process on a cold call — you're asking for twenty-five minutes and, separately, for their security questionnaire and DPA template so the compliance clock runs in parallel and costs them nothing. Making the first step "send me your paperwork" rather than "let's do a pilot" is what gets you past the buyer who is mentally pricing in privacy review, IT security, vendor qualification and a GxP assessment.
- What counts as a successful pharma cold call if they won't book?
A dated reason to call back plus one piece of real intelligence. Database lock in late September, next protocol starting feasibility in Q1, PDUFA in eleven months, the amendment already drafted — any of those gives you a specific return date and a specific opening line. "Send me an email" with nothing attached to it is a polite hang-up, not a soft yes. Trade the email for two facts or a callback date before you let them go.
- How do I sound credible without inventing numbers?
Use the metrics as things your buyer is measured on, not as market claims. "The teams I talk to are watching randomizations per site per month and screen failure rate, and the pattern is that half the green-lit sites contribute nothing" is credible and defensible. "Sponsors lose 8.4 million a month to enrollment delay" invites a challenge you can't win. Ask them for their number instead — a VP Clinical Operations who tells you their own screen failure rate has just done your qualification for you.