Build vs Rent: Who Should Own Your Family's Data Architecture

Overview

Building your family's data architecture means owning the system that holds your wealth data; renting means using a provider's system on their terms. The real question is not which is cheaper this year but who owns the picture when a provider changes. For the family's core record — the single source of truth — ownership usually wins, because the data outlives any vendor.

This is a quiet decision most families make by default, by pouring their data into whatever platform an advisor recommends. Made deliberately, it is one of the more consequential choices in how an office is built.

What does "build vs rent" mean for family data?

Build versus rent is the choice between owning your data architecture and using someone else's. "Build" does not mean running servers; it means the family owns the single source of truth and controls where it lives and who can access it. "Rent" means the consolidated picture sits inside a provider's system, in their format, under their terms of service.

The distinction is about control, not hardware. A family can "build" ownership on modern cloud tools without any physical infrastructure. What makes it built rather than rented is that the family, not the vendor, holds the master record.

Owning your data architecture is not about servers. It is about who holds the master record.

What are you actually renting?

When you rent, you are renting the place your family's picture lives — and accepting that it lives on someone else's terms. That means the provider's data format, the provider's access rules, and the provider's continuity. If the relationship ends, the question is what leaves with them and what you keep.

Renting is not wrong. It is efficient and often the right call for tools at the edges of the office. The risk is renting the centre — the core record of the whole family's wealth — without noticing that you have handed the most important asset to a vendor you can be switched away from.

When does renting make sense?

Renting makes sense for specialised, replaceable tools where the data is not the family's master record: a specific analytics tool, a niche reporting add-on, a portal for one asset class. If losing the tool tomorrow would be an inconvenience rather than a loss of the picture, renting is the efficient choice.

The test is displacement. If a tool disappearing would take part of your single source of truth with it, that function should be built and owned, not rented. If it would not, rent it and move on. Not everything needs to be owned; the core does.

Why does the single source of truth belong to the family?

The single source of truth belongs to the family because it is the one asset the office cannot be rebuilt without. Every coordination task, every decision, every succession depends on it. A record that central should not be exposed to a vendor's pricing changes, service decisions, or exit.

This is the same argument that runs through where family data should live and sovereign AI for family wealth: ownership of the core record is what makes the office durable. Rent the periphery; own the centre.

Rent the periphery. Own the centre. The single source of truth is the centre.

How do you get ownership without building infrastructure?

You get ownership by holding the master record in a system the family controls, while still using external tools around it. The lean approach is to own the data layer, not a data centre: one family-owned single source of truth, with providers plugging into it rather than holding it. The picture stays with the family; the tools remain replaceable.

This is what the Operating System is built to do — give a family an owned centre without the cost of building institutional infrastructure. Ownership becomes a design choice, not a capital project.

Frequently asked questions