One operating layer. Many client offices.
For multi-family offices
Each family needs their own books, access, and reporting rhythm. You need one operating layer—branding, templates, support, and a view across the book—without turning every client into another spreadsheet stack.
How a serious MFO actually runs
The work is not "one login for everyone." It is a client office per family, with your standards on top. FamilyOFX is built for that split—not a CRM with a portfolio widget taped on.
A workspace per family
Open a client organisation for each family. Their positions, documents, members, and permissions stay theirs. You enter when the work requires it—and that access is logged.
Your brand, live on every client
Logo, colours, and appearance from the parent. Clients work in your office, not a generic vendor skin.
Report once, share to the book
Design reports at the parent, share them to new clients, and keep a consolidated view when the investment committee asks how the book looks.
Support lands with you
Client questions do not disappear into a vendor mailbox. Requests route to the parent inbox so your team answers in context.
Calendars across clients
Shared calendars from eligible client offices aggregate at the parent—so capital calls, boards, and family meetings are not twelve separate tabs.
Usage billed at the parent
Client workspaces are not a surprise per-seat stack. The parent carries an agreed monthly Stripe invoice sized to the book. Until that invoice is active, new client offices open on Personal limits.
From assessment to an office you can operate
The same sequence most offices already know—map how you run, design the client model, then put the stack underneath it.
01
Explore
Map how families are served today. Where reporting, documents, and access actually live—and where the friction sits.
02
Design
Decide what belongs in each client workspace versus the parent. Roles, branding, and the reporting rhythm come before more tools.
03
Build
Open the parent, create client offices, share templates, and move the first families without boiling the ocean.
04
Operate
Enter clients when needed, answer from the parent inbox, and iterate as the book and the next generation change.
Questions from MFO teams
How the parent office works when you serve more than one family.
Multi-family offices use a parent plan with an agreed monthly Stripe invoice—not the published SFO price list. Tell us how many families you serve and we will size it. Until the parent subscription is active, new client organisations open on Personal limits. See Billing → Parent offices in the docs.
No. Each client organisation is its own workspace—positions, documents, members, and permissions are separated. Parent staff enter a client office to work; that access is recorded in the audit trail.
They see yours. Logo, colours, and light/dark appearance are set on the parent and apply when someone is working in a client office under you.
Yes. Onboarding includes Multi Family Office as an organisation type. If you already run families in separate tools, we can talk through how to open client workspaces without a big-bang migration.
Home shows recent clients, AUM across the book, and open requests. Reports can be designed at the parent and shared. Consolidated reporting looks across clients. Detailed books still live in the client workspace.
Ready to run the book from one office?
We will size a parent workspace to how you serve families—not a one-size SFO plan with extra logins.