The Upsell Script for Pharma Customers: Turning a Study Check-In Into an Expansion

1. 1

   0. Pre-call usage audit — do not dial without this

   Fill these in from your own systems, not from memory: **Adoption by site, not by seat.** How many activated sites are actually routing referrals through you versus sitting dark? "62 activated sites on the 301, 41 pulling referrals from the queue weekly, 21 that have never logged a pre-screen." Name the dark corners by region — Southeast US, Poland, the two Japanese sites that green-lit in February and have randomized zero. **Depth.** Which parts of the scope are they using? Pre-screening yes, referral routing yes, the site engagement dashboard never opened. Last login of the exec sponsor — if the VP, Clinical Operations hasn't logged in since the kickoff, do not build the call around a dashboard. **Outcome — one number, theirs.** Randomizations per site per month before you and after you. Screen failure rate on your referrals versus site-sourced. Cost per randomized patient. Pull it from their enrollment report or their own QBR language, not your case study. **Commercials.** Contract value, study-level or program-level, renewal or extension date, who signed it — often the Head of Patient Recruitment & Site Engagement, countersigned by procurement — whether that person is still in the role, discount level, and whether an add-on can co-term to the master services agreement. **Support and site escalations.** Any open issue with a coordinator, any complaint that landed with the CRO's project manager, any referral batch that screen-failed badly. A bad week in Wrocław three weeks ago changes this entire call. **Champion status.** Is your champion still running the study? Have they been pulled onto launch readiness? Has a new CMO or a new Executive Director, Clinical Development landed above them? The test: can you say one thing about their study they'd be mildly surprised you knew? If not, do the work.

2. 2

   1. Frame the call in the first thirty seconds

   "Thanks for the time. Two things, and I'll be straight about both. First — I pulled your randomization data by site for the last two quarters and there's a pattern in it I want to check with you, because I don't think it's about us, I think it's about which sites are getting fed. Second, depending on what you say about that pattern, there's a piece of what we do that may be relevant to the 301, and if I don't think it is by the end, I'll tell you and we'll skip it. Fair?" That's the whole opening. Agenda, homework, and a pre-commitment to walk away. Do not say the word "module."

3. 3

   2. Anchor on the result they already own — in their numbers

   Make them confirm out loud that the existing scope worked, before you go anywhere near new scope. "When we came on in March, the 41 sites we're feeding were averaging 0.7 randomizations per site per month against a forecast of 1.4. Last quarter those same sites were at 1.6. And the screen failure rate on our referrals came in at 22% against 38% on site-sourced. Does that match how it looks in your monthly, or am I reading it optimistically?" Then shut up. Their correction is worth more than your number — it tells you the metric they actually defend in front of the Executive Director, Clinical Development. Write their sentence down verbatim; it becomes line one of the business case they take to clinical finance. **If they can't confirm a result, stop the upsell.** Say it plainly: "Then let's not talk about anything new. Let's spend the twenty minutes on why you can't point to a number from what you're already paying for, because that's the conversation that matters before the extension comes up." That's not a lost call. It's the only version that protects the renewal.

4. 4

   3. Say the underuse objection out loud before they do

   They are sitting there thinking *21 of our sites have never used this.* Say it first and you're diagnosing. Let them say it and you're defending. "Here's what I'd push back on myself with if I were you. You've got 62 activated sites in scope and 41 pulling referrals. Twenty-one have never logged a single pre-screen. If I were sitting where you are, I'd be asking why I'd buy anything else before those 21 are live. So let me tell you what those 21 are actually doing. They're not idle. Eight of them are the CRO's second-tier site management group and the referrals are going through the coordinator's inbox instead of the queue — the work's happening, it's just invisible to your enrollment report. Six are in Poland where the DPA amendment is still sitting with your privacy team. And seven genuinely never onboarded, and that's on us, and I've got a name and a date for each of those." The reframe: dark sites are unrouted work, not wasted spend. Then be honest about whether the new scope touches them. Sometimes the answer is "it doesn't — you have an activation problem, not a gap in scope," and saying that buys you the right to come back after database lock.

