Pursuing or Defending a Failed Technology Project Claim: A Practical Guide

Summary. This guide takes a customer and a vendor, side by side, through a failed software implementation dispute from the first serious warning sign to settlement, arbitration award, or trial. It starts with the decisions that should come before any letter is sent: what the client actually wants (a fixed system, an orderly exit, or money), what the contract stack says, and who else is involved. Twelve numbered steps follow, covering contract triage, evidence preservation, a privileged project assessment, claim and defense mapping, notice and cure, termination and transition, the damages and cap analysis, choosing and starting the forum, pleading fraud and contract claims that survive a motion to dismiss, ESI discovery, experts and summary judgment, and settlement. Each step explains what to do, why, the governing authority, the pitfalls, the timing, and the cost, with separate notes for the customer and for the vendor. A timeline and cost table and an extended worked example involving a logistics company's failed CRM and dispatch rollout show the steps in sequence. Common mistakes, an FAQ, and takeaways close the guide.

At 4:40 on a Friday afternoon, the general counsel of Ironbridge Digital, a 300-person implementation firm, opens an email from the chief information officer of Corvane Logistics, a freight brokerage that is one of Ironbridge's largest clients. Attached is a 14-page "Notice of Material Breach and Demand for Cure." It lists nineteen alleged breaches of a master services agreement and two statements of work for a cloud CRM and custom dispatch module, demands a written cure plan within ten business days, reserves the right to terminate in thirty days, and states that Corvane is "evaluating claims for fraudulent inducement." The project is fourteen months late. Ironbridge has $2.4 million in unpaid invoices. Its engagement partner has been telling the general counsel for months that Corvane cannot make a decision and keeps changing the requirements.

Across town, Corvane's general counsel is wondering whether the letter she approved was a mistake. Her CIO wants Ironbridge gone. Her CFO wants the money back. Her chief operating officer wants the dispatch module working before peak season and is not sure anyone else can finish it.

Both lawyers face the same problem from opposite sides. What they do in the next thirty days will shape the case more than anything a judge or arbitrator does later. This guide is the playbook for that period and for what follows. For the substantive law (UCC classification, warranties, the economic loss rule, the cap fights), see Failed Software Implementations: Contract, Fraud, and Warranty Claims When an IT Project Goes Wrong. The check-off version is Troubled Technology Project Checklist: A Practical Checklist, and the forms referenced below are in Technology Project Dispute Toolkit: Notice of Breach Letters, Cure Plans, and Project Record Protocols.

The short answer

• Decide the objective before sending anything. A customer that needs the system working by a date has different leverage, and different risks, than one that wants out or wants money. The vendor must decide whether it is defending a relationship, a receivable, or its reputation.
• The contract stack is the battlefield. Read every document that may govern: MSA, SOWs, change orders, amendments, the license or subscription, and any sales documents incorporated by reference. Find the notice, cure, termination, limitation, IP, transition, and dispute resolution clauses before anyone speaks.
• Preserve on day one. Collaboration tools, ticketing systems, code repositories, and personal devices hold the decisive evidence. A litigation hold should issue as soon as a dispute is reasonably anticipated, which usually means the first breach notice or termination threat.
• Get a privileged, independent assessment. Retain a software project expert through counsel to tell the client, candidly, who caused what. The client's own team is the least reliable source on its own conduct.
• Follow the contractual process exactly. Specific notice, a real opportunity to cure, written responses, and documented escalation. A party that skips steps converts its own position into a breach.
• Secure the exit before terminating. Data, code, documentation, environments, and transition assistance are worth more in the first month than any damages claim.
• Model damages against the cap early. The limitation-of-liability clause sets the realistic range. The two ways above it are a direct-damages characterization of re-implementation costs and a fraud claim that survives.
• Plead to survive the motion to dismiss. Fraud claims need specific statements of present fact pleaded with particularity under Fed. R. Civ. P. 9(b). Puffery and restated contract promises will be dismissed.
• Most cases settle. The common windows are during cure, right after termination (when transition is negotiated), after document production, and after expert reports.

Before you start: four decisions that shape everything

1. What does the client actually want?

Many clients want all three customer objectives at once and do not see that they conflict. A customer that sends an aggressive fraud-laden notice will find it harder to get the vendor's best people to stay and fix the system. Put the objectives in order and choose the path that serves the first.

2. What is in the contract stack?

Collect every document that might govern. Implementation deals commonly involve a master agreement; one or more SOWs (often with phase-specific scope, pricing, assumptions, and acceptance criteria); change orders and change requests (signed and unsigned); amendments; the software license or subscription, which may be with a different company; a reseller agreement if the integrator resold the software; a data processing agreement; and sometimes a project charter or "blueprint" that the parties signed. The order-of-precedence clause tells you which controls in a conflict. Do not stop at the signed documents. Find the RFP, the vendor's proposal, demo scripts, and the negotiation emails; you will need them to evaluate any fraud theory and to construe ambiguous terms. For drafting background, see Negotiating a Master Services Agreement and Statement of Work.

3. Who else is involved?

Most enterprise projects have at least three parties: the customer, the integrator, and the software publisher. Some have a separate data migration contractor, a quality assurance firm, a hosting provider, or a staff augmentation firm whose people worked under the customer's direction. Each may share responsibility. Check whether the contracts allow joinder in a single arbitration (most do not, unless the clauses match), whether claims against the publisher require a different forum, and whether any party is a public entity subject to procurement rules, notice-of-claim statutes, or sovereign immunity limits.

4. Is there insurance or a parent guarantee?

