Ecosystem Directory
Aggregate metadata from every portco — vertical coverage, warm-contact counts, ecosystem health. No individual contacts visible.
Tier 03 · Enterprise · Funds + Family Offices + Portfolios
Your ecosystem, made queryable.
Without breaking the walls between entities.
Every portfolio company runs its own Connect Crew in its own private graph. You — the fund — see aggregate metadata only. Master Connect answers fund-level questions. Intro requests flow through a two-gate governance model: your approval, then the contact owner's. The operating-partner role, productised.
14
portfolio companies
5
verticals · ecosystem
2,847
aggregate warm contacts
$2.1M ARR influence
ROI · this quarter
The ecosystem shape
Parent · verticals · portcos. Queryable without merging.
Each portco is an independent tenant with its own private graph. The parent entity sees only what each portco opts in to publish to the ecosystem directory. Master Connect routes fund-level questions through this directory — aggregate metadata, not names.
Parent entity · fund admin
Temasek
8 portcos
Fintech
142 warm
12 portcos
Enterprise SaaS
210 warm
6 portcos
Biotech
78 warm
4 portcos
Climate
54 warm
9 portcos
Deep Tech
101 warm
14 portfolio companies · each runs its own private graph
Helix Tech
42w · Singapore
Kite Commerce
58w · Singapore
Polygon Labs
67w · APAC
Grupo Santander
29w · LATAM
Nebius AI
31w · EU
Seedstars SEA
38w · SEA
Blockworks Media
22w · US
Claritas Bio
14w · US
Sora Climate
11w · Singapore
Atlas Robotics
19w · JP
Meridian AI
36w · Singapore
Verdant Bio
9w · EU
Tidalwave Energy
8w · APAC
Orbit Trade
27w · Singapore
Two-gate intro governance
The operating-partner role, productised.
Portco asks. Fund approves at Gate 1 (governance). Contact-holding portco approves at Gate 2 (ownership). Both must agree. Neither can force the other.
1
Portco B
Asks via Master Connect
“Who in the ecosystem knows someone at Stripe?” — queries the directory (metadata only).
2
Portco B
Submits intro request
Target · purpose · urgency. Request enters Gate 1 queue.
3
Fund admin · Gate 1
Governance review
Approve · deny · request more context. Auto-approve policies skip manual review for same-vertical, low-stakes asks.
4
Portco A · Gate 2
Contact ownership decides
Portco A sees the approved request. They approve, deny, or suggest a different contact. Full final say.
5
Portco A's Crew
Intro drafted in Portco A's voice
Messenger Crew drafts the intro, routes to Portco A's Morning Connect for final approval.
6
All parties
Intro sent · tracked
Fund sees the outcome (meeting booked / deal closed). ROI rolls up to the ecosystem dashboard.
Aggregate by default · granular by opt-in
Three layers of visibility. Each portco controls their own.
If the fund could see everything by default, no portco would opt in. The walls ARE the feature. What's novel is that the walls are queryable.
Aggregate metadata
default ON · portco can opt out
Vertical coverage. Portco health. Ecosystem stats.
Directory metadata
opt-in per relationship class
“Portco X has 5 warm contacts at company Y” — no names.
Contact-level visibility
explicit opt-in per intro request
Only revealed to the fund admin when the holder portco approves at Gate 2.
What funds get
Strategic oversight. Zero leakage. Measurable ROI.
Gate 1 approval queue
Every cross-portco intro request lands in your admin console. Approve, deny, or request context. Configurable auto-approve rules.
Cross-entity lockdown
Sister portcos can't message each other without explicit Gate 1 approval. Isolation is architectural — not policy.
Ecosystem ROI tracking
Every approved intro → meeting booked → partnership formed is tracked and rolled up quarterly for LP reporting.
Vertical breakdown · live shape
A sample ecosystem: 14 portcos, 5 verticals.
This is what the fund admin sees at a glance. Each vertical rolls up portco count, aggregate warm contacts, and active intros. Click any vertical to drill into its portcos.
Fintech
8 portcos · 12 active intros
142
warm contacts
Enterprise SaaS
12 portcos · 9 active intros
210
warm contacts
Biotech
6 portcos · 3 active intros
78
warm contacts
Climate
4 portcos · 2 active intros
54
warm contacts
Deep Tech
9 portcos · 8 active intros
101
warm contacts
Built for
Where portfolio networks are the real asset.
Venture funds
Mapping the portfolio's network, not merging it
Portfolio founder asks for a warm Stripe intro. Fund admin sees: Kite + Polygon have warm contacts. Routes through whichever portco is warmest. Two gates approve. Intro flows in the portco's voice, not the fund's.
Family offices
One relationship view across every operating entity
12 operating companies, 40+ investments, principal wants the big picture. Each operating CEO sees only their entity. Legal sees the audit trail. Succession inherits every relationship intact.
Holding companies
Subsidiaries benefit from the parent's network
Parallel businesses under one roof, sometimes overlapping customers. Shared ecosystem for favourable intros. Hard walls where subsidiaries compete. Configurable per relationship pair.
Compliance + privacy posture
22-word privacy. Real enterprise guarantees underneath.
Classification is local. The graph is the user's. Every action is human-approved or user-authorised. No training on user data, ever.
PDPA
Singapore · compliant
GDPR
EU · compliant
SOC 2 Type II
on roadmap · H2 2026
Data residency
configurable per entity
Custom DPAs
per legal relationship
SSO · SAML / OIDC
identity provider ready
SCIM provisioning
auto onboard + offboard
Audit log
every action, every entity
Enterprise
Your ecosystem is ready to be queried.
30-minute fund demo. We'll walk you through the admin console, the two-gate flow, and the compliance posture. Then propose a pilot with three of your portfolio companies.