Coordinate a Banking Services RFP Response

A procurement lead sends over an RFP for banking services with a tight response date, then asks you flat out whether you can match a competitor's number. The RFP itself is thin on the details that actually drive pricing. You want to keep the relationship warm and the deal alive, but you cannot invent a fee or promise a dedicated team just to answer the question in the room. This conversation asks you to hold two things at once, respect for the customer's process and respect for your own bank's review requirements.

Why this conversation goes wrong

Procurement teams work on their own clock. They have a deadline from their leadership, a shortlist to narrow, and often a competing bid already in hand. When they ask you to match a number, they are not trying to trap you. They are trying to move their own process forward, and a fast answer feels like progress to them.

The trouble is that a real answer on pricing depends on facts the RFP has not supplied yet. Transaction volumes, implementation scope, service level requirements, none of that may be spelled out. If you answer the pricing question directly, you are guessing. If you answer the guarantee question directly, you may be committing your bank to staffing or terms nobody on your side has approved. Either mistake damages your credibility later, when the real numbers come back and do not match what you said on the call.

The other way this goes wrong is overcorrection. Some bankers get so worried about promising too much that they give the customer nothing, no timeline, no next step, no sense that the bank is engaged. That reads as disinterest, and procurement will read it that way even if your intent was caution.

How to prepare

Before you get on the call, read the RFP closely and mark what is missing. Most RFPs leave gaps in at least a few areas that matter for pricing and delivery.

1. Identify who on the customer's side owns transaction volume data, since that number drives most of the pricing model.
2. Note what implementation support the RFP implies but does not spell out, such as timeline, integration needs, or dedicated staffing.
3. Confirm the customer's actual decision date, not just the stated response date, since those two dates are often different.
4. Identify your own internal pricing and implementation contacts so you know exactly who receives the handoff once you have real numbers.

Doing this before the call means you are not scrambling for internal names while the procurement lead is waiting on the line. It also means your questions sound like due diligence rather than stalling.

What to say

Say the procurement lead at Meadow Health, a hospital system running this RFP, opens with pressure. She says, "We have a bid on the table from another bank that comes in well under your current fee structure. Can you match that number today so we can move forward?"

You answer without dodging the question, but without inventing a number either. You say, "I want to give you something you can actually rely on, not a guess. To make this comparison fair, I need to confirm your current monthly transaction volumes and what implementation support your team expects during rollout. Who on your side can get me those figures?"

She says, "Our treasury team ran volumes last quarter. I can have that file to you today, but our committee needs a response by Friday."

You say, "Friday works if I get that file this afternoon. I will route it straight to our pricing and implementation team and flag your Friday deadline so it gets priority. What I can commit to right now is that any number you receive from us will hold up under review. I am not going to give you something on this call that gets walked back next week."

That last line matters more than it sounds. It tells the procurement lead you take the process seriously enough to get it right the first time, which is a stronger signal than a fast number that turns out to be wrong.

Mistakes to avoid

Do not name a fee or a rate on the call just to keep the conversation moving. A number you cannot support gets remembered, and walking it back later costs you more credibility than taking a day to get it right.

Do not promise a dedicated implementation team, an expedited timeline, or any staffing commitment unless someone with authority to approve that has already signed off. Procurement will hold you to whatever you say, formally or not.

Do not treat a verbal request from one procurement contact as an approved proposal. RFP responses go through a review process for a reason, and skipping it to satisfy one phone call puts your bank at risk.

Do not ignore the customer's actual deadline. If Friday is real, say so to your internal pricing and implementation partners immediately, with names and source documents attached, not a vague note that something is due soon.

Do not go silent either. Giving the customer nothing while you sort out internal routing reads as disengagement. Tell them what you need, what you will do with it, and when they will hear back.

How to practice and score it

This conversation is hard to get right cold, because the instinct to just answer the question is strong and the discipline to slow down takes practice. Rehearsing it with a counterpart who pushes back the way a real procurement lead does, the way DealSpeak sets up, helps you find your own filler answers before a live RFP call exposes them.

A manager scoring this conversation should check for a few specific things. Did the banker ask about transaction volumes and implementation scope instead of guessing? Did the banker name a concrete next step and a realistic timeline instead of a vague promise? Did the banker avoid committing to a fee or a team without internal sign off? Those three questions separate a disciplined response from an improvised one.

If you handle a lot of commercial banking conversations, it helps to practice adjacent scenarios too. Working through how to map a commercial seasonal inventory plan builds the same muscle for asking precise scope questions before committing to numbers, and learning to frame a syndicated loan question carefully sharpens how you handle pressure to commit before terms are settled. Both live alongside more banking practice conversations built for commercial bankers working through exactly this kind of pressure.

Get this conversation right and procurement gets a partner who respects their process without stalling it. Get it wrong, either by guessing or by going quiet, and you lose the credibility that actually wins the business.

You can rehearse this exact conversation in the Banking practice conversations library before it happens for real. When you have this one down, read Map a Commercial Seasonal Inventory Plan next.