Pharma · Warm Call
Warm Call Script for Pharma: Turning a Referral Into a Second Meeting With Clinical Ops
The person picking up already knows what their morning looks like. They opened the enrollment curve, saw that 61 sites are green-lit and 34 have randomized at least one patient, and that the median across the activated ones is running under half a patient per month against a bid-defense forecast of 1.2. FPI was in March. The CRO wants a change order to add two countries. Somebody in the room has already said the words "protocol amendment," which means re-consent, another IRB cycle and a quarter gone. That is the headspace your referral just walked you into.
Warmth is a loan, not a grant. The referral bought you the pickup, roughly ninety seconds of suspended disbelief, and permission to ask a real question without a warm-up. It did not buy you interest, a problem, or budget — and in pharma it definitely did not buy you a shortcut through privacy review, IT security, vendor qualification, GxP assessment or MLR. A VP, Clinical Operations or an Executive Director, Clinical Development will be polite because a peer sent you, and they will still be mentally pricing in six months of internal work they'd have to personally sponsor. Your job on this call is to prove you understand that before they have to explain it to you.
The fastest way to burn the ninety seconds is to transplant the referrer's problem onto them. Ravi's cardiorenal study in Central Europe is not her oncology program in the US and Japan. Say so out loud — naming the reason you might be irrelevant is the single strongest credibility move available on a warm call into this industry, because every one of these buyers has sat through a vendor call where the vendor clearly read one press release. Below is the script, the objections in the language they'll actually use, and a full call with a buyer who is four weeks from a DSMB interim and in no mood.
The warm call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: write the provenance line
One sentence, out loud, before you dial. Small and checkable: "Ravi Chandrasekaran pulled down our site activation benchmark in the spring and said you'd picked up the ARC-3 program after the reorg." Not "Ravi thought you'd be interested." These people sit on the same TransCelerate working groups and the same DIA panels — they compare notes. Say exactly what the referrer said and nothing more. If Ravi said "you should call Elena," you say "Ravi said I should call you," full stop. One pharma-specific guardrail: you can name the person, you cannot name their protocol, their indication, their enrollment numbers or their CRO. If your provenance line leaks a detail about the referrer's study, you've just shown the buyer exactly how you'll talk about hers.
- 2
Pre-call: the relevance hypothesis about THEIR study
One sentence about their world, built from something with a date on it. Sources that actually work in pharma: - A ClinicalTrials.gov record where the estimated primary completion date moved twice - A site count that went up 40% mid-study — the sponsor is buying its way out of an enrollment miss - A new posting for "Associate Director, Patient Recruitment" — they've decided the CRO isn't fixing it - A recent CRL, an information request, or a PDUFA date inside twelve months - An indication where you know the I/E is punishing — prior lines of therapy, biomarker-positive, washout Write it as: "They're likely running behind on [specific], and the fix in front of them is [amendment / change order / more sites], all of which cost a quarter."
- 3
The open — 25 seconds, four beats
"Elena — Maya Oduya, from Corriden. Ravi Chandrasekaran suggested I call. He pulled down our site activation benchmark in the spring and said you'd taken over the ARC-3 program after the reorg. He may have oversold my usefulness. Have you got four minutes for me to check whether that's true, or shall I come back?" Name, referrer immediately, provenance, permission with a time box. When they say "Yes, Ravi mentioned you'd call" — that's the whole warmth budget landing in your hands. Spend five words on it: "Good, he said he'd flag it. Then I'll be quick." Do not ask how they know Ravi.
- 4
If they can't place the referrer
Half of pharma intro emails are skimmed on a phone between a JPM prep call and a governance meeting. Don't argue them into remembering. "No reason you would — it was two lines on a Friday. Short version: we run sponsor-direct patient identification that sits pre-consent, alongside the CRO, and we contract on randomizations rather than referrals. Ravi's team used us when their contract-to-green-light was running past 140 days. Worth four minutes or not really?" Fifteen seconds, in their language, no product tour.
- 5
The relevance bridge — the move the call lives or dies on
Referrer's world → the specific difference → a question that hands them control. "What Ravi was dealing with was a cardiorenal protocol where contract-to-green-light was running past 140 days and the sites that did activate were randomizing under half a patient a month. That's his protocol, not yours — yours is oncology, different site network, and you've got an in-house recruitment function he doesn't. So I genuinely don't know if this lands. Where's your curve sitting against forecast at the moment?" The "that's his protocol, not yours" beat is what separates this from every other vendor call they take. It proves you researched them and it disarms the brace for a pitch.
- 6
Discovery — three questions, four at the outside
You have four to twelve minutes and no agreed agenda. Eleven qualification questions reads as an abuse of the referral. 1. **Mechanical current state:** "Of the sites you've green-lit, how many have randomized at least one patient — and what's the median randomizations per site per month against what the CRO forecast in the bid defense?" 2. **Cost or friction in their numbers:** "What's your screen failure rate running at, and where are they failing — eligibility, washout, or lab values?" Then: "What does a month of slip cost you in run-rate?" 3. **Priority test:** "Is that a this-quarter problem or a live-with-it-until-the-next-protocol problem?" This question saves more wasted follow-ups than anything else you'll ask. Optional fourth: "Besides you, who else would have to care — is that clinical finance, or does your Head of Patient Recruitment own the site list?" Write down their phrasing verbatim. "It's not the site count, it's that the good sites are saturated" goes straight into the follow-up email and the meeting agenda.
- 7
Pre-empt the compliance wall before they raise it
In pharma, saying this first is worth more than answering it later. It tells them you've done this before. "Before you have to tell me — I know anything that touches an HCP or a patient triggers privacy, IT security, vendor qualification and a GxP assessment, and that MLR is two to three rounds and six to twelve weeks. I'd rather you didn't put us in that queue yet. Most of what we do sits pre-consent and never touches a promotional asset. What I'd want first is a scoping conversation on the process only, so you're submitting a two-page process description rather than a campaign." Then the parallel-track ask: "Send me your vendor security questionnaire and DPA template today. The completed pack, SOC 2, the HIPAA and GDPR positions and the Part 11 documentation are ready to go. That clock runs while your team decides whether this is even worth doing."
- 8
Reading the cool-off
Warmth withdraws politely. In pharma it sounds like: "Yeah, makes sense." / "Can you send something over and I'll route it to the CRO?" / "What's your pricing model?" before a problem is on the table / "Well, if Ravi rates you..." Stop and name it: "I'm getting the sense this isn't the pressing thing right now — which is fine, Ravi was guessing. Is it not the problem, or not the moment? If the answer is that ARC-3 is set and the next protocol is where the pain is, tell me and I'll come back in the autumn." A clean "not the problem" is a good outcome. It protects the referrer and stops you burning a quarter on a program that's already at LPI.
- 9
The close — date, length, named reason, named attendee
"Then here's what I'd suggest. You said 34 of 61 are producing and the median's 0.4 against a forecast of 1.2. Give me thirty minutes and I'll walk you through what we did on two comparable programs, sponsor-direct alongside the CRO — and I'd want your Head of Patient Recruitment and Site Engagement on it, because the useful question is which of those 27 silent sites are worth rescuing versus replacing. Thursday morning, or Monday after your DSMB?" If they genuinely can't commit: take a smaller real commitment with a date on your side. "I'll send two paragraphs and one chart — randomizations per site per month, ours versus the enrollment curve, on a study with I/E as tight as yours. Tell me Thursday whether it's worth thirty minutes." Then diarise Thursday yourself.
- 10
Same-day loop back to the referrer
Non-negotiable, routinely skipped, and the only reliable way a source produces a second referral. "Ravi — spoke to Elena, thank you for that. Her situation's different to yours; site count isn't the issue, it's that two-thirds of the activated sites haven't randomized. Thirty minutes with her and her recruitment lead on Monday. Appreciated." Three jobs: thanks them, tells you whether you can use their name again, and keeps the channel open. And note what you did not do — you didn't tell Ravi her randomization numbers in a way he could act on. Keep the loop-back at the level of "different problem to yours."
- 11
Language bank
**Works** - "Ravi suggested I call — he may have oversold my usefulness." - "That's his protocol, not yours, so I don't know if this lands." - "Is that a this-quarter problem or a live-with-it problem?" - "Then don't put us into MLR yet." - "If it needs a coordinator login, it fails." - "We contract on randomizations, not referrals." **Kills the warmth** - "So how do you know Ravi?" as an opener - "Ravi said you'd be really interested in this." - "Just to give you a bit of background on us..." - "As per the email below." - "Ravi was struggling with enrollment, so I imagine you are too." - Any sentence containing "end-to-end patient journey solution"
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Elena — Maya Oduya, from Corriden. Ravi Chandrasekaran suggested I call. He pulled down our site activation benchmark in the spring and said you'd taken over the ARC-3 program after the reorg. He may have oversold my usefulness. Have you got four minutes for me to check, or shall I come back?
Buyer
Ravi. Yes, he said someone would call. You've got four minutes, I've got a DSMB prep call at half past.
Rep
Good, then I'll be quick. What Ravi was dealing with was a cardiorenal protocol where contract-to-green-light was running past 140 days and the sites that did activate were randomizing under half a patient a month. That's his protocol, not yours — you're oncology, different site network, and you've got an in-house recruitment function he doesn't. So I honestly don't know if this lands. Where's your curve sitting against forecast?
Buyer
Below. Everyone is below. That's not a differentiator, Maya.
Rep
Fair. Below by how much — is it a site count problem or a per-site problem?
Buyer
Both, and it's mostly the US academic centers. We've green-lit 61 sites, 34 have randomized at least one patient, and the median across the activated ones is 0.4 a month against a bid-defense forecast of 1.2. And before you go anywhere with that — recruitment is in the CRO's scope of work.
Rep
It usually is. It's also usually the line item they're behind on. Have you had the change order conversation yet?
Buyer
Had it last month. They want two more countries and a feasibility re-run. Three months and a seven-figure number. And I'll save you some time — we used a recruitment vendor on the previous program. Roughly four hundred referrals, about half screen-failed on prior lines of therapy and washout, and by the end my coordinators stopped answering their emails. I'm not doing that to sites again.
Rep
That's the right thing to be angry about. You paid for volume and the sites absorbed the screening cost. Two things are different here, and you can hold me to both. We contract on randomized patients, not referrals — so the screen failure risk sits on my side of the line. And the pre-screen is built off your actual I/E, so if someone fails on a criterion we should have caught, we don't bill it. What did your screen failure rate end up at on that study?
Buyer
Forty-eight percent. Though I'd concede the protocol was partly to blame for that.
Rep
Most of them are. Does the ARC-3 I/E have the same shape, or did you tighten it?
Buyer
We loosened it in amendment three, which cost us re-consent and an IRB cycle and about a quarter. Which is exactly why I'm cautious. And look — even if I liked this, anything that touches a patient or a physician goes through privacy, IT security, vendor qualification and a GxP assessment before procurement opens a file. Then anything HCP-facing goes into MLR, which is two to three rounds and six to twelve weeks. That's six months of me personally sponsoring paperwork.
Rep
Then don't put us into MLR yet — I'd rather you didn't. Most of what we do sits pre-consent and never touches a promotional asset; the site receives a pre-qualified referral, not a piece of content. What's worth thirty minutes is a scoping conversation on process only, with whoever owns privacy, so you're submitting a two-page process description instead of a campaign. Separately — send me your security questionnaire and DPA template today. The completed pack, SOC 2, the HIPAA and GDPR positions and the Part 11 documentation are all sitting ready. That clock runs in parallel and costs you nothing.
Buyer
And the sites? Because if this needs a coordinator to learn another portal, it dies on arrival. My coordinators are running eleven other studies and mine is not their favourite.
Rep
Agreed, and if it needs a coordinator login it fails. The pre-screening happens on our side. The site gets a referral with the I/E boxes already checked and the consent conversation teed up — their workload goes down. Ask the one site director you actually trust what they'd say to that.
Buyer
Maybe. But we're four weeks from the interim analysis. Nobody in this building signs a new vendor this quarter.
Rep
Then this isn't a signature conversation. Let me ask the only question that matters: is the US academic site problem a this-quarter problem, or a live-with-it-until-the-next-protocol problem?
Buyer
It's a this-quarter problem that I can't fix this quarter. Which is a worse category.
Rep
Then here's what I'd suggest. You said 34 of 61 are producing at 0.4 against a forecast of 1.2. Give me thirty minutes to walk through two comparable programs where we ran sponsor-direct alongside the CRO — and I'd want your Head of Patient Recruitment and Site Engagement on the call, because the real question is which of those 27 silent sites are worth rescuing versus replacing. Thursday morning, or Monday once the DSMB is behind you?
Buyer
Monday. Send an agenda beforehand. And don't send me a deck about your company.
Rep
Monday, thirty minutes, agenda tonight — three lines: the 27 silent sites, how the randomization-based contract handles screen failures, and exactly what privacy will need from us. Nothing about us. I'll let Ravi know the intro was useful; he'll want to hear it.
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 didn't put us in that 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 genuinely needs review, you're submitting a two-page process description instead of a full campaign, and I've seen that clear in one cycle rather than three. |
| “We're four weeks from the interim — nobody signs anything new this quarter.” | Then this isn't a signature conversation. When does your next protocol start enrolling — Q3? The sites for that study are being selected right now and feasibility takes 90 days regardless of what the DSMB says. Give me thirty minutes with your ops lead to map that site list, so the day topline clears you're not starting from a blank feasibility questionnaire. |
| “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 randomizations per site per month against what they forecast in the bid defense? If it's a third of forecast, the change order to fix it — extra countries, feasibility re-run — costs you more than running a parallel channel. We're not replacing them. We've been added as a sponsor-direct vendor on studies where the CRO welcomed it, because they were the ones taking the weekly escalation call. |
| “Sites won't adopt another platform. Our coordinators are drowning.” | Agreed, and if it needs a coordinator login it fails — I'd tell you not to buy it. 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 teed up, so their workload goes down rather than up. Take the one site director you've got a real relationship with and ask them what they'd say to that. If they're lukewarm, I'll drop it. |
| “We tried a recruitment vendor last program. Half the referrals were screen failures.” | That's the right thing to be angry about — you paid for volume and your sites absorbed the screening cost. What was the screen failure rate in the end, and where did they fail: eligibility, washout, or lab values? We contract on randomized patients, not referrals, and the pre-screen is built off your actual I/E criteria. If we send someone who screen-fails on a criterion we should have caught, we don't bill it. That's the whole difference in one sentence. |
| “Privacy and IT security will take four months to clear you.” | They will if we start cold in month three. Send me your vendor security questionnaire and DPA template now — we have the completed pack, SOC 2, the HIPAA and GDPR positions and the Part 11 documentation ready to go. That work runs in parallel while your team decides whether this is even worth doing. It costs you nothing to start the clock, and if you walk away in six weeks you've lost nothing but an inbox thread. |
| “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 be sending to the CRO. If your run-rate is what I think it is and this pulls LPI in by six weeks, it's a redirection rather than a new ask. Who actually owns that study-level budget — you, or clinical finance? |
Questions reps ask about this call
- How is a warm call into pharma different from a warm call into any other industry?
The referral gets you the pickup and about ninety seconds. What it cannot do is shorten privacy review, IT security review, vendor qualification, the GxP assessment or MLR — so a pharma buyer is being friendly and simultaneously pricing in six months of internal work they'd have to personally sponsor. That means your first call has a job most industries don't: you have to show you know what the compliance path looks like before they explain it to you. Saying "I'd rather you didn't put us into MLR yet, most of what we do sits pre-consent" does more for your credibility than any capability statement.
- Can I name the referrer's company or study on the call?
Name the person, never the protocol. You can say "Ravi Chandrasekaran suggested I call — he pulled down our site activation benchmark." You cannot say "Ravi's Phase 3 in Central Europe was 140 days to green-light." Sponsors treat enrollment performance as competitively sensitive, and the buyer's first thought when you leak someone else's numbers is what you'll say about hers. Get explicit permission from the referrer on exactly which sentence you're allowed to repeat, and if in doubt describe the situation generically: "a cardiorenal program with an activation problem."
- Which title should I take the referral into — VP Clinical Operations, the Head of Patient Recruitment, or the CMO?
Take it to whoever owns the number you can move. If your pitch is randomizations per site per month and cost per randomized patient, that's VP, Clinical Operations or the Head of Patient Recruitment and Site Engagement. If it's field access, scientific exchange volume or insights logged per quarter, that's VP, Medical Affairs or the Director, Field Medical. If it's launch sequencing against a PDUFA date, that's Senior Director, Commercial Excellence / Launch Readiness. A Chief Medical Officer will take the referral call and then route you down — which is fine, but ask for the routing explicitly rather than hoping: "Should this sit with your ops lead or with recruitment?"
- The buyer says the CRO owns recruitment. Is the call dead?
No — it's the most common thing you'll hear and it's usually where the conversation actually starts. Move straight to numbers: what did the CRO forecast per site per month at the bid defense, and what is it doing now? If the answer is a third of forecast, the sponsor is already in change-order territory and paying for the miss twice. Position yourself as sponsor-direct and running alongside, not replacing. CROs frequently welcome it because they're the ones fielding the weekly escalation call about a curve they can't fix.
- What counts as a successful outcome on a pharma warm call?
A thirty-minute meeting with a date, a named reason built from their words, and a second attendee — usually the Head of Patient Recruitment or the study lead. A strong secondary outcome is the security questionnaire and DPA template landing in your inbox, because that starts a clock that otherwise adds months later. A clean "this isn't the problem" is also a win: it protects the referrer relationship and stops you spending a quarter on a study that's already past LPI. "Send me some info" is not an outcome.
- How do I practise this without burning a real referral?
Roleplay it out loud, because the failure modes are all verbal — burying the referrer's name in sentence three, transplanting the referrer's pain onto the prospect, or filling silence with a company overview. Run the call against a buyer who interrupts with "recruitment is in the CRO's SOW," "we're four weeks from the interim," and "the last vendor sent us four hundred referrals and half screen-failed," and time yourself: name, referrer, provenance and permission should be done in twenty-five seconds. Platforms like DrillCall let you drill exactly that opening against a difficult clinical ops persona until the relevance bridge lands inside the first minute.