Pharma · Pricing Negotiation Call
Pharma Pricing Negotiation Script: Holding Your Number After the Clinical Ops Technical Win
You've already won this one. The Head of Patient Recruitment & Site Engagement ran your pre-screen logic against the actual I/E criteria on protocol version 4.2, the VP of Clinical Operations sat in on the site-facing demo and asked whether coordinators needed a login (they don't), and last Tuesday she told you her Executive Director of Clinical Development is aligned. Nobody is re-evaluating anybody. What's left is the number — and in pharma, the number is not one number. It's a program build fee, a per-randomized-patient rate, a pass-through structure, a payment schedule, and a work order sitting under an MSA that procurement wants to benchmark against a fair market value band somebody built two years ago from a different therapeutic area.
This call will not feel like a fight. It will feel like a helpful conversation with someone who is on your side and just needs help getting it through sourcing. She'll open with "honestly, the study budget was locked at protocol finalization, we've got about half that," she'll mention what the CRO quoted for enrollment rescue in the change order, she'll offer you a case study as if it were cash, she'll wonder aloud whether it's cleaner to pick this up after the DSMB interim — and after each one she will go quiet and let you talk. Ten minutes of that and you've handed back thirty points and gotten a maybe.
The posture that works: stop selling, protect the per-randomized-patient rate above everything else (that rate becomes the benchmark every future protocol in this portfolio gets priced against), discount the one-time program build instead, and never move price without moving scope or getting something named in return. Your leverage is real — she's spent eleven weeks on this, burned political capital telling her ED it's you, and 40% of her sites still aren't green-lit while the burn runs regardless. Below is the script.
The pricing negotiation call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial — your three numbers, in pharma units
Write these down. Don't dial without them. ASK (what's on the quote): $1.42M — $220K program build (I/E-driven pre-screen logic, IRB-submittable recruitment materials, site enablement for 62 sites) plus $6,000 per randomized patient against a 200-randomization ceiling. TARGET: ~$1.28M, with the per-randomized-patient rate intact. FLOOR: $1.24M with my VP's sign-off. Below $1.15M I don't have a business and I say so. The rate I never move: $6,000 per randomized patient. That number goes into their vendor master and every protocol in this program gets priced off it for the next four years. I can ramp it for a first tranche, I can defer it, I will not cut it. The things I can give: the program build fee, payment terms, a deferred first invoice into the next fiscal, a ramped rate on the first 25 randomizations, monthly enrollment governance with my exec sponsor, an uplift cap on the next work order. The things I want back: the second protocol in the program named in the MSA, work order signed by a date, the vendor security questionnaire and DPA in my inbox this week, two sponsor reference calls, a blinded-then-named case study with an owner, and pre-qualified vendor status so protocol two doesn't restart the GxP assessment. Also know: who actually signs the work order (her, her VP Clin Ops, or clinical finance), whether sourcing has a category benchmark for recruitment vendors, and whether their fiscal year end is pressuring them, not me.
- 2
Opening — make her re-state the yes before she anchors
"Before we get into commercials — last week you said the team's aligned, that this is the direction, and that Dev's on board. Is that still where you are?" [Let her say yes. Out loud. It is much harder to threaten to walk twenty minutes after confirming you've won.] "Good. Then I'm not going to re-pitch anything. Let's spend the time on what has to be true to get a work order signed."
- 3
Reset the ratio in her numbers, not yours
"Just so we're measuring against the same thing. When we mapped this with your feasibility lead: you need 180 randomizations, you're tracking at 0.4 randomizations per site per month against a forecast of 1.1, and 40% of sites still aren't green-lit. Your run rate is $6.8M a month. The model we built has you pulling LPI in by roughly six weeks, and your screen failure rate coming down from 38% because we pre-screen against your actual I/E, not a marketing landing page. "The proposal on the table is $1.42M. That's about $7,900 all-in per randomized patient at the volumes we modelled, against six weeks of burn you don't spend. That's the shape of it. So — what needs to happen to get this signed?" [You are not justifying the price. You are establishing the ratio the discount gets measured against. Then stop talking.]
- 4
The low anchor — "the study budget was locked at protocol finalization"
Do not counter. Do not react to the figure. Get curious about how it was built. "Help me understand how you got to $700K. Is that a line clinical finance has already approved for recruitment on this protocol, or is it what's left in the study budget after the CRO's forecast?" Then the distinction that decides the deal: "Because there's a difference between 'there's $700K in the recruitment line' and 'there's $700K in the recruitment line and $4M of change-order money sitting with the CRO that's already been provisioned for exactly this problem.' Which one are we in?" If the number is genuinely hard, move scope — never price alone: "I can build you something at $700K. It won't be this. It's your 18 highest-potential sites instead of 62, it's the US only, and it's no second-tranche media if the curve doesn't move. Do you want me to price that version, or do we work on how to fund the full scope out of the study budget?"
- 5
The CRO change-order comparison
This is the pharma version of the competitor quote. Assume the number is real and assume it isn't the same thing. "That's a real number, I believe you. Can you send me the change order? Not to match it — I want to see the unit. Nine times out of ten the CRO's figure is per referral or per consented patient, not per randomized patient, and it excludes media spend, excludes the pre-screen build, and excludes the site-facing coordination. Those land back on you in month four as a second change order." Then: "And the honest question — if their number were the same as mine, would you still be having this conversation with me? Because their forecast is the one that produced 0.4 randomizations per site per month. We're not replacing them. We work alongside the CRO, and on two studies the CRO asked for us because they were the ones taking the escalation call from the sponsor every Friday."
- 6
The fair market value / procurement band
"Fair enough — what's the band built on? If sourcing benchmarked recruitment vendors on cost per referral, we're going to look expensive, because we don't get paid for referrals. We get paid on randomizations. Those are different units and the comparison will always come out wrong. "Here's what I'd offer: give me thirty minutes with Katrin in sourcing and I'll walk her through the unit conversion — cost per randomized patient, against your actual screen failure rate. If she still says we're outside the band after that, I'll take that seriously. But I don't want you defending my pricing model to procurement on my behalf with the wrong denominator." [This also moves you from adversary to ally, which is where you need to be for the rest of the call.]
- 7
The case-study trade — priced, and MLR-aware
When she offers to be a reference, treat it as currency and put a price and a date on it. "I'd genuinely value that, so let's make it real rather than a nice sentence. What can you actually commit to? Because a named case study with your logo goes to corporate comms and probably PRC, and I know what MLR cycle time looks like — two to three rounds, six to twelve weeks, and that's if it gets prioritised. "So here's the version I think you can actually deliver: a blinded case study — 'a top-20 sponsor, Phase III, immunology' — with the enrollment curve and the screen failure delta, reviewed and approved within 120 days of the first randomization. Plus two reference calls to peer sponsors, names agreed by us both. Plus you and I on a panel at SCOPE if the numbers hold. Written into the work order. "That's worth real money to me and I'll pay for it. Can you commit to it, and who signs off — comms or your ED?" [If she can't name an owner and a date, the discount comes off the table. Warmly. "Then let's not price something neither of us can deliver."]
- 8
The delay threat — "let's pick this up after the DSMB interim"
Don't panic and don't buy the quarter with margin. Make her do her own cost-of-delay maths out loud. "That's your call and I'll still be here. Practically though — site activation cycle time on this program is running 118 days contract to green-light. If we start the vendor qualification and the site enablement in March instead of January, we're activating in July, and your FPI-to-LPI window doesn't move because the DSMB moved. Does the enrollment curve survive that? "And the sites we've identified in Georgia and Poland — your feasibility team said those were the ones you wanted first. Do they still have capacity in Q3, or do they get eaten by the other eleven studies the coordinators are running?" Then offer structure, not discount: "If the issue is cash timing rather than the decision, I can solve that. Sign the work order this month, first invoice 1 April, build fee split across two quarters. You get this price and the money lands in the fiscal year you want it in. That costs me nothing. Ten points off costs me a lot."
- 9
The silence
She names a figure and stops talking. This is where the margin leaks. Rule: you may not improve your own offer twice in a row. After she goes quiet you have exactly two moves — say nothing, or ask a question about process. [Count to seven.] "…What's your reaction to that?" Or: "Once we've agreed the number, what's the approval path — does it go to Dev, or straight to sourcing?" Never fill silence with a number. The pause was the tactic.
- 10
The concession ladder — protect the rate, spend the build fee
Each move smaller than the last, each one traded, each one explained. Move 1 (≈8%): "I can take the program build from $220K to $110K. Here's what I need to justify it: the work order signed by the 26th, and your security questionnaire and DPA template in my inbox this week so privacy and IT run in parallel. Give me those two and I'll take it to my VP today." Move 2 (≈2%): "I can ramp the first 25 randomizations at $4,800 while we prove the curve. What I need for that is protocol two named in the MSA — not committed volume, just named — and two reference calls to sponsors I'll agree with you." Move 3 (final, structural, zero points): "I can't go further on the number. What I can do is net-60 instead of net-30, and monthly enrollment governance with my exec sponsor in the room. That's the last thing in my drawer." The line that keeps the rate intact: "I'll flex the build. I won't cut the per-randomized-patient rate, and I'll tell you why honestly — the moment $5,200 goes into your vendor master, every protocol in this program gets priced off it and I'll never get it back. You'd do the same. Take the build fee instead; it's a one-time cost and it doesn't set a precedent for your team either."
- 11
Using your VP properly — once, and for a trade
"$1.15M is outside what I can sign. I can go to my VP, but I can't walk in with just a request — I need an argument. If it's the second protocol named in the MSA and prepay on the build fee, I've got something to take in. Give me that and I'll go fight for it." Use this once. When you come back, come back final, and say why it's final: "He came back at $1.28M and he was clear that's it — it's tied to the 26th and to protocol two being in the MSA. If either of those moves, it re-approves and I don't think it comes back the same."
- 12
Landing it — the pharma signature path is longer than 'legal'
Confirm verbally, then in writing within the hour. And in pharma, 'signed' has four gates: "So let me read it back: $1.28M — $110K build, $6,000 per randomized patient with the first 25 ramped at $4,800, 200-randomization ceiling, net-60. From your side: work order signed by the 26th, protocol two named in the MSA, blinded case study within 120 days of first randomization, two reference calls. "Signature path — who executes the work order, you or Dev? Is legal already looking at the MSA redlines? Where are we on vendor qualification and the GxP assessment, and has privacy got our DPA? And does a PO need raising, or does this go against the study budget directly? "I'll send the revised work order in the next hour and I'll hold fifteen minutes Thursday to confirm sourcing is clear." Then the last line that protects the deal: "And to be straight with you — this number is tied to those terms and that date. If the 26th moves, I have to re-approve it. I'd rather tell you now than surprise you in three weeks."
- 13
Staying warm
Throughout, you are on her side of the table arguing with your own company on her behalf. Say it out loud: "I want to get this done." "Let me see what I can build." "I'll go fight for that." A firm no delivered warmly gets respected. A soft yes delivered nervously gets pushed a fourth time. Buyers who are good at this — and a Head of Patient Recruitment who has been through six CRO bid defences is very good at this — enjoy negotiating with someone who is also good at it. Losing your nerve is what invites the fourth ask.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before we get into commercials — last week you said the team's aligned and Dev's on board. Is that still where you are?
Buyer
It is. Your pre-screen against 4.2 was the cleanest thing we saw. Dev's comfortable. This is purely a commercial conversation now — and I'll be honest with you, the study budget was locked at protocol finalization. What's in the recruitment line is about $700K. So we're a long way apart.
Rep
Help me understand how you got to $700K. Is that a number clinical finance has approved for recruitment on this protocol, or is it what's left in the line after the CRO's original forecast was funded?
Buyer
It's what's in the line. There's obviously change-order money in the program, but that sits with Dev and I'd have to justify pulling it.
Rep
Then that's the conversation, isn't it — not whether $1.42M is the right price, but whether it comes out of the recruitment line or out of the money already provisioned for the thing that's gone wrong. You're at 0.4 randomizations per site per month against a forecast of 1.1 and 40% of sites aren't green-lit. Where does a month of slip get charged today?
Buyer
To the program. Fair point. But I'll tell you what I'm weighing it against — the CRO came back with an enrollment rescue change order at $3,900 a patient. Sourcing has a fair market value band for recruitment vendors and you're sitting above it. So even if I wanted to fund you, Katrin's going to bounce it.
Rep
Send me the change order — not to match it, I want to see the unit. Is $3,900 per referral, per consented patient, or per randomized patient? Because at a 38% screen failure rate those are three completely different numbers, and I'd bet the change order also excludes media and the pre-screen build. On the FMV band — what's it benchmarked on? If sourcing built it from cost per referral, we'll always look expensive, because we don't get paid for referrals. Let me take thirty minutes with Katrin and do the unit conversion myself. I don't want you defending my pricing model with the wrong denominator.
Buyer
I'll ask her. Look — I want to make this easy for you too. We'd be very happy to be a reference. We're a top-20 sponsor, that's worth something to you. Does that get us closer to a number that starts with a nine?
Rep
It genuinely is worth something and I'll pay for it — but let's make it real rather than a nice sentence, because I know what happens next. A named case study with your logo goes to comms and probably PRC, and MLR cycle time here is what, two to three rounds, six to twelve weeks? So the version I'll actually price is: blinded case study — top-20 sponsor, Phase III, immunology — with the enrollment curve and the screen failure delta, approved within 120 days of first randomization, plus two reference calls to sponsors we agree on. Written into the work order. Can you commit to that, and who signs it off — comms or Dev?
Buyer
Comms would have to. I can't promise the 120 days.
Rep
Then let's not price something neither of us can deliver — I'd rather take the reference calls, which you control, and leave the case study out of the commercials. Here's what I can do instead, and it's tied to two things. I'll take the program build from $220K to $110K. What I need for it: the work order signed by the 26th, and your vendor security questionnaire and DPA template in my inbox this week so privacy, IT and the GxP assessment run in parallel rather than sequentially. That's $1.31M.
Buyer
$1.15M and I'll get it through Dev this month.
Rep
…
Buyer
…I'm serious. That's the number I think I can defend.
Rep
I hear you. What's the approval path once we've agreed the number — does Dev execute the work order, or does it go to sourcing first?
Buyer
Dev signs, Katrin has to release the PO. Honestly, if we can't land this in the next fortnight I'd rather park it until after the DSMB interim in March. Cleaner for everyone.
Rep
That's your call and I'll still be here in March. Practically though — your site activation cycle time is running 118 days contract to green-light. Start in March and we're activating in July, and the DSMB moving doesn't move your LPI date. The Georgia and Poland sites your feasibility team flagged as first-wave — do they still have coordinator capacity in Q3, or do they get eaten by the other eleven studies? And if the issue is cash timing rather than the decision, I can just solve that: sign this month, first invoice 1 April, build fee split across two quarters. You get the money in the fiscal year you want it in and I don't have to touch the price.
Buyer
That actually helps. But $1.31M still isn't going to survive Katrin.
Rep
Then give me an argument I can take upstairs. I can't sign $1.15M. What I can do is go to my VP with a ramp — first 25 randomizations at $4,800 while we prove the curve — if protocol two is named in the MSA. Not committed volume, just named, so we're not restarting vendor qualification from zero next year. That gets us to $1.28M. What I won't move is the $6,000 per randomized patient, and I'll be straight about why: the moment a lower rate goes into your vendor master, every protocol in this program gets priced off it and I never get it back. You'd hold the same line. Give me protocol two and the 26th, and I'll go fight for the ramp today.
Buyer
Naming protocol two I can do — it's the same TA, same feasibility team. Get me the ramp and I'll walk it into Dev on Thursday.
Rep
Done. So: $1.28M — $110K build split across two quarters, $6,000 per randomized patient with the first 25 at $4,800, 200-randomization ceiling, first invoice 1 April, net-60. From you: work order signed by the 26th, protocol two named in the MSA, two reference calls, and the security pack to me this week. Revised work order in your inbox within the hour, and I'll hold fifteen minutes Thursday after you've seen Dev. One thing so it's not a surprise later — that number is tied to the 26th and to protocol two. If the date slips it re-approves, and I don't think it comes back the same.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Sourcing benchmarks recruitment vendors at a fair market value band and you're above it.” | What's the band built on? If it was benchmarked on cost per referral, we'll always look expensive, because we don't invoice for referrals — we invoice for randomizations. At your current screen failure rate of 38%, a $1,200 referral is a $1,900 randomization before anyone's absorbed the screening cost at site. Let me take thirty minutes with your sourcing lead and do the unit conversion myself, with your I/E and your actual screen failure history. If we're still outside the band after that, I'll take it seriously — but I don't want you defending my pricing model with the wrong denominator. |
| “Our CRO quoted enrollment rescue at $3,900 a patient in the change order. You're 50% above that.” | That's a real number and I believe it. Send me the change order — not to match it, but to check the unit. Is $3,900 per referral, per consented patient, or per randomized patient? And does it include media, the pre-screen build against protocol 4.2, and the site-facing coordination, or do those come back as a second change order in month four? Then the honest question: if their number were identical to mine, would you still be choosing them? Their forecast is the one that produced 0.4 randomizations per site per month. We're not replacing them — we've been added sponsor-direct on studies where the CRO asked for it, because they were the ones taking the Friday escalation call. |
| “We're not paying a program build fee. The last vendor bundled it into the per-patient rate.” | They did, and that's exactly why their per-patient rate looked so ugly by patient 40. I'd rather show you the build honestly than bury it. That said — the build is the line I'll flex, because it's a one-time cost and it doesn't set a precedent for either of us. I'll take it from $220K to $110K. What I need in return is the work order signed by the 26th and your security questionnaire this week so privacy and the GxP assessment run in parallel. What I won't do is bury it in the rate, because then the rate is the thing you're stuck with on protocol two. |
| “Make it fully performance-based. We'll pay per randomized patient, nothing up front.” | I'll take most of the risk — the majority of my revenue already sits on randomizations, which is more than your CRO is carrying. What I can't do is fund the build for free, because the build is the thing that makes the randomizations happen: encoding your I/E, getting the materials IRB-submittable, enabling 62 sites without a coordinator login. If that goes unfunded, I'm incentivised to send volume and let your sites eat the screen failures — which is precisely what happened to you last study. Here's the middle: build fee halved and split across two quarters, and I'll ramp the first 25 randomizations while we prove the curve. That's me carrying the risk on the part I control. |
| “Vendor qualification, privacy, IT security and the GxP assessment take four months. Let's agree the number then.” | They take four months if we start them cold in March. Send me the questionnaire and DPA template this week — I've got the completed pack, SOC 2, the HIPAA and GDPR positions and the Part 11 documentation ready to go. That runs in parallel with Dev signing. The reason I want the number now, not in four months, is that the price is built off a 26th signature and a Q1 site enablement window; if we're activating in July instead of March, it's a different scope and a different quote. Nothing about starting the security clock costs you anything or commits you. |
| “Let's park it until after the DSMB interim — cleaner for everyone.” | That's your call and I'll still be here. But the DSMB moving doesn't move your LPI date, and your site activation cycle time is 118 days contract to green-light. Park until March and you're activating in July, at which point the Georgia and Poland sites your feasibility team wanted first are absorbed by the other eleven studies their coordinators are running. If the real issue is cash timing rather than the decision, say so and I'll fix it for free: sign this month, first invoice 1 April, build fee split across two quarters. You get this price and the spend lands in the fiscal year you need it in. |
Questions reps ask about this call
- What should I have written down before a pharma pricing negotiation call?
Three numbers and a trade list. Ask (what's on the quote — build fee plus per-randomized-patient rate plus volume ceiling), Target (where you genuinely expect to land, usually 5–12% off), and Floor (the number needing VP approval, and the number where you walk). Then the trade list: what you can give that doesn't touch the rate — build fee, deferred first invoice, ramped first tranche, net-60, uplift cap, monthly enrollment governance — and what you want back: signature date, protocol two named in the MSA, the security questionnaire and DPA this week, named reference calls, a blinded case study with an owner. Nothing leaves the left column without something specific coming from the right.
- Should I discount the per-randomized-patient rate or the program build fee?
Almost always the build fee. The per-randomized-patient rate goes into the sponsor's vendor master and becomes the benchmark that every future protocol in that program, and often adjacent therapeutic areas, gets priced against. You will never recover it, and procurement will hold you to it at renewal. The build is a one-time line: cutting it costs you once. Say this out loud to the buyer — clinical ops leaders respect it, because they run the same logic on their CRO unit rates.
- How do I answer "our CRO will do this cheaper in a change order"?
Ask for the change order and check the unit before you say anything about price. CRO enrollment-rescue figures are frequently quoted per referral or per consented patient, and typically exclude media spend, the pre-screen build against the current protocol version, and site-facing coordination — all of which return as a second change order. Then ask the leverage question: "if their number were identical to mine, would you still be choosing them?" The answer is usually no, because the CRO's forecast is the one that produced the enrollment shortfall in the first place. Never say the CRO is worse; say precisely what isn't in the quote and what it costs.
- How do I price a case study when the sponsor's comms and PRC will take months to approve it?
Don't price the thing they can't deliver. A named, logoed pharma case study goes through corporate comms and often PRC — two to three rounds and six to twelve weeks is normal, and it frequently dies. Trade for what the buyer personally controls: two named reference calls to peer sponsors, an introduction to another therapeutic area team, or a blinded case study ("top-20 sponsor, Phase III, immunology") with a named owner and a 120-day deadline written into the work order. If they can't name an owner and a date, take the discount off the table — warmly.
- They want to push the PO past the DSMB interim or into the next fiscal. Do I discount to hold the quarter?
No — solve the actual problem, which is nearly always cash timing rather than the decision. Offer a deferred start: sign the work order this month, first invoice on the first day of their new fiscal, build fee split across two quarters. That costs you nothing. Before you offer it, make them do the delay maths out loud: at 118 days contract to green-light, a two-month slip pushes activation into a quarter where their first-wave sites have no coordinator capacity, and the DSMB moving does not move their LPI date or their monthly burn.
- What do I do when the buyer names a number and then says nothing?
Nothing, for seven seconds. The rule is that you may not improve your own offer twice in a row. After the silence you have two legal moves: stay quiet, or ask a question about process — "what's the approval path once we've agreed the number, does the ED execute the work order or does sourcing release the PO first?" Never fill the pause with a number or a sweetener. In a pharma deal the buyer has usually been through multiple CRO bid defences; the silence is deliberate, and paying for it teaches them there's another round in you.