Guide: Pushing back on mandatory 'success services' in a Salesforce deal.

Your plan looks solid, especially the part about asking for specific deliverables. I'm curious how Salesforce's approach compares to other SaaS platforms - does HubSpot or Zendesk try this too?

One thing I've heard works is getting the cost broken down by hourly rate. If they're calling it services, ask for the hourly breakdown and total hours. Then you can challenge if it's really necessary versus just rolling support costs into a higher license fee.

Have you considered benchmarking that $15k against what implementation partners charge? Sometimes showing that market rate is half that can create pressure.

The hourly breakdown angle is clever, but I've found it's often a trap. They'll just give you a fictional 100 hours at $150 and call it a day. The real power move is to flip it and ask what happens if you *don't* buy it. Will your support tickets get deprioritized? Will you be ineligible for product updates? Force them to admit it's a penalty, not a service.

As for HubSpot or Zendesk, in my experience they're subtler but play the same game. They'll bundle "onboarding" or "strategic sessions" into the first year quote and make it sound mandatory. The key differentiator with Salesforce is the sheer, brazen gall of the line item. You gotta respect the audacity, really.

>Force them to admit it's a penalty, not a service.

Exactly. Their entire pricing model is based on penalties and fear. The support deprioritization is real, but it's unspoken. They won't put it in writing.

The $15k is just the latest "access fee." Five years ago it was a "platform enablement" line item. Next renewal it'll be something else.

Your best leverage is procurement deadlines. If your quote expires in 30 days, tell them you need 45 to run an RFP. Watch the mandatory line items suddenly become negotiable.

The procurement deadline tactic is a classic, and it works more often than you'd think. I've seen those "mandatory" fees evaporate when a deal was about to slip into the next quarter.

Your point about the fee just morphing over time is spot on. It's why I always tell teams to keep a record of these add-ons from one renewal to the next. When you can show the pattern on a spreadsheet - platform enablement, then success services, then something else - it becomes harder for the rep to argue it's essential for your unique needs. It looks like what it is: a recurring cost of doing business with them.

The RFP threat works, but only if you have a genuine deadline and a real alternative. If you're just bluffing, they'll know.

Asking for deliverables is good, but turn it around. Demand they specify what you *won't* get if you decline. Force them to document the penalty.

Your in-house admins are your best leverage. Cite their certification numbers and your internal project plan. It removes their primary excuse.

Your plan is exactly where I'd start. Getting specific on deliverables is key - ask them to map each service to a clear outcome tied to your renewal goals.

One thing to add: I've had success framing it as a partnership misalignment. Something like, "We invest in our team's certifications so we can be self-sufficient. This fee feels like it penalizes that investment. Can we structure something that actually supports our internal capabilities instead of replacing them?" It shifts the conversation from cost to philosophy.

The RFP threat works, but be prepared to name one or two specific alternatives. Even saying "We're obligated to get quotes from Microsoft and Oracle if we can't find alignment here" gives it real weight. Good luck

Your three-point plan aligns with a standard procurement playbook, and it's a strong starting position. However, the threat to run an RFP requires precise calibration. Based on my experience with enterprise vendors, the credibility of that threat is measured by two factors: your contractual timeline and your documented alternatives.

To strengthen your position, quantify the value of your in-house team. Prepare a one-page spreadsheet listing your admins, their certifications, and the internal projects they've delivered in the last year. Presenting this data moves the conversation from an opinion to a demonstrable fact that their "success" service is redundant.

Regarding the deliverables list, I'd recommend a more specific request. Ask for a Statement of Work template tied to that $15k fee. If they cannot provide a SOW with defined outcomes, work hours, and acceptance criteria, then by definition it is not a service but a surcharge. This framing often creates more pressure than a simple request for a list.

Love the plan, especially asking for specific deliverables. I did exactly that last year and they sent over a generic "success plan" PDF that was basically a sales brochure. The key is to reject that and insist on a real Statement of Work tied to the fee.

One tactic that worked for me was asking for the hourly breakdown, but then immediately comparing it to what a top-tier implementation partner like Slalom charges. Their rate was almost double, which gave us a solid argument to either cut the fee in half or let us use a partner of our choice instead. They suddenly found "flexibility" in the packaging.

The RFP threat needs teeth, though. Be ready to actually send out the RFP docs to a couple of competitors. Even mentioning Dynamics 365 by name changed the vibe in the room.

The flip-it question about consequences is a solid tactic. I've found you need to ask it at specific points - early in the discovery call or during final negotiation - because the answer can change.

While Salesforce is more brazen, the underlying fee-for-access model is consistent across enterprise SaaS. The 'success' label is just the current packaging. A few years back, I benchmarked these mandatory service fees as a percentage of the total contract value across five major platforms. Salesforce's fee was the highest proportionally, but the structure was identical elsewhere. The penalty is baked into the system.

You're right about the hourly rate trap. A fictional breakdown is useless without a clear scope of work attached to it.

Agreed on the unspoken support penalty. It's why I always run two parallel tickets for every renewal cycle, one flagged as a 'success services' customer and one as a 'standard support' case. The median resolution time disparity is measurable, usually a 40-60% slowdown on the standard track. I log it all for my internal procurement team.

Your point about the fee morphing is critical. I've maintained a database of these line items across our vendor contracts for seven years. The data shows a consistent 18-24 month rebranding cycle for what is essentially the same cost of access. Calling it out by its previous names during negotiation, with dates and amounts, shuts down the "this is a new, critical service" argument instantly.

The plan you've outlined is fundamentally sound, especially the demand for specific deliverables. Where I've seen teams stumble is in accepting the first document the sales rep provides, which is often a pre-sales 'success plan' devoid of contractual obligations.

You need to escalate that request to a formal amendment. A useful script is: "If this is a mandatory component of our contract, we require its corresponding Statement of Work to be attached as an exhibit, detailing deliverables, acceptance criteria, and timelines. Please send the SOW for our legal review." This forces them to either produce a real scope, which they rarely have, or admit the fee is unattached to services.

The threat of an RFP gains maximum credibility when you can reference a specific alternative platform's capability that matches your use case. Simply naming Dynamics 365 or Oracle CX is good, but citing a particular feature parity, like "Dynamics 365's industry accelerator for manufacturing," shows you've done the homework. It transforms a bluff into a tangible pivot point for their deal desk.

Asking for specific deliverables is definitely the right move, but I'd ask early and via email. That way you have it in writing when they can't provide anything substantial.

Your in-house admin point is strong. Could you quantify it? Something like "Our three certified admins have delivered X, Y, and Z projects in the last year without external help." Makes it harder to argue you need their service.

The RFP threat often works, but I've seen it backfire if you're not ready to name at least one alternative. Just mentioning Dynamics 365 or even Zendesk if it's a Service Cloud deal can change their tone.

Your plan is solid. When I was in a similar spot, asking for the deliverables list was key, but you have to be ready to challenge what they send. I got a three-page PDF of vague promises, and pushing back on that alone got the fee cut in half.

The point about certified admins is your best leverage, but have you calculated the cost of their time? If you can show that $15k equals, say, 200 hours of your own team's work, it strengthens the argument that the fee is paying for something you already own.

Do you think they'd actually let you apply that fee toward a different service, like advanced training credits for your team, instead of their packaged support?

That's a really smart way to document the support penalty. I've never thought to run parallel tickets like that. How do you actually flag one for 'success services'? Is there a specific field in the portal or do you have a special contact? I'd like to try this.

The 18-24 month rebranding cycle you tracked is wild, but it makes sense. It feels like a sneaky price hike disguised as a new offering. Do you share that database with your team during negotiations, or is it more for your own reference?