Wealth managers, banks, insurers, and lenders all tried to run on plain Sales Cloud, and most of them hit the same wall. A household is not an account. A book of business is not a list of contacts. And a supervisory regime does not care that your CRM was not designed for it. Financial Services Cloud exists because these industries need the relationship model, the compliance scaffolding, and the integrations baked in, not bolted on later by a generalist.
We run FSC deep: full implementations and migrations off generic Salesforce orgs, household and client modeling that reflects how advisors actually serve relationships, advisor productivity tooling, and the supervisory and compliance infrastructure these firms are held to. Just as important is the integration work, the custodians, planning platforms, performance reporting, and lending systems, that determines whether FSC is a single source of truth or just another screen an advisor ignores.
The common failures: lifting a generic Salesforce org into FSC without rethinking the data model, so the household structure is cosmetic; advisor tools that add clicks instead of removing them; compliance treated as a reporting afterthought rather than a design input; and integrations to custodians or planning tools that break quietly and erode trust in the data. We design the relationship model, the supervision, and the integrations together, because in this industry they are the same problem.
We have built FSC for Registered Investment Advisors and financial firms for years, and wealth management is one of our deepest verticals. As a Salesforce Consulting Partner since 2017 with 150 Salesforce certifications and a 4.95 out of 5 rating from 92 Salesforce AppExchange reviews, we treat compliance and the custodian and planning integrations as first-class from day one, because that is what separates an FSC org advisors trust from one they work around.
The engagements we run most often on Salesforce Financial Services Cloud, from first implementation through optimization.
Advisor productivity, household and client modeling, planning and performance integrations, compliance evidence, and supervisory workflows.
Producer hierarchies, quote-and-bind workflows, claims, policy admin integration, and compliance/licensing tracking.
Commercial banking relationship management, deposits, lending pipeline, and integration with core banking systems.
Migrations from generic Sales Cloud or legacy CRMs (Redtail, Wealthbox, Practifi) to FSC without losing book context.
Integrations with Schwab Advisor Services, Fidelity Wealthscape, Pershing NetX360, Orion, eMoney, MoneyGuidePro.
SEC 17a-4 retention, FINRA 2210/3110 evidence, Reg BI documentation, and IAR/Form ADV workflows.
Engagements are measured by movement on the numbers that matter. These are the directions of travel we commit to.
Predictable phases. Clear deliverables. No surprises.
One to two working sessions to map your current state, business goals, and gaps. We come out with a written scope and recommendation.
Documented architecture, realistic timeline, and transparent commercial proposal. No surprises and no hidden scope.
Configuration, development, integrations, data migration, and QA, with weekly demos and on-the-fly adjustments.
Training, change management, hypercare, and ongoing optimization. We do not disappear at go-live.
Consultant-level analysis from the consultants delivering the work.
Why financial firms struggle to get value from Salesforce, the relationship, compliance and data design that fixes it, where AI fits under supervision, and a phased roadmap for banks, lenders, wealth managers and insurers.
Read the full post →A configurable graph on the client record that shows people, businesses, trusts and financial accounts connected to one another, with actions launched straight from each node. It matters when an advisor or banker needs to see that a business owner is also a trustee, a beneficiary and a guarantor before the next conversation starts.
Record access rules driven by participant roles and participant groups rather than ownership alone. Firms with information barriers, joint coverage teams or shared branches use it to grant access to exactly the relationship managers working a client. It replaces broad sharing settings and hopeful report filters, and it is usually the hardest security decision in the project.
Standard objects for accounts, holdings, securities, cards and loans, each linked to its owners and joint owners. Balances feed in from the systems of record. Rollup logic then totals them at the individual and household level, so a banker sees relationship value without opening several screens or waiting for a monthly statement run.
Reusable task templates that lay out every step, owner and deadline for a repeatable process. Examples include onboarding a trust, opening a commercial account or completing an annual review. Operations leaders use them so nothing is skipped when volume spikes, and supervisors can see which plans are running late across a team.
Guided assessments built on OmniStudio that capture needs, goals and suitability answers in a structured form and write them back to the client record. Salesforce has added AI checks that read uploaded documents and prefill linked fields. It fits firms that still collect fact-finds on paper or fillable documents and retype them, where errors and missing disclosures creep in.
Tools for tracking commercial and corporate banking deals with the parties, interactions and compliance approvals attached. Relationship teams log meetings with confidentiality controls and record who attended from each side. Deal information stays walled off from staff who should not see it, which is essential when advisory and lending sit in the same institution.
Choose how people, households, businesses and trusts will be represented, and whether person accounts are enabled, before anything else is configured. This choice shapes rollups, sharing, reports and every integration, and changing it after data is loaded means rebuilding far more than anyone expects. Settle it in workshops with advisors, operations and compliance together.
For each balance, position, policy or loan field, name the system that owns it and how often it refreshes. Salesforce should show and aggregate those figures, never act as a second ledger. Agree on reconciliation ownership too, because a mismatched balance on a client screen erodes trust faster than a missing feature.
Work through role hierarchy, compliant data sharing, branch structures and field-level restrictions with the compliance officer present. Test them with realistic personas such as an assistant supporting two advisors or a lender covering a shared region. Access defects found after go-live are both costly and reportable, so this step deserves dedicated test cycles.
Launch to a single advisory team, branch or line of business with real data loaded and integrations running. Watch where people still keep side spreadsheets, which screens they skip and which alerts they ignore. Then adjust page layouts, action plans and automation before a wider rollout makes those habits permanent for everyone.
Add wealth, retail banking, commercial lending or insurance groups one at a time, each with its own record types, processes and training. A phased expansion lets supervisors review evidence and reports for one group before the next arrives. It also keeps data migration batches small enough to validate record by record.
Salesforce briefly marketed Financial Services Cloud as Agentforce Financial Services and now uses the Financial Services Cloud name again, with Agentforce for Financial Services describing the AI capabilities. It is licensed per user, with sales-oriented and service-oriented options. Existing contracts use Enterprise, Unlimited and Agentforce 1 tiers; in September 2026 Salesforce announced Core, Advanced and Max editions for Agentforce Industries, with industry pricing taking effect later in the fall, so confirm which structure your quote uses. Some capabilities, such as Digital Insurance and Digital Origination, are packaged separately, and others appear only in higher tiers. Before signing, confirm with your account executive which features you rely on sit in your chosen edition and how prebuilt agents are metered. Ask how assistants, operations staff and read-only compliance reviewers should be licensed, plus sandbox entitlements and storage for holdings history.
Assistants, operations staff and supervisors rarely need the same features as advisors or relationship managers. Buying one edition for the whole firm often means paying for capabilities half the users never touch. Worse, a key feature may turn out to be missing for the people who need it. Map features to roles before the contract is drafted.
Loading years of transactions and positions into Salesforce bloats storage, slows reports and creates a second copy that drifts from the system of record. Most teams need current balances, recent activity and summary values. Keep detailed history in the source platform and link to it, or surface it on demand through an integration.
Household and relationship totals depend on rollup settings being configured and scheduled correctly. Firms that load accounts but never tune rollups end up with households showing zero assets or double-counted joint accounts, and advisors quickly stop trusting the summary. Before launch, check a sample of real households against their latest statements and fix every gap.
Many guided processes in the industry cloud, including discovery questionnaires and intake flows, are built with OmniStudio. Teams that staff the project only with standard administrators hit a wall when those components need configuring. Budget for OmniStudio skills from the start, or scope those features out of the first release deliberately.
A Salesforce Health Check reviews your org and gives you a ranked list of what to fix first, with effort estimates. It is the right starting point before an optimization project, a new cloud or an AI initiative.
Wealth management, banking, insurance and lending firms that need household and relationship views, financial accounts and compliance-aware workflows on Salesforce.
It depends on how much of the financial data model you need. Some firms are well served by Sales Cloud with custom objects: a broker-dealer we worked with runs capital raising on 5+ custom objects supporting 140+ associated persons.
Yes. A fee-only RIA automated post-meeting client surveys while staying SEC-compliant, sending 35+ surveys in its first months.
Yes. Published work includes an insurance agency with strict per-agent record privacy and a mortgage lender activating 30,000+ contacts.
Usually yes. The industry data model installs into an existing org, but the relationship model, record types and sharing often need rework. Some custom objects will map onto standard financial objects. We inventory what you have and decide what to keep, map or retire. Then we migrate in stages so users are not dropped into a completely new system on one weekend.
No. Core banking, custodial and policy administration platforms remain the systems of record for balances, trades, claims and policies. Financial Services Cloud sits on top as the engagement layer, where staff see those figures alongside relationships, tasks and conversations. Integrations bring summary data in on a schedule or in near real time, and processes that need the core system call out to it.
The data model lets one person relate to many entities, such as a household, an operating company, a trust and a foundation, each with its own role. Relationship views show those links together. A banker preparing for a business loan conversation can see the owner’s personal accounts and family connections, subject to the sharing rules that govern who sees what.
It can be. Salesforce packages insurance-specific capabilities, including brokerage features and Digital Insurance, alongside the core product. Carriers typically use them for producer management, policy servicing and claims visibility, while agencies focus on client relationships and renewals. Which pieces apply depends on your distribution model, so we confirm current packaging with Salesforce before recommending a configuration. Licensing and data model choices differ enough between the two that the decision deserves settling early.
Beyond a Salesforce administrator, plan for someone who understands the industry data model, someone comfortable with OmniStudio if you use guided processes, and an owner for each integration. Compliance should have a named contact who reviews sharing changes. Salesforce ships three major releases a year, so someone should read the industry release notes and test new features in a sandbox before each upgrade lands.
The CRM where sales pipeline lives, when it is built right.
The operating system for modern customer service, case, knowledge, voice, and AI agent assist together.
Scheduling, dispatch, mobile work orders and parts for teams that work on site.
Cross-channel marketing, email, mobile, journey, and data-cloud-powered personalization at scale.
Configure-price-quote, billing, subscription management, and quote-to-cash on Salesforce.
AI agents that handle real work inside Sales Cloud, Service Cloud, and Marketing Cloud.
Tech Talk
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.
