Handle a Procurement Request Before an RFP Is Issued

A procurement lead emails you two months before the formal process starts and asks for your best price. The question sounds simple, but it puts you in a tough spot. Answer it the wrong way and you either overstep your authority or leave the account looking unresponsive. This is one of the more common traps a key account manager in pharmaceuticals runs into, and it deserves a real plan instead of an improvised reply.

Why This Conversation Goes Wrong

Procurement teams often reach out early to test the market before they commit to a formal RFP. They want a sense of range, a feel for where a vendor will land, something to bring back to a director or a budget committee. That is a normal part of their job. The trouble starts when a key account manager treats the request as harmless and gives a number just to be helpful.

Once you name a figure, it becomes an anchor. Procurement will remember it, cite it later, and hold you to it even if the requirements change before the RFP is issued. You also create a fairness problem. If other vendors go through the formal process while you gave an early number outside it, your organization has effectively negotiated before negotiations opened. Legal and contracting teams built the RFP process to prevent exactly this. Skipping it, even with good intentions, weakens the position of everyone on your side of the table.

In pharmaceutical accounts the stakes run a bit higher. Procurement often coordinates with a group purchasing organization or a formulary committee, and an early number can ripple into decisions those groups make well before the RFP is public. A price you meant as a friendly estimate can end up in a spreadsheet that shapes the whole evaluation. That is why the goal in this conversation is not to be vague or unhelpful. It is to be precise about what you can and cannot do, and to say it in a way that keeps the door open.

How To Prepare

Before you respond to a request like this, know three things. Know your authorized pricing boundaries and who inside your organization owns pricing decisions before an RFP exists. Know who on your side handles contracting and legal review, so you can name a real person instead of a vague promise to follow up later. Know what your organization allows you to share before an RFP is issued, since most companies have a standard capability overview or a published pricing framework built for exactly this situation.

Pull up the account plan before you reply. Check whether procurement has approached this account before, what was shared last time, and whether any informal numbers already exist that you need to account for. If you do not know the RFP timeline or who owns requirements on the buyer's side, treat the conversation as a chance to learn that, not just a request to deflect. Write down the two or three questions you want answered before you pick up the phone or reply to the email. Walking in with questions ready keeps you from freezing when the buyer pushes back.

What To Say

Here is how a conversation like this can go.

The procurement lead says, "Can you send over your best price? We want a sense of where things could land before we go through the whole formal process."

You say, "I cannot negotiate terms outside the authorized process. I can walk you through our capabilities now, and I can connect you with the right contracting contact once requirements are set. What is driving the timing on your end?"

The lead says, "We expect to publish the RFP next month. My director wants a range before that goes out."

You say, "That is useful to know. I can send our standard capability overview today if that helps your director see what we bring, and I can have our contracting team reach out as soon as the RFP is confirmed. Who should receive that overview, and is there someone on your legal side I should loop in once we get to terms?"

Notice what each line does. The first response sets the boundary without sounding defensive, and it asks a real question, which keeps the conversation moving instead of shutting it down. The second response gives something of value, the capability overview, while making clear that pricing still runs through the authorized process. It also gathers two facts you actually need, who receives materials and who handles legal review. Neither response argues with the buyer or explains company policy at length. Both stay short, direct, and specific.

Mistakes To Avoid

A few mistakes come up again and again in this situation. 1. Giving a number just to be polite, even a soft range, since procurement will treat it as a real figure regardless of how casually you offered it. 2. Promising to beat a competitor's price when you have no idea what a competitor has actually offered, which can commit your organization to terms it never approved. 3. Agreeing to hold an informal commitment open until the RFP is issued, which creates an obligation your contracting team never signed off on. 4. Going around procurement to reach a clinical or research contact at the same account, which damages trust with the team that controls the formal process. 5. Staying silent or refusing to engage at all, which reads as unhelpful and pushes the buyer toward a vendor who answers questions, even the wrong way.

Each of these mistakes feels reasonable in the moment. That is what makes them dangerous. A rehearsed, specific response is the only thing that reliably beats the pull toward an easy but costly answer.

How To Practice And Score It

This conversation is easy to get wrong live and easy to get right with practice. Role play the exchange before a real procurement lead calls. Have a manager or peer play the buyer and push on the price question two or three times, since a real lead often will not accept the first boundary you set and will circle back with a different angle.

Score two things separately. First, did you protect contracting authority, meaning you never named a number, a discount, or a term outside the approved process. Second, did you keep the relationship moving, meaning you offered something real, asked a useful question, and named a next step instead of a dead end. A response that only does one of these is not good enough. A firm boundary with no offer sounds cold and leaves the buyer with nothing to bring back to their director. An offer with no boundary quietly gives away the thing procurement was actually asking for.

DealSpeak gives you a place to run this exact scenario before it happens with a real account on the line. The Pharmaceuticals practice conversations cover procurement escalations like this one alongside other situations key account managers face, including how to Run a Review Based on Facts After a Program Service Complaint and how to Coordinate a Scientific Resource for a Department Chair. Practicing the exact words, not just the general idea, is what makes the boundary sound natural instead of rehearsed when the real conversation happens.

A procurement lead who asks for your best price before an RFP is not doing anything wrong. Answer the question directly, protect the process, and give the buyer a real next step. Handled well, this exchange builds trust before the formal negotiation even starts.