Automatically Redline Contracts Using AI

# Redline Review: Master Services Agreement
**Reviewing Party:** SaaS Vendor (Provider)
**Counterparty:** Fortune 500 Customer

---

## 1. Summary of Key Risks

- **Uncapped, overly broad indemnification (Section 8):** Current language requires Provider to indemnify against "any and all claims" with no cap, no carve-outs, and no reciprocal obligation from Customer. This is the single most material risk.
- **60-day payment terms (Section 2):** Creates significant working capital strain for a SaaS vendor; industry standard is Net 30. No late fee or suspension rights are specified.
- **Broad IP assignment language:** Implied assignment of Provider's pre-existing IP, tools, and platform improvements to Customer would destroy the core SaaS business model; Provider must retain ownership of its platform with a license grant to Customer.
- **Ancillary concerns likely present in full MSA:** Limitation of liability cap, confidentiality reciprocity, termination-for-convenience notice period, governing law/venue, and service level / warranty scope all warrant review once full text is circulated.

---

## 2. Redlined Clauses

### Section 8 — Indemnification (HIGHEST PRIORITY)

**(a) Original Text:**
> "Provider shall defend, indemnify, and hold harmless Customer from any and all claims..."

**(b) Proposed Revision:**
> "Provider shall defend, indemnify, and hold harmless Customer ~~[DELETE: from any and all claims]~~ **[INSERT: from third-party claims to the extent arising out of (i) Provider's gross negligence or willful misconduct, or (ii) an allegation that the Services, as provided by Provider and used in accordance with this Agreement, infringe a valid U.S. patent, copyright, trademark, or misappropriate a trade secret of such third party (each, a "Covered Claim"). Provider's indemnification obligations shall not apply to the extent a claim arises from: (a) Customer Data or materials provided by Customer; (b) modifications to the Services not made by Provider; (c) use of the Services in combination with products not provided or authorized by Provider; or (d) use of the Services in violation of this Agreement or applicable law. Provider's total aggregate liability under this Section 8, together with all other liability under this Agreement, shall be subject to the limitation of liability set forth in Section [X]. Customer shall indemnify Provider on reciprocal terms for third-party claims arising from Customer Data and Customer's breach of this Agreement.]**"

**(c) Rationale:** Unlimited, first-party indemnity for "any and all claims" is uninsurable and could exceed the entire contract value many times over. Scoping to third-party claims with standard IP carve-outs, tying to the overall liability cap, and adding reciprocity is market-standard for enterprise SaaS.

---

### Section 2 — Payment

**(a) Original Text:**
> "Customer shall pay all undisputed invoices within sixty (60) days..."

**(b) Proposed Revision:**
> "Customer shall pay all undisputed invoices within ~~[DELETE: sixty (60)]~~ **[INSERT: thirty (30)]** days **[INSERT: of the invoice date. Any dispute must be raised in writing within fifteen (15) days of the invoice date, specifying the disputed amount and basis; undisputed portions must be paid on the original due date. Late payments shall accrue interest at the lesser of 1.5% per month or the maximum permitted by law. Provider may suspend Services upon ten (10) business days' written notice of non-payment of undisputed amounts.]**"

**(c) Rationale:** Net 60 imposes a 100% working-capital penalty versus standard Net 30 SaaS terms. Dispute procedures, late fees, and suspension rights are needed to prevent Customer from unilaterally withholding payment indefinitely.

---

### IP Ownership (Section Number TBD Based on Full MSA)

**(a) Original Text (representative, based on "broad IP assignment" concern):**
> "All work product, deliverables, and intellectual property created under this Agreement shall be the sole and exclusive property of Customer, and Provider hereby assigns all right, title, and interest therein to Customer."

**(b) Proposed Revision:**
> "~~[DELETE: All work product, deliverables, and intellectual property created under this Agreement shall be the sole and exclusive property of Customer, and Provider hereby assigns all right, title, and interest therein to Customer.]~~ **[INSERT: As between the parties, Provider retains all right, title, and interest in and to the Services, the Provider platform, and all software, tools, methodologies, know-how, templates, and other materials owned or developed by Provider, including any modifications, enhancements, derivative works, and improvements thereto, whether developed before, during, or after the Term (collectively, "Provider IP"). Provider grants Customer a non-exclusive, non-transferable, worldwide license to use the Provider IP solely as necessary to receive the Services during the Term. Customer retains all right, title, and interest in Customer Data. To the extent any deliverables are specifically identified in a SOW as "Customer Deliverables" and paid for as custom development, Provider grants Customer a perpetual, royalty-free license to use such Customer Deliverables for its internal business purposes; provided that Provider retains ownership of all underlying Provider IP embedded therein.]**"

