The Financial Services landscape
Buying in financial services runs on two tracks at once. The business sponsor, usually a head of retail banking, lending, or wealth, owns the problem and the budget. A second group owns the right to say no: information security, compliance, vendor risk management, and often an IT architecture board. A deal that only has the first track will stall at vendor due diligence. Get the risk team's questionnaire early and treat it as a milestone in the mutual plan, not a surprise in the last month.
- 01
Who owns CRM varies by size.
In community banks and credit unions it often sits with a COO or a small digital team, and the core banking vendor has outsized influence. Regional banks and larger wealth firms usually have a CRM or digital product owner and a formal RFP. Independent RIAs move fastest: the founder or COO decides, and custodian and portfolio integrations are the real scope.
- 02
Salesforce sells Financial Services Cloud across banking (commercial, retail, credit unions and community banks, mortgage and lending), insurance, and wealth and asset management.
Its pitch centers on pulling data from core banking, wealth, and insurance systems into one client view, with financial workflows and approvals built in, and with Agentforce, Data 360, Tableau, and Slack around it. For small RIAs, Salesforce also markets a pre-configured advisor accelerator it positions for firms of about 25 or fewer employees.
- 03
Two regulatory shifts give you a reason to call.
In 2024 the SEC amended Regulation S-P to require covered institutions such as brokers and advisers to keep a written incident response program and to notify affected individuals no later than 30 days after learning of unauthorized access to customer information. And since the SEC charged 16 firms in September 2022, with more than $1.1 billion in combined penalties, over off-channel communications, recordkeeping has stayed on every compliance agenda. Neither is a product feature. Both are reasons leaders will talk about where client data and conversations live.
Who buys, and how to open with them (6)
Head of Retail Banking or Consumer Lending
Cares about: Deposit growth, product depth per household, branch and contact center productivity, and how fast an application moves from first touch to funded.
“When a customer opens a checking account in a branch, how does the lending team find out that person also has a car loan somewhere else?”
- Where do referrals between branches, the contact center, and lending get logged today, and who sees whether they convert?
- How many systems does a banker open to prepare for a single customer conversation?
- Which product line do you most want to cross-sell next year, and what stops it today?
- How do you measure time from application to decision, and where does it slow down?
Head of Commercial Banking or Treasury Management
Cares about: Relationship profitability, onboarding time for new commercial clients, credit pipeline visibility, and coordination between relationship managers, credit, and treasury specialists.
“When a commercial client is onboarding, how many people outside the relationship manager are chasing the same documents?”
- How do you see the full relationship, including related entities, guarantors, and treasury services, on one screen?
- Where does the credit pipeline live before it reaches the loan origination system?
- How long does commercial onboarding take, and which step is the longest?
Head of Wealth Management or RIA Founder
Cares about: Advisor capacity, client retention through generational transfer, assets per household, and keeping the firm's book intact when advisors join or leave.
“If your best advisor left tomorrow, how much of what they know about their households would still be in your systems?”
- How do advisors prepare for a review meeting today, and how long does it take?
- Which custodians, planning tools, and portfolio systems need to feed the client record?
- How do you track the next generation in a household before the assets move?
Chief Compliance Officer
Cares about: Supervision evidence, communications review, retention of records, and limiting who can see which client data. Wants fewer exceptions, not more dashboards.
“I'd like to understand how you evidence supervision today before we propose anything that touches client communications.”
- Which communications and records do you need to retain and review, and where do they live now?
- How do you restrict access between business lines or between advisor teams?
- What would an AI-drafted client message need to go through before it is sent?
CIO or Head of Digital
Cares about: Integration with the core, the loan origination system, custodians, and the data warehouse; total cost to own; security architecture; and avoiding another system nobody maintains.
“Which system of record do you trust least for customer data today, and what would change if CRM became the place people actually work?”
- What integration layer do you use today, and what does it cost to add a new feed?
- Where is your customer master, and how many copies of the customer exist?
- What does your vendor risk review require, and how long does it usually take?
Chief Marketing Officer or Member Experience Leader
Cares about: Relevant, permitted outreach at life events; consent and opt-out handling; attribution from campaign to account opened or loan funded.
“When a member's situation changes, like a new home or a new job, how quickly does your next message reflect it?”
- How do you honor privacy opt-outs and channel preferences across every send?
- Can you connect a campaign to an account opened or loan funded today?
- Who approves marketing content, and how long does approval take?
The problems worth solving (6)
Fragmented customer view across product silos
Deposits, lending, cards, and wealth often run on separate systems with separate customer IDs. Bankers cannot see the full relationship, so cross-sell depends on memory and luck. Households, business owners with personal accounts, and related entities make it harder, because the relationship is a network, not a single account.
Where Salesforce fits: Financial Services Cloud models households, relationships, and financial accounts on the client record. Data 360 and MuleSoft bring in core and product system data so the banker sees one relationship.
Slow, document-heavy onboarding
Account opening and commercial onboarding involve many documents, signers, and checks. Status lives in email and spreadsheets. Clients wait, relationship managers chase paper, and operations cannot see where the queue is stuck. Every delay is a chance for the client to fund the account somewhere else.
Where Salesforce fits: Financial Services Cloud workflows and approvals track each onboarding step. Experience Cloud gives clients a portal to upload documents and see status. Flow automates handoffs between teams.
Advisor and banker capacity
Advisors and relationship managers spend hours assembling meeting prep, notes, and follow-up tasks. That time comes straight out of client conversations and prospecting. Firms that want to grow assets or loans without adding headcount have to give people back their week.
Where Salesforce fits: Agentforce agents in Financial Services Cloud can prepare meeting briefs, summarize calls, and create follow-up tasks and records, with human review before anything reaches a client.
Supervision and access control
Compliance needs to know who touched which record and who can see what. Shared CRM objects, team-based coverage models, and information barriers between business lines make standard sharing hard to configure. Teams often over-restrict, which breaks collaboration, or under-restrict, which creates risk.
Where Salesforce fits: Compliant Data Sharing in Financial Services Cloud lets admins and compliance managers define participant roles and share records with specific people or groups without code, on objects set to private or read-only defaults.
Referrals that disappear
A teller hears about a business owner's expansion plans. A mortgage officer learns a client is selling a business. These signals rarely reach the right partner, and nobody can tell leadership which referrals converted. Referral programs lose credibility when staff never see the outcome.
Where Salesforce fits: Sales Cloud and Financial Services Cloud referral and lead routing send the signal to the right specialist and report on conversion, so leaders can see which branches and teams create value.
Advisor transitions and book transfers
Wealth firms recruit advisors with books and lose advisors to competitors. Moving households, accounts, and history into the firm's system is slow and manual. When an advisor leaves, the firm needs reassignment, client outreach, and access removal on the same day, or the households follow the advisor.
Where Salesforce fits: Financial Services Cloud households and relationship data make reassignment a structured process, and Compliant Data Sharing changes access in one place.
The numbers leaders run on (6)
Products per household or member
The core measure of relationship depth for banks and credit unions. Financial Services Cloud household and financial account data shows it by segment and banker.
Assets under management per advisor
Wealth leaders use it to judge advisor capacity and growth. Custodian feeds into Financial Services Cloud roll up assets by household and advisor.
Time to onboard or time to fund
Measured from first contact to funded account or loan. Workflow timestamps in Financial Services Cloud show which step takes the longest.
Referral conversion rate
Shows whether cross-team referrals turn into revenue. Referral and opportunity records in Sales Cloud or Financial Services Cloud give the numerator and denominator.
Client or household retention
Losing a household or a commercial relationship costs years of revenue. Activity, service case, and balance trends in Salesforce help flag at-risk relationships before they move.
Pipeline by product line
Lending, treasury, and wealth leaders forecast differently, but all need visibility before deals reach the system of record. Opportunity data by product and stage feeds the forecast.
Product fit (7)
Cross-sell sequence (4)
- Sales Cloud Financial Services Cloud"We built custom objects for households and accounts and nobody trusts them." Or the team keeps asking for relationship views that standard objects do not model.
- Financial Services Cloud Data 360"Our core and custodian data shows up a day late," or marketing wants to segment on balances and product holdings it cannot reach today.
- Financial Services Cloud Agentforce"Advisors spend half a day preparing for reviews," or the contact center handles the same balance and status questions all day.
- Financial Services Cloud Marketing Cloud / Account Engagement"We still send the same newsletter to every member," or opt-outs are managed in a spreadsheet next to the email tool.
Objections, and what to say (5)
"Our core vendor already has a CRM module."
That module is often fine for logging calls on core accounts. Ask what it shows about wealth, lending pipeline, referrals, and service cases that live outside the core. Then ask how easy it is to change a workflow without a vendor ticket. Position Financial Services Cloud as the place bankers work across products, with the core staying the system of record for balances and transactions. Bring a picture of the integration, not a rip-and-replace slide.
"Compliance will never approve AI touching client data."
Agree that they should be careful. Then make the first use case internal: meeting prep, call summaries, and task creation that an advisor or banker reviews before anything goes out. Invite the CCO into design, not just approval. Ask what controls they would need to see, such as review steps, logging, and access limits, and map each one to configuration. Do not claim the product makes them compliant. Show that the controls are theirs to set and evidence.
"We tried Salesforce before and advisors stopped using it."
Ask what the advisors were asked to do in it. Most failed rollouts made CRM a data entry chore with nothing coming back. The fix is to give advisors something they cannot get elsewhere: custodian data on the household, prepared meeting briefs, and fewer screens. Propose a pilot with one team and a success measure they care about, like prep time per review. A partner health check on the old org can also show what to keep.
"Vendor risk review takes six months."
Then start it now, in parallel with discovery. Ask for the questionnaire and the reviewer's name this week. Salesforce has standard security and compliance documentation; get your solution engineer and security team engaged early. Put the review milestones in the mutual plan with dates. A long review only kills a deal when it starts after the business has already decided.
"We are a small RIA. This is built for big banks."
Salesforce markets a pre-configured advisor accelerator in Financial Services Cloud aimed at firms of about 25 or fewer employees. Scope to the essentials: households, custodian feed, meeting workflow, and compliant communications. Small firms win by doing less, well. A fixed-scope implementation with a partner keeps cost predictable, and the platform still has room when the firm acquires its next book.
Implementation watch-outs to raise before signature (5)
Decide the household and relationship model first
Households, business owners, trusts, and related entities drive reporting, sharing, and marketing. Changing the model after go-live means rework everywhere. Get operations, wealth, and compliance to agree on how a household is defined and who owns it before configuration starts.
Sharing rules are a compliance design, not an admin task
Information barriers, team coverage, and advisor-owned books need a written access model signed off by compliance. Compliant Data Sharing only works on objects with private or read-only defaults, so plan org-wide defaults early. Test with real users from each team before launch.
Integration scope hides in the core
Core banking, loan origination, custodians, and document systems each have their own data timing and access rules. Confirm what data the core vendor exposes, how often, and at what cost. Budget for integration testing with real volumes, not sample files.
Retention and communications capture
If email, texts, or AI-drafted messages flow through Salesforce, the firm's archiving and supervision process must cover them. Decide which system is the archive of record and how messages get there. Compliance should test the capture before advisors use the feature.
Advisor and banker adoption
Launch with something that saves time on day one, like prepared meeting briefs or consolidated household views. Train by role, not by feature. Track logins and activity by team for the first 90 days, and fix friction weekly instead of waiting for a phase two.
Qualify honestly
Strong fit
- A named business owner with a measurable goal, such as deeper households, faster onboarding, or advisor capacity
- Compliance and security engaged in discovery, not only at contract stage
- A known integration path to the core or custodian with data access confirmed
- A trigger event: core conversion, advisor recruiting push, acquisition, or exam finding
- Budget owner who has seen a similar project fail or succeed and knows what it takes
Risky fit
- The only sponsor is IT and the business has not described the problem
- Vendor risk review has not started and nobody knows who runs it
- The core vendor contract limits data access or charges per integration and nobody has checked
- The buyer expects Salesforce to make them compliant rather than support their controls
Case studies to send (4)
- A regional bank replaced ActiveCampaign with integrated Marketing Cloud across every product line →
- A fee-only RIA automated post-meeting client surveys while staying SEC-compliant →
- A business lender processing 24,000 leads a month built AI lead scoring and a Data 360 (formerly Data Cloud) roadmap to protect a limited sales team →
- A broker-dealer got a custom capital-raising system on Salesforce with 5+ objects and complex commission splits →
Questions (4)
When should I lead with Financial Services Cloud instead of Sales Cloud?
Lead with Financial Services Cloud when the customer manages households, relationships between people and entities, or financial accounts that need to appear on the client record. If the buyer only needs pipeline management for a small commercial lending team, Sales Cloud may be enough to start. Ask how they define a client before you decide.
Can I tell a bank or RIA that Salesforce is compliant with SEC or FINRA rules?
No. Rules like FINRA Rule 2210 on communications, SEC recordkeeping requirements, and the FTC Safeguards Rule for non-bank lenders and mortgage brokers apply to the firm and its processes. Salesforce provides controls such as access rules, approvals, and audit history that the firm configures and evidences. Say that, and bring compliance into design.
How do I handle credit unions differently from banks?
Credit unions talk about members, not customers, and often run smaller teams on tighter budgets. Their core vendor carries a lot of weight, so confirm integration access early. Expect privacy questions grounded in NCUA's Regulation P on notices and opt-outs before sharing with nonaffiliated third parties. Lead with member experience and staff capacity, and scope tightly.
When should I bring in Abstrakt?
Bring us in at discovery when the deal involves Financial Services Cloud design, custodian or core integration, or compliance-sensitive AI. We reply to AEs within four business hours, and we offer a free health check for customers you refer who already run Salesforce.
Sources (8)
- Salesforce: Financial Services Cloud and industry solutions
- Salesforce: Wealth management software
- Trailhead: Get started with Compliant Data Sharing
- SEC press release 2024-58: Regulation S-P amendments
- SEC press release 2022-174: off-channel communications recordkeeping charges
- FINRA Rule 2210: Communications with the public
- FTC: Safeguards Rule, what your business needs to know
- NCUA: Privacy of consumer financial information (Regulation P)