Vendors often carry technology errors and omissions (E&O) insurance, and many MSAs require it. Notify the carrier early; late notice can forfeit coverage, and many policies require consent before settlement. Customers should check whether any of their own policies cover business interruption from a failed system (usually not, but worth checking). If the vendor is a subsidiary, look for a parent guarantee.

Step 1: Triage the contract and calendar every clock

What to do. Within the first two or three days, prepare a short contract abstract covering: governing law and forum; dispute resolution steps (executive escalation, mediation, arbitration); notice requirements (addresses, method, who must sign); cure periods; termination rights for cause and for convenience, and what is payable on each; suspension rights; the limitation of liability, exclusions, and carve-outs; warranty terms and exclusive remedies; acceptance procedures, including deemed acceptance; change control; key personnel; IP ownership and licenses; transition assistance; data return; confidentiality; insurance; and any contractual limitations period. Calendar every deadline.

Why. Many IT disputes are lost on procedure before the merits are reached. A notice sent to the wrong address, a termination before the cure period ran, or a claim filed after a one-year contractual limitations period can be fatal.

Authority. Courts apply the contract's own standards when it sets them. In State v. International Business Machines Corp., 51 N.E.3d 150 (Ind. 2016), the Indiana Supreme Court held that the MSA's definition of a material breach ("material considering this Agreement as a whole") governed the termination for cause, and the common law Restatement factors applied only where the contract was silent. Contractual limitations periods are generally enforced if reasonable; under the UCC, parties may shorten the four-year period to not less than one year (this guide cites Article 2 through California's enactment, whose section numbers track the uniform text: Cal. Com. Code § 2725). For interpretive disputes over SOW language, see How Courts Read Contracts: Ambiguity, Extrinsic Evidence, and the Canons of Construction.

Customer notes. Look hard at deemed acceptance and production-use clauses. If the system went live, determine whether the customer signed an acceptance certificate, reserved rights in writing, or simply started using it. Look also at whether the contract requires the customer to pay undisputed invoices while disputing others.

Vendor notes. Look for customer-responsibility provisions, assumptions schedules, and dependencies. Identify every change request the customer approved, formally or by conduct, and every one it refused. Confirm whether you have a right to suspend work for nonpayment and what notice it requires.

Pitfalls. Relying on the "current" SOW without checking whether a later change order replaced its acceptance criteria. Missing a mandatory executive escalation step that is a condition precedent to arbitration.

Timing and cost. Two to five days. Typically a modest fee for an abstract and an initial strategy memo.

Step 2: Preserve the evidence and issue litigation holds

What to do. Issue a written litigation hold to every custodian (project managers, architects, developers, business leads, executives, steering committee members, and outside contractors), and to IT administrators who control systems. Suspend auto-deletion in Slack, Microsoft Teams, and email. Preserve the ticketing system (Jira, Azure DevOps, ServiceNow), the code repository with its full commit history, test management tools, shared drives (Confluence, SharePoint), project management tools, and calendar entries. Image the laptops and phones of key custodians who used personal devices or messaging apps. Export any vendor-hosted environments the client is about to lose access to. Send a preservation demand to the other side and, where appropriate, to third parties such as the publisher or a staffing firm.

Why. The project record is the case. The contemporaneous messages ("we are not ready for UAT"; "we keep moving the goalposts on them") decide who caused the failure. Lost ESI can lead to curative measures or, if a party acted with intent to deprive, to an adverse inference or default.

Authority. The duty to preserve attaches when litigation is reasonably anticipated, and counsel must take affirmative steps to locate and preserve relevant information (Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003)). Sanctions for lost ESI are governed by Fed. R. Civ. P. 37(e). See Litigation Hold and Evidence Preservation Checklist: A Practical Checklist and Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case.

Customer notes. If the vendor hosts the project tools (common for Jira and Confluence), demand an export now, while the contract is in force. Once the vendor is terminated, access may disappear.

Vendor notes. Consultants roll off projects constantly. Preserve departing team members' data before their accounts are deprovisioned, and remind subcontractors (including offshore delivery centers) of their preservation duties in writing.

Pitfalls. Issuing a hold but not stopping automated deletion. Forgetting ephemeral messaging and personal phones. Letting the project team "clean up" the ticket backlog before the dispute.

Timing and cost. Within 48 hours of anticipating a dispute. Forensic collection costs scale with the number of custodians and systems. The toolkit's project record protocol is designed for this step. For collecting and authenticating chat data specifically, see Collecting and Authenticating Messaging and Social Media Evidence: A Practical Guide.

Step 3: Build a privileged chronology and get an independent project assessment

What to do. Assemble a chronology from the documents, not from memory: proposal, signing, kickoff, design sign-off, each milestone (planned versus actual), each change request, each escalation, testing results, go-live, and the dispute. Then retain, through counsel, a software project management consultant to review the record and give a candid view of what went wrong and who caused it. Interview the client's key people with counsel present.

Why. Every failed project has two narratives, and both sides usually believe their own. A consultant who has seen dozens of implementations can tell the client, privately, whether its story will survive the other side's documents. That assessment shapes the notice, the settlement position, and the decision whether to sue.

Authority. Communications with counsel for the purpose of legal advice are privileged, including with employees at multiple levels of the company (Upjohn Co. v. United States, 449 U.S. 383 (1981)). Materials prepared in anticipation of litigation are protected work product (Hickman v. Taylor, 329 U.S. 495 (1947)), and the facts known and opinions held by a consulting expert who will not testify are generally protected from discovery under Fed. R. Civ. P. 26(b)(4)(D). A business "lessons learned" review, run by the project team without counsel, usually is not privileged and may be discoverable.

Customer notes. Ask the consultant specifically to evaluate the customer's own performance: decision latency, subject-matter expert availability, data readiness, scope changes. That is the vendor's case, and you need to know its strength.

Vendor notes. Ask whether the staffing matched what was sold, whether the design was competent, whether testing was real, and whether status reports were accurate. If the answer to any is no, the fraud exposure is real and settlement strategy should reflect it.

Pitfalls. Letting the consultant become a testifying expert too early, which exposes communications. Writing internal emails that characterize the project ("we blew it") outside privileged channels.

Timing and cost. Two to six weeks for a first assessment. Consultant fees for a focused review are commonly in the five figures; a deep review of a large project can cost more.

Step 4: Map the claims, defenses, and counterclaims

What to do. Build a matrix of every potential claim and defense, the elements, the evidence, the contract provisions, and the damages each would reach. Do this for both sides.

Why. The matrix shows which claims actually move the number. In most cases, two or three claims carry the case, and the rest are leverage or noise.

Authority. The economic loss rule and "duplicative of contract" doctrines vary by state. In New York, a fraud claim alongside a contract claim must allege a separate legal duty, a misrepresentation collateral or extraneous to the contract, or special damages (Bridgestone/Firestone, Inc. v. Recovery Credit Services, Inc., 98 F.3d 13 (2d Cir. 1996)). In Michigan and Wisconsin, only fraud extraneous to the contract survives (Huron Tool & Engineering Co. v. Precision Consulting Services, Inc., 209 Mich. App. 365 (1995); Kaloti Enterprises, Inc. v. Kellogg Sales Co., 2005 WI 111, 283 Wis. 2d 555). Texas allows tort damages for fraudulent inducement even where the loss is purely economic (Formosa Plastics Corp. USA v. Presidio Engineers & Contractors, Inc., 960 S.W.2d 41 (Tex. 1998)). Professional negligence claims against IT vendors are usually rejected (Hospital Computer Systems, Inc. v. Staten Island Hospital, 788 F. Supp. 1351 (D.N.J. 1992)).

Pitfalls. Counting every theory as additive. Overlapping claims usually reach the same damages and are capped the same way, unless one escapes the cap.

Timing and cost. One to two weeks, usually alongside Step 3.

Step 5: Run the contractual process. Notice, cure, assurance, and escalation

What to do (customer). Send a written notice of breach that complies exactly with the notice clause (address, method, signatory). Identify each breach specifically, tie it to the contract provision, describe the evidence briefly, say what an acceptable cure looks like, and set the cure deadline the contract allows. Demand a written cure plan with named resources, dates, and measurable exit criteria. Reserve all rights, including termination and claims for damages, and state that continued performance and payment are under reservation. If the contract or governing law allows it, couple the notice with a demand for adequate assurance of performance.

What to do (vendor). Respond in writing, on time, point by point. Accept what is true and propose a cure; dispute what is not and say why, with references to customer obligations, change requests, and approvals. Offer a cure plan that is achievable, because an unmet cure plan becomes the customer's best evidence. Request that the customer meet its own outstanding obligations, in writing. If the customer's notice is procedurally defective, say so, but respond on the merits anyway.

Why. A specific notice frames the later case. Courts and arbitrators look at whether the breaches in the termination letter match the breaches in the notice, and whether the breaching party was given a real chance to cure. A vendor's silence, or a boilerplate denial, reads as an admission.

Authority. Where the governing law includes UCC Article 2, a party with reasonable grounds for insecurity may demand adequate assurance and, after a reasonable time not exceeding thirty days, treat the failure to provide it as a repudiation (Cal. Com. Code § 2609; Cal. Com. Code § 2610). Many states recognize a similar common law right (Restatement (Second) of Contracts § 251). Material breach, where the contract is silent, is evaluated under Restatement § 241, including the likelihood of cure and the breaching party's good faith, so a credible cure plan can defeat a termination. The doctrine of substantial performance (Jacob & Youngs, Inc. v. Kent, 230 N.Y. 239 (1921)) protects a vendor whose deviations are minor.

Escalation and mediation. Many MSAs require executive escalation and sometimes mediation before arbitration or suit. Complete each step and document it. Settlement communications in those meetings are generally inadmissible to prove liability or amount under Fed. R. Evid. 408, but the protection is not absolute, and facts disclosed do not become privileged. Label the communications and keep business discussions separate from settlement discussions.

Pitfalls (customer). Listing every irritation as a "material breach," which dilutes the real ones. Sending a notice that also announces a decision to terminate, which suggests the cure period was illusory. Failing to fix the customer's own open obligations during cure.

Pitfalls (vendor). Promising a cure plan that requires customer resources the customer has not agreed to provide. Writing "we acknowledge the issues" without qualification. Pulling staff off the project during the cure period.

Timing and cost. The cure period is usually 30 days, sometimes shorter for payment defaults and longer for complex defects. Templates for the notice, the response, and the cure plan are in the toolkit.

Step 6: Decide whether and how to terminate, and secure the exit

What to do (customer). Before terminating, line up the exit. Confirm in writing what transition assistance the vendor must provide and at what rates; obtain current copies of all code, configurations, scripts, interface specifications, documentation, test assets, and credentials; export data from any vendor-hosted environment; confirm IP ownership; and identify the replacement integrator (or decide to stabilize in-house). Then choose the termination basis:

• For cause if you can prove a material breach that was not cured within the cure period. This preserves damages claims and usually avoids termination fees.
• For convenience if cause is doubtful, accepting the contractual wind-down payment, while preserving accrued claims if the contract allows.
• Partial termination of a single SOW or phase, if the MSA permits it, to keep useful services running.
• Termination in the alternative (for cause, or if cause is found lacking, for convenience) is sometimes used to limit wrongful-termination exposure; check whether the contract and governing law allow it, because some courts treat the alternative as an admission.