**(c) Rationale:** A blanket assignment would transfer Provider's core SaaS platform and general improvements to a single customer, destroying the business. The standard SaaS model is retention of platform IP with a use license; any custom deliverables should be licensed, not assigned, to preserve Provider's ability to serve other customers.

---

## 3. Open Questions / Items to Raise with Counterparty

1. **Limitation of Liability:** Is there a mutual LoL cap elsewhere in the MSA? We will require a cap at 12 months' fees, with standard carve-outs (confidentiality breach

# REDLINE REVIEW: MASTER SERVICES AGREEMENT
**Vendor (SaaS Provider) Perspective**

---

## 1. SUMMARY OF KEY RISKS

- **Uncapped Indemnity Obligation** – Broad, unlimited defense and indemnification exposure with no carve-outs for Customer negligence or misuse.
- **Extended Payment Terms (60 days)** – Cash flow impact; no late fees or interest provisions; accelerates vendor risk.
- **Vague IP Assignment Language** – Unclear scope of work product ownership; potential loss of pre-existing IP and improvements.
- **No Liability Limitation or Cap** – Indemnification clause not paired with damages cap; exposure is asymmetrical.
- **Broad Indemnity Scope ("any and all claims")** – Lacks standard exclusions (e.g., Customer-caused claims, third-party infringement due to Customer modifications).
- **No Survival Limitation** – No temporal boundary on post-termination indemnity obligations.

---

## 2. REDLINED CLAUSES

### **CLAUSE 2: PAYMENT TERMS**

**Original Text:**
> "Customer shall pay all undisputed invoices within sixty (60) days…"

**Proposed Revision:**
> "Customer shall pay all undisputed invoices within thirty (30) days of receipt. Invoices not paid by the due date shall accrue interest at the rate of 1.5% per month (or the maximum rate permitted by law, whichever is lower) calculated daily from the due date until paid in full. Customer shall also reimburse Provider's reasonable collection costs, including reasonable attorneys' fees, incurred in collecting overdue amounts."

**Rationale:**
Sixty days is unfavorable cash flow for a SaaS vendor; 30 days is market-standard. Late payment penalties and collection cost language protect against chronic delays and create incentive for timely payment.

---

### **CLAUSE 8: INDEMNIFICATION**

**Original Text:**
> "Provider shall defend, indemnify, and hold harmless Customer from any and all claims, damages, liabilities, and expenses (including reasonable attorneys' fees) arising out of or related to: (a) any claim that the Services infringe or misappropriate any intellectual property rights of any third party; or (b) Provider's breach of this Agreement."

**Proposed Revision:**
> "Provider shall defend, indemnify, and hold harmless Customer from any and all **[INSERT: third-party]** claims, damages, liabilities, and expenses (including reasonable attorneys' fees) arising out of or related to: (a) any claim that the **[INSERT: unmodified]** Services infringe or misappropriate any intellectual property rights of any third party, **[INSERT: provided that such infringement does not result from Customer's modification, combination, or use of the Services in a manner not approved in writing by Provider or in violation of Provider's Documentation]**; or (b) **[INSERT: Provider's material]** breach of this Agreement **[INSERT: that is not cured within thirty (30) days of written notice]**~~[INSERT: (c) any claim arising out of Customer's use of the Services in combination with non-Provider products or services, or any modification of the Services by Customer or third parties;]~~."

**Proposed Addition – Indemnity Carve-Outs:**
> "**[INSERT: Notwithstanding the foregoing, Provider shall have no obligation to indemnify Customer to the extent any claim arises from: (i) Customer's negligence, willful misconduct, or breach of this Agreement; (ii) Customer's use of the Services in a manner not authorized or documented by Provider; (iii) modification of the Services by anyone other than Provider; or (iv) combination of the Services with third-party products or services not approved by Provider in writing.]**"

**Proposed Addition – Indemnity Cap:**
> "**[INSERT: Provider's aggregate liability under this indemnification clause shall not exceed the fees paid by Customer in the twelve (12) months preceding the claim or $5,000,000, whichever is less. This cap shall not apply to either party's indemnification obligations for intellectual property infringement claims, but shall apply to all other indemnification claims.]**"

