Introduction
A limitation of liability clause rarely gets a second look before a contract is signed — it usually sits somewhere near the back, in the same gray, dense paragraph everyone skims past to get to the signature page. Then, one Tuesday afternoon, I got a call from a founder who was about to learn exactly why that clause exists. A customer was threatening to sue for damages north of ₹50 lakhs over a service disruption that wasn’t entirely my client’s fault, and for about ten minutes on that call, the founder genuinely believed the company might not survive the claim. It didn’t come to that. The reason it didn’t is the entire subject of this article.
The Call That Started It
The founder ran a mid-sized SaaS platform selling workflow automation software to enterprise clients. One of their larger customers experienced a multi-hour outage caused by a cascading failure that started with a third-party infrastructure provider, not my client’s own code. The customer’s operations team used the outage to build a case: lost productivity, missed deadlines on a client-facing project, and reputational damage they attributed directly to my client’s platform being unavailable. Their legal team sent a formal demand letter citing losses “in excess of ₹50 lakhs” and strongly implying litigation was the next step if it wasn’t resolved quickly.
The founder’s first instinct, understandably, was panic. Their second instinct — the right one — was to call me before responding to the demand letter at all.
Finding the Limitation of Liability Clause That Mattered
I’d drafted this client’s Terms of Service and customer agreement roughly eighteen months earlier, during a period when they were still closing five-figure deals and hadn’t yet landed a customer this large. Buried in Section 11 of that agreement was a limitation of liability clause I’d specifically structured to cap the company’s total liability at the fees paid by the customer in the preceding twelve months, combined with a broad exclusion of consequential, indirect, and incidental damages — including exactly the category of loss the customer was now claiming: lost productivity and downstream business impact.
The customer’s twelve-month fees came to a fraction of the ₹50 lakh demand. Once we responded to the demand letter citing the specific clause, quoting the relevant language directly, and explaining the legal basis under which it was enforceable, the conversation changed almost immediately. The customer’s legal team, expecting either a fight or a quiet settlement near their asking number, instead received a clear, well-supported position that their maximum recoverable exposure was contractually capped — and legally defensible. The dispute settled within the capped range, at a fraction of the original demand.
📋 Clause Breakdown: What the Limitation of Liability Clause Actually Did
The clause (illustrative language, adapted from the actual agreement):
“Except for the parties’ indemnification obligations, breaches of confidentiality, or liability arising from gross negligence or willful misconduct, in no event shall either party’s aggregate liability arising out of or related to this Agreement exceed the total fees paid by Customer in the twelve (12) months preceding the claim. Neither party shall be liable for any loss of profits, revenue, business, or any indirect, incidental, special, or consequential damages, whether or not advised of the possibility of such damages.”
Why it held up:
- A defined monetary cap, not an attempt to exclude liability entirely — Indian courts scrutinize total exclusions far more heavily than reasonable caps.
- A clear consequential damages exclusion, which is exactly the category “lost productivity” and “reputational damage” claims typically fall into.
- Carve-outs preserved for gross negligence, willful misconduct, confidentiality breaches, and indemnification obligations — this is what kept the clause from being struck down as unconscionable under Section 23 of the Indian Contract Act, 1872.
- Commercially reasonable framing, tied to actual fees paid rather than an arbitrary number, which courts have repeatedly treated as a sign of genuine risk allocation rather than a one-sided escape hatch.
The Legal Basis: Why This Actually Works Under Indian Law
A limitation of liability clause isn’t a magic shield — it works because Indian contract law specifically permits it, within limits. Sections 73 and 74 of the Indian Contract Act, 1872 establish that an injured party is entitled to compensation for losses arising naturally from a breach, but explicitly bar compensation for remote or indirect losses that go beyond what the parties reasonably contemplated at the time of contracting. That’s the statutory foundation a well-drafted consequential damages exclusion builds directly on top of.
The Supreme Court’s reasoning in cases involving commercial parties of comparable bargaining power — including the well-known HCC v. Shivalik Sugars line of authority — has consistently upheld liability caps in B2B contracts, precisely because both sides negotiated the risk allocation with eyes open. Where courts do intervene is under Section 23, which voids any contract term contrary to public policy — meaning a clause attempting to exclude all liability entirely, or one that produces a genuinely unconscionable result given the parties’ bargaining power, is far more likely to be struck down than a clause that caps liability at a defined, commercially reasonable amount while preserving exceptions for genuinely serious misconduct.
This is also exactly where a limitation of liability clause intersects with the cybersecurity obligations I’ve written about elsewhere: under Section 72A of the IT Act and the broader framework I cover in my breakdown of cybersecurity legal requirements and contract clauses that shift liability, a liability cap generally cannot be used to shield a party from its own gross negligence in protecting data — which is exactly why the clause above carves that scenario out explicitly rather than trying to cover it.
What Would Have Happened Without a Limitation of Liability Clause
It’s worth being explicit about the counterfactual, because this is the part founders underestimate most about having a limitation of liability clause in place. Without a properly drafted limitation of liability clause, the customer’s claim wouldn’t have been capped at anything — it would have proceeded as an open-ended dispute over what damages were “reasonably foreseeable” under Section 73, a standard that’s genuinely difficult to predict in advance and expensive to litigate. Even a partial win for the customer in that scenario could easily have exceeded the ₹50 lakh figure once legal costs, settlement pressure, and business disruption were factored in. The clause didn’t just cap the number — it removed the uncertainty entirely, which is often worth more to a founder than the rupee figure itself.
The Broader Lesson: Contracts Pay for Themselves Exactly Once
Every founder I work with eventually asks some version of the same question about a limitation of liability clause: is it really worth spending money on contract review before a dispute exists? This case is the honest answer. The Terms of Service that included this limitation of liability clause were drafted long before this specific customer, this specific outage, or this specific demand letter existed. Nobody could have predicted the exact scenario. What mattered was that the clause was drafted properly, generically, and defensibly enough to hold up whenever some dispute eventually arrived — which is the entire argument I make in more depth in why contracts function as strategic, trust-building assets rather than paperwork you tolerate. A limitation of liability clause is the clearest possible illustration of that principle: it did nothing for eighteen months, and then in one afternoon, it did everything.
How to Get Your Own Limitation of Liability Clause Right
If you’re reviewing your own customer or vendor agreements after reading this, here’s what to actually check for in your limitation of liability clause:
- Is there a defined monetary cap, ideally tied to fees paid over a set period, rather than either an unlimited exposure or a total exclusion of liability?
- Is there an explicit consequential damages exclusion covering lost profits, lost business, and indirect or incidental losses?
- Are the necessary carve-outs preserved — gross negligence, willful misconduct, confidentiality breaches, indemnification obligations, and (per the IT Act) data protection failures?
- Is the cap commercially reasonable relative to the size and nature of the relationship, rather than an arbitrary, unconscionably low figure that a court could strike down under Section 23?
- Has this clause actually been reviewed by a lawyer, rather than copied from a generic template? I’ve written separately about why AI-generated contract language is particularly risky for jurisdiction-specific clauses like this one — a limitation of liability clause is exactly the kind of provision where slightly wrong wording can mean the difference between an enforceable cap and an unenforceable one.
If your business handles customer data, this clause should also work in tandem with your broader compliance posture — see my full cybersecurity legal requirements checklist for how liability caps, indemnification, and data breach carve-outs fit together as one coordinated risk strategy rather than isolated clauses.
Conclusion: The Limitation of Liability Clause You Skip Reading Might Save You
A limitation of liability clause will never feel urgent while you’re negotiating a deal, closing a sale, or trying to get a contract signed before month-end. It only becomes urgent the day something goes wrong — and by then, it’s far too late to add one. This case didn’t get resolved because my client got lucky. It got resolved because the unglamorous, easy-to-skim clause near the back of an eighteen-month-old contract had been drafted properly the first time. If your customer or vendor agreements haven’t had a real legal review, I can take a look at yours directly, or explore more real contract-drafting guidance on the blog.
Frequently Asked Questions (FAQ)
1. What exactly is a limitation of liability clause? It’s a contract provision that caps the amount, or restricts the type, of damages one party can recover from the other if something goes wrong. In India, these clauses are enforceable under the Indian Contract Act, 1872, provided they aren’t structured in a way that’s unconscionable or contrary to public policy.
2. Is a limitation of liability clause enforceable in India? Generally, yes, particularly between commercial parties of comparable bargaining power. Courts scrutinize clauses that attempt to exclude all liability entirely far more heavily than clauses that set a defined, commercially reasonable cap.
3. What is typically excluded from a limitation of liability clause? Most well-drafted clauses carve out gross negligence, willful misconduct, breaches of confidentiality, indemnification obligations, and, increasingly, data protection failures under applicable law — these categories are usually not permitted to be capped or excluded entirely.
4. What’s the difference between a limitation of liability clause and an indemnity clause? A limitation of liability clause caps or restricts damages a party can be required to pay. An indemnity clause obligates one party to cover the other’s losses, often including third-party claims, and can work alongside a liability cap or be excluded from it entirely, depending on how the contract is drafted.
5. How should a startup determine what number to use as the liability cap? A common and defensible approach is capping liability at fees paid over a defined period, typically the preceding 12 months, since this ties the cap to the actual value of the relationship rather than an arbitrary figure that could later be challenged as unconscionable.
6. Can a limitation of liability clause cover data breaches? It can, but data breach liability should generally be carved out or handled separately from a general liability cap, and cannot be used to shield a party from gross negligence in protecting data under applicable law such as Section 72A of India’s IT Act.
7. What happens if a contract has no limitation of liability clause at all? Without one, damages are assessed under general principles like Sections 73 and 74 of the Indian Contract Act, which can result in significantly higher, less predictable exposure, since there’s no pre-agreed cap limiting the claim.
8. Are consequential damages exclusions the same as a liability cap? No, though they’re often used together. A liability cap limits the total dollar amount recoverable, while a consequential damages exclusion limits the type of losses that can be claimed at all, such as lost profits or reputational harm.
9. Can a limitation of liability clause be added to an existing contract later? It can be added to an existing contract through a signed amendment or addendum if both parties agree, though it’s far more effective — and far less contentious to negotiate — when included from the start of the relationship.
10. Should every business contract include a limitation of liability clause? In most commercial contexts, yes. Any agreement involving services, software, or ongoing obligations carries some risk of dispute, and a properly drafted liability cap is one of the most cost-effective forms of protection a business can put in place before that risk materializes.
Editorial note: Client details, company identity, and specific figures below have been altered and generalized to protect client confidentiality, as is standard practice when discussing real legal matters publicly. The clause mechanics, legal reasoning, and outcome described reflect a genuine pattern I’ve seen repeatedly in practice.