The Clause That Looks Harmless
Most unlimited liability clauses don't announce themselves. They don't say "you accept unlimited liability." Instead, they're structured as the absence of a protection: a contract that simply never caps what one party can claim from the other.
A developer signs a contract with a client. The project is delivered. But buried in the agreement is language that holds them responsible for "all damages arising from the services, including indirect and consequential losses." When a data incident occurs downstream — something the developer had no direct hand in — the client claims losses twenty times the value of the original contract. There is no cap. The clause allows it.
Unlimited liability doesn't only appear in IT contracts. Construction firms, marketing agencies, logistics providers, and SaaS companies all face it regularly. The financial fallout from a single unlimited-liability dispute can far exceed the value of the underlying contract.
A healthcare SaaS provider signs a vendor agreement containing broad indemnification language with no liability cap. When a data breach occurs — due to poor encryption by the client's own infrastructure team — the vendor is dragged into litigation covering losses that dwarf the annual contract value. The "unlimited" language is the lever the claim hangs on.
What It Looks Like in a Contract
Unlimited liability hides in several forms. Here's the most common:
The phrase "any and all" with no cap is the signal. It sounds like mutual protection, but in practice it means whoever suffers a loss — regardless of scale — can claim it in full from the other party.
Other forms to watch for:
Any clause listing "consequential," "indirect," or "punitive" damages without a monetary cap is exposing you to unlimited downside. Consequential damages alone can multiply the direct loss by 10x or more — lost profits, reputational harm, third-party claims.
Where Unlimited Liability Typically Hides
| Clause type | Where it appears | Risk level |
|---|---|---|
| Indemnification | Almost every commercial contract | High |
| IP infringement | Software licenses, agency contracts | High |
| Data breach / confidentiality | SaaS, healthcare, legal services | Very High |
| Fraud / gross negligence | All contract types | Medium (standard) |
| General service delivery | Service agreements, MSAs | Negotiable |
How to Negotiate a Cap
Most vendors expect to negotiate liability. The fact that a contract contains unlimited liability language doesn't mean you have to accept it. Here's the standard negotiation playbook:
- Propose a liability cap equal to 12 months of fees paid — this is the most common market standard
- Keep unlimited liability only for the things that genuinely require it: fraud, willful misconduct, death/personal injury, and data breaches involving personal data under GDPR
- Add mutual caps — if you're capping your liability, cap theirs too; asymmetric caps are a red flag
- Exclude consequential and indirect damages explicitly — "neither party shall be liable for loss of profits, loss of business, or indirect damages"
- If they won't cap IP infringement, ask for a carve-out requiring they indemnify you against third-party IP claims arising from their own materials
"Each party's total aggregate liability under this Agreement shall not exceed the greater of (a) the total fees paid or payable in the twelve (12) months preceding the event giving rise to liability, or (b) $[X]. Neither party shall be liable for any indirect, incidental, special, consequential, or punitive damages."
The Asymmetry Problem
The most dangerous pattern isn't bilateral unlimited liability — it's when only one party bears it. A vendor contract that caps the vendor's liability at one year of fees while leaving yours uncapped is a structural imbalance that most non-lawyers miss on a first read.
Look at both sides of every liability clause. If they're different, ask why. Asymmetric liability is always worth a conversation before you sign.
Does your contract have an uncapped liability clause?
Conditio flags unlimited liability language, missing caps, and asymmetric indemnification — before you sign.
Get started →