Salesforce for wealth management firms: RIAs and broker-dealers

RIAs, wealth managers and broker-dealers use Salesforce as the relationship layer around their portfolio and custody systems. It holds households, advisor coverage, onboarding, service requests, prospects and supervised marketing. Positions, balances and performance usually stay in the portfolio system and arrive through feeds. A good build makes clear which system owns each fact, keeps advisors out of spreadsheets, and gives compliance a record of what went to clients.

What does a wealth firm actually need Salesforce to hold?

It needs the relationship, not the ledger. Salesforce should answer who the client is, who serves them, what is open and what was said.

Advisors already have a portfolio platform and a custodian portal. What they usually lack is one place that joins the family, the team and the work in flight. That is the gap Salesforce fills.

• Households: spouses, children, trusts and entities grouped under one relationship, with a primary contact and a decision maker.
• Relationships outside the household: attorneys, accountants, trustees and other professionals linked to the client.
• Account summaries: registration type, custodian and a read-only balance, shown for context rather than edited here.
• Open work: new accounts in progress, service requests, review meetings and follow-up tasks.
• Prospects and referral sources, with the history of how each introduction arrived.
• Consent, communication preferences and a trail of outbound client messages.

If your firm is still deciding between Financial Services Cloud and core Salesforce, start with our separate guide on that choice. This article assumes the platform is chosen and focuses on how wealth teams run on it.

Which system should be the source of truth for account and portfolio data?

The custodian and the portfolio management system should own positions, balances, transactions and performance. Salesforce should own the relationship, the workflow and the notes.

Most wealth firms receive data from three kinds of source. Each needs a named owner before anyone writes an integration.

Summaries should flow one way into Salesforce unless there is a clear reason otherwise. Two-way sync of balances invites conflicting numbers in client meetings. Match records on a stable account number from the custodian, never on a client name.

Plan for late and failed files. A feed that silently stops leaves advisors quoting stale balances. Add a last-updated date to every summary and alert an owner when it ages past a set threshold.

How should client onboarding and account opening work in Salesforce?

Treat each new relationship as a tracked process with stages, owners and required documents. Salesforce coordinates the work; the custodian still opens the account.

A new client often means several accounts, transfers from other firms and signatures from more than one person. Without a shared tracker, operations staff chase status by email and advisors cannot answer the client.

• Capture the household and each account to open, with registration type and target custodian.
• Create a checklist of required items per registration, such as identity documents, trust paperwork and transfer forms.
• Assign each step to operations, the advisor or the client, with a due date.
• Record when paperwork went out for signature and when it came back.
• Close the onboarding only when accounts are funded and the custodian feed shows them.

Keep suitability and know-your-customer answers in the system your compliance team designates. Salesforce can store them, but only if field access and retention are designed for it.

How do service requests fit alongside advisor work?

Log every client request as a case with a type, an owner and a target date. That turns scattered emails into a queue the whole team can see.

Common request types include distributions, address changes, beneficiary updates, transfers and document requests. Each type can carry its own checklist and approval step. Distributions above a firm-defined amount might need a second reviewer before submission to the custodian.

Advisors should see open requests on the household record before any client call. Nothing erodes trust faster than a client asking about a transfer the advisor has never heard of.

How should advisor teams and coverage be set up?

Model the team, not just the lead advisor. Most households are served by a lead advisor, an associate and a service specialist, and all three need access.

Use account teams or a custom coverage object to record each role on the household. Base sharing on those roles so that coverage changes automatically change access. When an advisor leaves or books move, reassigning the team should be a single controlled step.

Be careful with firm-wide visibility. Some firms let every employee see every household; others restrict books to the covering team. Decide this with compliance before build, because changing the sharing model later touches every report.

How can Salesforce support prospecting and centers of influence?

Track referral sources as relationships in their own right. Accountants and estate attorneys often send more new households than any campaign.

Record each center of influence as a contact with a type, the advisor who owns the relationship and the households they introduced. That makes it possible to thank the right people and to see which relationships deserve more time.

• Link every new prospect to the person or event that introduced them.
• Log meetings and lunches with referral partners as activities, not private calendar entries.
• Report on introductions and converted households by referral source each quarter.
• Flag referral partners with no contact in a set period so relationships do not go quiet.

