Managing Client Reference Permission in an Asset Management RFP

A prospect asking for client references is testing more than your track record. It is testing whether you protect a confidential relationship under pressure, the same way a manager would if money were on the line. Give up a name without permission and you have already told the prospect something about how you handle client trust, and it is not the answer you meant to give.

Why This Conversation Goes Wrong

RFP leads under deadline pressure often treat a reference request like any other data field on the form. A consultant asks for two contacts, the lead scans the client list for a strong match, sends a name and a phone number, and moves to the next question. Nobody stopped to ask whether that client had agreed to be contacted. Nobody checked whether the account was going through a rough patch, whether the relationship owner had already promised the client a quiet quarter, or whether the client would say something during the call that hurts the pitch instead of helping it.

The pressure comes from three directions at once. The deadline is fixed and it will not move just because a permission check takes an extra day. The consultant frames the request as routine, so slowing down or asking questions feels uncooperative. And the RFP lead usually does not own the client relationship in question, which means they are making a judgment call about someone else's account under someone else's clock. Put those three things together and permission becomes an afterthought instead of a gate it should be.

How To Prepare

Preparation starts long before any consultant asks for a name. Build a standing list of clients who have already agreed to serve as references, organized by governance model, asset class, mandate size, and service history, and review it with the owner of client relations every quarter. When a request comes in, you are matching criteria against a list you have already cleared, not scrambling to find someone who fits and hoping they say yes on short notice.

Ask the consultant four things before you promise anything. What governance model and asset class do they want represented. What service experience matters most to them, a smooth onboarding, a market stress event, a change in mandate. Do they need names in the written submission itself or only once you reach the finalist stage. And what is the real deadline, not the one implied by urgency but the one you can confirm in writing.

Route every request through the person who owns that client relationship, with no exceptions, even when the match looks obvious and the clock is tight. That person knows things you do not, an unresolved fee dispute, a pending redemption, a compliance concern that makes any outside contact a bad idea right now. Skip that step because you feel confident the client will say yes, and you are gambling with someone else's relationship based on your own guess.

If your team is also managing a compressed timeline on the rest of the submission, the same discipline applies across the whole RFP. Protecting Review Quality When an RFP Deadline Moves Forward covers how to hold your standards when the schedule gets shorter, and the logic carries over directly, a moved deadline is not permission to skip a check on someone else's confidential relationship.

What To Say

A consultant says, "Send me two committee contacts by end of day, we want to call them before the finalist meeting."

The RFP lead answers, "I can tell you today whether we have a client that matches your criteria. I cannot share a contact without permission for this specific search. Can you tell me the governance model and asset class you want represented, and whether you need names now or at the finalist stage."

The consultant pushes back. "We are on a tight schedule. Other managers gave us names within the hour."

The RFP lead holds the line without getting defensive. "I understand the schedule matters to you. I am not declining, I am following the process that protects every client we represent, including whoever we put forward for you. I will confirm with the relationship owner today and get back to you by five o'clock with either a contact or a clear next step."

Notice what makes this work. The RFP lead never says no outright and never blames the process on someone else. Every sentence ends with a specific action and a specific time. The consultant walks away with less than they originally asked for, but they get something concrete to hold onto, which is usually enough to stop the pushing.

Mistakes To Avoid

Do not name a client or confirm their availability before permission is granted, even informally, even in a passing comment meant to be reassuring. A line like "I think Client X would be great for this" already tells the consultant who to expect, and walking that back later costs you more credibility than a short delay ever would.

Do not share contact information as a placeholder with a promise to confirm later. Once a name and a phone number leave your hands, you have lost control of the timeline, and the client may get a call before anyone asked them.

Do not let a finalist deadline change the standard. A rushed process is exactly when a client relationship is most likely to get treated as a sales asset instead of a trust that has to be earned every single time it gets used.

Do not go quiet instead of pushing back. If you cannot meet the exact ask, tell the consultant what you can do and by when, rather than leaving them without an answer while you sort things out internally. Silence reads as evasive even when your intentions are good.

How To Practice And Score It

Run this scenario with a reference who looks perfect on paper and has not consented, a large mandate, the exact asset class the consultant wants, a strong service story, and no signed permission. That gap is where RFP leads slip, because the temptation to just make the call yourself is strongest when the fit looks obvious.

Score the exchange against a short checklist. Did the RFP lead ask for the client profile and timing before promising anything. Did they name an owner of client relations rather than deciding alone. Did they give a specific date instead of a vague "soon." Did they avoid naming or describing the client before permission came through. A manager reviewing the recording should be able to answer each question with a plain yes or no, with no interpretation needed.

DealSpeak's Asset Management practice conversations give RFP leads a place to run this exact scenario against an AI counterpart that pushes back the way a real consultant does, with a scored transcript afterward showing exactly where the line held and where it broke. Teams that build their evidence base ahead of time, as described in Build an Evidence Register Before Writing an Asset Management RFP, find this conversation much easier, because the permission status is already known well before the question arrives.

The Close

A client reference is not a data field. It is a relationship someone else has trusted you with. Protect it the same way under a tight deadline as you would with no deadline at all. The RFP lead who holds that line, calmly and with a clear next step, earns more trust from the consultant than the one who hands over a name just to make the pressure stop.