TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Corporate
№ 141 Case Study — Corporate

How a Liability Cap Clause Saved a Georgina Company Millions

A software failure threatened a seven-figure claim against a small Georgina technology company. The limitation of liability clause in its services agreement stood between a bad week and a business-ending judgment.

Corporate6 min readGeorgina, OntarioCommercial contracts
All Corporate case studies
ClientAdaeze, Deepa and Anita, shareholders of a data-services company in Georgina
The issuea client threatened a large claim over a software failure, testing the limits clause in the services agreement
Servicecommercial contract drafting and dispute response
Resolutionclear win — the liability cap held, and the claim settled within it

The situation

Adaeze, Deepa and Anita were the three founding shareholders of a Georgina company that built data-processing tools for mid-sized logistics operators. The business had grown steadily for six years, reaching annual revenue in the range of $8 million, with Adaeze working as a pharmacist part-time alongside the company and Deepa continuing her career as a software developer while she held her shares. The company's largest customer relationship was a services agreement with a regional distribution operator, under which the company managed a data pipeline that fed the customer's inventory and shipping systems.

Two years earlier, the company had come to Treadstone Law to have its standard services agreement rebuilt from an older template that a founder had adapted years before from a form found online. The rebuilt agreement included a limitation of liability clause — a provision that caps how much one party can be forced to pay the other if something goes wrong, usually set as a multiple of fees paid, and a clause excluding liability for indirect losses like lost profits. At the time, the shareholders had asked whether the cap was really necessary, since the company had never had a major dispute. The advice was that a cap matters most exactly when a company hopes never to need it — and eighteen months later, that is precisely what happened.

Anita, the third shareholder, had joined the company two years earlier through a share purchase and took the lead on customer relationships. She had reviewed the rebuilt agreement at the time alongside Adaeze and Deepa and had specifically asked that the fee-based cap be tied to a rolling twelve-month period rather than a flat lifetime figure, so that long-standing customers with growing spend would carry a cap that grew with the relationship rather than staying frozen at an early, smaller number. That detail turned out to matter a great deal once the dispute arrived, since the customer's spend had roughly tripled since the agreement was signed.

The problem

A defect in a scheduled update to the data pipeline caused several days of incorrect inventory counts to flow into the customer's systems before anyone caught it. The customer's operations team had to unwind mis-shipped orders, recount stock across multiple locations, and re-run a batch of customer notifications. The customer's internal estimate of its losses — lost sales, labour to fix the records, and a handful of expedited shipping charges to make disappointed accounts whole — came in at roughly $1.4 million.

The customer's lawyer sent a formal demand letter seeking the full $1.4 million, framing the defect as a breach of the agreement's service-level commitments. For a company the size of Adaeze, Deepa and Anita's, a claim of that size was existential. The company carried commercial insurance, but the policy's limits and exclusions meant a judgment anywhere near $1.4 million would have forced a sale of the business, personal guarantees notwithstanding, or worse. The three shareholders, who between them held the company's full equity and had personally guaranteed a modest bank line, met with Treadstone Law within days of receiving the letter.

The central question was whether the limitation of liability clause negotiated two years earlier would actually hold up. The clause capped the company's total liability under the agreement, for any and all claims arising from the services, at an amount equal to the fees paid by the customer in the twelve months before the claim arose — in this case, roughly $340,000. It also excluded liability for indirect, consequential and lost-profit damages entirely. If enforceable, the cap would reduce a $1.4 million exposure to well under a third of that figure, and would knock out a large share of the customer's claimed damages before the cap was even reached, since much of the $1.4 million was arguably lost profit and consequential loss rather than a direct cost.

What we did

  1. Reviewed the clause against the actual facts of the defect. A limitation of liability clause is only as strong as its drafting and the facts it is applied to. We confirmed the clause was not buried in fine print inconsistent with the rest of the agreement, that it had been mutually negotiated rather than imposed unilaterally on a take-it-or-leave-it basis, and that nothing in the customer's claim pointed to gross negligence or wilful misconduct — conduct that many such clauses, including this one, carve out and refuse to protect against.
  2. Categorized the customer's claimed losses. We went through the customer's $1.4 million figure line by line. Roughly $950,000 of it was lost sales and margin the customer said it would have earned had the mis-shipments not occurred — classic consequential and lost-profit damages, squarely within the agreement's exclusion. The remaining roughly $450,000 was direct cost: labour hours to recount stock, expedited shipping fees, and system correction work. Only that direct-cost portion was even a candidate for recovery, and even that portion was still subject to the twelve-month fee cap of roughly $340,000.
  3. Responded to the demand letter with the contract's terms front and centre. Rather than disputing that a defect occurred — the company accepted responsibility for the error — the response set out the limitation clause, the exclusion of consequential damages, and the resulting cap, and offered to resolve the direct-cost portion of the claim within that cap.
  4. Negotiated a settlement anchored to the cap. The customer's lawyer initially pushed back, arguing the defect was serious enough to justify setting the clause aside. We held the position that the clause was validly formed, clearly worded, and directly on point, while acknowledging the company's error and its willingness to pay what the contract required. After several weeks of exchanges, the parties settled.
  5. Documented the settlement and repaired the relationship. The settlement agreement released all claims arising from the incident in exchange for payment, and included language preserving the ongoing services agreement so the two companies could continue working together. We also recommended a short post-incident review process be added to the agreement going forward, so future defects would be caught and disclosed faster.

The outcome

The dispute settled for roughly $325,000 — within the twelve-month fee cap and a fraction of the customer's original $1.4 million demand. The company's insurer contributed a portion of that amount under the policy's errors-and-omissions coverage, and the balance was paid from company funds without requiring the shareholders to call on personal guarantees or seek outside financing. The customer relationship, while strained for a period, continued under the same services agreement, and the parties added a more detailed incident-response schedule to their contract as part of the settlement.

Adaeze, Deepa and Anita later described the two-year-old decision to rebuild their template agreement as the single most consequential piece of paperwork the company had ever signed. Without an enforceable cap, the same defect could have produced a claim many times larger, argued in full against the company's total assets rather than against a contractually defined ceiling. The clause did not prevent the mistake or the customer's anger about it — but it did exactly the job it was written for, converting an open-ended risk into a bounded, insurable, survivable one.

The settlement negotiations also highlighted a second, quieter benefit of the earlier contract rebuild: a defined dispute-resolution process in the agreement, requiring a period of direct negotiation between senior representatives of both companies before either side could commence a lawsuit. That process kept the disagreement out of the Superior Court entirely, saving both companies the months of delay and additional cost that a filed claim would have added on top of the underlying dispute. Adaeze noted afterward that the settlement, while still a meaningful cost to absorb, was one the company could plan around and pay from operating funds — a very different outcome than an open-ended lawsuit with an uncertain end date and legal costs stacking on both sides for a year or more.

What you can learn from this

  • A limitation of liability clause is not boilerplate. Its wording — what it caps, what it excludes, and what carve-outs it allows for serious misconduct — determines whether it will actually protect a company when a real claim arrives.
  • Caps tied to fees paid, rather than a fixed dollar figure, scale with the size of the relationship and are generally easier to defend as reasonable when a dispute is scrutinized.
  • Excluding indirect and consequential damages, such as lost profits, is often more valuable than the dollar cap itself, since claimed losses in a real dispute are frequently dominated by exactly those categories.
  • A clause negotiated calmly at the start of a relationship carries far more weight than anything drafted under pressure once a dispute has already started.
  • Accepting responsibility for an error and disputing the amount owed are not contradictory positions — conceding the mistake while holding firm on the contract's terms is often the fastest route to a fair settlement.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a corporate problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →