How to Set Up HubSpot for an RIA or Wealth Management Firm

Every CRM conversation that matters is a conversation about the object model — which tables exist, and what each row represents. HubSpot ships four: contacts are individual people, companies are organisations, deals are transaction opportunities, and tickets are service requests arising from them. Those four describe a business that sells to a company and supports it afterwards. They do not describe an advisory firm, because the thing an RIA bills, reviews and reports on has no table.

This is the part most firms are never asked about, and it is the part that determines whether the CRM will fit. A partner who starts with dashboards and email templates has skipped it. The question to answer first is what your business model implies about the tables — and for an RIA the answer is two more of them.

A household is the family unit: the thing that is billed, the thing that gets reviewed, and the thing that is won or lost. It carries the service tier — private client, wealth management, core advisory, emerging, or legacy low-touch — the lead adviser, the next review date, the annual fee, and a status that moves from prospect through onboarding, active, at risk, transitioning and departed.

An account is where the money sits, and crucially where it does not. It carries the balance, the custodian, the account type — taxable individual, Roth IRA, employer 401(k) — and whether the asset is held away. That last flag is the one firms most often leave out, and it is the one that turns the assets you do not manage from an anecdote into a report an adviser can work through.

Contacts still matter, and they get the properties a person needs: role in the household, whether they are the trusted contact or a beneficiary, the most recent life event and its date, the next review topic, and the personal detail an adviser wants in front of them on a call. A contact can be associated with more than one household, which sounds like an edge case until the attorney who represents three client families arrives and a single-household model has nowhere to put them.

The growth path runs through the objects rather than alongside them. A referral arrives and becomes a household, not a person. Held-away assets are written down at that point rather than after the fact, which is what makes them workable by the advisory team. A plan is presented, paperwork goes out, and the relationship is funded from the custodian.

The deal pipeline mirrors that sequence — introduction, discovery meeting, plan creation with the finance team, plan presented, paperwork out, funds transferred — and stages advance on events rather than on someone remembering to drag a card. A signed document arriving is a stage change. So is a funding confirmation.

Service tier sets how often a household is reviewed, and the next review date is set from it rather than typed in. Workflows then do the work that otherwise depends on memory: reminders and tasks ahead of a review, recovery when paperwork stalls, follow-up on held-away assets, and a life-event watch that notifies the managing adviser so a human response follows within days rather than at the next scheduled call.

The difference this makes is not convenience. A review cadence that the system enforces is a cadence the firm can evidence, which is a different conversation with a compliance reviewer than a set of calendar habits distributed across advisers.

Because AUM lives on household records, total AUM is a roll-up rather than a rebuild. From the same data a firm can read AUM by household status, household status broken down by service tier, account balance by account type, held-away against managed, expected AUM in the active pipeline, and annual fee by household status.

The reports that change behaviour are the unglamorous ones: overdue reviews ranked by assets, and where the rest of a household’s money is. Both are only possible because the household and the held-away flag exist as data rather than as knowledge.

Where a firm wants more than balances, a transactions object sits beneath accounts as a child record and receives a feed from the portfolio system. That supports a transaction ledger and net-flow reporting inside HubSpot, and for a firm running its own fund, performance reporting in the same place the client relationship lives.

This is an addition rather than a starting point. Households and accounts are what the operating model needs; a transaction ledger is what a firm adds once it wants its business intelligence in one pane rather than two.

Most of the RIAs we work with arrive from Redtail, often tied into Orion, with an advisory team that avoids the system wherever it can. HubSpot integrates with Orion, Juniper Square and Redtail itself, so a firm can connect rather than move if it needs to — though a firm leaving Redtail usually wants the migration, not the bridge.

Calls, emails and meetings log to the contact and roll up to the household, so the relationship history is in one place instead of in individual mailboxes. Where a portal handles material requiring stricter controls, HubSpot’s enterprise data-management features cover sensitive-data handling — configured deliberately, not assumed.

A partner quoting this from scratch will price the object model, the properties, the workflows and the dashboards as bespoke work, and the number lands in the tens of thousands. We have built it already — the households and accounts objects, their properties, the review-cadence and life-event automation, and the reporting — and install it into a portal directly.

That covers most of it and not all of it. How your client-service team actually works, how you handle documents, and what an adviser expects to see when they open a household are specific to your firm, and that part is configuration rather than engineering. Removing the engineering is what makes the implementation affordable without removing the revenue-operations judgement.