How do we run marketing without creating compliance problems?

Design every automated message so it can be approved, archived and retrieved. Your compliance team and counsel set the actual rules; treat what follows as system design guidance rather than legal advice.

Wealth marketing is usually lower volume than retail marketing, but each message carries more supervisory weight. Build approval into the template process, not into individual sends.

• Approve templates centrally, then let journeys reuse them without per-message edits.
• Route a copy of every automated email to the firm's archiving system.
• Keep advisor-specific templates separate so supervision can see who each message came from.
• Store opt-outs in Salesforce and respect them across every tool that sends email.
• Keep a change log for journeys so reviewers can see what a client would have received on a given date.

One fee-only RIA we worked with ran this pattern in Marketing Cloud Account Engagement. A flow sends a feedback survey three days after a financial-planning meeting is marked complete. Each advisor has separate templates and journeys, and a six-email sequence primes prospects. A BCC-to-advisor setup tied into the firm's archiving system kept automated messages archived and supervised. The case study reports more than 35 surveys sent automatically in the first months.

How should Salesforce support meeting prep and client reviews?

Put everything an advisor needs for a review on one household page. Preparation should take minutes of reading, not an hour of gathering.

A useful review page shows household members, fed account summaries and open service requests. It also shows recent notes, life events and the last plan update. A review record can track the meeting date, agenda, attendees and follow-up tasks. Schedule reviews from a cadence field so households do not slip past their annual or semiannual date.

After the meeting, capture decisions and tasks on the same record. The feedback survey pattern above started from exactly this trigger: the review was marked complete.

Where does AI fit when client communications are regulated?

Use AI to draft, summarize and prepare, and keep a person responsible for anything that reaches a client. Treat AI output as a draft that follows the same review path as any other message.

Reasonable early uses include summarizing a household's recent activity before a review, drafting follow-up notes for advisor editing and suggesting next steps on service cases. Each keeps a human in the loop before anything is sent or recorded.

Before switching anything on, confirm with compliance how AI-drafted content is supervised and archived. Check with your Salesforce account team which AI features your licenses include and where data is processed.

Which reports matter to wealth firm leaders?

Leaders want coverage, pipeline, service and review completion from Salesforce. AUM by household usually comes from the portfolio system, and Salesforce should show that figure rather than calculate its own.

• New households and assets expected, by advisor and referral source.
• Onboarding in progress, with days open and the stage where each is stuck.
• Open service requests by type, owner and age.
• Reviews due, completed and overdue this quarter.
• Households per advisor, as a check on capacity.
• Summary AUM by household and advisor, drawn from the feed and labeled with its as-of date.

What mistakes do wealth firms make with Salesforce?

Most problems come from unclear data ownership and from treating compliance as a later phase. Both are cheaper to settle before the build starts.

• Letting staff edit balances in Salesforce, so two numbers circulate for the same account.
• Building households without agreed rules for trusts, entities and adult children.
• Automating client email before the archiving and approval path is proven.
• Copying every field from the old CRM instead of deciding what advisors really use.
• Setting sharing by individual advisor, then struggling when teams and books change.
• Launching without a named owner for each custodian or portfolio feed.

Custom builds also need discipline. One broker-dealer client tracked both sides of capital-raising deals using custom objects in Sales Cloud. That build added Engagement and Investment objects, validation rules on stage gates and three contact record types with role-based security. It worked because the data model was designed around how the firm operated, not bolted on later.

What should a wealth firm put in phase one?

Start with households, coverage, service requests and a read-only portfolio summary. Add onboarding workflow and supervised marketing once the core record is trusted.

• Household and relationship structure, loaded and cleaned from the old CRM.
• Advisor team roles and a sharing model approved by compliance.
• One inbound feed of account summaries with ownership and alerting agreed.
• Service request types with owners, target dates and checklists.
• A household page layout built for review meetings.
• Core reports for pipeline, service backlog and reviews due.

Later phases can add onboarding automation, center-of-influence tracking, compliant marketing journeys, a client portal and AI-assisted preparation. Each one builds on a household record that advisors already trust.