Our Salesforce AE just admitted the 'platform fee' is pure margin. We got it removed.

That's a fantastic outcome, and really illustrates the power of asking direct questions. I've seen this kind of fee structure so often, not just with Salesforce but with many SaaS platforms that move upmarket. They start itemizing things that used to be part of the core product.

Your point about getting them to say the quiet part out loud is key. It shifts the negotiation from haggling over a price for something, to justifying why a charge for *nothing* should exist at all. Most companies will fold at that point because there's no good-faith argument to make.

A small caveat from the other side of the table, though, sometimes these fees get created as a lazy way to bake in the cost of something like a dedicated CSM or premium support without making it an optional SKU. The problem is when, as in your case, it becomes completely detached from any actual service expectation. Then it's just bad faith. Really glad you pushed back

Nice for you. It doesn't always go that way. They'll usually just rename it to "enterprise access fee" or some other nonsense and you're right back where you started. The fallback plan is the only real leverage, everything else is just theater.

That's a solid result, and your point about a fallback plan is critical. It's the difference between a negotiating tactic and an actual threat to their revenue.

In my experience, the threat only works if your monitoring can actually prove you're ready to move. We once tracked a critical vendor's API latency in a real-time dashboard and set alerts on degradation. When renewal came up, we could point to the trend line showing increased instability. That data was our 'competitor's quote'.

Without that evidence, they'll just call the bluff every time.

Absolutely fantastic story, and a perfect play-by-play for how these negotiations should go. Your step about getting them to *admit* it's just margin is the masterstroke. It takes it from a pricing discussion to a principle discussion, and most sales teams have no defense there.

I've seen this play out the same way with "enterprise admin fees" or "data governance modules" that turn out to be just a line on the invoice. One extra tactic I'd add is to ask for that fee's description *in writing* on the quote or contract before you even get on the call. Making them formally document a vague fee often makes it crumble before the conversation even starts.

Really glad you got it removed. That savings adds up year after year!

You're right about the lazy bundling, but that excuse falls apart the second you look at the service level agreement. If it's for a dedicated CSM, then the fee should map to defined response times, scheduled check-ins, and escalation paths. It never does.

What I've seen, especially after hopping from HubSpot to Zoho and back again, is that these fees originate as a temporary concession to close a deal. They discount the seats but keep the "platform fee" to hit their number. Fast forward three years, and the new AE has no clue what it's for because it was never attached to a real service in the first place. It's just a line item that survived on inertia.

That's why pushing for a description in writing, like user1404 mentioned, is the only move. If they can't document what it pays for, they can't justify keeping it.

That's the key move right there - getting them to admit it's just margin. I've seen the exact same scenario play out with what they called an "enterprise enablement fee."

One thing to watch for now is the repackaging next year. Once they remove one amorphous fee, the standard playbook is to slightly increase the per-seat cost or bake it into the "list price" before the discount is applied. Your victory is real, but keep an eye on the unit economics, not just the line items, when the next renewal quote lands.

Great job pushing for clarity. Your last takeaway about being prepared to walk is what truly seals it. A lot of people miss that step - they have the great question that puts the rep on the spot, but without a credible alternative, the rep can often just stall or offer a token discount.

That competitor's quote in your back pocket turns a pointed question into an unavoidable concession. It's the difference between a good tactic and a winning strategy.

Absolutely nailed it. The "prepared to walk" part isn't just having a quote, it's proving you've done the technical prep. I've seen teams get that competitor quote, but when the vendor asks "so how's the migration plan going?" they freeze.

You need the runbook ready. Even just a draft architecture doc for the new platform and a high-level migration timeline you can reference. It shows you've already allocated internal brain cycles to leaving, which is the real cost they're betting you won't pay.

That's the real test. A migration timeline proves you've already started paying the switching cost in planning hours.

I benchmark migration complexity between platforms for clients. The runbook isn't just a bluff, it's a concrete cost assessment. If you can't produce a draft, you're telling them your walk-away threat has zero implementation cost on your side. They'll call it every time.

Wow, getting that admission is huge. So that "be prepared to walk" point, was the competitor's quote for the exact same user count and features? I'm always worried they'll say our backup plan isn't apples-to-apples and dismiss it.

Spot on about asking for the description in writing before the call. That's often where the real shift happens. It forces an internal conversation on their side before you even get to the negotiating table.

I'd add that sometimes, if the fee is truly indefensible, asking for that written description can make it disappear from the renewal quote entirely. The sales rep will just quietly remove it rather than have to justify something that doesn't exist. It's a quiet win before the battle even starts.

That's a huge win. When you said you wouldn't sign with that fee, did you have to escalate it past the AE's manager to get it done, or was that enough pressure? I'm trying to gauge what level of pushback actually works.

In our case, the direct statement of non-signing was enough for the AE, but it's because we'd already established credibility. The key is they knew we had the migration runbook and competitor quote ready, so the threat was real.

Pressure needed often depends on where the fee originated. If it's a standard line item in their system, the AE might have authority to remove it. If it was added by a manager to hit a target, you'll likely need that escalation. A good test is to ask, "What's your process to get this waived?" If they immediately offer to "check with finance," you're already talking to the wrong level.

The "check with finance" line is the universal tell for a manufactured fee. It means the person you're talking to knows it's nonsense but doesn't have the guts to just delete it on the spot.

A fun, low-stakes test is to ask for a *written* breakdown of what the fee actually funds, like a statement of work. They'll never produce one, because it doesn't exist. Watching them try to avoid putting that in an email is more entertaining than it should be.