One contact at an institutional investor is not a relationship. It is a thread. If that person changes jobs, goes on leave, or turns out not to be the decision-maker, the thread breaks and so does your pipeline.
Short answer: A stakeholder map is a structured view in your CRM of everyone who influences an investor’s decision, including their role, stance, and your coverage. It shows who decides, who recommends, who evaluates, and where you have no relationship at all.
Why Institutional Decisions Need a Map
Institutional allocation is a layered process. According to Dakota’s explanation of public pension decision-making, strategic allocation is set by the board and investment committee, consultants screen and qualify managers, staff runs diligence, and the final commitment is delegated or sent up for approval depending on the plan’s authority. The same source notes that smaller plans lean more on consultants and the largest plans on staff.
That structure repeats across investor types:
- Pensions: board, investment committee, CIO, asset class heads, analysts, operations, legal, and consultants. A pension manager selection overview outlines how staff and consultants review, the board votes to search, and finalists present before a hire vote.
- Endowments and foundations: investment office staff, committee members, and trustees
- Family offices: principals, next-generation family members, a CIO or advisor, and sometimes a family council
- Funds of funds: investment team, operational due diligence team, and an investment committee
An industry primer on institutional investing at Nasdaq cites more than 85 percent of US institutional asset owners using investment consultants, which is why consultants belong on almost every map. And with six to eighteen months from first meeting to signed subscription being standard for institutions, you have a long time to learn the people involved, or to discover too late that you never met them.
The Roles to Capture
Tag every contact with their role in the decision. A simple set covers most situations:
- Decision-maker: votes or signs off, such as a board or investment committee member
- Recommender: brings the proposal forward, such as a CIO, asset class head, or consultant
- Evaluator: runs diligence, such as an analyst or operations reviewer
- Influencer: shapes opinion without a formal vote, such as a consultant researcher or senior colleague
- Gatekeeper: controls access or scheduling
- Day-to-day contact: handles documents, reporting, and logistics
- Champion: advocates for your firm internally
Add a stance field with simple values such as Champion, Supportive, Neutral, Unknown, and Skeptical. “Unknown” is valuable because it shows where you need to learn more.
What to Record for Each Stakeholder
Keep it professional and useful:
- Name, title, and organization or entity
- Role in the decision and stance
- Who they report to and which committees they sit on
- Relationship owner at your firm and relationship strength
- Last meaningful interaction and next step
- Topics they care about, such as strategy fit, fees, ESG, or reporting
- Communication preferences
- Expected tenure or rotation, such as board terms or advisor changes
- Governance calendar items, such as investment committee and board meeting dates
If you have defined custom fields for these, follow the guardrails in Customization Without Chaos so the map stays consistent.
How to Build the Map in Your CRM
- Start with the organization and entity record. Use the entity hierarchy to reflect trusts, funds, and related entities.
- Add every known contact, including people you have not met. A name on the map with “Unknown” stance is better than a blind spot.
- Tag role and stance using structured fields or tags.
- Link consultants to their investor clients so you can see who influences which relationship. See managing consultant relationships and product ratings.
- Record reporting lines and committee membership in notes or fields.
- Log meetings against every attendee, not just your primary contact.
- Add governance dates, such as committee and board meetings, as tasks or events.
- Review quarterly, and after any personnel change.
An Illustrative Map
Imagine a mid-sized public pension. Your map might show:
- Board and investment committee (final vote): not yet met, stance unknown
- CIO (recommender): two meetings, supportive
- Private equity head (recommender): one call, neutral
- Senior analyst (evaluator, runs diligence): five interactions, champion
- Operational due diligence lead (evaluator): none yet
- General consultant and a private markets specialist (influencers): linked, product rating pending
- Legal counsel (side letters): none yet
In one glance you can see the gaps: no contact with the operational due diligence lead before diligence, and no strategy for the committee.
Measure Coverage with Saved Views
Once stakeholders are tagged, build views that expose risk. Useful examples:
- Pipeline records with only one contact
- Records in Due Diligence with no operational due diligence contact
- Investors with no meeting involving a decision-maker or recommender in 90 days
- Investors where the consultant is not linked
- Contacts with stance “Unknown” on active pipeline records
The search and filter tools and custom dashboards make these routine. Pair them with CRM alerts so single-threaded relationships trigger a prompt.
Use the Map at Every Stage
- Early engagement: identify who to meet beyond your first contact
- Due diligence: make sure operations, legal, and compliance reviewers have what they need
- Committee preparation: support your champion with materials aimed at the questions decision-makers ask
- Documentation: know who negotiates side letters and who signs
- Post-close: keep the map current for retention and re-up
Handle Turnover and Change
People move. Titles change. Boards rotate. Capture changes quickly, and consider how automated updates can help. AI-powered contact enrichment can flag title and firm changes from email signatures. If a champion leaves, the map shows who else knows you, which protects the relationship. Our guide on what happens when a key person leaves applies on both sides of the table.
Keep It Professional and Private
Stakeholder notes are business records. Follow a few rules:
- Record facts relevant to the business relationship, not personal speculation
- Avoid sensitive personal information
- Assume notes could be reviewed internally or in response to a regulatory or data subject request
- Limit access to sensitive relationships using role-based permissions
- Align practices with your GDPR obligations
Common Mistakes
- Mapping only the people you have already met
- Treating the consultant as a footnote
- Tagging stance once and never updating it
- Keeping the map in a slide deck instead of the CRM
- Skipping operations and legal contacts until late in diligence
Frequently Asked Questions
What is a stakeholder map in a CRM?
It is a structured record of the people who influence an investor’s decision, with their roles, stance, and your relationship coverage.
Who are the key stakeholders at a pension fund?
Typically the board, investment committee, CIO, asset class heads, analysts, operations and legal reviewers, and investment consultants.
How often should we update stakeholder maps?
After meetings, after personnel changes, and at least quarterly for active pipeline records.
Can stakeholder mapping work for family offices?
Yes. Map principals, next-generation members, advisors, and attorneys, and note which entities each person governs. See CRM for family offices.
Schedule a demo with Satuit to see how SatuitCRM supports multi-contact, multi-entity relationship mapping for institutional investors.
