Portfolios
See across companies without removing the walls.
Cross-workspace portfolios link companies together. A parent sees its subsidiaries through explicit relationships, and every company still decides what happens in its own.
A portfolio view is useful only if the walls still hold.
It is designed so a parent’s view never weakens a subsidiary’s isolation.
What a portfolio includes.
Org relationships
Parent and subsidiary links between workspaces, defined explicitly at the shell level.
Portfolio executive access
A named role that sees the portfolio. It does not widen access inside any company.
Consolidated reports
One report across companies, with every figure citing its source company.
Independent authorization
A cross-company task is authorized separately in each company it touches.
How a cross-company task runs.
Request
An executive asks for a task that spans two or more companies.
Split
Brigham.ai breaks it into one piece per company.
Authorize
Each company checks and approves its own piece under its own rules.
Report
Results come back labelled with the company that produced them.
Ask it
What you can ask.
- ›“Which portfolio companies are behind on their monthly close?”
- ›“Compare pipeline across all subsidiaries. Cite each source.”
- ›“Which company has the most open approvals?”
- ›“Draft the quarterly portfolio update with sources named.”
- ›“What do two of our companies both need from the same vendor?”
- ›“Ask each company to confirm their open risks.”
Questions about portfolios.
Do workspaces stay isolated?
Yes. A workspace is still the boundary. Portfolios add explicit, audited relationships between workspaces and nothing else crosses.
How is leakage tested?
Tests are adversarial, aimed at proving that unrelated organizations cannot read each other.
Does a parent see everything?
Only what the relationship and each company’s own rules allow. Protected domains such as finance still need a named grant.
Keep reading.
Tell us how your portfolio is built.
Get started and tell us how your companies relate.