What to do (vendor). If the customer terminates, decide quickly whether to contest the termination or accept it and pursue fees. Continue to honor transition obligations, because refusing them shifts sympathy and may breach the contract. If the customer has not paid, check whether you have a contractual right to suspend; do not disable systems or withhold the customer's own data without clear contractual authority.

Why. A wrongful termination converts the customer from plaintiff to defendant. A termination without the exit secured leaves the customer dependent on a hostile vendor for its own system.

Authority.

• Material breach and cure. State v. IBM shows the contract's materiality standard governs. A termination for an immaterial breach is itself a repudiation.
• IP ownership. Contractor-written software rarely qualifies as a work made for hire under 17 U.S.C. § 101, so ownership usually depends on a signed written assignment under 17 U.S.C. § 204(a). Without one, a paying customer usually has an implied nonexclusive license to use and modify custom code (Asset Marketing Systems, Inc. v. Gagnon, 542 F.3d 748 (9th Cir. 2008)). See Work Made for Hire Determination Checklist: A Practical Checklist.
• Owner's copies. The owner of a lawful copy of a computer program may make copies or adaptations that are an essential step in using it, and archival copies, under 17 U.S.C. § 117, but courts disagree on when a licensee counts as an "owner," so do not rely on § 117 as the exit plan.
• Self-help. Remote disabling or locking a customer out of a system can create exposure under 18 U.S.C. § 1030 and state law, beyond contract damages.
• Emergency relief. Where a vendor refuses contractual transition cooperation and the customer faces business-stopping harm, a temporary restraining order or preliminary injunction under Fed. R. Civ. P. 65 may be available. If the contract requires arbitration, check whether it allows court applications for interim relief or provides for an emergency arbitrator.
• Vendor insolvency. If the vendor or publisher is in bankruptcy, a licensee may retain its rights in licensed intellectual property, including under an escrow agreement, under 11 U.S.C. § 365(n).
• Public entities. Federal contracts follow 48 C.F.R. pt. 49; state and local procurement codes often have their own termination procedures and claim deadlines.

Pitfalls. Terminating before the cure period runs. Terminating for reasons different from those in the notice. Terminating without a replacement plan. A vendor stopping transition work over a payment dispute.

Timing and cost. Exit planning should start during the cure period. Transition assistance periods of 60 to 180 days are common. Replacement integrators typically need weeks of discovery before they can quote remediation work credibly.

Step 7: Model the damages and run the cap analysis

What to do. Build a damages model early and refine it. For the customer, the categories usually include:

1. Fees paid for deliverables that were never accepted or have no value.
2. Cost to complete or remediate the system as originally scoped (cover), net of the unpaid contract price.
3. Internal costs: employee time diverted to the project beyond plan, overtime, temporary staff, extended legacy system costs, duplicate licenses.
4. Business losses: lost profits, lost customers, penalties paid to the customer's own customers, shipping errors, write-offs.
5. Incidental costs: consultant reviews, data cleanup, re-testing.

For the vendor: unpaid invoices, work performed but not invoiced, wind-down costs, and, if the termination was wrongful, lost profit on the remaining committed term.

Then run each category through the limitation-of-liability clause: Is it excluded as consequential? Is it within a carve-out? What is the cap amount and how is it measured (fees paid in the prior twelve months, fees payable under the SOW, total contract value)? Does the cap apply per claim or in aggregate? Does it apply to the vendor's fee claims too?

Why. The cap analysis sets the realistic settlement range. Both sides should know it before the first serious settlement discussion.

Authority.

• Certainty. Lost profits must be proven with reasonable certainty and, for consequential damages, must have been within the parties' contemplation (Kenford Co. v. County of Erie, 67 N.Y.2d 257 (1986)). Once the fact of damage is proven, uncertainty about the amount weighs against the wrongdoer (Story Parchment Co. v. Paterson Parchment Paper Co., 282 U.S. 555 (1931)).
• Direct versus consequential. Lost profits and similar losses can be general damages when they flow directly from the breach of the particular contract (Tractebel Energy Marketing, Inc. v. AEP Power Marketing, Inc., 487 F.3d 89 (2d Cir. 2007); Biotronik A.G. v. Conor Medsystems Ireland, Ltd., 22 N.Y.3d 799 (2014)). The same reasoning supports treating the cost of cover as direct; under Article 2, cover is a buyer's primary remedy (Cal. Com. Code § 2712), and consequential and incidental damages are defined separately (Cal. Com. Code § 2715).
• Carve-outs. A "willful misconduct" carve-out generally does not reach a vendor's deliberate, economically motivated decision to stop performing (Metropolitan Life Insurance Co. v. Noble Lowndes International, Inc., 84 N.Y.2d 430 (1994)). New York will not enforce an exculpatory clause against gross negligence or conduct that smacks of intentional wrongdoing (Kalisch-Jarcho, Inc. v. City of New York, 58 N.Y.2d 377 (1983)).
• Failure of essential purpose. If the exclusive repair remedy failed, the customer may reach general Code remedies (Cal. Com. Code § 2719), but many courts enforce a separate consequential damages exclusion anyway (Chatlos Systems, Inc. v. National Cash Register Corp., 635 F.2d 1081 (3d Cir. 1980)).

For general damages methodology, see Building a Damages Case: A Practical Guide from Pleading to Verdict and Damages Proof and Expert Model Checklist: A Practical Checklist.