5. 5

   4. Find the seam — diagnostic questions, no module talk

   Lead with where value leaks out of their workflow, not with what you sell. - "Once we hand a randomized patient to the site, who owns them from there? Is that the coordinator, the CRA, or nobody in particular?" - "What's your dropout rate through the primary endpoint looking like against what you assumed in the sample size calculation?" - "What generates the Monday morning fire drill on this study right now — is it activation, is it randomization, or is it retention?" - "Who's asking you for a number on this that you can't produce today? Is the CMO asking about the readout date?" - "When you scoped us originally, what did you deliberately cut because it was too big a bite at the time?" That last one is the highest-yield question on the call. Most pharma expansions were scoped and cut in the original bid — usually retention, usually the open-label extension, usually the second protocol. You're not selling something new. You're reopening a decision they already made once, under different timeline pressure.

6. 6

   5. Build the incremental case in their arithmetic

   The bar isn't "this is valuable." It's "this beats the next-best use of the same money and the same three weeks of my ops team." Four steps, out loud, with the price in the same breath. "Let me do this in your numbers and you tell me where I'm wrong. **The unit.** Your cost per randomized patient on the 301 is running about $11,400 all-in. Every patient who drops before the week-52 primary endpoint is a patient you have to replace, so that's $11,400 plus the calendar. **The volume.** You're at 19% dropout through primary endpoint against the 12% you powered on. On a target of 1,200 randomized, that gap is roughly 84 patients. **The capture rate.** If retention support closes half of that gap — and I'd rather under-promise to you than to your Executive Director — call it 42 patients. That's about $480,000 in re-randomization you don't spend, and it's the difference between hitting LPI in the protocol window and not. **The net.** It's $12,000 a month, one region, twelve months. $144,000. Against $480,000 that's a bit over 3x, and if you think my capture rate is generous, give me a number you believe and we'll rerun it right now." Handing them the pencil on the assumption is what makes this a business case rather than a pitch. And say the price before they ask for it — in clinical ops, a vendor who makes you ask for the number is a vendor who's about to hide something in the change order.

7. 7

   6. Cost the implementation in hours and names

   Budget is the stated objection. Bandwidth is the real one, and it's usually true — your champion is running database lock on one study while feasibility runs on the next. "Here's the honest ask on your side. One 60-minute session with whoever owns retention operationally — I think that's your clinical trial manager, not you. Then about two hours a week from that person for three weeks while we map the visit windows and the touchpoint schedule to the protocol. That's the whole implementation. What I'm not asking for: a new coordinator login. Nothing lands on the site. If a coordinator has to learn a new SOP for this, it fails, and I'd rather tell you that now than find out in month four. On our side we do the config, we draft the patient-facing touchpoints against your approved language, and my CSM runs the CRA briefing. If this needs more than four hours a week from your team, I've mis-scoped it and I'll say so." Put the work you'll absorb on the table here, not later as a concession.

8. 8

   7. The ask — small, specific, reversible, co-termed

   Do not ask for all three protocols and every region on call one. "Here's what I'd propose rather than a full scope change. Give me the US Southeast — that's 14 sites, the region with your worst dropout — for two quarters. Success criterion is yours, not mine: you tell me what dropout number through the primary endpoint makes this worth continuing. If we don't hit it, we stop, and there's nothing to unwind on the site side because they never had to do anything differently. If we do hit it, we extend to the rest of the 301 and to the 302 at your MSA anniversary, and we co-term it so you're managing one agreement and one vendor qualification, not two." Co-terming to the existing master services agreement is the most underused unlock in pharma expansion. It turns a new purchase — with a fresh vendor qualification, a fresh GxP assessment, a fresh IT security review — into an amendment to a supplier you've already cleared. Say that explicitly, because that's the part your champion repeats internally.

