An asset management RFP looks like a long list of questions. Firm history, investment philosophy, team, process, risk management, performance, fees, operations and compliance. Then comes a due diligence questionnaire (DDQ) that can run longer than the RFP itself. Most managers answer it like a form. Our read is that the institution running the search is using all those answers to decide one thing. Can we trust this team with our money for the next ten years?
Who's reading an asset management RFP
On the other side, there's usually an investment committee or board at a pension plan, endowment, foundation or insurer. Often an investment consultant runs the search for them, screens the responses and brings a shortlist to the committee. Operational due diligence staff review how the firm runs behind the scenes.
So the response has to work at three levels. The consultant, who reads dozens of responses and scores them. The operational reviewer, who checks controls, systems and service providers. And the committee members, who may only see a summary and a few pages from the finalists.
Why trust decides it
Most finalists have good performance, or they wouldn't be finalists. What separates them is whether the committee believes the performance will continue, and whether the firm will behave the way it says it will when markets turn.
That belief comes from consistency. The philosophy described in the RFP matches the process. The process matches the portfolio. The team listed is the team that'll manage the money. The risk controls described in the DDQ match what the operational reviewer hears on a call. Every inconsistency, even a small one, gives the reader a reason to doubt.
Where responses usually lose trust
Boilerplate philosophy. Phrases that could describe any manager in the category. "Disciplined, repeatable, research-driven" tells the reader nothing about you.
Answers that don't match. The RFP says one thing about team turnover and the DDQ says another. A consultant comparing them side by side will notice.
Performance without context. A table of returns with no explanation of what drove them, what didn't work and how the portfolio behaved in hard periods.
Fees buried or vague. Fee schedules spread across sections, or terms that only make sense after a phone call.
Walls of text. Long answers that bury the point, written for compliance review and never for a reader.
Making the response easier to believe
Start every answer with the direct answer, then the detail. Use the same numbers, names and dates everywhere they appear, and keep one source of truth for all of it across the RFP and the DDQ.
Explain the process with a picture where you can. A simple diagram of how an idea becomes a position does more than three paragraphs. Show performance in context, including the periods that didn't go well and what the team learned from them. In our experience, committees trust managers who explain a bad stretch plainly.
Name the people, and say how long they've worked together. Show fees in one clear table. And build the finalist version, the short document the committee sees, as carefully as the full response.
Anything that shows performance has to go through compliance, and firms registered with the SEC follow specific rules on how performance appears in marketing. Build that review into the timeline from the start, so it never becomes the step that makes you late.
How it plays out
Here's a use case. A mid-size fixed income manager responds to a public pension plan's search, run by a consultant.
The first draft reused last year's answers. The philosophy section was two paragraphs of general language. The team section listed seven people without saying who made decisions. Performance was a single table with no commentary.
The rebuilt response opened each section with a one-line answer. The philosophy section showed how the team's view on credit risk turned into specific positioning, with one example from their own portfolio that compliance cleared. The team section showed who decides, who supports and how long they've worked together. Performance came with a short explanation of the two hardest years. Fees went into one table. The DDQ answers were checked line by line against the RFP so every number matched. The consultant's feedback after the search singled out how easy the response was to evaluate.
Questions we hear about asset management RFPs
Should the RFP and DDQ be written by the same people?
They can be split, but one person should own consistency across both. Most trust problems start when two teams answer overlapping questions differently.
How much design does an institutional response need?
More than most firms give it, and less than a marketing brochure. Clear structure, readable tables and a few diagrams help a consultant score faster. The goal is clarity, so keep the decoration light.
Where can a designed proposal help most?
At the finalist stage. When three managers present to a committee, the document the committee keeps is often what they remember. That's where a proposal built for a buying committee and a clear executive summary pay off.
How long should each answer be?
As long as it needs to be to answer the question, and no longer. Lead with the answer in one or two sentences, then the support. If the RFP sets a word or character limit, treat it as a ceiling, and use the space you save to make the important answers clearer.
Should we include a cover letter?
A short one, signed by the person the committee will deal with most. Use it to say why this mandate matters to your firm and who'll be on the account, and keep it to a page.
The short version
An asset management RFP is decided on whether the committee trusts you. Make every answer consistent across the RFP and the DDQ, lead with direct answers, show performance in context and name the people who'll manage the money.
If you're heading into a finalist round that matters, start a proposal.
