8 Salesforce FSC Project Later... My Verdict: Don't
8 Salesforce Financial Services Cloud projects. Declarative and coding enhancements. Mostly greenfield implementations. And I caution against it.
Spoiler, and no surprise to anyone familiar with Salesforce, cost comes into play. I’ll go into more detail on each of these, but here’s the high-level sum up:
💸 “Features” – Light value, heavy price tag. Salesforce’s quirks are baked in, turning customization into a nightmare. Account Contact Relationships require incantations to deal with programmatically. Making Action Plans behave the way users assume it should took more effort than building it from scratch. And you'll likely only leverage a few of these bells & whistles.
📊 Built-in data model – Similar diminishing returns. If you’re buying FSC, you already know what fields you need on a Financial Account. Hire an intern for a week, get the same outcome without the recurring invoice.
🔫 Triggers – Black box. Impossible to control. My team ended up abandoning FSC objects and rebuilding them custom just to escape them.
Considering FSC? Trying to escape FSC? Trying to force FSC to obey your business requirements? Codality knows the traps, we’ve solved them, and we’ll build you what FSC promises... without the recurring Salesforce tax if you haven't signed the contract yet 😉
Jessie Grenfell
Jessie has spent 20+ years architecting and delivering software for organizations where complexity is the norm — financial services, insurance, nonprofits, and regulated industries where getting it wrong isn't an option. She specializes in the hard problems: unique operational workflows, cross-system integrations, and the kind of compliance requirements (HIPAA, CCPA, SOC 2) that most developers treat as someone else's job.
At Codality, she leads every principal engagement from discovery through delivery — because she's seen what happens when that thread gets cut.