Find hidden connections between stakeholders across clients: former colleagues, industry peers, and mutual contacts.
Why This Matters
As a fractional CMO managing multiple clients, you accumulate a network of stakeholders across companies. Sarah Chen at Acme Corp might be a former colleague of Josh Wong at BetaCorp. With Relationship Intelligence, Armbrain scans all your client minds and finds these connections automatically.
Use your client portfolio for warm referrals and introductions.
When to Use This
- Before a client meeting - check if any of their stakeholders connect to your other clients
- When a client needs a vendor or partner - see if someone in your network already knows a good fit
- During new business development - discover that a prospect's CEO used to work with your existing client's VP
- Quarterly portfolio review - map the full relationship web across all your clients
Discovering Relationships
Step 1: Resolve Entities
Armbrain scans client minds and matches stakeholders when you ask:
"Scan my clients for stakeholder connections"
Armbrain calls relationships, which:
- Reads all stakeholders from every active client mind
- Matches people by name similarity, role, and company context
- Creates canonical entity records with aliases (e.g., "Sarah Chen", "S. Chen", "Sarah C." all map to the same person)
- Infers relationships between entities that appear across multiple client minds
You get back a summary:
Found 12 entities across your client minds.
5 new entities resolved, 3 updated.
Run this periodically after onboarding a client, adding stakeholder memories, or saving meeting notes. Each scan picks up new connections.
Step 2: View the Relationship Map
"Show me my stakeholder relationship map"
Or filter to a specific client:
"Show me relationship connections for Acme Corp"
Armbrain calls relationships and returns a visual map of who knows who:
## Relationship Map: Acme Corp
Sarah Chen (CEO, Acme Corp) - Josh Wong (CTO, BetaCorp)
Relationship: former colleagues [85% confidence]
Mike Rivera (VP Marketing, Acme Corp) - Lisa Park (CMO, GammaTech)
Relationship: industry peers [92% confidence]
Each relationship shows:
- Who - the two people and their roles/companies
- Type - former colleagues, industry peers, mutual connections, or mentioned together
- Confidence - how sure Armbrain is about the match (only 80%+ shown by default)
Step 3: Confirm or Dismiss
Confirm accurate relationships:
"Confirm the Sarah Chen / Josh Wong relationship"
This sets the confidence to 100% and marks it as verified. Verified relationships always appear in future maps.
If a match is wrong (two different "Mike Smith" people, for example):
"Dismiss the Mike Smith / Mike Smith relationship"
Dismissed relationships are permanently excluded from all future results.
Confidence Levels
Armbrain assigns confidence based on how strong the evidence is:
| Confidence | What It Means | Example |
|---|---|---|
| 95% | Exact name match across clients | "Sarah Chen" appears in both Acme and BetaCorp client minds |
| 90% | Name + matching role/title | "Sarah Chen, CEO" in both places |
| 80-89% | Name similarity with supporting context | "S. Chen" and "Sarah Chen" with overlapping company history |
| Below 80% | Low confidence, hidden by default | Common names without distinguishing context |
To see low-confidence matches:
"Show me all relationship connections including unverified ones"
Real-World Scenarios
Warm Introduction
You prep for an Acme Corp meeting. You notice their CEO, Sarah Chen, worked with Josh Wong at BetaCorp (another client). In the meeting, mention that you work with Josh Wong at BetaCorp. This builds trust.
Referral Opportunity
GammaTech needs a new SEO vendor. Your map shows GammaTech's VP Marketing knows an SEO agency founder through a mutual contact. You can make a warm intro.
Prospect Research
A prospect reaches out. Before the call, you scan relationships and find their CTO worked with an existing client stakeholder. You now have an angle for the conversation and a potential reference.
Tips
- Run entity resolution after onboarding a new client. New stakeholder data creates new connection opportunities.
- Confirm relationships you know are real. This improves future results and builds a verified network map over time.
- Dismiss false matches promptly. Common names generate false positives. Dismissing them keeps your map clean.
- Check the map before discovery calls. Hidden connections are your unfair advantage in sales conversations.
- Record stakeholder information consistently. The relationship map is only as good as the stakeholder data in your client minds. Use the
stakeholdermemory type when noting key people.