The Hidden Cost of Salesforce

The Cost Stack Nobody Talks About

Salesforce Financial Services Cloud licensing runs $150–$330 per user per month. For a 30-advisor firm, that is $54K–$119K per year before anyone has customized anything, built a report, or connected a data source. But that licensing figure is just the floor.

The full cost picture for most wealth management firms looks like this:

• Implementation: $75K–$250K initial build — and it is never truly "done"
• Consulting retainers: $5K–$25K/month for ongoing changes, bug fixes, and new reports
• AppExchange add-ons: $10–$50/user/month each, and most firms run 3–7 of them (DocuSign, Conga, Geopointe, etc.)
• Data migration: $20K–$75K every time you change something fundamental
• Training: $5K–$15K annually, because the system keeps changing and people keep turning over
• Integration development: $25K–$100K per custodian or portfolio system connection

To put those numbers in context: a 50-advisor firm — call them Flat Iron Wealth — might pay $200K/year in Salesforce licenses, $180K/year in consulting retainers and project work, and $60K/year across their AppExchange stack. That is $440K per year for CRM. The licensing line item is less than half the total.

These ranges reflect real patterns across wealth management firms. Where your firm lands depends on headcount, customization depth, integration complexity, and how often your needs change. But almost universally, the licensing number firms budget for is a significant undercount of what Salesforce actually costs.

The Consulting Dependency Cycle

The consulting cost problem is not just about the dollar amount — it is about the structure. Salesforce is a platform built for extensibility, which means customization is always available as the answer to any operational need. That is genuinely useful. It is also how firms end up in a cycle that is hard to exit.

The pattern looks like this: you customize Salesforce to fit a workflow — consultants build custom objects, Process Builder flows, Lightning components. Those customizations create complexity. That complexity requires the same consultants to maintain it, because no one internally understands how the pieces connect. The consultants, naturally, recommend further customization to solve the next problem. Repeat.

The Tribal Knowledge Problem

After a few years of this cycle, your consultant knows how your Salesforce instance works better than you do. The configuration lives in their head and their notes, not in your documentation. If you want to switch consultants — whether due to cost, quality, or relationship reasons — you face a re-discovery engagement ($15K–$30K) just to bring a new firm up to speed. Most firms decide the switching cost is not worth it, which is exactly the leverage that makes consulting retainers sticky.

The Release Problem

Salesforce releases updates three times per year. Each release can break custom work. Flows stop functioning. Custom Lightning components behave unexpectedly. Integrations that relied on a particular API behavior fail silently. Firms with heavily customized instances spend real money after every Salesforce release on emergency consulting to diagnose and fix what broke. This is not a hypothetical — it is a routine budget item for mature Salesforce users in wealth management.

The Lock-In Is Not What You Think

The common concern about Salesforce lock-in is that your data is trapped in Salesforce. That is solvable — data can be exported. The deeper lock-in is the consulting dependency itself. The more you have customized Salesforce, the more you need someone who understands those customizations to keep them working, change them, or document them for anyone else. You are not locked into Salesforce. You are locked into your specific consultant's institutional knowledge of your instance.

Breaking the Cycle

Consultants are not the villains in this story. They are doing exactly what Salesforce's architecture encourages: building solutions inside the platform for every problem a firm brings them. The dependency model is the problem, not the people executing within it.

Breaking the cycle does not require abandoning Salesforce. It requires moving the functions that drive consulting dependency to platforms better suited for those tasks — and letting Salesforce do what it does natively well without needing constant customization to extend it.

Milemarker's approach addresses the dependency at its source:

• Extract your data out of Salesforce: Analytics and reporting no longer require Salesforce customization when your data lives in Snowflake. Query directly. No SOQL. No consulting required for new reports.
• Milemarker Workflow for advisor-facing needs: Purpose-built for wealth management workflows — onboarding, reviews, compliance steps — without requiring Salesforce Flow or Process Builder customization to handle them.
• Milemarker Automation for operational workflows: Handles the automation use cases that firms currently build in Salesforce using consulting hours, without the Salesforce complexity or maintenance overhead.
• Standard integrations via Milemarker: Pre-built connections to custodians and portfolio systems replace custom Salesforce integration development. No $50K–$100K integration project per system.

The goal is not to rip out Salesforce. It is to make Salesforce a simple, stable system of record that does not require constant consulting to function, adapt, and integrate. Simple systems break less. Simple systems require less consulting. Simple systems are easier to hand off if you ever do decide to change.

What to Keep in Salesforce, What to Move Out

Not every Salesforce use case has a better home elsewhere. The goal is not wholesale migration — it is strategic rationalization. Keep what Salesforce does well natively. Move what requires ongoing customization and consulting to do adequately.

Frequently Asked Questions