How to negotiate vendor indemnification for third-party IP infringement in SaaS agreements?

Negotiate SaaS IP indemnification by capping liability, defining scope, and requiring prompt notice. Use TermScore to automate your contract review today.

September 10, 2026TermScore Research636 words

How to Negotiate Vendor Indemnification for Third-Party IP Infringement

To negotiate effective IP indemnification, demand an uncapped obligation where the vendor defends, indemnifies, and holds the customer harmless against all third-party claims alleging the SaaS platform infringes intellectual property rights. Ensure the scope covers legal fees, settlements, and final court-awarded damages.

The Anatomy of a Robust IP Indemnity Clause

A standard "Vendor-friendly" clause is often riddled with loopholes. As a customer, you must ensure the language is comprehensive. A strong clause must include the following components:

  • Defense Obligation: The vendor must control the defense but pay for your choice of counsel if a conflict of interest arises.
  • Scope of Damages: Coverage must extend to all losses, including reasonable attorney fees, court costs, and settlement amounts.
  • Injunctive Relief: If the software is enjoined, the vendor must either procure the right to continue use, modify the software to be non-infringing, or provide a pro-rata refund of prepaid fees.

Key takeaway: Never accept a clause that limits the vendor's liability for IP infringement to the amount paid in the previous 12 months. IP litigation costs often exceed $500,000; your indemnity must be uncapped.

Action Item: Review your current SaaS agreements to see if "Indemnification" is listed under the "Limitation of Liability" section. If it is, you are likely capped.

Common Red Flags in SaaS IP Indemnity

Vendors often attempt to narrow their exposure through specific exclusions. Watch for these common "red flags" that signal a weak protection:

Red FlagWhy It Is Dangerous
Modification ExclusionIf you customize the software via API, the vendor may deny coverage for any infringement claim.
Combination ExclusionIf the SaaS works with your other software, vendors often claim the infringement is caused by the "combination," not their code.
Notice RequirementsVendors may demand "prompt" notice, using any delay as a reason to void their duty to defend.

Negotiating the "Combination" Exclusion

Vendors frequently argue that they cannot be responsible if their software is used in combination with other products. Push back by limiting this exclusion to cases where the infringement would not have occurred but for the combination. This ensures that if the vendor’s core code is inherently infringing, they remain liable regardless of your tech stack.

Action Item: Strike "combination" exclusions that are overly broad. Require the vendor to prove that the infringement was caused solely by the third-party component.

The Step-by-Step Negotiation Process

  1. Identify the Risk: Determine if the SaaS platform relies on open-source libraries or proprietary algorithms that are high-risk for patent trolls.
  2. Request Uncapped Indemnity: Propose that IP infringement claims be carved out of the general limitation of liability.
  3. Define the Process: Require the vendor to provide written notice of a claim within 10 business days and mandate that they do not settle without your written consent if the settlement impacts your business operations.
  4. Secure the Right to Counsel: If the vendor’s counsel is not acting in your best interest, ensure you have the right to hire separate counsel at the vendor's expense.

Jurisdictional Considerations

While SaaS agreements often default to Delaware or California law, IP infringement is governed by federal law (the Copyright Act and the Patent Act). Regardless of the governing law clause, the vendor's duty to indemnify is a matter of contract interpretation. Ensure your indemnity clause is explicitly "governed by the laws of [Your State]" to maintain consistency with your master service agreement.

Key takeaway: Ensure the indemnity survives the termination or expiration of the agreement. Infringement claims often surface years after the software was implemented.

Action Item: Add a "Survival" clause specifically for IP indemnification to ensure protection continues for at least 3 years post-contract.

Automating Your Contract Review

Negotiating these terms manually is time-consuming and prone to human error. TermScore uses advanced AI to instantly scan your SaaS agreements, identifying weak IP indemnification clauses and comparing them against industry benchmarks. By using TermScore, you can pinpoint exactly where your contracts fail to protect your business and generate redlines that align with market standards in seconds.

T

TermScore Research

Our legal AI analyzes thousands of contracts to surface market standards, common pitfalls, and actionable insights for anyone who signs agreements.

Get the contract red-flag checklist

Join landlords and freelancers getting clause breakdowns and benchmark data. No spam.

Keep reading

Don't guess. Get your TermScore.

Upload your lease, employment contract, or agreement and let our AI flag every risk in seconds.

Score my document free