Customer notes. Separate "cost to get what we contracted for" from "cost of a better system." Scope creep in the remediation project is the vendor's best damages attack. Track internal time contemporaneously from the day the dispute starts; reconstructed time estimates are weak evidence.

Vendor notes. Model the customer's best case honestly, including the fraud scenario. If the fraud scenario is plausible, the cap is not your ceiling.

Pitfalls. Treating every dollar spent as damages. Ignoring mitigation. Forgetting that the vendor's unpaid fees will offset the recovery.

Timing and cost. A preliminary model within the first month; an expert model later. The toolkit includes a damages model outline.

Step 8: Choose and start the forum

What to do. Confirm the dispute resolution clause. If it requires arbitration, decide whether the clause covers all claims (including fraud in the inducement) and all parties, which rules apply, how many arbitrators, the seat, and whether there are limits on discovery or damages. If the case will be in court, confirm subject matter jurisdiction (diversity under 28 U.S.C. § 1332 is common in commercial disputes; check the citizenship of every LLC member), venue under 28 U.S.C. § 1391 or the forum selection clause, and whether a declaratory judgment action under 28 U.S.C. § 2201 would let a vendor pick the forum first.

Arbitration authority. Arbitration agreements are enforceable under 9 U.S.C. § 2; a court must stay a case referred to arbitration on request (9 U.S.C. § 3; Smith v. Spizzirri, 601 U.S. 472 (2024)) and may compel arbitration (9 U.S.C. § 4). Courts decide arbitrability unless the parties clearly and unmistakably delegated it (First Options of Chicago, Inc. v. Kaplan, 514 U.S. 938 (1995)), and a valid delegation must be enforced even if the argument for arbitration seems weak (Henry Schein, Inc. v. Archer & White Sales, Inc., 586 U.S. 63 (2019)). A challenge to the contract as a whole, including a claim that the entire MSA was fraudulently induced, generally goes to the arbitrator unless directed specifically at the arbitration clause or delegation provision (Rent-A-Center, West, Inc. v. Jackson, 561 U.S. 63 (2010)). A party that litigates first and moves to arbitrate later risks waiver, and waiver no longer requires a showing of prejudice (Morgan v. Sundance, Inc., 596 U.S. 411 (2022)). An appeal from the denial of a motion to compel arbitration automatically stays district court proceedings (Coinbase, Inc. v. Bielski, 599 U.S. 736 (2023)).

Pleading in court. A complaint must state a plausible claim (Bell Atlantic Corp. v. Twombly, 550 U.S. 544 (2007); Ashcroft v. Iqbal, 556 U.S. 662 (2009)), and fraud must be pleaded with particularity. The October 2019 ruling in Hertz Corp. v. Accenture LLP, No. 19-cv-3508 (S.D.N.Y. Oct. 25, 2019), is the cautionary model: the court held that pitch-deck statements about "800 experts" and "the best talent in the world" were puffery, held that allegations that the vendor misrepresented its framework expertise and code testing failed Rule 9(b) because they did not identify what was said, by whom, and when, and dismissed the statutory deceptive practices claim with prejudice. The breach of contract claim went forward, and the court declined to decide at the pleading stage whether the contract's damages limitations barred the claimed damages.

Customer pleading checklist. For each misrepresentation: the exact words (quote the email, slide, or proposal section), the speaker and their role, the date and medium, the recipient, why it was false when made (not later), how the speaker knew, why the customer relied, and why reliance was reasonable notwithstanding the integration clause. Plead the contract claim around specific SOW provisions and acceptance criteria, not general "failure to deliver a working system."

Vendor response. A motion under Fed. R. Civ. P. 12(b)(6) aimed at the fraud and tort counts (puffery, particularity, economic loss rule, duplicative of contract, non-reliance clause) is usually worthwhile, because narrowing the case to contract claims puts the cap in play. Motions to dismiss damages categories are often deferred, as in Hertz. The vendor's counterclaim for unpaid fees should be filed with the answer if it is compulsory.

Pitfalls. Filing in court despite a broad arbitration clause, then losing months to a motion to compel. Pleading fraud from memory instead of documents. Naming individual salespeople as defendants for leverage without a factual basis, which invites a Fed. R. Civ. P. 11 motion.

Timing and cost. Drafting a complaint or demand typically takes two to four weeks once the record is assembled. Motions to dismiss and to compel arbitration add three to nine months. For arbitration clause analysis, see Selecting and Drafting an Arbitration Clause and Arbitration, Mediation, and Choosing a Dispute-Resolution Forum: A Practical Guide.

Step 9: Run discovery around the project record

What to do. Negotiate an ESI protocol at the Rule 26(f) conference that addresses collaboration platforms (Slack, Teams), ticketing systems, code repositories, test tools, and short-message data, including formats (threaded conversations with metadata, ticket histories with change logs, repository exports), custodians, date ranges, search methodology, and privilege logging. Serve requests under Fed. R. Civ. P. 34 targeted at the decisive categories: the sales file; staffing plans and résumés of people actually staffed; internal status reports and risk registers (which often differ from the ones shown to the customer); defect logs; test results; change request files; and internal communications about the customer. Take a deposition of the other side's organization under Fed. R. Civ. P. 30(b)(6) on staffing, methodology, testing, and project governance. Subpoena third parties under Fed. R. Civ. P. 45: the software publisher, subcontractors, and the replacement integrator (whose assessment of the inherited system is often the most candid document in the case).

Why. Internal vendor documents show whether the team was what was sold and whether status reports to the customer matched internal reality. Internal customer documents show whether the customer caused delay. Both sides know this, which is why discovery fights in these cases are intense.

