Is Salesforce still the best for Fortune 500? 500-user deployment feedback

I'm a product ops lead at a 300-person fintech. We run Salesforce Sales Cloud and Service Cloud for about 400 users globally, alongside a custom CPQ and Marketo.

**Core comparison for a 500-user deployment:**
* **Real pricing:** List is $150/user/month for Sales Cloud Enterprise. At 500 users, you'll negotiate, but expect ~$100-120/user. Real cost is 2-3x that with mandatory Success plans (~$50k/year starter), implementation partners, and add-ons like CPQ or Marketing Cloud.
* **Deployment & admin overhead:** Initial global rollout with basic custom objects and workflows took 9 months with a big SI partner. Ongoing, you need 1 dedicated admin per ~150 users. Complex automations become a maintenance burden quickly.
* **Where it clearly wins:** Ecosystem and compliance. For a global Fortune 500, pre-built integrations for SAP/Oracle and granular data residency controls are battle-tested. No other platform has as many ISV solutions for niche needs.
* **Honest limitation & support:** It breaks when over-customized with code. Apex triggers can grind performance. Enterprise support is slow for non-critical tickets (48-hour response common). You pay for Premier+ ($90k/year) for anything resembling a strategic partner.

**My pick:** For a **global, compliance-heavy Fortune 500 rollout with complex legacy integrations,** Salesforce is still the default. The safe choice is expensive and requires internal admin headcount. If your processes are simple or mostly greenfield, tell us your core CRM use case and budget per user.

Oh, the licensing complexity is real. Even after you negotiate that user price down, you'll get surprised by platform fees, like additional API call costs if your integrations scale. The real kicker for us was the "add-on tax" - once you're committed, features like advanced workflow or data storage cost a premium.

And on customizability becoming a burden, it absolutely can. We built this beautiful, complex automation suite. Fast forward two years, and new hires couldn't figure out why records updated the way they did. We spent more on a consultant to document our own system than we did building parts of it. It's a double-edged sword.

For a 500-user global rollout, the admin overhead is significant. We found we needed a full time technical admin AND a business-process admin, almost like an internal product manager, just to keep things running and handle change requests. Have you factored that headcount into your TCO?

Management's idea of a "safe" enterprise choice is often just the one that's easiest to justify to the board, not the most operationally sound. That licensing complexity you've heard about isn't a rumor, it's a revenue model. The base user fee is just the cover charge.

Your question about customizability becoming a burden hits the real issue. The platform's flexibility is a sales feature that turns into a technical liability. You'll end up with a bespoke application built on a rented foundation, and your team will be on the hook for all its undocumented quirks. Ask yourself if you really want to be in the software development business for your CRM.

At 500 users, you're buying a platform plus an entire services economy to support it. Is that still the "best fit" or just the most familiar?

Nailed the bit about the services economy. That's the real lock-in, long after the go-live party. The platform is almost a loss leader for the ecosystem.

You see it when you try to hire. The market is flooded with "certified administrators" who can click through setup menus, but finding someone who can actually reason about the business logic tangled in your org is a fortune. You're not just paying Salesforce. You're funding an entire parallel industry of consultants who speak a proprietary dialect.

So it's not just a rented foundation. It's a rented foundation where you have to pay the architect's union every time you want to move a wall. Familiar? Sure. Best fit? That assumes you needed a custom-built house to begin with.

Your point about needing one dedicated admin per 150 users is optimistic. At 400 users with Service Cloud and custom CPQ, we needed two full-time admins just to keep the lights on and handle basic change requests. The maintenance load scales exponentially, not linearly, once you go beyond basic workflows.

That mandatory Success plan you mentioned is particularly galling. For $50k a year, you'd expect more than glorified documentation and a quarterly call. It's a tax for the privilege of having a complicated product.

And while the ecosystem is a selling point, it's also a trap. "Pre-built integrations" for SAP often mean you're paying an SI another six figures to make them actually work for your specific business logic.

You're right about the admin ratio being optimistic. In our 550-user Sales Cloud deployment, we measured it as "admin effort hours per user per quarter" and saw a clear inflection point after implementing Process Builder and custom objects. The baseline support wasn't the issue, it was the change management.

That success plan fee is particularly difficult to budget for because it's not tied to any measurable output, like reduced ticket resolution time. It becomes a fixed cost of doing business, which makes the total cost of ownership calculations misleading.

Have you found any effective way to push back on or justify that specific fee to finance? We've tried linking it to project roadmap support, with limited success.

You're spot-on about the "rented foundation." That's what makes the cost of change so high later.

I've seen teams build incredible, tailored solutions, but then get stuck on an older Salesforce release because the upgrade path for their custom logic is either impossible or costs more than the original build. The flexibility feels empowering at the start, but it really does lock you into their upgrade cycle and pricing model.

It becomes less about the software and more about managing the business risk of your own customizations.