Pharma · Renewal Call
Pharma Renewal Call Script: How to Save a Clinical Recruitment Account Six Weeks Out
Your MSA with a mid-cap sponsor expires in six weeks. You went in last year on a Phase 3 rescue — 46 planned US sites, 34 activated, randomizations running at 0.6 per site per month against a 1.4 forecast — and for two quarters you were the thing standing between the VP, Clinical Operations and a protocol amendment. Then Q2 happened. Your tickets went quiet for nine days during their hardest enrollment stretch, your referral pre-screen was tuned to the wrong eGFR cut, and their cost per randomized patient went the wrong way on a slide with your logo on it in a portfolio review. Adoption never left the patient recruitment team. Medical Affairs never onboarded. And a competitor has been in the Head of Patient Recruitment's inbox since October with a number 27% lower.
This pharma renewal call script is built for that call, and the first rule is that it is not a renewal call — it is a save call. The order form is the last five minutes, not the first five. If you open with "so what would it take to get this done," you confirm what they already suspect: you only show up when money is due. If you open with ticket 4417, the date it sat, what broke inside your support org, and what you did about it before this meeting, the same VP, Clinical Operations will start negotiating with you instead of against you.
Every number below is a placeholder — swap in your own account's data before you dial, and do not walk in with a number you cannot show on a screen. Pharma buyers verify. The VP, Clinical Operations will have the enrollment dashboard open. The Head of Patient Recruitment & Site Engagement can pull screen failure by criterion in four clicks. The Executive Director, Clinical Development sat through the same QBR you did. Getting one figure wrong ends the meeting.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: the renewal autopsy (do this the day before, not the morning of)
Pull and read, do not skim: 1. Every support ticket, 12 months: ID, open date, first response, resolution, who escalated. Flag everything over 48 hours to first touch. Know your three worst by number. In our example: #4417 (May 14, 11 days to first response), #4602 (June 2, 9 days), #4655 (escalated to their VP with the words "this is unacceptable" in the thread). 2. Delivery data in their metrics, not yours: randomizations per site per month you sourced vs. the enrollment curve; screen failure rate on your referrals broken out by reason — eligibility, washout, lab values; cost per randomized patient by quarter. 3. Seat and workflow usage by function: patient recruitment at 88% weekly active, 31 of 60 seats never logged in, Medical Affairs never onboarded, RS-2140 never launched on the platform. 4. Site-side friction: how many of the 34 activated sites hit a login wall you promised they'd never see. 5. MLR history: the unbranded disease-awareness asset that took four rounds and 71 days when you scoped two rounds. Have the review log. 6. Your own turnover: two CSM changes in ten months. Name that before they do. 7. Every QBR commitment you didn't deliver. Write the list. You will read part of it out loud. 8. Their org: did the person who signed still own the study budget? Did their champion move to the launch team? Is the CMO now involved? Before you dial, get written internal sign-off on: the named delivery lead, the escalation SLA, the onboarding hours, and your price floor. A second broken promise ends this account permanently.
- 2
Opening: name it before they have to (first 60 seconds, you go first)
"Dana, the MSA is up in six weeks and I know that's why this is on the calendar. I'd rather not talk about the renewal yet. I want to talk about this year, because from where I'm sitting it wasn't the year we sold you. Here's what I can see. Ticket 4417 sat eleven days without a first response in May, right in the middle of your Q2 enrollment push. 4602 sat nine. 4655 got escalated to you personally and you shouldn't have had to send that email. You had two CSM changes in ten months. Screen failure on the patients we referred ran 41% in Q2 against the 22% we scoped, and your cost per randomized patient went from about $9,200 to $13,600 in that quarter. And we only ever got live with Priya's team — Medical Affairs never onboarded, RS-2140 never launched, 31 of the 60 seats you're paying for have never been logged into. That's my side of it. What am I missing, and what did it actually cost you?" Then stop talking. Do not fill the silence.
- 3
Listening phase: let it be worse than you thought (40–50% of the call)
No "but." No "to be fair." No defending the referrals that failed on washout because their site didn't run the lab. You may be right and you will lose the renewal being right. Probes, in their language: - "Where did the screen failures actually fail — eligibility, washout, or lab values? Do you have it split out?" - "When the curve slipped, what was the internal conversation? Did anyone raise a protocol amendment to loosen I/E?" - "Who did you have to explain the cost per randomized patient to? Did this reach your CMO?" - "Did the CRO use this against you in the change-order conversation?" - "You said the sites were 'done with us' — tell me about that. Which sites, and what did the coordinators say?" Write it down visibly. Read it back: "So: Q2 response times, the pre-screen tuned to the wrong criterion, eleven sites hitting a portal login we said would never exist, four MLR rounds on the unbranded piece, and Medical Affairs never getting onboarded at all. Anything else?" Ask "anything else?" a second time. The second ask is where the political damage comes out.
- 4
The apology: once, specific, unhedged
"The Q2 response times were our failure. We reorganised support in April and your tickets got queued behind two enterprise escalations. That's an explanation, not an excuse — you bought a 24-hour first response and we missed it on nineteen tickets in that quarter. And the pre-screen: we built it off the synopsis, not the final amended I/E, so we were screening on the wrong eGFR band for seven weeks. You paid the screening cost for that. I'm not going to spread that around — it's ours." One apology. Do not repeat it later in the call; repetition reads as a technique.
- 5
Proof of change: show, don't promise
"Three things, and I'd rather show you than tell you. One — structural. We split the delivery queue by study phase in August and staffed it. Your median first response since September 1 is 2.9 hours across fourteen tickets. That's your account's log, not a company average, and I'll send the export. Two — already done, and I didn't ask you first. Two weeks ago we rebuilt the pre-screen logic against the current amended I/E, criterion by criterion, and re-ran it against your last 300 referral records. On the rebuilt logic, projected screen failure comes out at 24%. Priya has the file. I also cleared the three open tickets in your queue last Thursday. Three — the vendor pack. Your privacy and IT security teams re-qualify annually. Our refreshed SOC 2, the HIPAA and GDPR positions, the 21 CFR Part 11 documentation and the signed DPA are all with your vendor management portal as of last week, so that clock isn't starting from zero in six weeks. And the thing I can't fix: the four MLR rounds on the unbranded asset. That happened partly because we submitted creative before we agreed the reference pack. Going forward we submit process-only descriptions pre-consent and let your team own anything that touches a promotional claim."
- 6
Rebuild on what works: find the person, not the feature
"You said the referral packet with the I/E boxes pre-checked is the one thing your coordinators actually liked. Tell me who's using it and what it replaced. If we disappeared in six weeks, whose Monday breaks? My guess is Priya's, and I notice she isn't on this call. What I'd want to understand is what your site activation cycle time looked like on the sites we sourced versus the rest — you were at 118 days contract-to-green-light on the study overall. If the pre-qualified sites moved faster, that's a number worth putting in front of your Executive Director, Clinical Development before anyone decides anything." Quantify in their language: coordinator hours not spent chart-pulling, screening visits avoided, a site that randomized instead of going dark. Then be quiet about it — do not turn it into a pitch.
- 7
Handling the competitor
"I'd assume you've had [Competitor] in your inbox. I'd be surprised if you hadn't. What did you like about them?" Then scope it honestly: - "Have they been through your privacy review and IT security, or is it still commercial?" - "Have they scoped the migration — who moves the referral records and the consent audit trail?" - "What are they contracting on: referrals, or randomized patients?" The reframe, said plainly and once: "If they're pricing per referral and we price per randomized patient, the two numbers aren't comparable. The question your CMO will ask is cost per randomized patient, not cost per lead — and at a 41% screen failure rate you already know what per-referral pricing does to that number. That's the arithmetic I'd want you to run before you compare the two quotes. The other thing I'd want you to price is the six months. Vendor qualification, GxP assessment, a new DPA, re-papering the site-facing materials, and Priya rebuilding a referral workflow that currently works — during RS-2140 feasibility. I'm not saying don't do it. I'm saying the license delta isn't the switching cost." Do not disparage them. Do not match on price here.
- 8
The 90-day plan: build it live, in their words
Four fields per line — what, who by name on both sides, by when, and what "done" looks like. "Here's what I'd write down, and I want you to add to it and cut what's wrong. 1. Pre-screen accuracy — rebuilt logic goes live on CV-3021 week of the 14th, owned by Anna Wu on my side and Priya on yours. Done = screen failure on our referrals at or under 25% measured over the first 60 referrals, reported weekly. 2. Support — Sam Ortiz is your named escalation, direct line, 4-hour first response on anything P1, effective at signature. Done = the log, sent monthly, whether it's good or bad. 3. RS-2140 — feasibility site list mapped against your I/E in the first three weeks so you're not starting from a blank feasibility questionnaire when the readout clears. Needs two hours from your feasibility lead. That's an ask of you, not of me. 4. Medical Affairs — I'm not going to promise an MSL workflow rollout in 90 days. That needs your Director, Field Medical in the room and it needs an MLR scoping conversation first. What I'll commit to is getting that scoping meeting booked by day 30. 5. Sites — zero coordinator logins. If any site is asked to log in to anything of ours, that's a P1 and Sam owns it. 6. Governance — 30/60/90 reviews with a written usage report. First one is dated on this plan. What I need from your side: an internal owner for the RS-2140 mapping, and Priya's name on line one. A plan where only the vendor has obligations is a wish list, and part of why adoption stalled last year is that nobody on your side was accountable for it." Tie a commercial consequence: a break clause at six months, or SLA credits written into the contract. Signing an SLA credit is worth more than a discount because it proves you expect to be held to it.
- 9
Only now: the commercial conversation
Earn the transition out loud: "If we agree that plan is real, can I show you what renewal would look like?" - Lead with structure, not the number. "You're paying for 60 seats and using 29. I'd rather right-size to 30 than discount 60 — I'd rather be right than big, and it kills the shelfware conversation permanently." - Anchor on the study metric: "Priced against randomized patients rather than seats, the question becomes what a month of delay costs you at your burn rate — and where that gets charged today." - Any discount is traded: multi-year, an earlier signature, a reference call with another VP, Clinical Operations, or naming us on RS-2140 at feasibility. - Do not offer a discount as an apology. For a genuinely bad year, service credits for the affected months are the honest instrument — specific, finite, and they don't reset your floor. - "Where does this get funded — study budget, the change-order line you'd otherwise send to the CRO, or a central ops budget? And is that yours or clinical finance's?"
- 10
Multi-thread and close
"Walk me through what actually happens between now and signature. Does this go back through vendor qualification? Does privacy need to re-look at the DPA? Does procurement already have [Competitor]'s number in writing?" Then: - "I'd like Priya on the next call — she owns line one of this plan." - "I'd also like fifteen minutes with your Executive Director, Clinical Development, or whoever presents the enrollment curve at portfolio review. If they're the one holding the slide, they should hear the 90-day plan from me, not from you." - Book the next meeting on the call. Never "I'll follow up." - Temperature check, honestly: "On a scale where 1 is you've already decided to leave — where are we right now, and what moves it?" Take the honest answer over the polite one. Within 24 hours, send four things: the 90-day plan with names and dates, the ticket export you quoted, the rebuilt pre-screen file, and a one-page summary of what they told you went wrong in their own words. That last document does more work than any proposal.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Dana, the MSA is up in six weeks and I know that's why this is on the calendar. I'm not going to talk about the renewal yet. I want to talk about this year first, because it wasn't the year we sold you. Ticket 4417 sat eleven days without a first response in May. 4602 sat nine. 4655 you escalated yourself and you shouldn't have had to. Two CSM changes in ten months. Screen failure on our referrals ran 41% in Q2 against the 22% we scoped, and your cost per randomized patient went from about $9,200 to $13,600 in that quarter. And we never got past Priya's team — Medical Affairs never onboarded, RS-2140 never launched, 31 of your 60 seats have never been logged into. That's what I can see. What am I missing, and what did it cost you?
Buyer
You want the honest version? What it cost me was a slide. Marcus put the enrollment curve up at portfolio review in July with cost per randomized patient on it, and your logo was on the sourcing line. I had to explain to Dr. Lindqvist why the rescue vendor was making the number worse. We were seven weeks from the interim analysis and I was fielding questions about whether we should just amend the protocol and loosen the eGFR criterion — which is three months and a re-consent, and I did not want to do it.
Rep
So you were defending us in front of the CMO while we were nine days late answering Priya's tickets. Can I ask — did the amendment conversation actually get to the DSMB prep, or did it stop at Marcus?
Buyer
It got as far as clinical development drafting the language. We didn't file it. And to be clear, Priya is the only reason you're in this room. She fought for you when I'd have cut it in August. She rebuilt half the pre-screen mapping herself in a spreadsheet because nobody at your end was answering.
Rep
The Q2 response times were our failure. We reorganised support in April and your tickets got queued behind two enterprise escalations. That's an explanation, not an excuse — you bought a 24-hour first response and we missed it nineteen times in that quarter. And the pre-screen was built off the synopsis instead of the amended I/E, so we were screening on the wrong eGFR band for seven weeks and you absorbed the screening cost. That's ours. What else is on the list? I'd rather hear all of it now.
Buyer
The sites. You told us in the pilot that no coordinator would ever need a login. Eleven sites got a portal invite. Site 0114's coordinator is running eleven other studies and she called our CRA to complain, so now the CRO has it on their escalation log, which means it's in a monthly report that goes to Marcus. And the unbranded awareness piece went four rounds through MLR and took 71 days. Medical Affairs will not go near you again on the back of that.
Rep
Let me read back what I've got. Q2 response times. Pre-screen tuned to the wrong criterion for seven weeks. Eleven sites hit a login we promised didn't exist, and it's now on the CRO's escalation log. Four MLR rounds and 71 days on an unbranded asset. Medical Affairs never onboarded. Anything else?
Buyer
Yes. Price. [Competitor] came in at 27% under you and they've been talking to procurement since October. Tomás has their quote. And our budget got tighter because the PDUFA on our respiratory asset slipped after the information request, so commercial pulled money back and everything got re-baselined. I can't take a flat renewal to clinical finance right now even if I wanted to.
Rep
That's fair, and I'd assume you'd have talked to them. What did you like about what they showed you? And practically — have they been through your privacy review and IT security yet, or is it still commercial?
Buyer
They've had a scoping call with feasibility. Not security. What I liked is they've done four cardiorenal Phase 3s and their site list overlapped ours by about sixty percent.
Rep
That overlap is real and I won't argue it. The thing I'd want you to check before you compare the numbers is what they're contracting on. If they price per referral and we price per randomized patient, those aren't the same quote — at a 41% screen failure rate you already know what per-referral pricing does to cost per randomized patient, and that's the number that ends up on Marcus's slide, not the license fee. Separately: vendor qualification, GxP assessment, a new DPA, and Priya rebuilding the referral packet during RS-2140 feasibility. That's the switching cost I'd want priced next to the 27%.
Buyer
You're telling me the same thing your predecessor told me in the January QBR. He committed to a dedicated pod and a Part 11 documentation refresh and I never saw either. So forgive me if 'we've restructured support' doesn't land.
Rep
He did commit to both and neither happened, and I'm not going to defend it. Here's what I can show instead. Your median first response since September 1 is 2.9 hours across fourteen tickets — I'll send the export from your account, not a company average. Two weeks ago we rebuilt the pre-screen against the current amended I/E and re-ran it over your last 300 referral records; projected screen failure comes out at 24%. Priya has the file, ask her. And the refreshed SOC 2, HIPAA and GDPR positions and the Part 11 pack went into your vendor management portal last week — that one is genuinely late and it's done now. I also cleared the three open tickets in your queue on Thursday.
Buyer
Priya mentioned the file. She said the eGFR logic looked right this time. But she's got RS-2140 feasibility starting in three weeks and no capacity to run another onboarding, so if your plan involves her training Medical Affairs, it's dead on arrival.
Rep
Then it doesn't. Line one of the 90-day plan is the rebuilt pre-screen going live on CV-3021 — Anna Wu owns delivery, Priya owns sign-off only, thirty minutes a week, done is screen failure at or under 25% across the first sixty referrals. Line two is Sam Ortiz as named escalation with a four-hour P1 first response written into the contract with credits attached, not as a promise. Line three is the RS-2140 site list mapped against your I/E in the first three weeks — that one needs two hours from your feasibility lead and it's an obligation on your side, not mine. Medical Affairs isn't in the 90 days at all. What I'll commit to is a process-only MLR scoping meeting with your Director, Field Medical by day 30 — no creative, no claims, two pages. If that plan is real, I'll walk you through what renewal looks like. If it isn't, tell me now.
Buyer
The credits in the contract get my attention more than the discount would, honestly. But I'm not the only signature. Procurement will want the two quotes side by side and Marcus owns the study budget line this year, not me — that changed in the re-org.
Rep
Then Marcus should hear this from me rather than from you. Can we get thirty minutes with you, Marcus and Priya in the next ten days, and I'll bring our delivery lead so the plan has a face on it? I'll send the plan, the ticket export and the pre-screen file within 24 hours so nobody's reading it cold. Last thing — on a scale where 1 is you've already decided to leave, where are we right now?
Buyer
Two weeks ago you were a 1. Right now, a 3. What moves it is the first sixty referrals coming in under 25%, and Marcus not having to defend the sourcing line again at portfolio review.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “[Competitor] came in 27% under you and procurement already has the quote.” | I'd expect them to. Before you compare the two, check what they're contracting on — referrals or randomized patients. If it's per referral, the two numbers aren't measuring the same thing, and cost per randomized patient is what ends up on the portfolio review slide. Run their quote at your actual screen failure rate and see where it lands. Then price the switching cost properly: vendor qualification, GxP assessment, a new DPA and privacy review, re-papering the site-facing materials, and Priya rebuilding the referral packet during RS-2140 feasibility. I'm not asking you to ignore 27%. I'm asking you not to compare a license fee to a total. |
| “Half your referrals screen-failed in Q2. Why would we sign another twelve months of that?” | That's the right thing to be angry about — you paid the screening cost for our error. The failures were concentrated on one criterion: we built the pre-screen off the synopsis instead of the amended I/E and screened the wrong eGFR band for seven weeks. It's rebuilt against the current criteria and re-run over your last 300 records; projected failure comes out at 24%. What I'd put in the contract is that we contract on randomized patients and that anyone who screen-fails on a criterion we should have caught doesn't get billed. If we can't hold under 25% over the first sixty referrals, you've got a break clause at six months. |
| “We're two weeks from database lock on CV-3021. Nobody is signing anything new this quarter.” | Then this doesn't need to be a signature conversation this month. RS-2140 starts enrolling when — Q3? The sites for that study are being selected right now and feasibility takes 90 days regardless of what we do. Give me two hours with your feasibility lead to map that site list against the draft I/E, so the day topline clears you're not starting from a blank feasibility questionnaire. If the renewal papers in week five instead of week two, that's fine — I'd rather the work started. |
| “The CRO owns recruitment. It's in their scope of work and there's a change order pending.” | It usually is in scope, and it's usually the line they're behind on. What's the actual randomization rate per site per month against what they forecast in the bid defense? At 0.6 against 1.4, the change order to fix it will cost you more than a parallel channel does. We're not replacing them. On the sites we sourced, the CRO stopped getting the escalation calls — and right now they're the ones logging the site 0114 complaint into a monthly report Marcus reads. |
| “Sites told us your referral packet needed another login. Our coordinators are drowning and I won't do that to them again.” | That should never have happened and it's the failure I'd most want to be judged on. The design is that the site receives a pre-qualified referral with the I/E boxes already checked and the consent conversation teed up — zero logins. Eleven sites got a portal invite because of a misconfigured template on our side. It's written into the 90-day plan as a P1 with a named owner: if any site is asked to log into anything of ours, that's a four-hour escalation. Pick two sites you trust and let me get their coordinators on a fifteen-minute call to confirm what they'd actually want. |
| “Four rounds and 71 days in MLR on one unbranded piece. Medical Affairs won't touch you again.” | Understood, and I'd rather not put anything in that queue right now. Most of what we do sits pre-consent and never touches a promotional asset. What I'd propose for day 30 is a process-only scoping conversation with your MLR lead, privacy and your Director, Field Medical — no content, no claims, nothing branded. If we define what genuinely needs review, you're submitting a two-page process description instead of a campaign. The 71 days happened because we submitted creative before we'd agreed the reference pack. That's a sequencing error and it's mine. |
| “Even if I want this, privacy and IT security have to re-qualify you annually and that's four months.” | It's four months if we start cold, and last year we did. Your refreshed pack went into the vendor management portal last week — SOC 2, HIPAA and GDPR positions, the 21 CFR Part 11 documentation, and the DPA already executed and unchanged. That clock is running now, in parallel with you deciding whether this is worth doing, and it costs you nothing. Worth noting the same four months applies to anyone new, and they haven't started. |
Questions reps ask about this call
- What makes a pharma renewal call script different from a standard SaaS save call?
Three things. First, the calendar isn't fiscal — it's the study. Nobody signs during database lock or the two weeks before an interim analysis, so your bridge is almost always the next protocol's feasibility window, not this quarter. Second, switching isn't a migration, it's a re-qualification: vendor security review, GxP assessment, a new DPA, Part 11 documentation and often a fresh privacy review, all of which the buyer has to personally sponsor. Third, the buyer's damage is usually political. A VP, Clinical Operations who defended you in front of a CMO when cost per randomized patient moved the wrong way is carrying a wound your ticket log doesn't show. Ask about the slide, not just the SLA.
- What should I pull before a pharma save call?
The full 12-month ticket log with first-response times and escalation history; randomizations per site per month you sourced against the enrollment curve forecast; screen failure rate on your referrals split by reason — eligibility, washout, lab values; cost per randomized patient by quarter; site activation cycle time on sites you touched versus the rest; seat and workflow usage by function; any site that hit a login you promised wouldn't exist; the MLR review log with round count and days; your own CSM turnover; and every QBR commitment you didn't deliver. Then check whether the person who signed still owns the study budget after the last re-org — often they don't.
- Should I discount if we genuinely had a bad year?
No. A price cut reframes twelve months of delivery failure as a pricing dispute, tells them list was always soft, and resets your floor permanently. Service credits for the specific months affected are the honest instrument — finite, specific, and tied to what actually broke. Better still, write the SLA and a performance threshold into the contract with credits attached: screen failure at or under a stated rate over the first sixty referrals, four-hour first response on P1, a break clause at six months. Pharma buyers respond to a vendor who volunteers to be measured, because that's how they contract with CROs already.
- How do I handle the renewal landing during database lock or a topline readout?
Stop asking for a signature and ask for work instead. Say plainly that this isn't a signature conversation, then bridge to the next protocol: the sites for that study are being selected now and feasibility takes 90 days whatever happens with the readout. Ask for two hours with the feasibility lead to map the site list against the draft I/E. If you're doing useful work in week three, the paperwork in week five is administrative. If you push for signature during lock, you'll get a deferral that hands the competitor six more weeks.
- Who else needs to be in the room besides the person who signed last year?
At minimum the Head of Patient Recruitment & Site Engagement — usually your power user and often the reason you're still being considered — plus whoever now owns the study budget line, which after a re-org may be the Executive Director, Clinical Development rather than the VP, Clinical Operations. If any part of your scope touches HCPs, get the Director, Field Medical into the MLR scoping conversation early. And find out whether procurement already holds the competitor's quote; most stalled pharma renewals die in vendor management, not in the business.
- How do I practise this call before I make it?
Run it out loud against a buyer who fights back the way a real VP, Clinical Operations does — someone who names the ticket number back at you, quotes their own screen failure rate by criterion, mentions the CRO escalation log, and says the words "your predecessor promised me that in the January QBR." DrillCall lets you drill the opening thirty seconds until you can name your own failures without flinching, and rehearse the moment where you refuse to discount and offer contractual credits instead. That's the exchange most reps fold on, and it's the one that decides the account.