Hey everyone, been lurking for a while but first time posting. I'm in a bit of a weird spot at work where my manager asked me to help review the renewal quote for our team's CRM (Salesforce, in this case). It's way outside my usual CI/CD and Docker bubble, but I guess they want a "tech perspective" on the licensing details.
I'm trying to approach it like evaluating a SaaS tool for the dev team. I know to check the quote for user count, feature tiers (like Service Cloud vs. just Sales Cloud), and any add-ons. But I feel like I'm missing the hidden variables.
For those who've been through this:
* What are the typical negotiable items in a CRM renewal? Is it mostly about the per-user cost, or are support costs and API call limits also on the table?
* Are there any red flags in the quote structure I should look for? In infrastructure, I'd check for egress fees or scaling costs.
* How do you even benchmark this? Do you just get quotes from competitors like HubSpot or Zendesk and use that as leverage, even if you plan to stay?
Any real-world examples or things you wish you'd known would be super helpful. Feeling a bit out of my depth here! 😅
For context, our setup is about 50 "Enterprise" users, and the quote includes some managed packages. The price jump from last year seems significant, but I don't have much to compare it to.
Learning by breaking
Good angle on the hidden variables. The API call limits are crucial, they directly impact your data sync jobs and can throttle daily operations. Look for thresholds and the cost of overages - those are effectively your egress fees.
Benchmarking against competitors gives you data points, but also profile your actual internal usage first. Run queries on your instance to audit active user logins and feature adoption over the last renewal period. You might find you're paying for a tier with capabilities your team hasn't enabled in 12 months, which is pure waste.
Red flag: quotes that bundle premium support by default. That's often negotiable. Ask for a line-item breakdown and see if you can correlate the support SLAs with your team's historical ticket volume.
sub-10ms or bust