Salesforce
Financial Services Cloud Implementation

Salesforce says Financial Services Cloud unlocks data from core banking, wealth and insurance platforms and unifies it around the customer. Its product page lists these capabilities, among others:

• Client and household view: core banking, custodian, policy and third-party data in one client record.
• Sales cycle management: prospecting through onboarding, including referrals and account opening.
• Service processes: prebuilt processes such as banking disputes and insurance claims.
• Data connectivity: prebuilt APIs for integrations such as MoneyGuidePro, Experian and Mastercard.
• AI agents: prebuilt Agentforce agents for banking, wealth and insurance work, with data residency controls, guardrails and audit trails.

Salesforce says teams already on Sales Cloud or Service Cloud can activate Financial Services Cloud in their org. For connecting the core systems, see our Salesforce integration services.

In Salesforce's learning content, yes. Trailhead's basics module is titled "Meet Agentforce Financial Services" and says "Financial Services Cloud is now called Agentforce Financial Services." Its data model units use the new name too.

Salesforce's own product pages still use the old name. On salesforce.com/financial-services, the product is Financial Services Cloud, within Salesforce for Financial Services, and the pricing page lists editions such as Financial Services Cloud Sales Core and Financial Services Cloud Service Max. Agentforce for Financial Services appears there as an add-on, the AI agents, not as the product name. In practice the two names refer to the same product, so check both when you read documentation, release notes or license quotes. This page uses Financial Services Cloud, the name on Salesforce's price list.

Salesforce sells Sales and Service editions at three levels. Prices are per user per month in US dollars, billed annually, and Salesforce says they are for information only and subject to change.

Salesforce lists add-ons on the same page: Digital Insurance and Digital Origination are included in Max and are add-ons for Core and Advanced. Implementation cost depends on scope; our implementation cost guide explains what moves it.

1. Map business lines. Decide which teams go live first: advisers, bankers, service or insurance.
2. Choose editions. Match Sales or Service, and Core, Advanced or Max, to each team.
3. Design the data model. Clients, households, financial accounts and the relationships between them.
4. Connect source systems. Core banking, custodians, policy administration and data providers.
5. Migrate and reconcile. Load client and account data and check it against the source.
6. Configure processes and controls. Onboarding, referrals, service cases, access and audit.
7. Test, train and launch. User acceptance testing, training, cutover and support in the first weeks.

To plan yours, book a discovery call.

The data model is what separates Financial Services Cloud from a generic CRM. Salesforce describes one view of each client and household, with core banking, custodian, policy and third-party data brought into the client record, and prebuilt processes for selling, onboarding and service.

• Households and relationship groups: clients grouped with the people they share finances with, so advisers see the whole relationship.
• Financial accounts: accounts, holdings and policies held by one or several people, linked to each client and household.
• Sales and onboarding processes: prospecting, referrals and account opening.
• Service processes: prebuilt processes such as banking disputes and insurance claims.
• Action plans: Trailhead says action plans and action plan templates help staff manage and track manual, repeatable tasks, such as verifying client data during onboarding, so each rep follows the same steps.

Lenders can add Techila's own Salesforce loan origination software, LendSuite, which is built on Salesforce Financial Services Cloud.

Four decisions come before the build in every segment: the data model, the core systems to connect, the compliance review and the licenses. What each one involves differs by business line.

On the data model, Trailhead recommends that new users "use standard features and objects" rather than the objects in the managed package, and represents individual clients as person accounts. Trailhead also notes that once person accounts are turned on, they cannot be turned off, so that choice is made first.

We work through these four decisions in the assessment phase. To start, book a discovery call.