Software disputes usually come down to a handful of recurring claims: breach of contract when a project or service fails to deliver what was promised, copyright infringement when code is copied without authorization, trade secret misappropriation when proprietary information walks out the door, open source license violations when free code is used outside its terms, and warranty claims when commercial software doesn’t work as sold. What you can actually recover depends less on the strength of the underlying facts than on three things most people underestimate: what the contract says about liability and remedies, whether you filed inside the statute of limitations, and whether you preserved the digital evidence that proves your version of events.
Breach of Contract and SLA Problems
Most software disputes begin with a contract that stopped working. A client hires a developer, the parties sign a Statement of Work with deliverables and milestones, and then features arrive late, functionality fails to match the specifications, or the final product doesn’t do what the client needed. When a developer misses what the Statement of Work describes, the client has a direct breach claim.
The reverse is just as common. A client changes requirements mid-project, withholds feedback, or refuses to pay for completed milestones. Developers in that position need signed change orders for every scope change. Without them, the fight becomes competing narratives about who deviated first.
SaaS and Service Level Agreements
Software-as-a-service contracts bring their own version of breach claims, usually built around uptime guarantees. A typical SLA promises 99.9% or 99.99% availability and specifies credits the vendor owes when it falls short. The catch is that most SLAs make those credits the customer’s sole remedy, often capped at a fraction of a monthly fee. If your maximum credit is 50% of one month’s fees, that ceiling controls even when the outage cost you far more.
Notice provisions can also quietly destroy the right to credits. Many SLAs require you to report the outage and request credits within a short window, sometimes as little as five days. Miss that deadline and the remedy is gone.
Who Owns the Code
Ownership questions catch businesses off guard more than almost any other software issue. Federal copyright law defines a “work made for hire” in two ways: work created by an employee within the scope of employment, and work specially commissioned from an independent contractor that falls within certain narrow categories and is covered by a signed written agreement designating it as work for hire.1Office of the Law Revision Counsel. U.S. Code Title 17 – Definitions
When code qualifies as a work made for hire, the employer or hiring party is treated as the author and owns the copyright. The parties can agree otherwise, but only through a signed written agreement.2Office of the Law Revision Counsel. U.S. Code Title 17 – Ownership of Copyright Custom development is usually handled by independent contractors, and most custom software does not fit neatly into the statutory categories eligible for work-for-hire treatment. Without a clear written assignment of copyright in the contract, the developer who wrote the code may retain ownership even though the client paid for the work.
Copyright Infringement and the DMCA
Source code is protected by copyright the moment it is written. When someone copies, distributes, or builds on that code without authorization, the owner can bring an infringement claim.1Office of the Law Revision Counsel. U.S. Code Title 17 – Definitions These disputes typically surface when a former contractor reuses code from a prior engagement, a competitor reverse-engineers a product, or an employee takes proprietary code to a new job.
The financial exposure is heavy. A copyright owner can choose between actual damages plus the infringer’s profits, or statutory damages ranging from $750 to $30,000 per work infringed. Willful infringement pushes the ceiling to $150,000 per work.3Office of the Law Revision Counsel. U.S. Code Title 17 – Remedies for Infringement: Damages and Profits Courts can also issue injunctions ordering the infringer to stop using the software, which in practice can shut down a product or force an expensive rewrite.4Office of the Law Revision Counsel. U.S. Code Title 17 – Remedies for Infringement: Injunctions
A separate liability layer exists under the Digital Millennium Copyright Act. Cracking a license key, disabling DRM, or circumventing access controls on software violates federal law regardless of whether the underlying code is actually copied.5Office of the Law Revision Counsel. U.S. Code Title 17 – Circumvention of Copyright Protection Systems The law also targets anyone who creates or distributes tools designed primarily for circumvention, which frequently appears in licensing enforcement cases where a user modifies controls to avoid paying for additional seats or features.
Trade Secret Misappropriation
Proprietary algorithms, data architectures, and internal tools that give a company a competitive edge can qualify as trade secrets under the Defend Trade Secrets Act. A federal claim requires two things: the information has economic value because it is not publicly known, and the owner took reasonable steps to keep it confidential.6Office of the Law Revision Counsel. U.S. Code Title 18 1839 – Definitions Courts look for concrete evidence of those steps: confidentiality agreements with employees and contractors, access controls inside the codebase, and structured offboarding when people leave.
The remedies can be aggressive. A court can order the return of stolen information and bar further use. Financial damages include the owner’s actual losses plus any unjust enrichment the misappropriator gained, or alternatively a reasonable royalty. When theft is willful and malicious, a court can award exemplary damages up to twice the actual damages and shift attorney’s fees to the losing party.7Office of the Law Revision Counsel. U.S. Code Title 18 1836 – Civil Proceedings
Open Source License Violations
Open source code is free to use, not free of obligations. Every open source component carries a license imposing conditions on how the code can be used, modified, and distributed. Copyleft licenses like the GPL require anyone who distributes modified versions to release their modifications under the same license. When a company incorporates GPL-licensed code into a proprietary product without disclosing the source, the license is violated and the right to use the code terminates. Continued use at that point becomes copyright infringement, with the same statutory damages exposure as any other unauthorized copying.
These violations get discovered more often than companies expect. Automated code-scanning tools can detect even small snippets of open source code inside a proprietary codebase, and groups like the Software Freedom Conservancy actively enforce copyleft licenses. The practical defense is a Software Bill of Materials cataloging every open source component in your products, along with its license terms and compliance obligations. A code audit before any major release, acquisition, or investment is where that work pays for itself.
Warranty Claims When Software Is Sold as a Product
When software is sold as a product rather than licensed as a service, Article 2 of the Uniform Commercial Code can apply. Courts have generally treated off-the-shelf, mass-market software as “goods” under the UCC, while custom-developed software is more likely to be classified as a service. The distinction matters because the UCC imposes implied warranties that the product is fit for its ordinary purpose and suitable for any particular purpose the buyer communicated to the seller.8Legal Information Institute. U.C.C. – Article 2 – Sales
If commercial software crashes constantly, cannot perform the basic functions it was marketed for, or is incompatible with standard systems, the buyer may have a breach of warranty claim. Sellers often try to disclaim these warranties through license fine print, and enforceability varies. If you are buying software and the vendor’s contract disclaims all warranties, negotiate warranty protections in before signing rather than hoping the UCC will backstop you later.
How Liability Caps Shape What You Can Recover
Nearly every commercial software agreement caps the maximum amount one party can owe the other. A common structure ties the cap to total fees paid under the contract over the prior twelve months. The agreement will also typically exclude recovery of indirect losses like lost profits, lost revenue, reputational harm, and business interruption.
These clauses dramatically limit what you recover even on a strong claim. If you paid $50,000 annually for software that caused $500,000 in business losses, and the contract caps liability at twelve months of fees, your maximum recovery may be $50,000. Courts generally enforce these provisions in arms-length commercial agreements between sophisticated parties.
There are limits. Most jurisdictions will not enforce a cap that effectively eliminates all meaningful remedy, and carve-outs are standard for certain categories of harm. Intellectual property infringement, confidentiality breaches, and willful misconduct are commonly excluded, meaning full damages remain available for those claims. Negotiating those carve-outs before signing is far easier than arguing enforceability after a dispute arises.
Deadlines You Cannot Miss
Every software claim has an expiration date. Miss it and the claim is dead regardless of its merits. The deadline turns on the legal theory:
- Copyright infringement: three years from the date the claim accrues. In circuits that apply the discovery rule, the clock starts when you discover or should have discovered the infringement. The Supreme Court confirmed in 2024 that when a claim is timely under the discovery rule, damages can reach back to the initial infringement even if it happened more than three years ago.9Office of the Law Revision Counsel. U.S. Code Title 17 – Limitations on Actions10Supreme Court of the United States. Warner Chappell Music, Inc. v. Nealy
- Trade secret misappropriation: three years from the date the misappropriation is discovered or should have been discovered through reasonable diligence.7Office of the Law Revision Counsel. U.S. Code Title 18 1836 – Civil Proceedings
- Breach of a software sales contract under the UCC: four years from the date the breach occurred, regardless of when you learned about it. The parties can agree to shorten this to as little as one year, but cannot extend it past four.11Legal Information Institute. U.C.C. 2-725 – Statute of Limitations in Contracts for Sale
- General breach of contract: varies by state, typically three to six years.
For warranty claims, the clock usually starts when the software is delivered, not when the defect is discovered. The exception is a warranty that explicitly covers future performance, where the deadline runs from when the breach is or should have been found.11Legal Information Institute. U.C.C. 2-725 – Statute of Limitations in Contracts for Sale
Evidence to Preserve Early
Software disputes are won on documentation. The technical nature of the claims means you need both the legal agreements and the digital records showing what actually happened during the project.
Start with the contracts: the Master Service Agreement, any End User License Agreements, and the Statement of Work with its specifications. Collect every signed change order. On the technical side, gather bug reports, error logs, and version control histories. Commit timestamps establish when specific code was written or altered and by whom. Export all project communications from email, Slack, and project management tools. The combination is what lets you draw a direct line between a promised feature and a missed delivery.
As soon as a dispute becomes reasonably likely, you have an obligation to preserve relevant evidence. Issue a litigation hold notice to everyone in your organization who controls relevant data. The notice should describe the dispute, identify the types of data that must be kept, and make clear that automatic deletion policies are suspended until the matter is resolved. That includes backup tapes, server logs, and automated retention schedules that might overwrite relevant records. Coordinate with IT so nothing relevant is lost through routine processes. Failing to preserve evidence can result in sanctions and adverse inferences at trial, where the court instructs the jury to assume the destroyed evidence was unfavorable to you.
Court or Arbitration
The formal process starts with either filing a Summons and Complaint with a court clerk or submitting a Demand for Arbitration if the contract requires it. Many software agreements include mandatory arbitration clauses directing disputes to the American Arbitration Association or a similar body.12American Arbitration Association. AAA File a Case Check your contract before picking a forum; filing in court when the agreement requires arbitration wastes time and money because the court will likely send you to arbitration anyway.
Many software contracts also require mediation or another form of alternative dispute resolution before anyone can file suit. Courts treat these clauses as conditions that must be satisfied first, and skipping the step can get the case dismissed rather than paused. If a statute of limitations runs while you sort out the procedural error, the claim may be gone for good. Read the dispute resolution section carefully, complete any required mediation in good faith, and keep the documentation that proves you did.
Once the defendant is served, the response clock starts. In federal court, a defendant has 21 days after service to file an Answer or a motion to dismiss.13United States Courts. Federal Rules of Civil Procedure State courts set their own deadlines, commonly 20 to 30 days. If the defendant misses the window, the filing party can seek a default judgment for the damages requested. Software cases tend to involve heavy discovery because of the volume of digital records, code repositories, and technical communications, which is why many of them settle once both sides see the strength of the other’s evidence.