**Proposed Addition – Survival/Duration:**
> "**[INSERT: Provider's obligations under this Section 8 shall survive termination of this Agreement for a period of two (2) years, after which all indemnity obligations shall expire.]**"

**Rationale:**
(1) "Third-party" narrows exposure to external claims only; excludes Customer-to-Customer disputes. (2) "Unmodified" and modification carve-out prevent liability for Customer-induced infringement. (3) "Material breach" + cure period protects vendor from trivial defaults triggering indemnity. (4) Explicit carve-outs (Customer negligence, unauthorized use, third-party modifications) are market-standard risk allocations. (5) Cap ties indemnity exposure to contract value, preventing runaway liability; IP carve-out reflects reputational risk in IP claims. (6) Two-year tail prevents indefinite tail liability and allows underwriting of insurance.

---

### **CLAUSE 8A: INDEMNITY PROCEDURE (Proposed Addition)**

**Proposed Addition:**
> "**[INSERT: (a) **Notice.** Customer shall promptly notify Provider in writing of any claim subject to indemnification, provided that failure to provide prompt notice shall not relieve Provider of its obligations except to the extent Provider is materially prejudiced by the delay.**
>
> **(b) **Control.** Provider shall have the right, at its expense, to assume the defense and settlement of any third-party claim, provided that Provider shall not settle any claim without Customer's prior written consent (not to be unreasonably withheld). Customer shall provide reasonable cooperation in the defense of any claim.**
>
> **(c) **Remedies.** If Services become, or in Provider's opinion are likely to become, subject to an infringement claim, Provider may at its option and expense: (i) procure the right for Customer to continue using the Services; (ii) replace or modify the Services to make them non-infringing while providing substantially equivalent functionality; or (iii) if neither (i) nor (ii) is reasonably available, terminate the affected Services and refund Customer all prepaid fees attributable to the remainder of the then-current term.**]**"

**Rationale:**
Standard indemnity procedure language protects vendor by controlling defense strategy, limiting customer settlement discretion, and providing practical remedies (including IP license procurement or redesign) that are preferable to open-ended damages.

---

### **CLAUSE [X]: INTELLECTUAL PROPERTY & WORK PRODUCT (Flagging for Revision)**

**Context:** The original MSA excerpt does not include explicit IP assignment language, but you flagged "broad IP assignment language" as a concern. Assuming the full agreement contains similar language, here is a redline template:

**Original Text (Assumed):**
> "All work product, materials, tools, methodologies, and deliverables created or developed by Provider in connection with the Services shall become the exclusive property of Customer."

