Every Platform Gets This Wrong
Open any wealth management platform today and the first thing you see is a list of accounts. An RRSP here. A TFSA there. A non-registered account. A corporate trading account. Each one a separate row in a separate view.
Now picture the family behind those accounts. A matriarch with a personal portfolio and a spousal RRSP. A family trust holding real estate and private equity. A holding company that owns dividend stocks and an operating business. A foundation making annual charitable grants. Two adult children, each with their own registered and non-registered accounts, one a beneficiary of the trust and a director of the holdco.
That family doesn't experience their wealth as twelve separate accounts. They experience it as one interconnected family. But the advisor's technology forces them to see it as twelve separate rows — and to manually piece together the family picture every time a client calls, every quarter-end, every report.
This is the account-centric architecture problem. And it's the foundational design flaw that makes wealth management technology feel like it's working against the advisor rather than for them.
What Entity-Centric Architecture Looks Like
Entity-centric architecture starts from a different premise. Instead of organizing data around brokerage accounts, it organizes around the entities that own those accounts — the people, trusts, corporations, foundations, and partnerships that constitute a family's wealth structure.
In an entity-centric system, the trust isn't a line item. It's a first-class object with its own attributes: trustees, beneficiaries, terms, jurisdiction, tax residency, distribution schedule. The holding company isn't an account number — it's a node in the family structure with ownership links to the people who control it and the entities it owns.
Accounts still exist, of course. But they roll up into entities. And entities form families. The hierarchy is: accounts → entities → families. Not the reverse.
This matters for three practical reasons.
1. The Advisor Sees What the Client Sees
When a client calls and asks "how is our family doing?" the advisor needs to answer that question across every entity, every account, every asset class. In an account-centric system, this requires pulling data from multiple screens, running ad hoc reports, and often opening a spreadsheet to consolidate the numbers.
In an entity-centric system, the family view exists natively. One screen. All entities. All accounts. All asset classes. The advisor sees what the client sees — a unified picture of family wealth.
This isn't a reporting feature bolted on top. It's a consequence of how the data is structured from the ground up.
2. Succession Planning Becomes Visible
The great wealth transfer is fundamentally an entity-level event. When the patriarch passes, what happens to the family trust? Who becomes the successor trustee? What are the distribution triggers? How does control of the holding company transfer? Which accounts need to be retitled, and to whom?
Account-centric platforms can't answer these questions because they don't model the relationships. Entity-centric platforms can, because the relationships between people and entities are explicit in the data structure.
For advisors who want to retain heirs — and given that the majority of heirs change their parents' advisor, retention is existential — the ability to show the next generation a clear picture of family governance is a competitive advantage. The heir doesn't care about account numbers. They care about understanding the family structure and their role within it.
3. Canadian Complexity Demands It
The Canadian wealth landscape is structurally more complex than many markets. Alter ego trusts, joint partner trusts, inter vivos family trusts, testamentary trusts, graduated rate estates — each with distinct tax treatment and regulatory requirements. Holding companies subject to RDTOH refund mechanisms. Individual Pension Plans. Prescribed Rate Loans between spouses. Family foundations with disbursement quotas.
These aren't edge cases for Canadian advisory firms. They're the daily reality. And they're all entity-level structures that account-centric platforms handle poorly, if at all.
A platform that models these entities natively — with their attributes, relationships, tax implications, and governance rules — doesn't just save time. It reduces the compliance risk that comes from managing complex structures in spreadsheets where a formula error or a missed beneficiary designation can have significant consequences.
Why Nobody's Built This Before
The honest answer: it's harder. Account-centric architecture mirrors how custodians organize data — by account number. Building an entity-centric layer on top requires a fundamentally different data model, a different UX paradigm, and a deep understanding of how wealth structures actually work in practice.
Most wealth technology companies are engineering-led. They build what's technically clean and what custodian data makes easy. Entity-centric architecture requires domain expertise — the kind that comes from years of sitting across the table from families, mapping their structures on whiteboards, and understanding why the trust deed matters as much as the portfolio allocation.
It also requires rethinking the user interface. Account-centric platforms rely on familiar paradigms: tables, lists, drill-downs. Entity-centric platforms need visual mapping — relationship diagrams that show ownership, control, and beneficiary designations across generations. This is a harder design problem, but it's the one that actually matches how advisors think.
The Architecture Is the Moat
In SaaS, features can be copied. An entity-centric data model cannot — at least not easily. Once an advisory firm maps their clients' family structures into an entity-centric platform, that mapping becomes deeply embedded in their workflow. The trust relationships, ownership chains, beneficiary designations, and governance notes constitute institutional knowledge that doesn't exist anywhere else.
For Canadian advisory firms managing complex multi-entity families, the question isn't whether entity-centric architecture is better. It's how much longer they can afford to model families in spreadsheets while the great wealth transfer accelerates around them.
This is the second in a series exploring the technology, architecture, and strategy behind modern Canadian wealth management.