Just received a Salesforce renewal quote with a new line item I haven't seen before: a **$50,000 "Platform Success Fee."** This was presented as a non-negotiable charge for "ensuring platform stability and innovation." It's separate from implementation, support, or training. My procurement team is pushing back, but the account rep is holding firm, suggesting it's standard for "enterprise-scale usage."
From a CI/CD perspective, this feels like a hidden tax on the deployment pipeline. We've heavily automated our Salesforce deployments using a combination of Salesforce DX and Jenkins pipelines. Our `Jenkinsfile` orchestrates everything from metadata validation to production pushes.
```groovy
pipeline {
agent any
stages {
stage('Validate & Test') {
steps {
sh 'sfdx force:mdapi:convert -r ./src'
sh 'sfdx force:source:deploy -c -l RunLocalTests -u devhub'
}
}
// ... deployment stages to various sandboxes
}
}
```
My question to the community: **Has anyone successfully negotiated this fee away or had it reduced?** Is this truly a standard charge now, or is it a leverage point because they see our high deployment frequency and complex org? Specifically:
* Did labeling it as a "mandatory platform access fee" come up?
* Were you able to tie concessions on this fee to a commitment on their side, like guaranteed API limit increases?
* Does this often get rolled into the per-user license cost upon pushback?
Any data points on actual negotiation outcomes would be invaluable for our renewal talks next month. We're considering anchoring our counter by threatening to strip back our upcoming Service Cloud expansion if this fee remains.
--crusader
Commit early, deploy often, but always rollback-ready.
Yeah, I've seen this pop up more recently with larger accounts. They often introduce new fees during renewal when they feel you're locked in. Calling it "non-negotiable" is a pretty standard pressure tactic.
From a community management angle, I'd suggest framing your pushback around transparency and partnership. Ask them to specifically define what services or outcomes this fee buys that aren't covered by your existing support and subscription costs. That usually forces a more honest conversation.
It's absolutely negotiable, but you'll likely need procurement to formally reject the quote and be willing to let the renewal date lapse. Have you tried escalating past your account rep to their manager? Sometimes that's all it takes.
~Harry
Great point about pushing for specific definitions. That transparency tactic works because it forces the vendor to either provide a concrete value proposition for the fee or expose it as purely operational overhead.
When they do try to define it, you'll often get a list of things you're already paying for in your support plan or that should be part of the core subscription. My standard playbook here is to request a side-by-side matrix mapping this fee's deliverables against our current contract's service descriptions. It usually collapses under its own weight.
Escalation is key, but be prepared for the manager to also lean on the "standard for your tier" line. Have your procurement team ready with a clean, redlined version of the quote with this line item deleted as your official counter-proposal. Letting the renewal date approach without signing creates real leverage.
null
The matrix comparison is a solid tactic, but in my experience, the "standard for your tier" pushback can be quantified against your own usage. They're implying this fee correlates to your scale and complexity.
When they say that, I immediately pull our own platform analytics: number of monthly active users, transaction volumes, API call counts, and the volume of metadata changes deployed through our pipeline. If our usage hasn't changed dramatically tier-wise since the last renewal, the fee is not for scale but for margin. Presenting that data shifts the conversation from subjective definitions to objective contract terms.
Your redline counter-proposal is the right final step, but precede it with that data-driven rebuttal. It prevents them from framing your pushback as merely procedural and anchors it in the actual value exchange, or lack thereof.
You're right about escalation sometimes being all it takes. A few renewals back, I had a similar "mandatory" fee appear. My rep wouldn't budge, but a single email to their manager, cc'ing my finance lead and politely asking for the contractual basis of the new charge, got it removed in 48 hours. The key was having the paper trail ready.
That said, I'd add one caveat to your point about letting the renewal date lapse: for a platform as central as Salesforce, that's a high-stakes game of chicken. I've found it's more effective to start the escalation process *early*, right when the quote arrives, and to schedule a call with the manager *before* the formal rejection. It frames it as a collaborative discussion to resolve a blocker, not a confrontational ultimatum.
The "non-negotiable" line is almost always a first-position tactic. Once you move past the rep, the conversation usually changes.
— francesc
>starting the escalation process *early*
Agree this is better than waiting, but your 48-hour success story is luck. I've seen these "mandatory" fees get defended up three management levels once the finance team has baked them into a quarter's forecast.
The paper trail is critical, but it needs to be more than a polite email. Your counter should include:
- A screenshot of the prior year's invoice showing the line item didn't exist.
- Your usage data showing no exponential growth that would trigger a new "tier."
- A direct ask for the amendment document that authorizes this new charge against your MSA.
Without that, their legal/contracts team will just back the rep's play and you're stuck.
show me the bill
Good to hear your procurement team is already pushing back. From your Jenkins snippet, it looks like you're doing the heavy lifting on stability and deployments yourselves anyway. A $50k "success" fee on top of that automation is a hard sell.
I've seen this fee waived, but never without escalating past the rep and tying it directly to a lack of additional services. One tactic that worked for us was asking them to itemize any dedicated personnel or specific innovation projects this fee would fund for our account over the next year. They couldn't, and it folded.
Since they're leaning on the "enterprise-scale usage" angle, your CI/CD pipeline metrics are your best weapon. Compare deployment frequency and success rates from your last renewal period to now. If your automation is handling scale efficiently, their fee is just margin. Have you pulled those logs yet?
Always A/B test.