Family Relationship Architecture
How a wealth management firm modeled multi-generational households in Zoho CRM, mapping family relationships and account ownership across generations.
Client details generalized to protect confidentiality.
Advisory firms serving families rather than individuals, where a standard contact and account structure cannot express who is related to whom.
The Challenge
A standard contact and account model could not represent how the firm actually served clients. A household included spouses, adult children, trusts, and entities, with accounts owned in combinations that did not map to a single primary contact. Advisors kept relationship context in their heads and in notes, which meant coverage depended on the individual advisor and transitions between advisors lost information that was never written down.
The Solution
Household as a First-Class Record
The household is its own record rather than an attribute of a contact, so relationships and totals attach to it.
- Households module with member links
- Household-level rollup fields
- Primary and secondary relationships
- Multiple households per individual supported
Relationship Mapping
Relationships between individuals are explicit and typed, so the structure is readable by someone who has never met the family.
- Typed relationship links between contacts
- Generation indicator per member
- Bidirectional relationship display
- Trust and entity members supported
Account Ownership Structure
Accounts record who owns them and in what capacity, including joint and entity ownership.
- Ownership junction between account and contact
- Capacity and percentage per owner
- Entity and trust ownership modeled
- Ownership history retained
Household Rollups and Coverage View
Assets and activity roll up to the household, which is the level at which the firm actually manages the relationship.
- Rollup of account values to household
- Activity coverage by member
- Next generation contact tracking
- Household review scheduling
Apps in This Solution
Zoho CRM
Under the Hood Technical detail
- Structural Decision
- Households are a separate module rather than a field on Contact, because an individual can belong to more than one household, which a field cannot express. Adult children with their own households and shared accounts with parents is the ordinary case, not an edge case.
- Ownership Junction
- Account ownership sits in a junction record carrying capacity and percentage, rather than a lookup to a single owner. Joint and entity ownership are common enough that a single-owner model forces data into the wrong shape immediately.
- Generation Tracking
- Each member carries a generation indicator, which is what makes next-generation coverage reportable. The firm’s stated retention concern was losing assets at wealth transfer, and that risk was previously unmeasurable.
- Rollup Direction
- Values roll up from accounts to household rather than being maintained at household level. Maintained totals drift; derived totals do not.
- Notable Constraint
- Family structures change through divorce, death, and remarriage. Relationships carry effective dates and prior relationships are retained rather than deleted, so historical context survives a structural change.
The Results
- Household relationships are explicit rather than held in advisor memory.
- Joint and entity account ownership is modeled correctly.
- Next generation coverage is reportable, which it was not before.
Serving Families in a Contact Model?
We have built household and relationship architectures for wealth management and advisory firms. Tell us how your clients are structured.