Institutional Sales: Uncovering Investment Policy Constraints

An institutional allocator can sound genuinely interested in a strategy and still sit nowhere near an approvable mandate. The real limits live inside the investment policy statement, the delegation of authority, and whatever screen the retained consultant runs before a manager search reaches committee. A sales rep who skips past those limits to talk about fit spends weeks chasing a deal that a board policy was always going to block. The fix is not a sharper pitch. It is a short set of questions asked early, before you ever describe a manager as a match for the mandate.

Why This Conversation Goes Wrong

Reps treat a warm comment as momentum. When an allocator says a strategy sounds interesting, it feels awkward to respond with a question about what might block it. So the rep moves forward, drafts a proposal, and schedules a call with the consultant, all before learning that the board caps illiquid exposure at a level the strategy exceeds by a wide margin.

The allocator rarely volunteers the constraint on their own. A CIO or plan staffer may not think to mention a liquidity rule because it feels like background information, not news. They also may not be the person who owns the final interpretation of that rule. A staff member can describe a policy loosely while a consultant or board committee reads the same language much more strictly. If you do not ask, you inherit whichever version of the policy the person in front of you happens to remember.

The cost shows up later, and it shows up in front of people who matter. A proposal that ignores a debt limit or a governance requirement gets flagged in committee, sometimes weeks after you thought the deal was moving. That is a bad way to lose a mandate, and it damages your credibility with the allocator even when the strategy itself was sound.

How to Prepare Before the Call

Before you get on the phone, read whatever public information exists on the plan or foundation, current allocations, recent manager searches, and the name of the retained consultant if one is listed anywhere. That background lets you ask sharper questions instead of generic ones.

Prepare a short list of constraint categories to test, rather than a single open ended question about policy. Ask about liquidity terms, the use of derivatives or debt, governance and reporting requirements, geographic or sector restrictions, and any screen tied to diversity or responsible investing. Foundations, pensions, and endowments write these limits differently, so do not assume the same wording means the same thing across institutions.

Also decide how you will find out who owns interpretation of the policy. The person on the call might be an investment officer, a consultant, or a committee chair, and each one has a different amount of authority to say whether a constraint actually applies to your strategy. If your team has practiced this kind of call before, the Asset Management practice conversations hub has more scenarios built around institutional buyers, and it helps to run through a few before a call with an unfamiliar plan.

What to Say

Here is how the exchange plays out with a foundation CIO who raises a vague concern early in the call.

The CIO says, "We want more flexibility in the portfolio, but our board stays cautious." You respond, "When your board talks about flexibility, are they thinking about liquidity, the use of derivatives, governance oversight, or something else." The CIO says the two sticking points are quarterly liquidity and a cap on borrowing.

You say, "Let me check our approved materials for documentation on those two points specifically. Who on your side should confirm how the committee reads that language before we schedule diligence." The CIO names the consultant who wrote the original policy language and offers to loop them in.

That response does not turn a policy conversation into a claim that your strategy fits. You have not said the fund meets the liquidity rule or stays under the debt cap. You have identified the actual constraint, found out who can verify it, and asked for a named person to confirm the committee's interpretation before diligence starts. That is a very different position than promising fit on a call and finding out later that you were wrong. The same discipline applies to describing what your process does rather than what it will guarantee, which is covered in Explain an Investment Process Without Turning It Into a Promise.

Mistakes to Avoid

A few habits turn this conversation into a wasted cycle.

1. Describing the manager as a fit before you hear the specific constraint. A vague sense that the allocator likes the strategy is not the same as knowing what their policy allows.
2. Treating one contact's description of a rule as the committee's official position. A staff member's summary and a board's actual reading of the same clause can differ.
3. Assuming a constraint mentioned in passing is fixed and current, rather than checking it against the plan's own cycle for reviewing its investment policy.
4. Promising, even informally, that your product satisfies a requirement you have not confirmed against the plan's actual policy language.
5. Moving straight to scheduling diligence without naming a person who owns interpretation of the constraint you just uncovered.

Any one of these mistakes can survive a single call. Stack two or three together and you end up presenting to a committee that stops the review in the first ten minutes, for a reason you could have found out weeks earlier. If the plan has public reporting requirements tied to diversity or responsible investing, the same discipline applies. Read Responding to Public Plan Questions About Manager Diversity Reporting for how to handle that specific version of the constraint conversation.

How to Practice and Score It

This conversation is easier to teach than to explain in the abstract. Have a sales manager or a peer play the allocator and drop in one constraint, a liquidity rule, a debt cap, a governance requirement, partway through the call. Afterward, have the rep write down three things, the exact constraint as stated, the person who can verify it, and the specific material they plan to request or check. If any of the three fields is blank or vague, the call needs another pass.

Score the reworded response against the original one. A rep who says "we should be a good fit here" gets marked down. A rep who asks one direct question that tests a named constraint, and follows it with a request to confirm ownership, gets marked up. This is also where a tool built for this kind of rehearsal helps. DealSpeak lets a rep run this exact scenario against an AI counterpart, take the allocator through several turns, and get scored on whether they separated a real constraint from a passing comment.

After the practice round or the actual call, check the rep's notes against the plan's committee calendar and its cycle for reviewing the investment policy. That comparison tells you whether the constraint is timely enough to change your near term plan or just a passing concern raised without any near term consequence.

Keep the Constraint at the Center

None of this requires a longer call or a more aggressive pitch. It requires one clear question about the policy limit that actually matters, asked before you say the word fit. Ask it early, name the person who can confirm it, and you save both sides weeks of work on a deal that was never approvable in the first place.