SaaS Liability Caps and Indemnity: Map the Claim Before the Number

AI-generated editorial illustration by Viaclause. People and setting are fictional.

A liability cap and an indemnity clause answer different questions. Read them together before treating a year of subscription fees as your maximum exposure or recovery. Start with a specific incident, identify which obligation it could trigger, and then trace that obligation through the cap, exclusions and claim procedure.

Use the vendor breach response record to connect the facts, governing clause and proposed response.

This guide gives US procurement and legal teams a proposed comparison record. It does not determine whether a clause is enforceable or whether a particular loss is recoverable. Those questions require the applicable documents, facts and law.

Why the headline number can mislead

Consider two published examples, not market benchmarks. HubSpot's September 16, 2026 terms, section 10.4, calculate the general aggregate limit using subscription amounts paid or payable in the twelve months before the event giving rise to a claim. They except specified obligations, including customer indemnification and HubSpot's IP indemnification. Section 10.3 separately excludes specified damage categories. Section 9.2 describes the covered third-party IP claims, exceptions and a thirty-day notification requirement.

Google Cloud's posted terms, sections 12 and 13, illustrate a different cross-reference structure. Section 12.1 expressly makes its indirect-liability restriction subject to section 12.3. That section lists unlimited liabilities, including section 13 indemnification obligations. Section 13 then defines coverage, exclusions and procedural conditions. The published terms have applicability qualifications, including for offline agreements; confirm the version governing your purchase.

The reading task is therefore more precise than finding the word “indemnity.” Identify which restriction an exception modifies. An exception to a money ceiling should not silently become an exception to every other limitation in your comparison sheet.

Make one row for each possible claim

Use the following fields for each scenario that matters to the purchase. Copy the exact section references beside your answers. Leave an unanswered field as “unresolved,” rather than filling it with a generic AI explanation.

• Incident: what happened, to whose system or information, and when?
• Claimant and recipient: who is demanding payment or a remedy, and from whom?
• Possible obligation: ordinary breach, a specified indemnity, payment or another identified provision. Record alternative readings for counsel.
• Coverage conditions: what facts must exist for that provision to apply? Which exclusions could matter?
• Money ceiling: exact formula, fee scope, time window, aggregate or per-claim wording, and any stated higher limit or exception.
• Damage categories: what losses are excluded, and which exceptions expressly reach that exclusion?
• Handling the claim: notice deadline, recipient, defense control, cooperation, settlement consent and treatment of defense costs.
• Decision: accept the identified exposure, request a specific revision, or obtain legal advice on an unresolved interpretation.

Keep customer obligations visible too. A comparison that measures only what the vendor could pay misses the other side of the bargain. Where an order changes the main terms, use the order-form and master-agreement comparison before calculating anything.

Test the formula with actual invoice dates

Hypothetical calculation, not a reading of either vendor's agreement: suppose a clause caps covered liability at fees actually paid for one named service in the twelve months before the incident. The customer paid $18,000 on January 1, 2026. The incident occurs on July 1, 2026. No other payment for that service falls in the stated window. The fee total is $18,000, not $9,000 merely because six months have elapsed.

Change just the payment schedule: six monthly payments of $1,500 fall before the incident. The total becomes $9,000. The same annual subscription price produces a different calculation under this deliberately simplified wording.

Now suppose the clause says “paid or payable,” covers several services, or measures the window before a claim rather than an incident. Stop and recalculate using that wording. Do not automatically add every future payment in a multiyear deal. Ask which amounts fall within the defined fee base and period.

This arithmetic estimates a contractual ceiling under stated assumptions. It does not establish liability, prove damages, resolve exclusions or predict a payment. Do not report the number to finance as an expected recovery.

Turn an open issue into a useful negotiation question

A broad request for “better indemnity protection” leaves too much unsaid. A more useful question identifies the scenario and the unresolved interaction:

For the third-party claim described in our attached scenario, which indemnity provision would apply? Please identify the applicable monetary limit, any separate damages exclusion, and whether defense costs consume that limit. We also need the notice and settlement-control requirements.

This is a proposed discussion prompt, not a contractual amendment. Put an agreed change in the appropriate contract document and have counsel review the resulting language. Save the scenario, cited provisions and financial inputs in the lawyer review packet.

If a claim has already arrived, preserve it and escalate promptly. A comparison exercise must not delay a required notice. The notice delivery record helps separate sending evidence from proof of the required delivery step.

Sources

• HubSpot Customer Terms of Service, modified September 16, 2026, sections 9.2, 10.3 and 10.4. Specific illustration of indemnity scope, procedure, damage exclusions and cap exceptions.
• Google Cloud Terms of Service, checked September 27, 2026, sections 12 and 13 and introductory applicability qualifications. Specific illustration of cross-referenced exceptions; not a claim about every customer's agreement.

By Anirudh Menon, Viaclause editor. Sources checked September 27, 2026. The worksheet and examples are editorial proposals, not legal review.