9. 9

   8. Check whether the buying committee moved

   The Head of Patient Recruitment & Site Engagement who signed the original scope may not be able to sign this one. "Last time this went through you and then procurement, and it sat under the study budget for the 301. Is that still the path, or has the threshold changed? And has anyone new landed above you since — I know you've got a new CMO." Also ask: "Does an amendment to existing scope re-trigger the GxP assessment, or does it ride on the qualification you already did?" If a new procurement policy, a new privacy lead, or a company-wide cost review has landed since your original deal, you are running a fresh evaluation dressed as an expansion. Better to know that on this call than in week six when the questionnaire arrives.

10. 10

    9. Close and document — write the email they'll forward

    Same day, short, structured. It contains: 1. The result they confirmed, **in their words** — "you said the 1.6 per site per month is the only reason the curve is holding" 2. The gap they described, in their words 3. The value math with their assumptions, including the capture rate they gave you 4. The price, stated plainly 5. The implementation ask in hours and named roles 6. The pilot scope, the region, the success metric they defined, and the decision date 7. The named next step with a date on the calendar Write it for the person they forward it to — the VP, Clinical Operations or the Executive Director, Clinical Development who wasn't on the call. Not for your CRM.

11. 11

    10. Park signals — when not to push

    Do not run the upsell if you see any of these. Push through them and you convert a renewable account into an at-risk one for an incremental line item: - An unresolved escalation from a site or from the CRO's project manager - Database lock inside four weeks, or a DSMB interim in flight - A champion who's just been moved onto launch readiness or a different program - A flat or declining referral trend you can't explain - A CRL, a clinical hold, or a failed interim on the parent program - A company-wide cost review or pipeline prioritisation announced in the last quarter When you park, park explicitly and give it a date: "You've got lock on the 12th. I'm not going to put anything in front of you before that. Can I have thirty minutes the week of the 20th, and I'll bring the same numbers?"

1. Rep

   Thanks for making the time. Two things and I'll be honest about both. First, I pulled randomization by site on the 301 for the last two quarters and there's a pattern I want to check with you. Second, depending on what you say about it, there's something in our scope that may be relevant — and if I don't think it is by the end of this, I'll say so and we'll skip it. Fair?

2. Buyer

   That's a longer agenda than a check-in. Go ahead, but I've got lock on the 302 in six weeks and I'm not signing anything this quarter, so calibrate accordingly.

3. Rep

   Noted, and I'll come back to that. The pattern: the 41 sites we're feeding were at 0.7 randomizations per site per month when we started in March. Last quarter they were at 1.6 against your forecast of 1.4. Screen failure on our referrals came in at 22% against 38% site-sourced. Does that match your monthly, or am I reading it generously?

4. Buyer

   The 1.6 is right. I'd argue about attribution — we also opened seven sites in the Southeast in that window and the CRO changed regional monitors. It wasn't all you.

5. Rep

   That's fair and I'm not going to claim it all. What I'd say is the screen failure number is harder to attribute elsewhere — the 22% is on referrals we pre-screened against your I/E, and that gap is 16 points. But let me get in front of the thing you're actually thinking. You've got 62 activated sites and 21 that have never logged a pre-screen. If I were you I'd be asking why I'd buy anything else before those 21 are live.

6. Buyer

   I have asked that. My Head of Patient Recruitment raises it every month. And frankly some of those sites are ones we paid activation costs on that have randomized zero patients, which is a conversation I'm already having with the CRO.

7. Rep

   Then let me split those 21 for you, because they're not one problem. Eight are under the second-tier site management org and the referrals are going through the coordinator's inbox — the work is happening, it just doesn't show in your report, and I can fix the reporting without touching the coordinator. Six are Poland, where your DPA amendment is still with privacy. Seven never onboarded and that's ours — I've got a name and a date for each. What I'm not going to tell you is that anything new fixes those 21. It doesn't.

8. Buyer

   Alright. So what is it you're actually here to sell me?

9. Rep

   Before I answer that — when you scoped us originally, what got cut because it was too big a bite?

