How to Segment Allocators by Mandate, Not Just AUM
Allocator segmentation is often reduced to a spreadsheet filter: investor type, AUM band, geography, and a senior title. Those fields are useful for reducing a large universe. They are not enough to decide where a fund manager should spend relationship capacity.
The reason is straightforward. AUM describes capacity; it does not describe appetite, authority, timing, or a credible path to a commitment. Two firms with the same AUM can have entirely different allocation processes, client constraints, alternatives programs, and decision calendars. One may belong in the active raise. The other may be a well-resourced but irrelevant name.
For alternative asset managers, segmentation should therefore start with mandate logic. The question is not “which allocators are large enough?” It is “which allocators have a plausible reason to evaluate this strategy, through a decision process we can realistically reach?”
Why AUM Is an Incomplete Filter
AUM matters because it provides context for potential check size, organizational scale, and research capacity. It becomes misleading when it substitutes for a coverage thesis.
A large advisory firm may have little room for the strategy because alternatives are centrally controlled, its offering structure does not fit the platform, or its client base does not support the required minimums. A smaller family office or specialist wealth manager may be a stronger prospect because the decision-maker has more flexibility, a clearer strategy fit, and a more direct path to diligence.
That is why a flat “top 500 by AUM” list creates activity without necessarily creating probability. It tells the team where capital may exist. It does not tell the team where the current fund belongs.
The Four Questions That Create a Useful Segment
A practical segment should answer four questions before it reaches the active pipeline.
| Question | What it tests |
|---|---|
| What kind of allocator is this? | The channel, organization, and basic role in the capital market. |
| Why could our strategy fit? | Mandate, investment focus, client context, vehicle compatibility, and relevant constraints. |
| Where is the decision made? | The investment committee, alternatives team, home office, CIO, consultant, or other decision node. |
| What must happen next? | The specific research, introduction, diligence, or follow-up action required to advance the relationship. |
The first two questions establish relevance. The latter two determine whether the team can act on it. All four belong in the working record.
Segment by Channel and Decision Architecture
Different allocator channels require different coverage logic. An independent RIA, a platform-affiliated wealth firm, a family office, and an institutional consultant may all appear in a broad market map. They should not be worked with the same sequence or message.
For an independent RIA, the key issue may be whether the investment team has discretion, an alternatives program, and an appropriate client implementation path. For a platform-affiliated adviser, the more important question may be whether the relevant approval sits at a home office or model-portfolio team. For a family office, the team may need to establish who owns direct manager diligence and whether the opportunity is for a principal allocation, a co-investment relationship, or a broader sourcing dialogue.
The segment is not complete until the decision architecture is visible. A relationship with a local adviser can be valuable while still being the wrong entry point for a platform approval. The CRM should distinguish between the relationship holder and the actual decision node rather than recording both as one generic “prospect.”
Add Mandate Relevance Before Priority
Mandate relevance is a written explanation of why a particular allocator belongs in this raise. It should be specific enough for another person on the team to challenge or defend.
For each selected firm, record the evidence that supports inclusion, the conditions that would make the opportunity viable, and the evidence that would cause the team to defer or disqualify it. This creates a more honest pipeline. It also protects the team from relationship bias—the tendency to keep a familiar name active after the mandate logic has weakened.
The Allocator Database is designed to support that path from broad universe to prioritized coverage. The RIA Database, family office database, and wealth manager database should be treated as channel-specific starting points, not interchangeable exports.
Build a Coverage Sequence
Once relevance is documented, group the universe into three operating cohorts:
- Active coverage: firms with a credible mandate rationale, a plausible access path, and a named next action.
- Research queue: firms with potential but one unresolved question on authority, timing, mandate, or vehicle fit.
- Monitor or exclude: firms that are out of scope, inaccessible for the current raise, or not yet supported by a meaningful inclusion thesis.
This structure turns segmentation into an allocation decision for the distribution team. It also prevents the active list from becoming a holding place for every firm that looks attractive in a database.
Use CRM to Preserve the Decision
Segmentation is not complete when the list is filtered. It is complete when each active account has an owner, a decision-node type, a mandate-relevance rationale, a priority, and a dated next action.
That is the point at which allocator intelligence becomes capital formation infrastructure. The database supports research; the CRM governs execution. When the two are connected, the team can see which segments move, which decisions stall, and where a coverage model needs refinement for the next raise.
Use the Data Preview to inspect the field and workflow context before building a live coverage universe. The objective is not a longer target list. It is a smaller, clearer set of relationships that the team can explain, own, and advance.