SaaS Agreement Review
Salesforce CRM + CPQ — 3-Year Enterprise Agreement, $180K/Year
About this sample. This is one example of what a successful Resolvix SaaS Agreement Review looks like. The scenario: a 120-person professional services firm evaluating a 3-year Salesforce CRM + CPQ subscription at $180K per year ($540K total commitment). Reviewed from the buyer's perspective. Your engagement will reflect your specific agreement, vendor, and risk tolerance. All company names, figures, and clause language are illustrative.
Executive Summary
Overall Verdict
Critical issues (must resolve before signing):
- 7% annual price increase right (§8.3). On a $180K base, uncapped compounding gives Salesforce the contractual right to raise your year-3 bill to approximately $206K — an additional $26K per year — without renegotiation. This is roughly 2.5× the current CPI rate and has no ceiling.
- 60-day auto-renewal notice window (§12.1). You must notify Salesforce in writing of non-renewal at least 60 days before the anniversary date. Miss it by one day and you are contractually committed to another full year at the then-current (escalated) price.
The auto-renewal trap and the price escalator are the two highest-leverage negotiation points. Salesforce enterprise teams will negotiate both — they are not take-it-or-leave-it on terms. Start by requesting CPI-linked increases (typically 3–4%) and a 90-day notice window. Both are standard in large enterprise renewals and represent no concession on Salesforce's core economics.
1. Data, Privacy & Security
This section covers where your data lives, who can use it, what happens in a breach, and what Salesforce does with your data after termination.
| Provision | What the Agreement Says | Assessment | Priority |
|---|---|---|---|
| Data ownership | Customer data is owned by the Customer at all times. Salesforce processes it as a data processor under Customer's instructions. | OK | — |
| Aggregated data use | Salesforce may use "aggregated, anonymized data derived from Customer's use" to improve its products and services. | Gap | Should |
| Breach notification | Salesforce must notify Customer within 72 hours of confirmed discovery of a security incident affecting Customer data. | OK | — |
| Data deletion on termination | Customer has 30 days post-termination to export data; Salesforce deletes all copies within 60 days of termination. | Adequate | — |
| Subprocessors | Salesforce publishes a subprocessor list; Customer consents to additions with 30-day prior notice and a right to object. | OK | — |
The Aggregated Data Gap — What to Watch
The aggregated/anonymized data clause is standard in enterprise SaaS agreements and legally permissible, but it has a practical implication: your pipeline data, deal sizes, win rates, and sales process patterns inform Salesforce's product decisions and benchmarking reports. The clause does not restrict Salesforce from selling insights derived from your data (in aggregate) to third parties including your competitors, as long as the data cannot be attributed to you individually.
Realistic outcome: Salesforce will likely decline the AI training restriction but may accept a narrow benchmarking carve-out. Push for it — the worst they say is no.
2. Commercial & Renewal Traps
This is where the highest financial risk lives in enterprise SaaS agreements. Four provisions in this agreement warrant attention.
Auto-Renewal: 60-Day Notice Window — Critical Trap
Under §12.1, you must deliver written notice of non-renewal no later than 60 days before the anniversary date. At $180K/year, missing this window by a single day commits you to a full additional year — escalated to approximately $193K in year 2 and $206K in year 3 — with no exit. This window is operationally dangerous because most procurement teams track renewals by contract end date, not a pre-deadline notice requirement.
Why 90 days (not 60): 90-day notice windows are the standard for enterprise agreements of this size. The change also gives you time to run a competitive RFP if Salesforce's renewal pricing is unacceptable.
Annual Price Increase Cap: 7% — Critical
Current language (§8.3): "Salesforce reserves the right to increase the subscription fee at each annual renewal by up to seven percent (7%) over the prior year's fee, effective upon written notice delivered no less than 90 days before the renewal date."
At 7% compounding: Year 1 = $180,000 / Year 2 = $192,600 / Year 3 = $206,082. That is a $26,082 increase over three years with zero additional value delivered. The current CPI (as of Q2 2026) is approximately 2.8%. A 7% cap is 2.5× inflation with no ceiling and no performance trigger.
Fallback: If Salesforce will not accept CPI linkage, negotiate a hard 3% annual cap with no CPI reference. At 3%, year 3 cost is $190,818 — a $10,818 increase versus $26,082 at 7%. The difference on a single 3-year deal is $15,264.
Usage-Based Overage: List Price — High
§9.2 provides that usage in excess of licensed quantities (users, API calls, storage) is billed at "then-current list price." Salesforce list prices are typically 20–40% above negotiated contract rates. This creates a structural incentive for organic overage to occur at significantly inflated rates.
No Cancellation Refund (Note)
§12.3 states that all fees are non-refundable upon cancellation for any reason other than Salesforce's material breach. This is standard for enterprise SaaS and is not negotiable — but it reinforces why the auto-renewal notice window is critical. You cannot pay for a year and then cancel for a pro-rated refund.
Taken together, the 7% escalator, 60-day notice window, and list-price overage billing create a scenario where a firm that enters at $180K exits year 3 paying $206K+ — with no mechanism to exit mid-term, and no refund if they miss the renewal window. The commercial terms in this agreement are systematically biased toward Salesforce's revenue protection. All three are negotiable.
3. Liability & Indemnification
| Provision | Current Terms | Assessment | Priority |
|---|---|---|---|
| Liability cap | Salesforce's aggregate liability capped at fees paid in the prior 12 months ($180K). | Adequate | — |
| Consequential damages exclusion | Neither party liable for lost revenue, lost data, or indirect damages. Standard mutual exclusion. | Standard | — |
| IP indemnification | Salesforce indemnifies Customer against third-party claims that the Salesforce platform infringes any patent, copyright, or trade secret. Strong, unlimited carve-out from the liability cap. | Strong | — |
| SLA uptime commitment | 99.9% uptime for production environments. Excludes scheduled maintenance, force majeure, and Customer-caused outages. | Weak credits | Should |
| SLA remedy (credits) | Service credits: 1 day of pro-rated fees per hour of downtime below SLA threshold. | Weak | Should |
| Data loss indemnification | No specific indemnification for data loss events; falls under the general liability cap. | Gap | Nice |
SLA Credits: Why 1 Day Per Hour Is Weak
At $180K/year, one day of pro-rated fees equals approximately $493. One hour of CRM downtime for a 120-person professional services firm costs far more in lost productivity — a conservative estimate of 120 people × 1 hour × $75/hour fully-loaded cost is $9,000. The credit structure is not a deterrent; it is a rounding error.
Realistic outcome: Salesforce will likely offer a compromise around 10%/15%/25% tiers. Accept it — it is a meaningful improvement over the current structure and does not require a dollar concession from Salesforce on the contract price.
The 12-month fee cap ($180K) is appropriate for a SaaS agreement of this size and type. Unlike development contracts where a liability cap set at 30 days of fees is dangerous, a 12-month cap on a subscription service means your worst-case recovery is equal to your annual spend — which is a reasonable risk transfer for a hosted software service. Do not expend negotiating capital on the liability cap here; deploy it on the price escalator instead.
4. Full Risk Register
| Clause | Plain Language | Risk | Priority |
|---|---|---|---|
| §6.4 — Aggregated Data Use | Salesforce may use anonymized data derived from your usage to improve products. | Medium | Should |
| §6.6 — Breach Notification | 72-hour notice on confirmed security incidents. | Low | — |
| §6.8 — Data Deletion | 30-day export window; 60-day deletion. Adequate for transition planning. | Low | — |
| §8.3 — Annual Price Increase | Up to 7% per year, compounding. No CPI link or ceiling. | Critical | Must |
| §9.2 — Overage Pricing | Excess usage billed at list price, not contracted rate. | High | Must |
| §10.1 — Liability Cap | Salesforce liability capped at prior 12 months of fees. | Low | — |
| §10.3 — IP Indemnification | Salesforce indemnifies against third-party IP claims. Unlimited carve-out. | Strong | — |
| §11.2 — SLA Uptime | 99.9% uptime; credits at 1 day/hour of downtime. | High | Should |
| §12.1 — Auto-Renewal Notice | 60-day written notice required to avoid auto-renewal. No reminder obligation on Salesforce. | Critical | Must |
| §12.3 — No Refund on Cancellation | All fees non-refundable except on Salesforce material breach. | Medium | — |
5. Redlines & Talking Points
Must-Have Changes (Non-Negotiable)
- Replace §8.3 price escalator with CPI-linked cap (target: lesser of 3% or CPI-U). This is the highest-dollar-value item in the negotiation. Do not sign without this change or a hard 3% ceiling as fallback.
- Extend §12.1 auto-renewal notice window from 60 to 90 days, and add a mandatory Salesforce reminder at 120 days. The reminder obligation is low-cost for Salesforce and eliminates the operational trap entirely.
- Add contracted-rate language to §9.2 overage pricing. Overages billed at list price can add 20–40% to an unexpected usage event. The fix is simple and Salesforce routinely accepts it.
Should-Have Changes
- Improve SLA credit schedule from 1 day/hour to a percentage-of-monthly-fees tier structure (10%/20%/30%). This is a meaningful remedy for genuine outages and costs Salesforce nothing if their platform performs as committed.
- Add AI training restriction to §6.4 aggregated data clause. Salesforce will likely decline, but it is worth requesting — particularly if your CRM data includes proprietary sales methodologies, deal structures, or pricing intelligence.
Nice-to-Have
- Add a benchmarking restriction to the aggregated data clause (no competitor reports derived from your data).
- Add a data portability exhibit specifying the format (CSV, JSON, or API export) for your data on termination — ensures you can migrate to a competing platform without a custom data extraction project.
- Request a most-favored-nation (MFN) pricing clause for renewals — if Salesforce offers a comparable firm lower pricing, you receive parity.
Trade-Off Strategy
Open with the CPI escalator and auto-renewal changes together in a single redline submission. These are both buyer-friendly, commercially reasonable, and standard in large enterprise renewals. If Salesforce pushes back on the CPI link, offer to accept the 7% cap in year 1 only in exchange for a hard 3% cap in years 2 and 3 — this limits the compounding effect while giving Salesforce a first-year concession they can present internally.
Action Steps
| # | Action | Owner | Timing |
|---|---|---|---|
| 1 | Submit redlines on §8.3 (price escalator), §12.1 (auto-renewal window), and §9.2 (overage pricing) to your Salesforce AE | Procurement / Legal | Before signature |
| 2 | Set a calendar alert for 120 days before each anniversary date, regardless of what the final notice window is | Procurement Lead | Day of signing |
| 3 | Request improved SLA credit tier table and add AI training restriction to §6.4 as secondary asks | Procurement / Legal | With initial redlines |
| 4 | Document all agreed-upon changes in a mutually signed Order Form amendment — verbal assurances from the AE are not binding | Legal | Before signature |
| 5 | If Salesforce declines the price escalator cap, obtain a written quote from at least one competing CRM vendor (HubSpot Enterprise, Microsoft Dynamics) and use it as leverage in final negotiations | Procurement Lead | Week of negotiations |
| 6 | Execute agreement once must-have redlines are accepted | Authorized signatory | Post-negotiation |
Every material clause reviewed from the buyer's perspective. Every commercial trap surfaced with dollar impact, not just legal language. A negotiation playbook you can use in the next vendor meeting. This is what a Resolvix SaaS Agreement Review delivers — every time.