10. Buyer

    Retention. We cut retention because we didn't believe a vendor could touch patients post-consent without dragging us through IRB and a re-consent cycle, and I still mostly believe that.

11. Rep

    Then let's do the arithmetic first and the IRB question second, because if the arithmetic doesn't work the IRB question is academic. You're at 19% dropout through the week-52 primary endpoint against 12% powered. On 1,200 randomized that's about 84 patients you have to replace at roughly $11,400 cost per randomized patient. If retention support closes half that — and I'd rather under-promise — that's 42 patients, call it $480,000, and more importantly it's the difference between hitting LPI in the protocol window and explaining a slip to your CMO. It's $12,000 a month, one region, twelve months. $144,000.

12. Buyer

    Your half is generous. And the money isn't the issue — the issue is that anything patient-facing post-consent goes back to the IRB as a protocol amendment, that's a central IRB cycle plus every local one, and I am not re-consenting 600 patients to save a line item. You've also been qualified as a pre-consent recruitment vendor. A patient-touching scope means privacy review, a new GxP assessment and probably Part 11 on whatever system holds the touchpoint record. That's four to six months of work I personally have to sponsor.

13. Rep

    Run it at your number then — what capture rate do you believe? And on the regulatory piece: the touchpoints are visit-window reminders and travel logistics, they carry no protocol-specified assessment and no source data, which is why on the studies where we do this it's gone in as an administrative amendment, not a re-consent. But I'm not going to argue that with you — I'd rather your regulatory lead tell me I'm wrong in a thirty-minute call than have me assert it. On qualification: we ride the MSA and the assessment you already did, and I'll send the Part 11 pack and the DPA today so it's in parallel, not sequential.

14. Buyer

    Two points, not four. And even at two points I'd want it in one region only — I'm not putting a new workflow across 62 sites while my team is doing lock.

15. Rep

    Two points is 24 patients, $274,000, so it still clears $144,000 — and one region is exactly what I was going to ask for. Southeast, 14 sites, your worst dropout region, two quarters. You define the dropout number that makes it worth continuing. Nothing lands on the coordinator — no new login, no new SOP. On your side it's one 60-minute session with your CTM and two hours a week from her for three weeks, and I'd start it after lock, not before.

16. Buyer

    After lock, and only if regulatory says it's an administrative amendment. If they say re-consent, this is dead and I don't want to hear about it again this year.

17. Rep

    Agreed, and I'll write it that way. Two things I need from you: thirty minutes with your regulatory lead and privacy in the next fortnight on process only — no patient materials, no content — and confirmation that an amendment to existing MSA scope doesn't retrigger procurement. Last time this went through you and then procurement under the 301 study budget. Is that still the path, or has the new CMO changed the threshold?

18. Buyer

    Threshold's the same for an amendment. New spend over $250k now needs three bids, which is another reason to keep this at one region. Send the recap and copy my Head of Patient Recruitment.

What usage data should I pull before an upsell call with a clinical operations customer?

Not seats — sites and outcomes. Pull: activated sites in scope versus sites actually routing referrals through you, split by region and by whoever's managing them (sponsor-direct, CRO, second-tier SMO); randomizations per site per month for your sites before and after you started, against their enrollment curve forecast; screen failure rate on your referrals versus site-sourced; site activation cycle time from contract to green-light where you touched it; and cost per randomized patient if they've shared it. Then get the commercial facts: MSA versus study-level contract, extension date, who signed, whether they're still in the role. The test is whether you can say one thing about their study that mildly surprises them.

How do I time an upsell around database lock, a DSMB interim, or a PDUFA date?

You don't push through any of them. Database lock inside four weeks, an interim analysis in flight, a CRL or a clinical hold on the parent programme — all park signals. But parking isn't retreating: use the call to book the specific next date and to point at the next protocol. "Your 302 starts enrolling in Q3, feasibility takes 90 days regardless, give me thirty minutes with your ops lead the week after lock." On the commercial side, a Senior Director, Commercial Excellence / Launch Readiness working against a PDUFA date they don't control will not commit budget to anything that's contingent on a label they haven't seen — so scope the pilot to something that holds value whether the date slips or not.

