Discuss Manager Differentiation Without Overstating the Case

Every asset manager tells a consultant that their strategy is different. Consultants hear this claim so often that the words alone carry no weight anymore. Your job in Consultant Relations is not to win the differentiation argument. Your job is to point the conversation toward documented choices the consultant can check for themselves, and to stop the moment a description turns into a promise about future results.

Why This Conversation Goes Wrong

Most differentiation conversations fail for one of two reasons. The representative either recites a generic list of strengths that could describe any firm in the category, or the representative gets nervous about sounding generic and overcorrects by making a forecast. Both mistakes cost credibility. A consultant who has covered forty managers in a category has heard "high conviction" and "disciplined process" so many times that the phrases trigger skepticism rather than interest. And a consultant who hears a specific promise about future outperformance now has a reason to write down a concern rather than a strength.

The deeper problem is that differentiation is not really about your firm. It is about the consultant's research question. A consultant comparing managers for a fixed income mandate cares about different distinctions than one comparing managers for a concentrated equity mandate. If you walk into the conversation with one fixed answer to "how are you different," you will spend half the meeting on distinctions the consultant does not care about. The conversation goes wrong when the representative treats differentiation as a script instead of a response to a specific question.

How to Prepare Before the Call

Before you meet with a consultant, write down the four or five places where your strategy actually diverges from category peers in a way you can document. Good candidates usually fall into a short set of categories. The team defines its investable universe differently. The team builds conviction through a specific research step other firms skip. The team tests assumptions against a documented process before adding a position. The team sizes exposures using a rule you can describe. The team reviews decisions on a schedule and with a level of scrutiny you can point to.

For each of those points, find the source. A claim about research depth needs a description of the actual research step, not an adjective. A claim about an experienced team needs a current, verified biography, not a claim about tenure that nobody has checked recently. A claim about a disciplined process needs the name of the committee or control that enforces it. If you cannot name the document, the policy, or the person who owns a claim, do not bring that claim into the meeting. Ask the internal owner to clarify it first.

This preparation also means knowing what you will not claim. Decide in advance that you will not say a process will produce a particular outcome, will not compare your firm's returns to a competitor's by name, and will not speculate about how a strategy will perform in a scenario that has not been tested. Consultants build their own return expectations. Your role is to describe the process accurately, not to underwrite their forecast.

What to Say When the Consultant Pushes Back

Start by asking the consultant where they usually see meaningful differences in this category. You might say, "When you compare managers here, where do you usually see the real differences show up, research process, portfolio construction, trading, risk oversight, or something else." Their answer tells you which of your prepared points actually matters to them, so you stop wasting time on distinctions they already consider settled.

Suppose the consultant responds with something like this. "Every manager I meet with tells me they run a high conviction process. I have stopped finding that phrase useful." Do not defend the phrase. Redirect toward something you can document. You might say, "That is fair, the phrase gets used everywhere. Would it help more if I walked through how the team documents a challenge to a position before it gets sized down, or would you rather see how we monitor concentration once a position is built." Notice this response does not argue that your process is better. It offers two specific, checkable things and lets the consultant pick.

If the consultant picks documentation of position challenges, follow through concretely. "I can send you the approved summary of that process, and I can connect you with the analyst who runs it so you can ask about a specific example from the portfolio." That is the entire move. You named a real document, a real person, and you made no claim about what the process guarantees. If the consultant then asks whether that process leads to better outcomes, say plainly that you cannot answer that question, and that the track record and the risk statistics are the place to evaluate outcomes, not your description of the process.

Mistakes That Undermine Your Credibility

The most common mistake is answering a specific question with a general strength. A consultant asks about trading discipline and gets an answer about the firm's history. That mismatch tells the consultant you were not listening, and it wastes the time they set aside for this meeting.

The second mistake is stacking adjectives without sources. Words like experienced, disciplined, and distinct sound fine in a sentence, but a consultant who has done real due diligence treats every one of them as a placeholder for a question they intend to ask later. If you cannot answer that later question yourself, name the person who can.

The third mistake is treating every consultant conversation as adversarial. Most consultants are not trying to catch you in an exaggeration. They are trying to build an accurate picture so they can represent your strategy correctly to their own clients. Overstating your case risks more than a bad outcome for you, it risks the consultant recommending you for a mandate you cannot actually deliver on, which damages the relationship far more than admitting a limitation would have.

The fourth mistake is silence when you do not know something. A person in Consultant Relations who says "I do not have that figure, let me confirm it and follow up by tomorrow" earns more trust than one who guesses. This same instinct applies broadly. Answer Consultant ESG Data Requests by Defining the Terms covers a related version of this problem, where vague terminology creates the same credibility risk that vague differentiation claims do.

How to Practice and Score the Conversation

The skill here is narrow enough to practice on its own. Pick three claims your firm makes about differentiation and force yourself to state, out loud, the exact document or person behind each one. If you stumble, that claim is not ready for a consultant meeting.

Then rehearse the redirect. Have someone play a skeptical consultant who dismisses your first answer as generic, the way real consultants often do, and practice offering two specific, checkable alternatives instead of defending the original phrase. Score yourself on three things. Did you name something a researcher could verify? Did you avoid any statement about future performance? Did you stay anchored to the consultant's actual question instead of your prepared pitch?

DealSpeak's Asset Management practice conversations let you run this exact scenario against an AI counterpart that pushes back the way a real consultant does, and the scoring shows you exactly where a claim went unsupported or where a description drifted into a promise. Managers can use the same practice sessions to check whether relationship teams are staying inside approved material, which matters as much for differentiation conversations as it does for Keep a Consultant Fee Comparison Inside the Commercial Process.

Differentiation conversations reward precision, not confidence. Say what you can document, name who owns the parts you cannot answer yourself, and let the consultant's own research confirm the rest. That approach holds up under scrutiny far better than any version of "we are different" ever will.