Technology & AI
What Every In-House Counsel Should Know About Negotiating ERP Implementation Contracts: A Litigator's Perspective
Mar 06, 20266 min read
Business is built on the back of technology. As business organizations become more sophisticated in their operations, so too does their information technology systems. To match the growing scope and complexity of business operations, software has been developed to ensure the entire enterprises functions smoothly. Software in this sense may be a bit of a misnomer as these platforms—called enterprise resource planning systems or ERP—function as an organizational backbone, spanning the entirety of the business while handling core functionality and ensuring all operations run smoothly.
As one would expect, the process of designing, customizing, and installing these systems—called an implementation or ERP implementation—can be lengthy, costly, and fraught with danger. If the implementation stalls, or worse, fails, then the business itself may lose the ability to operate in part or altogether. This can pose a near existential threat to the enterprise. What’s worse, there is a statistically better-than-even chance that an ERP implementation will fail in some respect. McKinsey has estimated that three-fourths of ERP implementations “fail to stay on schedule or within budget” and two-thirds have a negative return on investment. RubinBrown, an ERP consultancy, estimates that anywhere between 55%-75% of ERP implementations fail. And Deloitte has estimated that implementations fail at a rate as high as 90%.
These statistics should serve as alarm bells alerting in house counsel to the very real risk of significant litigation involving potential bet-the-company type claims. As such, in house counsel, responsible for protecting their business organizations, must be attuned to the possibility that an ERP implementation will fail—and—situate their organization(s) in the position best able to address those failures.
This article provides insight—gleaned from litigating several of these failed implementations—into the various contractual obstacles that in house counsel may face should they find themselves filing suit to recover the damages caused by a failed implementation. Below are examples of several contractual provisions that the consultants responsible for ERP implementation use to limit the scope of their potential liabilities arising from a failed implementation. The hope here is that in house counsel who are alerted to these types of contractual provisions may be able to negotiate better agreements or, at the very least, situate the enterprise in the best way possible should litigation ultimately be filed.
At their core, ERP platforms govern how a company accesses, integrates, and leverages its data. ERP platforms, such as Microsoft Dynamics 365, are generic, enterprise-wide software platforms. They handle core business functions at the highest of levels, e.g., compliance, sales, salary, human resources, tax, inventory, etc… Because these platforms are so generic in nature, they have to be “implemented” or customized to fit the specific needs of specific business organizations. The implementation is thus another word for organization-specific customization. Implementations are typically performed by consultancies.
Depending on the organization’s size, these implementations can take months if not years. The implementation process itself is a complicated one, usually rolled out in phases. Typically, the consultant responsible for the implementation will assess and analyze the organizations needs and IT infrastructure. They customize the ERP platform for these specific needs. They will roll out the platform, typically at a specific location to start, and begin assessing its performance. Troubleshooting and error correction will then be done over the span of several months. And once the platform is shown to be viable, enterprise-wide rollout is typically the last result.
ERP implementations are often necessitated by structural business changes. For example, mergers and acquisitions may require the buyer to integrate the seller’s data into its own systems. This often involves mapping and migrating legacy data into a shared ERP environment.
Similarly, enterprises relying on outdated platforms—such as COBOL systems or on-premises custom solutions—must upgrade to remain operationally viable. Natural growth and expansion also drive ERP adoption. As new business lines or geographic locations are added, they generate new data silos. An ERP system helps unify these disparate sources into a single integrated platform.
A lack of integration across departments can also be a compelling reason for ERP deployment. As business units expand, the absence of cross-functional visibility can cripple decision-making and impede efficiency. ERP platforms solve this by consolidating and centralizing operations. Finally, regulatory requirements often necessitate ERP adoption.
Publicly traded or heavily regulated entities must ensure accurate and auditable reporting. ERP platforms support these requirements through standardized financial and operational modules, making compliance more manageable and reliable.
Sometimes, these issues are relatively minor—a hiccup in the overall process that can be fixed. Other times, however, the failures can be catastrophic, impeding the ability of the business to function for long periods of time. Recent lawsuits show the magnitude of the consequences from a failed ERP implementation: Sunshine Mills v. Ross Systems resulted in a $61.4 million jury verdict. Hawaii Department of Transportation v. Ciber concluded with a $31.8 million recovery. Copart v. Sparta yielded a $20 million jury award.
The contractual process governing an ERP implementation is fairly standard. Common across all implementations are Master Services Agreement (MSA) paired with multiple Statements of Work (SOWs), phasing the project over time on a scope-by-scope basis.
Of critical importance to in house counsel negotiating these contracts, MSAs often contain boilerplate provisions that severely limit the enterprise’s ability to obtain a recovery that fully compensates the organization should it find itself in litigation over the ERP platform.
For in-house counsel, two things are critical: (1) understanding the provisions that may later impair recovery and (2) negotiating MSAs and SOWs to best situate the organization should it find itself in litigation. The contractual provisions described below are key roadblocks that may impair business enterprises from recovering all their damages in a lawsuit and in house counsel must pay particular attention to them.
ERP implementation contracts are often stacked against the customer unless vigilantly negotiated.
Waivers of consequential damages are one of the most significant risks. These provisions can eliminate claims for lost profits and other indirect damages. In the context of ERP failure, this could mean no recovery for business disruption, reputational harm, or even third-party claims arising from the platform’s malfunction. These are potentially high-dollar claims as enterprises can lose significant amounts of revenue should they be unable to operate for a given length of time. Moreover, the trickle-down affect of being unable to meet contractual obligations to third-parties—and the liabilities that this inability might create—could result in extremely significant claims being filed against the business. All of this would take place without any recourse against the consultancy responsible for the failed implementation.
Reliance disclaimers are another critical area. These clauses typically assert that the customer is not relying on any pre-contractual representations. The practical effect is that they may bar fraud claims, especially those seeking rescission. Whether such provisions are enforceable often depends on the jurisdiction, making it essential for counsel to analyze the precise language and applicable legal standards. This is a particularly important consideration as the laws of a jurisdiction like Texas significantly differ from other states when it comes to the language required for an enforceable waiver. The significance of entire agreement and merger clauses is an important related concern here as well. The key for these types of contractual provisions is a deep understanding of what the applicable law requires for a disclaimer to be enforceable.
Warranty provisions also require close scrutiny. Representations regarding the platform’s performance may provide a foundation for asserting breach claims. However, if the agreement contains broad disclaimers of implied warranties, statutory protections may be lost. Compounding the risk, limitations on liability clauses often cap recoverable damages to the fees paid under a specific Statement of Work. This can render litigation economically unviable, even when the failure is catastrophic.
Attorney’s fees provisions can heavily influence the decision to litigate. Some MSAs preclude fee recovery altogether, while others permit only the prevailing party to recover. In either case, the enterprise must consider whether the financial burden of litigation is justified in light of these constraints.
Forum selection and choice of law provisions can also introduce complications. Many MSAs designate the law and venue of the consultant’s home jurisdiction, which may be less favorable to the enterprise. The intricacies of an unfamiliar legal system can materially affect the outcome and viability of any legal action.
ERP implementations are high-risk, high-reward projects. For in-house counsel, protecting the enterprise starts with scrutinizing and negotiating the MSA. Business teams may view these contracts as routine IT matters, but history shows that a poorly implemented ERP can become a bet-the-company problem.
These are the key takeaways for in house counsel: Always review boilerplate provisions, particularly those limiting liability and disclaiming reliance. Push for reasonable warranties, fee recovery, and venue clauses. Stay close to the implementation process. If red flags appear, act quickly—termination and mitigation are sometimes the most prudent legal strategies.
By engaging early and proactively, in-house counsel can position the enterprise not only to succeed in its ERP rollout but to withstand the consequences if it doesn’t.