How do I expand scope without triggering a whole new vendor qualification?

Structure it as an amendment to the existing master services agreement and co-term it to the current renewal. Say that out loud on the call, because it's the sentence your champion repeats internally: one agreement, one supplier record, one qualification instead of two. Then ask directly whether the amendment retriggers the GxP assessment, privacy review or IT security — the answer varies by company and by whether the new scope touches patient data or moves from pre-consent to post-consent. Send the completed security questionnaire, DPA, SOC 2 and Part 11 documentation the same day so that clock runs in parallel with their evaluation rather than after it.

The customer says the CRO already owns the scope I'm trying to expand into. How do I handle it on an upsell?

Don't position it as replacement — sponsors don't enjoy renegotiating a CRO relationship mid-study. Ask for the number: what is the actual performance against what the CRO forecast in the bid defense, whether that's randomizations per site per month or dropout through the primary endpoint. If they're behind, the change order to fix it usually costs more than a parallel sponsor-direct channel. Frame yourself as running alongside, and if you have examples where the CRO welcomed it because they were the ones absorbing the sponsor's monthly escalation call, say so plainly.

Should I discount the add-on when a pharma buyer says the budget is committed?

No. Discounting teaches them the original contract was padded and that waiting produces a better price on every future expansion. Instead, ask what it's committed to and when it resets, then look for the redirection: a rescue line in the study budget, change-order money earmarked for the CRO, or an underperforming vendor line in the same budget. Anchor against their burn — if the run-rate is $6M a month, four weeks pulled forward on LPI reframes the ask entirely. And check the authority question in the same breath: a new CMO or a new procurement threshold requiring three bids over a certain figure turns your expansion into a fresh evaluation.

What if my champion has moved and I'm now dealing with someone new?

Treat it as a fresh evaluation with a head start, not an expansion. A new VP, Medical Affairs or Executive Director, Clinical Development has no ownership of the original decision and every incentive to re-examine inherited vendors. Run section 2 harder than usual — get the incumbent result confirmed in their numbers before you introduce anything — and check whether your original champion was promoted (good: an internal advocate one level up) or quietly sidelined (bad: your programme may be associated with their loss of standing). If it's the latter, park the upsell and spend the quarter rebuilding proof.

• All Pharma playbooksEvery call type for Pharma, in one place.

Other Pharma calls

• Cold CallPharma Cold Call Script: Getting Thirty Seconds With Clinical Ops and Field Medical Leaders
• Demo CallThe Pharma Product Demo Script for Clinical Operations Buyers Who Came to Find Where It Breaks
• Discovery CallDiscovery Call Questions for Pharma: A 25-Minute Diagnosis with Clinical Ops and Medical Affairs
• Pricing Negotiation CallPharma Pricing Negotiation Script: Holding Your Number After the Clinical Ops Technical Win
• Renewal CallPharma Renewal Call Script: How to Save a Clinical Recruitment Account Six Weeks Out
• Warm CallWarm Call Script for Pharma: Turning a Referral Into a Second Meeting With Clinical Ops

The same call in a neighbouring market

• Upsell Call for SaaSThe Upsell Script for SaaS Customers That Survives a Seat Utilization Report
• Upsell Call for Financial ServicesThe Upsell Script for Financial Services Customers: Expanding an Account Without Restarting Vendor Diligence
• Upsell Call for InsuranceUpsell Script for Insurance Customers: From Claims Account Review to a Recovery Module Expansion

Related reading

• Selling Into Pharma Clinical Ops: The Study Is Already Behind, and That's Your OpeningClinical Ops buyers live inside a timeline that is already slipping — here is how to sell into that without pretending to be a clinician.
• Upsell Teardown: The Account Review That Ended With Two Products and No DiscountA line-by-line teardown of a routine account review that turned into a two-product expansion at full price, including the exact language that held when the customer asked for a bundle discount.