FOR MULTIFAMILY OFFICES AND FIRMS SERVING FAMILIES
One operating system. Every family kept completely separate.
Serve every family from one system, without two families ever touching.
A multifamily office multiplies the single-family problem: every family has its own entities, custodians, advisors, deadlines, and confidences, and the office must hold them all without ever letting them blur. ArkLegacy is built family-first: each family is its own permissioned record, and the office is a disciplined operator across them, never a commingler of them.
01 · THE WEIGHT
What this actually feels like from the inside.
Every family is a bespoke stack
Each relationship arrived with its own spreadsheets, folder tree, and reporting format. The office's real operating system is whatever each relationship manager remembers about their families.
Reporting cycles multiply by family
The quarterly pack is rebuilt by hand for every family, every cycle. Growth in families means growth in assembly hours, not in service.
Confidentiality by carefulness
When shared drives and generic tools hold many families, separation depends on people being careful with folder permissions and email threads. Careful is not a control.
Relationship-manager turnover is a client risk
When an RM leaves, their families' context leaves with them: what was promised, what is pending, and why decisions were made. The handover is a document at best, a scramble at worst.
02 · TODAY’S WORKFLOW
Where the pieces live right now.
- 01Each family's recordlives in that RM's folders, spreadsheets, and memory.
- 02The deliverables calendarlives in personal task lists that leave with their owners.
- 03Who may see whatlives in folder permissions and old email threads.
- 04The reporting packsare rebuilt per family, per cycle, by hand.
- 05The office's historyis reconstructed from sent mail when a trustee or auditor asks.
None of these pieces is wrong on its own. The problem is that the whole picture exists nowhere, so the family or one exhausted person becomes the integration layer.
03 · THE ARKLEGACY OPERATING MODEL
The same record, run for this family’s shape.
01
Separate family workspaces
Each family is its own permissioned record with strict access boundaries. Working in one family's workspace exposes nothing about another's; separation is structural, not procedural.
02
Relationship-manager workflows
RMs run their families through owned items, due dates, and evidence, so service delivery is a reviewable queue per family instead of a private working style.
03
Family-specific portals and briefings
Each family gets its own briefing, report package, and advisor permissions, generated from that family's record and cited to that family's documents. Nothing generic, nothing shared.
04
Office auditability without leakage
Office leadership can see that work is on time and controls are followed across the book, while family financial detail stays inside each family's boundary.
05
Recurring deliverables, visible workload
Quarterly reports, filings, renewals, and reviews recur as owned items across the book, so workload and bottlenecks are visible before a deadline finds them.
ALREADY IN THE PRODUCT · EXPLORE EACH IN THE LIVE DEMO
- Cited family briefingThe per-family briefing with a citation on every claim, as it works in the demo today.OPEN
- Family MapOne family's entities, ownership, property, accounts, and debt as a living structure.OPEN
- Owned-item queueDeliverables and follow-through with owners, due dates, and status history.OPEN
- Advisor permissionsEach professional scoped to their lane inside a family's record.OPEN
- Audit trailAn append-style record of changes, approvals, and evidence inside each family.OPEN
04 · STATUS, STATED HONESTLY
What is live, what is in build, what is planned.
The demo shows one family's workspace working end to end. The office-wide commercial layer is product direction, labeled honestly:
- IN THE DEMO TODAYPer-family record, briefing, and queueThe single-family operating loop the rest of this page describes.
- IN BUILDStrict per-family tenant isolationProductizing the single-family system into structurally isolated family workspaces.
- PLANNEDWhite labelingOffice-branded portals, briefings, and report packages.
- PLANNEDManagement fees and client billingFee schedules, invoicing, and billing for the office's client families.
- PLANNEDShared expense allocationAllocating shared office costs across families under a stated policy.
- PLANNEDPooled investment allocationRecording pooled vehicles with per-family allocation and statements.
05 · SITUATION-AWARE AI, SHOWN HONESTLY
What the AI sees in a record like this one.
Illustrative example, computed from the same synthetic family record the live demo runs on. Every claim cites the record behind it; missing information is named instead of guessed; the professional who should review the next step is part of the answer.
THE QUESTION
“What does this family need from the office before Friday?”
The Q2 distribution and estimated-tax transfer is in progress with a July 31 due date and the draft calculation attached. It is this family's nearest hard deadline.
LA-3D1The buy-sell restatement is waiting on signatures, not work: the draft is at counsel and the item sits with a named owner. Worth a nudge before the family call.
LA-6E10The freshness rule has flagged the plant appraisal as stale and opened the refresh action, so the next report package will say so instead of quietly reusing the old number.
E4LA-2
WHAT THE RECORD DOES NOT KNOW
Anything agreed on the last family call that has not been entered as an owned item in this family's workspace yet.
WHO SHOULD REVIEW THE NEXT STEP
the relationship manager, before the family call
Honest status: this intelligence is deterministic and computed only from the family’s own record. No external AI provider is active in the current preview, and nothing here is generated by one. Guidance is informational and permission-aware; it is never legal, tax, investment, or insurance advice.
06 · PRIVACY, PERMISSIONS, AND BOUNDARIES
Who sees what, and where the product stops.
- Relationship managerThe full working record of the families assigned to them. No others.
- Office leadershipWork status, deadlines, and control adherence across the book, without another family's financial detail.
- Family membersTheir own family's record, scoped by the roles the family grants.
- Outside advisorsTheir open items and referenced records inside the families that engaged them.
Access is role-scoped, explicit, and logged; family records are context for the family’s own questions, never training material. ArkLegacy coordinates information and action across the family and its professionals. It does not replace legal, tax, investment, or insurance professionals, and consequential actions stop and wait for a person.
07 · ASKED PLAINLY
Questions this audience actually asks.
- Is multifamily tenancy live today?
- Stated honestly: the product runs one family's record end to end today, and that is what the public demo shows. Strict per-family isolation is the core of the current engineering phase, and multifamily deployments are scoped as design partnerships during the private preview. Nothing on this page presents unbuilt tenancy as live.
- Can one family ever see another family's data?
- No, by design. Each family is its own permissioned record with structural boundaries, and office-level views are limited to work status and control adherence rather than family financial detail.
- What about white labeling, management fees, and client billing?
- White labeling, management-fee tracking, shared expense allocation, pooled investment allocation, and client billing are planned product direction for offices and are labeled exactly that below. They are not live, and we will not present them as if they were.
- How would our families' existing records come in?
- Family by family: statement and CSV imports, structured manual records with a stated valuation basis, and read-only connections where a pathway exists. Each family's record is built inside its own boundary from day one.
See it before you share anything. Then decide.
The live demo runs entirely on a synthetic family, so you can walk every surface first. Private preview; membership is by invitation and a person reviews every request.