Why we model households, not accounts

Published August 2026 · By the UltimateCRM team

The unit of advice is the family

Think about what an advisory conversation is actually about. Spending is household spending. Goals — retire together, fund the kids' college, leave something behind — are household goals. Taxes are usually filed jointly. Estate questions are, by definition, about what happens between people. Even "individual" facts like a 401(k) balance only mean something in the context of the family's whole picture. The client is the household; the contacts are members of it.

What contact-centric systems get wrong

• Scattered records. The meeting note lands on whichever spouse happened to call. Six months later you're searching three records for one conversation.
• Documents on the wrong person. Is the estate plan under him, her, or the trust? In a person-centric tree, someone has to guess — twice: once filing, once retrieving.
• Split finances. Net worth divided across two contact records isn't net worth; it's two half-pictures that have to be mentally merged in every meeting.
• Planning blind spots. Retirement outcomes for couples hinge on joint dynamics — survivor income, spousal benefits, the widow's tax penalty. Person-centric data literally cannot represent the scenario that matters most.

What household-first means in practice

In UltimateCRM the household isn't a tag — it's the architecture:

• Every contact belongs to a household, even singles (a household of one), so there is exactly one way to file everything and no orphaned records.
• Rollups by default. Notes, tasks, documents, and activity on any member surface on the household — open the family and see the whole story.
• One wealth profile per household feeds net worth, planning, and KYC alike. Enter a fact once; every view agrees. (It's also why our KYC data doesn't go stale.)
• The file tree is the household — documents live in a per-household folder structure, and placement itself says whether something is family-level or personal.
• Life changes are handled structurally. When someone moves households — a marriage, a divorce, an adult child striking out — their files and records re-home automatically instead of dangling.

It's a correctness issue, not a preference

The deepest reason is planning math. Our retirement engine models couples properly — per-spouse retirement ages, per-spouse deferred balances and RMDs, survivor income, and the switch to single tax brackets at the first death. None of that is computable from two disconnected person records; the household dataset isn't a nicer way to organize the inputs, it is the input. Firms feel the difference at the worst possible time: when a spouse dies, a contact-centric system offers a record to close, while a household system offers the surviving family — history, documents, and plan intact.