Authority. Discovery must be relevant and proportional (Fed. R. Civ. P. 26(b)(1)). Deposition limits and scheduling are managed under Fed. R. Civ. P. 16. Disputes over the number and identity of deponents are common in large IT cases; in the March 2020 discovery ruling in Hertz Corp. v. Accenture LLP, No. 19-cv-3508 (S.D.N.Y. Mar. 9, 2020), the magistrate judge resolved a dispute over the depositions the vendor sought to take. A clawback order under Fed. R. Evid. 502 protects against privilege waiver in large productions. Business records such as tickets and status reports are usually admissible under Fed. R. Evid. 803(6) if properly authenticated under Fed. R. Evid. 901, and voluminous ticket data can be presented through summaries under Fed. R. Evid. 1006.

Pitfalls. Agreeing to produce Slack as individual messages stripped of thread context. Forgetting offshore delivery centers and subcontractors, whose records the vendor may or may not control. Producing the customer's own "lessons learned" deck without a privilege review. When the other side stonewalls, see Bringing or Opposing a Motion to Compel Discovery: A Practical Guide. For deposition strategy with adverse project witnesses, see Cross-Examining an Adverse Witness at Deposition: A Practical Guide.

Timing and cost. Document discovery in a large implementation case commonly runs six to twelve months. ESI processing and review is often the largest single cost in the case.

Step 10: Retain testifying experts and prepare for summary judgment

What to do. Retain, separately from the consulting expert if possible, a testifying software project management expert and a damages expert. Give them the full record, not a curated set. The project expert should address the standard of performance under the contract and accepted practice, staffing, design quality, testing, governance, and a causation analysis that allocates delay between the parties (a "windows" or critical-path style analysis borrowed from construction delay practice is common). The damages expert should build from the project expert's causation findings. Disclose them under Fed. R. Civ. P. 26(a)(2).

Why. Factfinders cannot judge whether a CRM integration layer was competently designed without help. And a damages number without a causation analysis is an invitation to a Daubert motion.

Authority. Expert testimony must meet Fed. R. Evid. 702; as amended in 2023, the rule requires the proponent to show by a preponderance that the testimony is based on sufficient facts and reflects a reliable application of reliable methods. The gatekeeping duty applies to experience-based experts (Kumho Tire Co. v. Carmichael, 526 U.S. 137 (1999)), and a court may exclude opinions connected to the data only by the expert's say-so (General Electric Co. v. Joiner, 522 U.S. 136 (1997)). Experts may rely on facts or data of a type reasonably relied on in the field (Fed. R. Evid. 703). See Expert Witnesses After the 2023 Amendment to Rule 702: Daubert, Disclosure, and Cross-Examination.

Summary judgment. Many IT cases have issues suited to Fed. R. Civ. P. 56: whether the UCC applies; whether the limitation clause bars categories of damages; whether a carve-out applies; whether fraud claims are barred by a non-reliance clause; whether a contractual limitations period has run. The movant must show the absence of a genuine dispute (Celotex Corp. v. Catrett, 477 U.S. 317 (1986)), and the nonmovant must offer evidence on which a reasonable factfinder could rule for it (Anderson v. Liberty Lobby, Inc., 477 U.S. 242 (1986)). Materiality of breach and causation of delay are usually fact questions; the cap and its carve-outs often are not.

Pitfalls (customer). A delay expert who attributes every slipped milestone to the vendor without addressing the customer's late decisions. A damages expert who prices a re-implementation broader than the original scope.

Pitfalls (vendor). An expert who blames the customer without reading the vendor's own internal risk register.

Timing and cost. Expert work commonly runs three to six months and is one of the largest costs. For deposition preparation, see Taking and Defending an Expert Deposition: A Practical Guide.

Step 11: Negotiate settlement and a transition agreement

What to do. Use the natural settlement windows: during cure, at termination, after document production, after expert reports, and before trial. Build a settlement range from the cap analysis and a probability-weighted view of the fraud claim. A settlement in an IT dispute often has more than money in it: a write-off of unpaid invoices, a payment or credit, a structured transition (delivery of code, documentation, knowledge transfer, continued hosting for a period), IP assignment or license confirmations, data return and deletion certifications, non-disparagement, mutual releases with carve-outs for confidentiality and IP indemnities, and sometimes a reference or press statement.

Why. Many disputes are worth more to both sides resolved quickly than litigated. The customer needs the system; the vendor needs to stop the fees and protect its reputation.

Authority. Settlement communications are generally inadmissible to prove or disprove the validity or amount of a disputed claim (Fed. R. Evid. 408). For the negotiation itself, see Planning and Running a Litigation Settlement Negotiation: A Practical Guide; for documenting it, Drafting a Settlement Agreement and Release: A Practical Guide. The toolkit includes a settlement and transition agreement template.

Pitfalls. Releasing claims before the transition deliverables are actually delivered; tie the release's effectiveness to delivery. Releasing the publisher unintentionally through a broad "affiliates and partners" definition. Forgetting the E&O carrier's consent requirement.

Timing and cost. Mediation in a commercial IT case often takes one or two days with a mediator experienced in technology disputes. Preparation is where the cost lies.

Step 12: Try the case or the arbitration

What to do. If the case does not settle, prepare the story as a chronology the factfinder can follow: what was promised, what was delivered, what each side knew, and when. Use demonstratives built from the ticket data and status reports. Prepare motions in limine on the other side's damages theories, expert opinions, and characterizations of internal messages. In arbitration, prepare witness statements and expect the tribunal to focus on documents.

