You’re paying five or six figures a year for software your company depends on every single day. Then one morning, it stops working and so does your business. Here’s a scenario that’s becoming more common every year in Chicago’s tech ecosystem: your company relies on a SaaS platform for something critical. Customer relationship management, payment processing, inventory tracking, project delivery. The vendor’s sales team promised 99.9% uptime. You signed the contract. You migrated your data. You built your workflows around their product.
And then it goes down. Maybe for a few hours. Maybe for a few days. And while the vendor’s status page says “we’re working on it,” your team can’t serve customers, your revenue pipeline is frozen, and your clients are calling you asking what’s going on. When the dust settles, you check the contract and discover that the vendor’s only obligation is to give you a service credit worth a fraction of your monthly fee. Meanwhile, your actual losses are orders of magnitude larger.
So what do you do? Keep using the platform and hope it doesn’t happen again? Switch vendors and walk away? Sue?
The answer matters more than you might think because under Illinois law, what you do after the breach can determine whether you can recover damages at all. A skilled business litigation attorney in Chicago should guide you through your options.
The Gap Between SLA Credits and Real Damages
Most B2B SaaS contracts include a Service Level Agreement (SLA) that sets performance benchmarks, typically uptime guarantees. The industry standard is 99.9% availability, which sounds impressive until you realize that still allows for nearly nine hours of downtime per year. But here’s the part that catches most business owners off guard: the remedy baked into most SLAs for failing to meet that benchmark is a service credit. Not a damages payment. A credit toward future service, usually somewhere between 5% and 15% of your monthly fee.
Let’s put real numbers on that. Say you’re paying $10,000 a month for a SaaS platform that handles your order management. The vendor has a major outage that lasts 48 hours during your busiest week. Your SLA credit? Maybe $500 to $1,500. Your actual losses: missed orders, angry customers, emergency workarounds, overtime for your team. Potentially $100,000 or more. That gap is where disputes happen. And that gap is where understanding your rights under Illinois contract law becomes critical. This is where having a litigation lawyer with industry specific knowledge and experience in Chicago comes in handy.
Is an SLA Breach Actually a Breach of Contract?
This is the threshold question and the answer depends entirely on how the contract is written. If the SLA is incorporated into the master agreement as a binding obligation, meaning the vendor has committed to meeting those uptime standards, then a failure to meet them is a breach of contract, plain and simple. You’d analyze it the same way you would any other breach of contract claim in Chicago: there was a valid contract, you performed your obligations (you paid your fees), the vendor failed to perform theirs (they didn’t maintain the promised uptime), and you suffered damages as a result.
But here’s the catch. Many SaaS vendors draft their SLAs as aspirational targets rather than firm commitments. You’ll see language like the service is provided “as is,” or that uptime goals are “targets” rather than guarantees, or that service credits are the customer’s “sole and exclusive remedy” for any downtime. If the contract says the vendor will use “commercially reasonable efforts” to achieve 99.9% uptime rather than committing to it, proving breach gets significantly harder.
The difference between “we guarantee 99.9% uptime” and “we will use commercially reasonable efforts to achieve 99.9% uptime” might look like lawyer hair-splitting. In litigation, it’s the difference between a winning case and a losing one.
The Critical Decision: Keep Using the Software or Walk Away?
Here’s where SaaS disputes get legally interesting and where a recent Illinois Supreme Court decision reshapes the analysis. When your SaaS vendor materially breaches the contract, whether through catastrophic downtime, data security failures, or other performance failures, you face what Illinois law treats as a fork in the road. You can either terminate the contract and sue for damages, or continue the contract and sue for damages. But if the injured party continues upholding its end of the bargain, then it cannot stop performing its obligations of the contract later.
This principle was formally adopted by the Illinois Supreme Court in PML Development LLC v. Village of Hawthorn Woods, 2024 IL 128770, which established what’s known as the “partial breach doctrine” in Illinois. While that case involved a land development agreement rather than a SaaS contract, the legal framework it established applies squarely to the kinds of disputes that arise between SaaS vendors and their business customers. Here’s the core holding: if the other side materially breaches the contract, you have the right to walk away to treat the contract as over, stop performing, and sue for your full damages. That’s the first-to-breach rule, and it’s been part of Illinois law for a long time.
But if you don’t walk away, if you keep using the software, keep paying your invoices, keep building your business around the vendor’s platform, then you’ve made an election to continue the contract. And that election has consequences.
What Happens When You Keep Performing
In PML Development, both parties materially breached a development agreement. The Village breached first by interfering with PML’s operations and refusing to issue required permits. PML could have terminated the agreement at that point but it didn’t. Instead, it continued operating on the property, sought mandamus orders to compel the Village to comply, and kept reaping the economic benefits of the deal. When PML itself later breached by failing to pay property taxes and convey the property, the question became: does PML’s decision to keep performing after the Village’s breach affect its right to recover?
The Illinois Supreme Court said yes but not in the way you might expect. The court held that when a party elects to continue performing after the other side’s material breach, the breach is treated as partial rather than total. The injured party can still sue for damages caused by that breach. But, and this is the critical part, by continuing the contract the injured party remains bound by its own obligations. If it then breaches those obligations, the other side gets to sue too.
The practical result: both PML and the Village had viable breach of contract claims against each other. Neither party’s breach wiped out the other’s right to recover. The court remanded the case so the trial court could calculate each side’s damages and offset them.
Why This Matters for Every SaaS Customer in Chicago
Think about how this plays out in a typical B2B SaaS dispute. Your vendor has a major outage that costs you six figures in lost business. Let’s say that, based on the wording of the contract, it is a material breach. Under the first-to-breach rule, you have the right to terminate the contract, stop paying, and sue for your damages. But here’s the reality: you’ve spent months migrating your data to this platform. Your entire team is trained on it. Your workflows are built around it. Walking away means weeks of disruption while you find and implement a replacement disruption you can’t afford. So you do what almost every business does: you stay. You keep using the software. You keep paying your monthly fees. Maybe you complain. Maybe you negotiate a service credit. But you don’t terminate.
Under PML Development, that decision means you’ve elected to continue the contract. The vendor’s material breach converts to a partial breach. You can still sue for the damages the outage caused but you remain bound by your obligations under the contract. If you later stop paying your invoices in frustration, or violate the usage terms, or breach a data handling provision, the vendor now has a viable breach of contract claim against you. This is the trap. The very thing that makes SaaS relationships so sticky: the switching costs, the data migration burden, the operational dependency, is the same thing that can complicate your legal position if you’re not careful about how you respond to a breach. Having a business litigation lawyer in Chicago familiar with recent Illinois case law and who has industry specific experience and knowledge in the tech space can guide you through your options.
The Limitation of Liability Problem
Even if you navigate the election-of-remedies issue correctly, SaaS contracts create a second obstacle that often matters just as much: the limitation of liability clause. Nearly every B2B SaaS agreement contains two provisions that work together to limit what you can recover. First, a liability cap typically limiting the vendor’s total exposure to the fees you paid in the twelve months before the breach. Second, a consequential damages waiver, a clause in which both parties agree not to seek indirect, consequential, or special damages, including lost profits, lost revenue, and business interruption costs.
This is critical because in a SaaS outage, the vast majority of your real-world losses are consequential damages. The subscription fee itself is a rounding error compared to the downstream business impact. Illinois courts generally enforce these clauses in commercial contracts between sophisticated parties. The principle is freedom of contract if two businesses negotiated and agreed to these terms, courts will hold them to it. That said, Illinois law also requires that limitation of liability clauses be strictly construed against the party benefiting from them. Ambiguity in these provisions cuts against the vendor, not the customer.
And there are circumstances where these limitations don’t hold up. If the vendor engaged in willful misconduct or gross negligence, many contracts carve those situations out of the liability cap. Some contracts also carve out data security breaches, confidentiality violations, or intellectual property infringement. Whether your specific contract includes those carve-outs, and whether the facts of your situation trigger them, is where the real legal analysis lives.
What About When They Lose Your Data?
SLA failures aren’t just about downtime. In the SaaS world, some of the most damaging breaches involve data: either losing it, exposing it, or holding it hostage. Data breaches are an increasingly common source of B2B contract disputes. When your SaaS vendor gets hacked and your customers’ data is exposed, you’re the one who has to deal with regulatory reporting requirements, credit monitoring costs, forensic investigations, and the reputational fallout. Those costs can be enormous and the contract you signed may severely limit what you can recover from the vendor that caused the problem. Data portability disputes arise when a customer tries to leave. Many SaaS contracts require 90-day termination notices but only give you a 30-day window to retrieve your data and even then, the data may come back in a proprietary format that’s essentially unusable without expensive conversion. I’ve seen situations where companies lost years of business-critical information because the contract didn’t adequately address what happens to data after termination.
Data ownership ambiguity is another flashpoint. SaaS contracts frequently include language granting the vendor broad rights to use, analyze, and aggregate customer data for the vendor’s own purposes. Customers often don’t realize the scope of what they’ve agreed to until a dispute forces them to actually read the fine print. Each of these scenarios can give rise to a breach of contract claim but the strength of that claim depends heavily on what the contract actually says about the vendor’s obligations around data security, data ownership, and post-termination data handling.
What You Can Actually Recover
If you do have a viable breach of contract claim against a SaaS vendor, the damages framework works the same way it does in any Illinois breach case: the goal is to put you in the position you would have been in had the contract been performed. But PML Development adds an important nuance. If you’ve elected to continue the contract as most SaaS customers do, your damages are calculated on the assumption that both parties will continue to perform. You’re compensated for the loss you suffered as the result of the specific breach, not for the loss of the entire remaining contract. This is different from what you’d recover if you terminated the agreement outright, where damages account for the full loss of the other party’s remaining performance. Direct damages are the most straightforward: the difference between what you paid for and what you actually received.
Consequential damages, lost profits, lost customers, business interruption costs are where the real money is, but they’re also where the contractual limitations hit hardest. If your contract contains a consequential damages waiver, you’ll need to find a way around it: a carve-out that applies, an argument that the waiver is unconscionable, or conduct by the vendor that falls outside the limitation’s scope. Incidental damages the costs of mitigating the breach, like the expense of emergency workarounds, temporary substitute services, or hiring consultants to manage the fallout are often recoverable and sometimes overlooked. And remember: Illinois law requires you to mitigate your damages. You can’t simply let the losses pile up. Taking reasonable steps to minimize the impact of a SaaS failure isn’t just good business it’s a legal obligation that courts will hold you to.
The Lesson: Read the Contract Before You Need to Sue Over It
If there’s one takeaway from the disputes I see in this space, it’s this: the time to think about your SaaS vendor’s obligations isn’t after something goes wrong. It’s before you sign. A civil litigation lawyer is great to have in your pocket when you need it. But I would advise that every Chicago tech company owner look at the SLA closely. Is uptime a guarantee or just a target? Are service credits your sole remedy, or do you retain the right to pursue actual damages? Are there meaningful termination rights if the vendor consistently fails to meet its benchmarks? Negotiate the limitation of liability. Push for carve-outs for data breaches, confidentiality violations, and gross negligence. Consider negotiating a “super cap” for catastrophic events typically three to five times the annual fees rather than accepting the standard one-times-annual-fees limitation. Nail down data rights. Make sure the contract clearly states that you own your data, that you can retrieve it in a usable format upon termination, and that the vendor’s rights to use your data are limited to what’s necessary to provide the service.
Understand your termination rights and use them strategically. This is where PML Development should change how you think about SaaS disputes. If your vendor materially breaches the contract, you have a right to walk away. If you choose to stay, know that you’re making a legal election that keeps you bound to the contract. That’s not necessarily the wrong choice, but it should be a deliberate one, made with legal advice, not a passive default because switching vendors feels inconvenient.
Bottom Line
SaaS platforms are the backbone of modern business operations, and when they fail, the consequences are real and immediate. But the contracts governing these relationships are often written to protect the vendor, not you. And as the Illinois Supreme Court made clear in PML Development LLC, what you do after a breach, whether it is to stay or walk away, shapes your legal rights going forward. Understanding what your SaaS agreement actually says about performance obligations, liability limits, and data rights, and knowing the legal consequences of your response when things go wrong is the difference between having real legal recourse and being stuck with a service credit that doesn’t come close to covering your losses. If you’re dealing with a SaaS vendor that failed to deliver what it promised or if you want to make sure your contracts protect you before a problem arises let’s talk.
At Ansari Business Litigation, we work with tech companies, startups, and businesses across industries that depend on software to run their operations. Whether you’re facing a live dispute or just want a second set of eyes on a contract before you sign, I can help you understand where you stand and what your options are.
Schedule a free 30-minute consultation today! No obligation, no pressure, just a straight conversation about your situation.
This post is for general informational purposes only and does not constitute legal advice. For guidance specific to your situation, please consult with a qualified attorney.