Family office

Ownership across entities, and whether each one can actually meet what is committed against it.

Family office in SigmaPointPi
/verticals/family-office

A family office is a graph, not a list. Entities own other entities, commitments sit at one level and the assets that satisfy them sit at another, and the question that matters is whether a given entity can meet its obligations from what it actually controls.

This holds the ownership edges, computes look-through ownership at any depth, and tests solvency per entity against commitments falling due.

Where everything sits

This view hit a snag
This view hit a snag
What went wrong
What went wrong

How to work this page

Build the ownership graph

Each edge is a percentage held by one entity in another, with its date. Cycles are refused at entry, because an entity cannot own itself through a chain and a graph that permits it produces meaningless look-through.

Read look-through ownership

Effective ownership of any asset by any entity, computed through every path. A 60 percent holding in a company that holds 50 percent of an asset is 30 percent look-through.

Record commitments with their call schedule

Uncalled capital is an obligation even though no money has moved. It appears against the entity that signed it.

Test solvency per entity

Liquid assets against commitments falling due in the window. An entity that is wealthy on paper and illiquid against a capital call is the failure mode this exists to catch.

On a phone

Family office on iPhone 15 Pro Max

Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.

Questions people actually ask

How deep does look-through go?

Any depth. The computation walks every path and sums them, so an asset reached through three intermediate entities is counted correctly rather than truncated.

Can entities share vendors or banking?

No. Each entity is separate at the data level, which is the point. Consolidated views are computed on top and never by merging the underlying records.