**Proposed Revision:**
> "All **[INSERT: custom]** work product, materials, and deliverables created exclusively for Customer under a SOW shall become the property of Customer **[INSERT: upon full payment of all fees]**. Provider retains all right, title, and interest in:
>
> (a) **[INSERT: all pre-existing intellectual property, tools, templates, methodologies, processes, know-how, and materials owned or developed by Provider prior to or outside the scope of this Agreement;]**
>
> (b) **[INSERT: any improvements, enhancements, generalizations, or derivative works based on Provider's pre-existing IP, even if developed using data or feedback from Customer;]**
>
> (c) **[INSERT: all work product that is general in nature or applicable to multiple customers, including any aggregate or anonymized insights derived from Customer's use of the Services;]**
>
> (d) **[INSERT: all copies, compilations, or derivative works of the foregoing.]**
>
> Customer grants Provider a perpetual, irrevocable, royalty-free license to use any feedback, suggestions, or ideas provided by Customer to improve the Services and Provider's offerings generally. **[INSERT: Custom deliverables shall be subject to a reasonable escrow or source code escrow arrangement if requested by Customer.]**"

**Rationale:**
Prevents loss of vendor IP portfolio and allows continuous product improvement; clarifies that pre-existing tools and generalizable improvements remain vendor property. Escrow option (at Customer expense) addresses Customer concerns about vendor viability without surrendering core IP. This is standard for SaaS and professional services.

---

### **CLAUSE [X]: LIABILITY LIMITATION (Assuming Present or Needed)**

**Proposed Addition (If Not Present

1. **Summary of Key Risks**
- **Indemnity is likely uncapped and one-sided** in favor of Customer, creating potentially unlimited exposure for the vendor.
- **Payment term of 60 days** is unfavorable for a SaaS vendor and should be shortened, ideally to 30 days or less.
- **IP ownership / assignment language** appears broad and may sweep in vendor pre-existing technology, platform, tools, know-how, and general learnings.
- **Termination rights and post-termination economics** are not described in the excerpt and should be checked to ensure vendor can suspend/terminate for nonpayment and recover committed fees.
- **Confidentiality and governing law** are not included in the excerpt; these should be reviewed for overbroad obligations, residuals restrictions, venue, and unfavorable forum selection.

2. **Redlined Clauses**

### Clause 2. Payment
**Original text:**  
“Customer shall pay all undisputed invoices within sixty (60) days...”

**Proposed revision:**  
“Customer shall pay all undisputed invoices within ~~[DELETE: sixty (60)]~~ **[INSERT: thirty (30)]** days **[INSERT: after receipt]** of invoice. **[INSERT: Any disputed amounts must be identified in writing in reasonable detail within fifteen (15) days after receipt of the applicable invoice, and Customer shall timely pay all undisputed amounts. Overdue undisputed amounts shall accrue interest at the lesser of one percent (1.0%) per month or the maximum rate permitted by law. Provider may suspend performance upon written notice if undisputed amounts remain unpaid for more than fifteen (15) days after the payment due date.]**”

**Rationale:**  
A 60-day payment cycle is long for a SaaS business and negatively affects cash flow. This revision shortens the payment period, limits invoice disputes to good-faith specific objections, and adds standard interest/suspension remedies for nonpayment.

---

### Clause 8. Indemnification
**Original text:**  
“Provider shall defend, indemnify, and hold harmless Customer from any and all claims...”

**Proposed revision:**  
“Provider shall defend, indemnify, and hold harmless Customer ~~[DELETE: from any and all claims]~~ **[INSERT: from any third-party claims, demands, suits, or proceedings]** **[INSERT: to the extent]** arising ~~[DELETE: from any and all claims]~~ **[INSERT: out of allegations that the Services, as provided by Provider and used by Customer in accordance with this Agreement, infringe such third party’s United States intellectual property rights]**. **[INSERT: Provider shall have no obligation to the extent a claim arises from (i) Customer materials, data, specifications, or instructions; (ii) modification of the Services by any party other than Provider; (iii) use of the Services in combination with products, services, or data not provided or approved by Provider, if the claim would have been avoided but for such combination; or (iv) Customer’s use of the Services in breach of this Agreement or applicable documentation.]** **[INSERT: If the Services become, or in Provider’s opinion are likely to become, the subject of an infringement claim, Provider may, at its option and expense, (a) procure for Customer the right to continue using the affected Services, (b) modify or replace the affected Services so that they are non-infringing without materially reducing their functionality, or (c) terminate the affected Services and refund any prepaid fees for the terminated portion of the unused subscription term. This Section states Provider’s sole and exclusive liability, and Customer’s sole and exclusive remedy, for any third-party intellectual property infringement claims.]**”

**Rationale:**  
The current language appears unlimited and potentially applies to all claims of any kind. For a SaaS vendor, indemnity should be limited to third-party IP infringement claims tied to the vendor’s services, with customary exclusions and exclusive remedies.

---

### Limitation of Liability
**Original text:**  
*Not provided in excerpt.*

**Proposed revision:**  
**[INSERT: EXCEPT FOR (I) A PARTY’S GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR FRAUD, (II) CUSTOMER’S PAYMENT OBLIGATIONS, AND (III) A PARTY’S BREACH OF ITS CONFIDENTIALITY OBLIGATIONS, IN NO EVENT SHALL EITHER PARTY’S AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT EXCEED THE FEES PAID OR PAYABLE BY CUSTOMER TO PROVIDER UNDER THIS AGREEMENT IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM. IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, REVENUE, DATA, GOODWILL, OR BUSINESS INTERRUPTION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.]**  
**[INSERT: FOR CLARITY, PROVIDER’S INDEMNIFICATION OBLIGATIONS SHALL BE SUBJECT TO THE FOREGOING LIABILITY CAP, PROVIDED THAT SUCH CAP FOR PROVIDER’S IP INFRINGEMENT INDEMNITY MAY BE INCREASED TO TWO (2) TIMES THE FEES PAID OR PAYABLE UNDER THIS AGREEMENT IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM.]**”

**Rationale:**  
Because your stated concern is uncapped indemnity, the agreement should expressly subject indemnity to the general liability cap or, if the customer pushes back, to a negotiated super-cap. This is one of the most important economic protections for the vendor.

---

### IP Ownership / Assignment
**Original text:**  
*Not provided in excerpt, but user flagged “broad IP assignment language.”*

**Proposed revision:**  
**[INSERT: As between the parties, Provider retains all right, title, and interest in and to the Services, software, Documentation, Provider technology, templates, tools, workflows, processes, know-how, methods, inventions, data models, and any modifications, enhancements, updates, or derivative works thereof, including any of the foregoing developed or used in connection with performing the Services (“Provider Materials”).]**  
**[INSERT: Customer owns all right, title, and interest in and to Customer Data. To the extent any deliverables are expressly identified in an SOW as custom deliverables created exclusively for Customer and paid for by Customer, Provider hereby grants Customer a non-exclusive, perpetual, worldwide license to use such deliverables for Customer’s internal business purposes, subject to Customer’s payment of all applicable fees.]**  
**[INSERT: Notwithstanding anything to the contrary, no assignment to Customer shall include any Provider Materials, Provider’s pre-existing intellectual property, or any generalized know-how, ideas, concepts, techniques, or skills acquired in the course of performing the Services.]**  
**[INSERT: If the Agreement currently provides for assignment of all work product or developments to Customer, such assignment shall be limited to the specific custom deliverables expressly identified in the applicable SOW, excluding all Provider Materials.]**”

**Rationale:**  
Fortune 500 customer paper often uses “work made for hire” or broad assignment language that is inappropriate for SaaS and professional services. The redline preserves your platform, pre-existing tools, and residual know-how while giving the customer appropriate rights to paid-for custom deliverables.

---

### Termination for Nonpayment / Suspension Rights
**Original text:**  
*Not provided in excerpt.*

**Proposed revision:**  
**[INSERT: Provider may suspend access to the Services or terminate this Agreement or any SOW upon written notice if Customer fails to pay any undisputed amount when due and such failure continues for fifteen (15) days after written notice thereof.]**  
**[INSERT: Except where Customer terminates for Provider’s uncured material breach, all fees paid or payable under this Agreement are non-cancelable and non-refundable, and if this Agreement or any SOW is terminated by Customer for convenience, Customer shall pay Provider for all Services performed and all fees accrued through the effective date of termination, together with any non-cancelable committed fees for the remainder of the then-current subscription term or SOW term.]**”

**Rationale:**  
The vendor needs clear leverage to address late payment and avoid being forced to continue service without payment. If the customer seeks termination for convenience, the vendor should recover committed economics for the contracted term.

---

### Confidentiality
**Original text:**  
*Not provided in excerpt.*

**Proposed revision:**  
**[INSERT: “Confidential Information” does not include information that: (i) is or becomes publicly available through no fault of the receiving party; (ii) was known to the receiving party without restriction before receipt from the disclosing party; (iii) is rightfully received from a third party without breach of any obligation of confidentiality; or (iv) is independently developed without use of or reference to the disclosing party’s Confidential Information.]**  
**[INSERT: Notwithstanding anything to the contrary, Provider may use Customer Confidential Information solely as necessary to provide the Services and to improve, support, secure, and maintain the Services, provided that Provider does not disclose Customer Confidential Information except as permitted under this Agreement.]**  
**[INSERT: Provider may also use aggregated and de-identified data derived from Customer’s use of the Services for analytics, benchmarking, security, and service improvement purposes, provided such data does not identify Customer or any individual.]**”

**Rationale:**  
These are standard confidentiality carveouts and operational use rights needed for a SaaS vendor to perform, maintain, and improve the service. If omitted, the confidentiality clause can inadvertently restrict routine service delivery and product improvement activities.

---

### Governing Law / Venue
**Original text:**  
*Not provided in excerpt.*

**Proposed revision:**  
**[INSERT: This Agreement shall be governed by and construed in accordance with the laws of the State of [Vendor

### 1. Summary of Key Risks
- **Uncapped, one-way indemnity**: Exposes vendor to unlimited liability for customer claims, including IP infringement, without reciprocity.
- **60-day payment terms**: Delays cash flow significantly; standard for SaaS vendors is 30 days.
- **Broad IP assignment**: Forces vendor to assign all developed IP to customer, undermining SaaS proprietary rights.
- **Missing termination protections**: Allows customer unilateral termination without adequate notice or payment obligations.
- **No liability cap**: No overall limitation of liability, amplifying indemnity risks.

### 2. Redlined Clauses

#### Clause 2. Payment
**(a) Original:** Customer shall pay all undisputed invoices within sixty (60) days...

**(b) Proposed:** Customer shall pay all undisputed invoices within **[INSERT: thirty (30)]~~sixty (60)~~** days...

**(c) Rationale:** 60-day terms strain vendor cash flow in a SaaS model with ongoing hosting costs; 30 days is market standard and aligns with vendor's key concern.

#### Clause 8. Indemnification
**(a) Original:** Provider shall defend, indemnify, and hold harmless Customer from any and all claims...

**(b) Proposed:** **[INSERT: (a) Each party shall defend, indemnify, and hold harmless the other party from any third-party claims arising from its own gross negligence, willful misconduct, or breach of confidentiality obligations. (b) Provider shall defend, indemnify, and hold harmless Customer solely from third-party claims that the Services infringe such third party's intellectual property rights, provided such claim does not arise from Customer Data, modifications by Customer, or Customer's combination with non-Provider materials. Indemnification obligations under this Section 8(b) shall be capped at one (1) year of aggregate fees paid by Customer in the twelve (12) months preceding the claim. (c) The indemnified party shall: (i) promptly notify the indemnifying party in writing; (ii) grant control of the defense and settlement; and (iii) reasonably cooperate. ~~Provider shall defend, indemnify, and hold harmless Customer from any and all claims...~~]**

**(c) Rationale:** Original is uncapped and one-way, creating unlimited vendor exposure; proposing mutuality, IP carve-outs, notice/cooperation requirements, and a fee-multiple cap (1x fees) is market-standard for SaaS vendors to limit risk while providing customer protection.

#### Assumed Clause 5. Intellectual Property (based on broad IP assignment language flagged)
**(a) Original:** All intellectual property rights in deliverables developed under this Agreement shall be owned by Customer...

**(b) Proposed:** **[INSERT: Provider retains all right, title, and interest in the Services, pre-existing IP, and any improvements thereto. Subject to payment in full, Provider grants Customer a non-exclusive, non-transferable, worldwide license to use the Services during the Term solely for Customer's internal business purposes. ~~All intellectual property rights in deliverables developed under this Agreement shall be owned by Customer...~~]** 

**(c) Rationale:** Broad assignment strips vendor of core SaaS IP ownership; license-only approach preserves vendor proprietary rights while enabling customer use, standard for SaaS MSAs.

#### Assumed Clause 9. Limitation of Liability
**(a) Original:** [No limitation of liability clause present or assumed silent/unfavorable.]

**(b) Proposed:** **[INSERT: Neither party shall be liable for any indirect, incidental, consequential, special, or punitive damages, or lost profits. Each party's aggregate liability shall not exceed the fees paid by Customer in the twelve (12) months preceding the claim, excluding indemnification obligations.]**

**(c) Rationale:** Absence of liability cap exposes vendor to disproportionate damages; inserting standard exclusions and fee-multiple cap protects against uncapped risks tied to indemnity.

#### Assumed Clause 10. Termination
**(a) Original:** Customer may terminate for convenience upon 30 days' notice...

**(b) Proposed:** **[INSERT: Either party may terminate for material breach with 30 days' notice and opportunity to cure (except for non-payment or confidentiality breach by Customer, which are non-curable). Upon termination, Customer shall pay all fees for Services rendered. ~~Customer may terminate for convenience upon 30 days' notice...~~ Provider may terminate for convenience with 90 days' notice.]**

**(c) Rationale:** One-sided convenience termination leaves vendor uncompensated for ramp-up costs; mutual breach-only termination with pay-for-services protects vendor revenue.

### 3. Open Questions / Items to Raise with Counterparty
- Confirm details of any SOWs (e.g., scope, fees, timelines) and whether they include vendor-favorable SLAs or uptime guarantees.
- What is the proposed governing law and venue? (Propose Delaware law and New York courts if not specified, favorable for SaaS vendors.)
- Seek business input on acceptable indemnity cap multiple (proposed 1x; could negotiate to 0.5x if low-risk Services).
- Clarify definition of "Services" to exclude vendor background IP and ensure customer data indemnity is mutual.