Skip to main content
Solutions

Family Offices

A family office’s problem is rarely access. It is record-keeping that has to survive decades, staff turnover and eventually a succession.

One transaction boundaryThree stacked elements — a record, a rule and a ledger posting — enclosed by a single boundary, indicating that all three commit together or not at all.ONE TRANSACTION BOUNDARYRecordwhat is trueRulewhat is permittedPostingwhat it did to the bookscommit together

What it changes

  1. Records that outlive the people who made themAn append-only audit trail and a register rebuildable from its own history mean “who owned what in 2031” is answerable in 2045.
  2. Concentrated positions modelled honestlySingle-asset vehicles, illiquidity stated plainly, and lockups enforced rather than remembered.
  3. Controlled accessRoles per member, with conflicting-role detection and every irreversible action needing two people.
Ask, agree, then actThree steps. One person requests, a different person approves, and only then does the state change. The approval binds to what was requested, so editing it afterwards invalidates the sign-off.Requestone personApprovea different oneActnow it movesThe approval binds to what was asked.Edit it afterwards and the sign-off is void.
Every irreversible act on this platform takes this shape, whatever the subject of the page: one person asks, a different one agrees, and only then does anything move.

What it includes

Multi-entityOrganizations within a workspace, with members confined to one where appropriate.
Document data roomContent-hashed versions, so the valuation relied on is provably the one on file.
SuccessionWallet recovery and forced transfer as documented, approved procedures rather than improvisation.

See it against something real.

Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.

Your instrument, against this modelAn unspecified asset on the left feeds four stages: structure, compliance policy, the offering book and the register. The asset is drawn as an outline because it is the reader's, not the platform's.Your assetwhatever it isStructurePolicyBookRegister