Authority. Relevance and unfair prejudice objections under Fed. R. Evid. 401 and Fed. R. Evid. 403 are common against inflammatory internal messages. An arbitration award can be vacated only on the narrow grounds in 9 U.S.C. § 10, and parties cannot expand judicial review by contract (Hall Street Associates, L.L.C. v. Mattel, Inc., 552 U.S. 576 (2008)). See Drafting and Opposing Motions in Limine: A Practical Guide.

Timing and cost. Trial or a final arbitration hearing in a complex IT case is commonly 18 to 36 months after filing. Total fees through trial for each side often reach seven figures in large cases; smaller disputes can be run more economically in arbitration with limited discovery.

Timeline and cost overview

These figures are typical ranges for disputes over mid-size and large enterprise projects. Smaller disputes move faster and cost less, particularly in arbitration.

Extended worked example: Corvane Logistics and Ironbridge Digital

The deal. Corvane, a freight brokerage, signed an MSA with Ironbridge Digital in 2024 governed by Texas law, with AAA commercial arbitration seated in Dallas and a delegation of arbitrability to the arbitrator. SOW 1 (fixed fee, $3.1 million) covered configuration of a cloud CRM platform licensed directly from its publisher. SOW 2 (time and materials, estimated at $2.6 million with no cap) covered a custom dispatch module integrated with Corvane's transportation management system. The MSA caps liability at the fees paid under the applicable SOW, excludes consequential damages and lost profits, carves out gross negligence, willful misconduct, and "fraud," and has a merger clause that says the agreement supersedes prior proposals but does not disclaim reliance. The SOWs list named key personnel, including a lead architect, and give Corvane the right to approve replacements.

Step 1 (triage). Corvane's counsel finds that the notice clause requires notice to Ironbridge's general counsel by courier as well as email; the Friday notice went only by email. She re-sends it properly on Monday, restarting the 30-day cure clock. Ironbridge's counsel finds a one-year contractual limitations period running from "the date the claim arose" and calendars it for both sides.

Step 2 (preservation). Both sides issue holds. Corvane discovers that the project Jira instance is hosted on Ironbridge's account and demands an export, which Ironbridge provides within a week. Ironbridge suspends deprovisioning for eleven consultants who rolled off the project during the prior year.

Step 3 (assessment). Corvane's consulting expert reports that the dispatch module's integration layer was poorly designed and that the named lead architect was replaced after two months by a less experienced engineer without Corvane's approval. The expert also reports that Corvane took an average of 23 days to answer design questions the SOW required it to answer in five, and that Corvane added a load-matching feature mid-build without a signed change order. Ironbridge's consulting expert reaches similar conclusions from the other direction and adds that Ironbridge's internal risk register rated the integration "red" for four months while weekly status reports to Corvane showed "amber."

Step 4 (mapping). Corvane's strongest claims are breach of the key-personnel clause and failure of the dispatch module to meet SOW 2's acceptance criteria. Its potential fraud claim rests on a proposal statement that Ironbridge had "built and deployed this integration pattern for three national brokerages," which internal documents may show was not true, and on the gap between internal and external status reports. Under Texas law, the merger clause does not by itself bar the fraud claim because it does not clearly disclaim reliance (Italian Cowboy Partners, Ltd. v. Prudential Insurance Co. of America, 341 S.W.3d 323 (Tex. 2011); compare Schlumberger Technology Corp. v. Swanson, 959 S.W.2d 171 (Tex. 1997)), and Formosa Plastics permits tort damages for fraudulent inducement. Ironbridge's strongest positions are Corvane's decision delays, the unapproved scope change, the cap, and its $2.4 million fee claim.

Step 5 (notice and cure). Corvane's re-sent notice narrows nineteen alleged breaches to six, each tied to a provision. Ironbridge responds in ten days with a cure plan: a new lead architect from its national practice (Corvane may interview and approve), a redesigned integration layer in three sprints with defined acceptance tests, and a request that Corvane commit to five-day decision turnaround and sign a change order for load matching. Both sides keep the cure discussions separate from a parallel, labeled settlement channel.

