This clause specifies the methodology for calculating the maximum amount of liability one or both parties can face under a SaaS (Software-as-a-Service) agreement. Rather than leaving liability unlimited, SaaS vendors typically cap their exposure at a specific dollar amount, which is often calculated as a multiple of fees paid (such as 12 months of subscription fees, or 1x annual contract value). The clause details how this cap is computed—for instance, whether it applies per incident or in the aggregate for all claims in a given period, whether it includes or excludes certain categories of damages, and whether different caps apply to different types of breaches. A well-drafted clause provides clarity and predictability for both parties; a poorly drafted one creates ambiguity that leads to disputes when claims arise.
The practical impact of this clause is substantial because it directly determines the maximum financial exposure for both the vendor and the customer. For vendors, a reasonable cap protects them from catastrophic liability that could exceed the contract's profitability. For customers, an inadequate cap may mean that if the SaaS platform fails catastrophically, their recovery is limited to a small fraction of their actual losses. The clause also intersects with the consequential damages exclusion (Clause 245)—together, these provisions can severely limit a customer's remedies. Additionally, the calculation method matters greatly: a cap based on "fees paid in the 12 months preceding the claim" is more favorable to customers than one based on "fees paid in the month of the claim," because it's a larger number.
If you're a customer, negotiate for a liability cap that's proportionate to the value and criticality of the SaaS service. For mission-critical systems, push for a cap of at least 12-24 months of fees, or negotiate a higher cap for specific breach categories (like data breaches or security failures). Ensure the cap is calculated on an annual or 12-month basis, not monthly. Carve out certain liabilities from the cap entirely, such as breaches of confidentiality, data protection violations, and indemnification obligations. If you're a vendor, ensure the cap is reasonable relative to your contract value and risk exposure, and clarify that it applies per incident and in the aggregate. Both parties should explicitly state whether the cap applies to direct damages only, or whether it also limits indirect and consequential damages (which should already be excluded under Clause 245).
Frequently Asked Questions
What does this clause mean in simple terms?
This clause specifies the methodology for calculating the maximum amount of liability one or both parties can face under a SaaS (Software-as-a-Service) agreement. Rather than leaving liability unlimited, SaaS vendors typically cap their exposure at a specific dollar amount, which is often calculated as a multiple of fees paid (such as 12 months of subscription fees, or 1x annual contract value).
Why should I care about this clause?
The clause details how this cap is computed—for instance, whether it applies per incident or in the aggregate for all claims in a given period, whether it includes or excludes certain categories of damages, and whether different caps apply to different types of breaches. A well-drafted clause provides clarity and predictability for both parties; a poorly drafted one creates ambiguity that leads to disputes when claims arise.
What are my options?
The practical impact of this clause is substantial because it directly determines the maximum financial exposure for both the vendor and the customer. For vendors, a reasonable cap protects them from catastrophic liability that could exceed the contract's profitability.
How does this affect small businesses?
For customers, an inadequate cap may mean that if the SaaS platform fails catastrophically, their recovery is limited to a small fraction of their actual losses. The clause also intersects with the consequential damages exclusion (Clause 245)—together, these provisions can severely limit a customer's remedies.