Describe Firm Capabilities in an RFP Using Only Verified Facts

Capability questions in an RFP tempt everyone on the response team to sound bigger than the firm actually is. A prospect reading fifty of these responses a year catches inflation fast, and once they catch one claim that does not hold up, they discount every other claim in the document. As the RFP lead, your job is to write capability answers that are accurate, specific, and defensible under a follow up question from a due diligence team.

Why This Conversation Goes Wrong

Capability sections invite exaggeration because the team wants to look comprehensive next to competitors. A portfolio manager describes what the firm could theoretically do. A relationship manager remembers a client win from three years ago and assumes it still applies today. A writer under deadline reaches for words like comprehensive, full service, and highly experienced because they sound strong and take no time to verify. None of these people are lying. They are filling gaps with confidence instead of evidence, and the RFP goes out the door with claims nobody in operations actually signed off on.

The real damage does not show up during the pitch. It shows up during due diligence, when the prospect's consultant calls the operations team to verify a claim and gets a different answer than the one written in the response. Or it shows up after the mandate is won, when the client asks for the custom report the RFP promised and the delivery team says that format requires a separate build. At that point you are not managing a capability gap anymore, you are managing a credibility problem, and those take far longer to repair.

How to Prepare Before You Write a Word

Before drafting any capability answer, build what amounts to an evidence register, a running list of what the firm can state, who confirmed it, and what document backs it up. This does not need to be complicated. A spreadsheet with the claim, the owner, the source document, and the date confirmed is enough to stop guesswork before it reaches the page.

For each capability question in the RFP, identify the operational owner who can confirm the claim in writing. This is usually not the person the sales team would ask first. A performance claim needs sign off from performance measurement or compliance, not from the portfolio manager who feels good about the numbers. A reporting claim needs sign off from operations, not from the client relationship team that has only seen a demo. A technology claim needs sign off from the team that actually maintains the system, not from the person who sold the service internally three years ago.

Ask each owner three things. What exactly can we state. For which clients, structures, or share classes does it apply. What document, policy, or system record supports it. If the owner cannot answer the third question, the claim is not ready to submit, no matter how confident the owner sounds in the hallway.

Also ask about conditions. Many real capabilities come with strings attached, a minimum account size, a specific data format, an extra onboarding step, or a separate agreement. Leave a condition out and a true statement becomes a misleading one the moment a client tries to use it.

What to Say When the Team Pushes Back

The hardest part of this job is rarely the writing. It is the conversation with a colleague who wants a stronger claim than you can verify. Here is how that exchange might go.

A senior relationship manager tells you, "Just say we offer custom reporting. Every serious competitor claims that, and if we hedge it we look weak next to them."

You respond, "I checked with operations this morning. Standard reporting covers the formats listed in our template. Anything outside that list needs scoping and a lead time we have not quoted yet. If I write custom reporting without qualification, we are promising something the delivery team has not agreed to deliver."

The relationship manager pushes again. "The client will just assume we can do it anyway. Everyone writes it that way."

You hold the line. "Then let's write what we can support. I can say we provide standard reporting across the formats in the template, and that custom formats are available on request with a scoping conversation. That is true, it still shows range, and nobody on the delivery side gets blindsided when the client asks for it after signing."

That last line does the real work. You are not refusing to sound capable, you are offering a version of the claim the firm can actually stand behind, plus a path for the prospect to ask for more.

Mistakes to Avoid

Watch for a short list of habits that turn a defensible response into a liability.

1. Writing from memory instead of from a document. If nobody can point to a policy, report, or system record, the claim is a guess dressed up as a fact.
2. Copying language from a competitor's marketing material or your own website into an RFP answer without checking it against current operations. Marketing copy is written to sound good, not to survive a due diligence call.
3. Treating "we have done this before" as "we can always do this." A one time exception made for a large client is not a standard capability.
4. Leaving out conditions because they make the answer look weaker. A condition is not a weakness, it is what makes the claim usable.
5. Skipping the independent review step because the deadline is tight. A rushed answer that gets caught during due diligence costs far more time than the review would have taken.

How to Practice This Conversation Before It Matters

The skill here is not writing, it is holding a boundary with a colleague who outranks you or has more tenure, while still sounding like a team player instead of an obstacle. That skill is hard to build by reading a checklist. It gets built by running the conversation out loud, several times, against pushback that feels real.

A manager can score this by listening for whether the RFP lead names the specific evidence behind a claim instead of restating the claim more firmly, whether the lead offers an alternative the team can actually use instead of a flat no, and whether the lead holds the same position on the second round of pushback as on the first. A lead who folds under a second round of pressure will fold in front of a prospect too, and that pattern is much cheaper to catch in practice than to discover during a live RFP cycle.

This is the kind of scenario that benefits from rehearsal with a counterpart who pushes back the way a real colleague or a real prospect would. DealSpeak's Asset Management practice conversations include this exact scenario, along with related situations like reading board questions during a client review, covered in Plan an Annual Client Review Around Board Questionsand explaining a performance gap in Resolve a Benchmark Mismatch Question in a Client Review. Practicing the pushback in a low stakes setting means the first time you hold this line for real is not also the first time you have said the words out loud.

The Payoff of a Narrow Answer

A narrow, verified capability answer beats a broad claim every time a prospect actually checks it, and institutional prospects check. Say what you can prove, name the conditions, and give the prospect a clear way to ask for more. That approach costs you nothing in the pitch, and it saves you a difficult conversation with a client after the mandate is already signed.