Step 6 (exit planning). While cure proceeds, Corvane confirms that SOW 2 contains a present assignment of custom deliverables (so it owns the dispatch code, apart from Ironbridge's preexisting accelerators, which are licensed), obtains the full repository, and gets a remediation quote from another integrator. Ironbridge misses two of three sprint exit criteria. Corvane terminates SOW 2 for cause on day 45, keeps SOW 1 in force for CRM support, and invokes 90 days of transition assistance at contract rates. Ironbridge disputes cause but provides the transition.

Step 7 (damages). Corvane's model: $2.9 million in SOW 2 fees paid; $2.2 million quoted by the new integrator to complete the dispatch module as originally scoped (excluding $600,000 for features Corvane added later); $700,000 in extra internal costs; and $1.8 million in lost margin from manual dispatching during peak season. Against the cap (SOW 2 fees paid, $2.9 million), the contract claim realistically reaches the cap; the lost margin is excluded unless fraud is proven. Ironbridge's model: $2.4 million in unpaid invoices, of which $1.1 million relates to SOW 1 work Corvane does not dispute.

Step 8 (forum). Corvane files an arbitration demand asserting breach of SOW 2 and fraudulent inducement, quoting the proposal sentence, naming its author, and alleging specifically why it was false. Ironbridge counterclaims for fees. Corvane's state court action against the publisher, under the separate subscription agreement, is stayed by agreement.

Steps 9-10 (discovery and experts). Document exchange confirms that Ironbridge had completed one comparable integration, not three, and that the proposal author knew it. Ironbridge's documents also show that its delivery lead warned internally that the architect swap was "a risk we're not telling them about." Corvane's documents show that its operations team repeatedly delayed design approvals. The parties exchange expert reports.

Step 11 (settlement). At mediation, Ironbridge's exposure above the cap on the fraud claim drives the result. The parties settle: Ironbridge writes off its disputed SOW 2 invoices, pays $1.6 million, delivers remaining documentation, confirms Corvane's ownership of the dispatch code with a license to embedded accelerators, and continues SOW 1 support for a year at a discount. Corvane pays the undisputed $1.1 million in SOW 1 invoices. Mutual releases become effective only on delivery of the transition deliverables.

Common mistakes

1. Sending the notice before deciding the objective. An aggressive notice can destroy a workable cure.
2. Defective notice. Wrong address, wrong method, or missing signatory restarts the clock or invalidates the termination.
3. Terminating without the exit secured. Losing access to code, data, and environments costs more than the dispute.
4. Treating the client's account as the record. The documents usually tell a more mixed story.
5. Vendor self-help. Disabling systems or holding data hostage over fees creates new claims.
6. Pleading fraud from the pitch deck. Superlatives are puffery; plead specific statements of present fact.
7. Damages that buy a better system. Separate the original scope from upgrades.
8. Letting a short contractual limitations period run during prolonged negotiations. Get a written tolling agreement.
9. Releasing claims before delivery. Make the release conditional on transition performance.

Frequently asked questions

We are the customer. Should we keep paying while we dispute the work? Pay undisputed amounts unless the contract allows withholding, and dispute the rest in writing following the invoice-dispute procedure. Withholding everything can give the vendor a breach claim and a suspension right.

We are the vendor. Can we stop work if the customer stops paying? Only if the contract gives a suspension right and you follow its notice requirements. Otherwise, stopping work may itself be a breach. Never disable systems or withhold customer data without clear contractual authority.

Do we have to arbitrate a fraud claim if the MSA has an arbitration clause? Usually yes. A claim that the whole contract was fraudulently induced generally goes to the arbitrator unless the challenge is specifically to the arbitration clause or its delegation provision.

Can we sue the salesperson personally? Individuals can be liable for their own fraud, but naming them adds cost and may lead to motions. Do it only when the facts support it and there is a reason beyond pressure.

How long does a failed-implementation case take? Arbitration commonly takes 12 to 24 months; litigation through trial commonly takes 18 to 36 months. Many cases settle within the first year.

Should the consulting expert also testify? Often not. Keeping the consulting expert separate preserves privilege over candid early analysis. Some clients use the same firm with different individuals.

What if the software publisher, not the integrator, is the real problem? Evaluate the license or subscription agreement separately: its warranties, remedies, cap, and forum. Publishers usually have stronger disclaimers and lower caps, but fraud theories about product capability are aimed at them.

Takeaways

• Decide the client's objective first, then choose the process that serves it.
• Read the whole contract stack and calendar every clock before sending any letter.
• Preserve collaboration, ticketing, and code repositories immediately.
• Get a privileged, independent assessment, including of your own client's conduct.
• Follow notice and cure exactly; respond to notices in writing, point by point.
• Secure data, code, IP, and transition assistance before terminating.
• Model damages against the cap; the fraud claim and the direct-damages characterization of re-implementation costs are the only ways above it.
• Plead fraud with documents, not adjectives.
• Use the natural settlement windows, and tie releases to delivery.

This document is general information, not legal advice for any particular situation; the law changes, and the facts matter.

Related Documents

Related Articles

• Failed Software Implementations: Contract, Fraud, and Warranty Claims When an IT Project Goes Wrong: the substantive law behind each step.
• Negotiating a Master Services Agreement and Statement of Work: how the contract terms you are now enforcing were meant to work.
• Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case: preservation duties and sanctions.
• Expert Witnesses After the 2023 Amendment to Rule 702: Daubert, Disclosure, and Cross-Examination: admissibility of project and damages experts.
• Motions to Compel and Discovery Sanctions Under Rule 37: From Meet and Confer to Default Judgment: enforcing discovery of the project record.

Related Guides

• Collecting and Authenticating Messaging and Social Media Evidence: A Practical Guide: collecting Slack and Teams data that will hold up.
• Bringing or Opposing a Motion to Compel Discovery: A Practical Guide: when the other side will not produce its internal reports.
• Building a Damages Case: A Practical Guide from Pleading to Verdict: turning the damages model into proof.
• Planning and Running a Litigation Settlement Negotiation: A Practical Guide: structuring the settlement process.
• Arbitration, Mediation, and Choosing a Dispute-Resolution Forum: A Practical Guide: forum choices and their tradeoffs.
• Taking and Defending an Expert Deposition: A Practical Guide: deposing the other side's project expert.

Related Checklists

• Troubled Technology Project Checklist: A Practical Checklist: the steps in this guide as check-off items.
• Litigation Hold and Evidence Preservation Checklist: A Practical Checklist: hold notices and system preservation.
• Damages Proof and Expert Model Checklist: A Practical Checklist: testing the damages model before the other side does.
• Work Made for Hire Determination Checklist: A Practical Checklist: confirming who owns the custom code.

Related Toolkits

• Technology Project Dispute Toolkit: Notice of Breach Letters, Cure Plans, and Project Record Protocols: the letters, plans, logs, and agreements referenced in this guide.
• Settlement Negotiation Toolkit: Case Valuation Worksheets, Concession Plans, and Offer Letters: valuing the case against the cap.
• Motion to Compel Arbitration Toolkit: Clauses, Declarations, and Appellate Strategy: enforcing or resisting the MSA's arbitration clause.