Financial Services Cloud: what the package does, and where it stops
FSC is a good package. It is also a package, and every wealth or lending firm we have worked with hit the same four walls within a year. Here is what the package does well, where it stops, and what we built around it at two named firms.
Bohdan PyrihCEO, AdvirixWhat you get out of the box
Financial Services Cloud adds a data model to Sales and Service Cloud that most firms would otherwise build badly: Person Accounts for individuals, Households, Account-Contact Relations for who belongs to which household in which role, Financial Accounts with balances and holdings, and Action Plans for cadences such as onboarding, KYC review and annual reviews. If households, relationships and financial accounts are the centre of your work, that model is worth the licence.
At Alterra Advisors, a wealth-management firm, the model was in place and half-used: household naming drifted, member roles were out of sync, and the team spent 70–80% of the day in Salesforce doing by hand what the model could do for them. The first work was not new features. It was reworking the household-centric model so Person Accounts, Households, relations and financial accounts stayed consistent, and only then automating on top of it.
Wall one: custodian data
Schwab, Fidelity and Pershing do not send you FSC objects. They send files and feeds, and a firm that pastes them into spreadsheets has no client view, only a client folder. At 49 Financial, a planning firm custodied with Charles Schwab, the custodian integration was inconsistent and there was no true 360-degree view. The fix was event-driven: Platform Events and Change Data Capture carrying custodian data into the org, so 100% of it landed in one client view, and advisers became 60% more efficient because the screen finally matched the job.
Wall two: managed packages
Many wealth firms extend FSC through a managed package such as Salentica. The accelerators are real. So are the limits: fields you cannot add, storage you cannot exceed, automation you cannot change, and triggers that fight your own logic for governor limits. 49 Financial hit all four. We built a custom extension layer with child and external objects for the high-volume and specialised data, and used event-driven integration so the package's triggers and ours never collided. The firm kept Salentica and avoided the lock-in.
Wall three: referral and advocate programmes
FSC has a Referrals object. It does not have your tiers, your points, your cadences or your conversion rules, and it has no opinion about who owns a referral when two advisers claim it. At Alterra the referral and advocate workflow lived in people's heads. We put it in Salesforce with Apex and Flow: origin and owner routing, stage movement with required fields and validations, task-based cadences, conversion and disqualification paths, tier progression and engagement dates for advocates, and the dashboards that made advocate relationships measurable for the first time. Zero critical errors after deployment.
Wall four: reporting a CFO can check
AUM, pipeline and compliance cadence on one dashboard, in real time, instead of a spreadsheet updated on Friday. This is the wall firms hit last and feel most, because the board sees it. It is also the one that cannot be built first: reporting on dirty household data produces confident wrong numbers. At 49 Financial, real-time AUM, pipeline and compliance tracking for leadership came after the data and integration work, not before.
Do you need FSC at all?
Not always. A lender running simple deal stages, or a fintech with its own core system, often does better on Sales Cloud with a documented layer than on FSC with half the model unused. The licence difference is real money every month. On the first call we ask what sits at the centre of your work: if it is households, financial accounts and relationships, FSC earns its place; if it is a pipeline and a product catalogue, it probably does not. The Health Check report says which, with the reasoning written down.
What to check in your own FSC org this week
- Pick ten households at random. Are the names, members and roles consistent with what the advisers know?
- Where does custodian data live today: in objects, in files, or in someone's inbox?
- List every field or automation you wanted and could not add because of a package. That list is the extension layer.
- Open the referral report. Does it show owner, stage and conversion, or only a count?
- Ask the CFO which number on the dashboard they would bet on. If the answer is none, start with the data.
How to decide in one meeting
Five questions, asked in order, with the people who will use the system in the room. One: what sits at the centre of the work, a household or a deal? Two: which external system holds the money: a custodian, a loan system, your own ledger? Three: which managed package, if any, is already in the org, and what has it stopped you doing? Four: which report does the board actually read, and who updates it today? Five: who will own the org on your side after the project? The first two answers decide FSC or Sales Cloud. The third decides whether an extension layer is needed. The fourth decides where the data work starts. The fifth decides whether any of it will hold.
Three FSC orgs, three different problems: Alterra Advisors, 49 Financial, GoodLeap. The page on Financial Services Cloud has the short version.