What is a liability cap in a contract?

A liability cap is a contractual maximum on how much one party can be required to pay the other for claims under the agreement. Startups often negotiate caps equal to fees paid over a period (commonly twelve months), alongside exclusions for consequential damages, with limited carve-outs for items like unpaid fees or willful misconduct.

Is a 12-month fees liability cap standard for startups?

A twelve-month fees cap is a common commercial pattern in SaaS and services MSAs, but it is not a legal rule. Whether it fits depends on deal size, insurance, data risk, and bargaining power. Early-stage companies sometimes need a greater-of floor when fee history is too small to be meaningful.

What happens if there is no liability cap?

Without a cap, recoverable damages may be limited only by law, proof, and the consequential-damages exclusion (if any). For a startup, that can mean paper exposure far beyond contract value. Many teams treat uncapped liability as a hard stop and escalate to counsel before signing.

Do liability caps cover indemnity claims?

Only if the contract says so. Some agreements apply the cap to all claims; others carve indemnity (especially IP indemnity) out of the cap. Always read the limitation of liability and indemnity sections together, including any order-of-precedence language.

What is the difference between a liability cap and a consequential damages waiver?

The consequential damages waiver excludes categories like lost profits or indirect damages. The liability cap limits the dollars recoverable for remaining claims (often direct damages). You usually want both, drafted so carve-outs do not quietly undo either protection.

Should liability caps be mutual?

Mutual caps are generally easier to defend operationally: each side's downside is bounded relative to the commercial deal. One-sided caps favoring a large vendor or customer are common starting points, counter with mutuality or explain why asymmetry matches who controls the risk.

Liability Cap for Startups: What It Means and How to Negotiate

In plain English

A liability cap limits how much one party can owe the other if something goes wrong under a contract. For startups, it usually ties to fees paid (often 12 months), sits next to a consequential-damages exclusion, and includes narrow carve-outs. Treat uncapped liability as a walk-away signal unless counsel says otherwise.

Not legal advice. This is operational guidance for founders and ops. Escalate material risk to a licensed attorney.

By version90 staff Published Sep 13, 2026 Updated Sep 18, 2026 How this was made

Why founders care about the liability cap

Somewhere in every MSA is a quiet paragraph that decides what happens if the deal turns into a dispute. Not the marketing page. Not the SOW. The limitation of liability.

If your side of the table still lives in MSA_final_FINAL(2).docx, this is one of the clauses that gets edited while Track Changes is mysteriously "off." Read it twice.

Related reading: Indemnity clauses explained and the Startup MSA redline checklist.

What is a liability cap?

A liability cap (part of a limitation of liability clause) sets a maximum dollar amount one party can recover from the other for claims arising under the agreement.

Common structures:

Structure	Typical language pattern	Startup watch-out
Fees-based (aggregate)	Cap = fees paid in prior 12 months	Confirm "paid" vs "payable"; confirm aggregate vs per claim
Fixed dollar	Cap = $X	Easy to understand; may be too low or too high vs deal size
Greater-of	Greater of $X or 12 months fees	Useful when early ARR is tiny
Uncapped	No cap / "all damages"	Hard stop for most startups

Caps usually sit beside an exclusion of consequential, incidental, special, and lost-profits damages. The exclusion reduces "everything went sideways" theories; the cap bounds what's left.

How should startups set the number?

There is no universal "correct" multiple. Ops-friendly heuristics teams actually use:

Customer paper (you buy): Push for a mutual cap tied to fees you pay that vendor, often 12 months of fees under the order form / SOW.
Vendor paper (you sell): Offer a clear fees-based cap; resist "greater of fees or $5M" if your insurance and cash runway can't absorb it.
Early ARR: If 12 months of fees is $8k, a pure fees cap may be too small for the other side. Negotiate a floor (greater-of) you can insure.
High-risk services: Data processing, payments, healthcare-adjacent work often invites higher caps or more carve-outs, budget counsel time.

Pair the number with insurance you actually carry. A contractual promise your policy excludes is a founder bedtime story with a bad ending.

What are liability cap carve-outs?

Carve-outs are claim types that sit outside the cap (or outside the consequential-damages exclusion). They are where deals go from "bounded" to "suddenly uncapped again."

Carve-out you often see	Why it appears	Negotiation cue
Unpaid fees	Seller wants invoices enforceable	Usually fair
Willful misconduct / fraud	Public policy / bargaining power	Narrow definitions; avoid "gross negligence" laundry lists unless counsel agrees
IP indemnity obligations	Infringement can be large	Often capped separately or tied to indemnity only
Confidentiality / data breach	Sensitive data risk	Scope to breach of confidentiality obligations, not every privacy claim ever
Indemnity generally	Broad "indemnity is uncapped"	Fight open-ended versions; see indemnity guide

Redline cue: If carve-outs list everything interesting in the contract, you do not have a cap. You have a decorative paragraph.

Mutual vs one-sided caps

Ask two questions:

Does the cap apply to both parties? One-sided caps favoring the bigger party are common in vendor paper, and fair game to push back on.
Does the cap apply to indemnity? Some drafts cap direct damages but leave indemnity uncapped. That can be intentional; it should never be accidental.

More: vendor contract review checklist.

Redline cues that matter in Word

When you open the .docx (please, not a PDF screenshot of Word):

Search for "limitation of liability," "liable," "cap," "aggregate," "consequential."
Confirm whether the cap is per claim or in the aggregate.
Diff the current draft against the last approved version, silent Net-30→Net-60 edits have cousins in the liability section.
Keep one canonical file. If you're arguing about liability language across v7, v7_REAL, and FINAL(2), fix version control first.

Walk-away signals

Treat these as escalate-or-exit unless a licensed attorney says otherwise:

No liability cap at all for your side.
Cap so low it is symbolic ($100) while obligations are broad.
Carve-outs so wide the cap is empty.
Cap applies only to them; you remain uncapped.
Cap language that conflicts with a separate indemnity schedule and nobody can explain which wins.

About this page

Who. Written by version90 staff at Latent Ape LLC, the company that builds version90, working with AI tools. We build contract software and run our own contracts through it; we are not a law firm, and nothing here is legal advice.

How. Each piece starts from the review workflow version90 is built around. AI drafts and structures the text; staff edit, fact-check, and rewrite it before it is published, and we update the date shown above whenever the substance changes.

Why. The library exists to give founders and ops teams a shared standard for reviewing contracts without a legal department. If you spot an error, email [email protected] and we will fix the page.