Red Flags to Check Before Signing Your CRM Renewal

Most CRM contract problems get discovered at the next renewal, when it’s too late to negotiate them away. This is a vendor-agnostic checklist of the specific clauses worth reading closely before signing — regardless of which CRM you’re on.
Auto-renewal and notice period
- Does the contract auto-renew by default, and what’s the notice period to opt out?
- Is the notice window long enough to actually run an evaluation of alternatives before it closes?
- Does auto-renewal lock in the current seat count, or does it reset to a higher committed minimum?
Price escalators
- Is there a built-in annual price increase, and is it capped or open-ended?
- Does the increase apply to existing seats, or only to new ones added after renewal?
- Are add-on modules subject to separate, uncapped price increases?
Seat-count minimums and true-ups
- Is there a minimum seat commitment that doesn’t shrink if actual usage drops?
- How does a mid-term “true-up” for added users work, and how does it differ from the renewal-time rate?
- Can seats be reduced before the next renewal, or only at renewal itself?
Feature gating and tier lock-in
- Are features you currently rely on being moved to a higher tier at renewal?
- Does the new contract quietly bundle add-ons you didn’t ask for into the base price?
Data export and exit terms
- What does the contract guarantee about data export format and timeline if you leave?
- Is there a fee for data export or an extended “read-only” access period after cancellation?
| Clause | Why it matters |
|---|---|
| Auto-renewal with short notice window | Locks you in before an alternative can be evaluated |
| Uncapped annual escalator | Compounds every year regardless of usage |
| Seat minimum with no true-down | You pay for shrinkage the same as growth |
| No guaranteed export format | Real switching cost hidden until you try to leave |
Bring an alternative to the table, not just objections
A red-flag checklist gives you leverage in the conversation, but leverage works better paired with a concrete alternative — a projected number for what a custom portal would cost for your light users instead of more seats, run through the savings calculator. For the fuller pre-purchase version of this checklist, see RFP questions to ask before buying a CRM portal add-on.
Frequently asked questions
How is this different from a Salesforce-specific renewal negotiation guide?
This checklist covers contract clauses that apply to any CRM vendor’s paperwork. Salesforce-specific renewal tactics — timing, discount structures unique to that platform — are covered separately for readers on that specific CRM.
Should we push back on every red flag we find?
Prioritize the ones with real financial exposure — uncapped escalators and seat minimums with no true-down — over cosmetic issues. Vendors have more room to move on some clauses than others, and a focused ask lands better than a long list.
What if the vendor won’t remove a clause we flag?
That’s useful information on its own — it tells you how much leverage you actually have at this renewal, and whether the alternative (reducing seat dependency structurally) is worth accelerating.
Related articles
- Technical Signs Your CRM or Portal Locks You In
Contract clauses aren’t the only lock-in risk. Proprietary schemas, non-portable workflows, and API limits can tra…
- RFP Questions to Ask Before Buying a CRM Portal Add-On
The questions that surface hidden per-seat costs, lock-in risk, and integration gaps before you sign a CRM portal or cli…
- Data Ownership: SaaS CRM vs. a Custom-Built Portal
HIPAA, GDPR, and SOC 2 govern how a vendor handles your data — not who controls where it lives. That distinction matters…
- TCO: SaaS Add-Ons vs. Custom-Built Software
A total-cost-of-ownership framework comparing SaaS add-on licensing to a custom build — beyond the sticker price of eith…