All Categories

If It Isn't in the ERP Contract, Don't Count on It: Protecting Your Company Before an ERP Implementation

9/9/2026

Somewhere in a conference room right now, an enterprise software salesperson is saying, “Yes, the system does that.”
But, nobody is writing it down.
Eighteen months later, that sentence could be at the center of a seven-figure ERP implementation dispute. Failed ERP implementations are not always caused by technology alone. Many begin much earlier, during the sales and contracting process, when expectations about functionality, integrations, implementation timelines, data migration, staffing, or customization are discussed but never adequately documented in the ERP contract or Statement of Work (SOW).
By the time the project is delayed, over budget, or unable to deliver promised functionality, the customer may discover that the sales presentation and the written contract tell very different stories.
For companies considering Oracle, NetSuite, SAP, Microsoft Dynamics, Workday, Epicor, Sage, or another enterprise software platform, the lesson is simple: document what you are buying before you sign.
Understand Who Is Across the Table During the ERP Sales ProcessDuring the enterprise software sales cycle, the vendor is trying to close a transaction. The long-term business relationship may develop after implementation begins, but sales personnel are generally incentivized to move the deal toward signature.
That does not mean every representation is misleading. It does mean companies should independently verify important claims and document the representations that influence the purchasing decision.
If your decision to purchase an ERP system depends on a particular capability, integration, implementation timeline, staffing commitment, or business outcome, do not rely solely on a sales presentation or verbal assurance.
Get the commitment in writing and, whenever possible, incorporate it into the governing ERP agreements.
Put Critical ERP Requirements Into the Statement of WorkThe ERP Statement of Work is one of the most important documents in an enterprise software implementation.
Before signing, make sure the SOW and other governing agreements clearly address the requirements that matter to your organization.
Functional RequirementsAvoid vague language such as “supports multi-entity consolidation.”
Identify the actual business processes the ERP system must perform, particularly those demonstrated during the sales process. Where possible, test those processes using your company's own workflows and data.
ERP IntegrationsIdentify each system that must integrate with the new ERP platform.
The agreement should address:

The systems being integrated
The direction of data flow
The frequency of data transfers
Which party is responsible for building each integration
Testing requirements
Responsibility for correcting integration failures

Data MigrationDefine what data will be migrated and what constitutes a successful migration.
The SOW should address:

Types of records being migrated
Years of historical data
Data cleansing responsibilities
Validation and testing
Reconciliation requirements
Acceptance standards

Do not leave “data migration” as a broad deliverable without defining what successful migration actually means.
ERP Acceptance CriteriaAcceptance criteria should be objective and measurable.
The contract should identify the tests or milestones that determine whether the ERP implementation has been successfully delivered and what happens when those criteria are not satisfied.
Companies should also carefully negotiate when implementation payments become due and whether payments are tied to successful completion of defined milestones or acceptance criteria.
Change Orders and Scope ChangesERP implementation disputes frequently involve disagreements about whether required functionality was included in the original scope or constitutes additional work.
The contract should establish:

How scope changes are identified
Who can authorize a change
How change orders are priced
Whether additional time is permitted
What happens when the customer and vendor disagree about whether something is actually out of scope

A poorly defined change-order process can turn an initially manageable ERP implementation budget into a dramatically more expensive project.
Key Implementation PersonnelThe people assigned to an ERP implementation matter.
If the vendor or implementation partner sells the project based on the experience of particular consultants, consider identifying key personnel in the SOW and requiring notice or consent before those individuals are replaced.
Location of ERP Implementation PersonnelDetermine whether critical implementation work will be performed by U.S.-based personnel, offshore resources, or a combination of both.
If staffing location, time-zone availability, industry expertise, security requirements, or communication expectations matter to your organization, document those requirements before signing.
If an ERP vendor or implementation partner makes an important promise during the sales process but resists documenting it in the agreement, that resistance itself deserves scrutiny.
Vet the ERP Implementation Partner SeparatelyMany enterprise software projects involve more than one company.
The software publisher may sell the ERP licenses or cloud subscription while a third-party ERP implementation partner or systems integrator performs much of the actual implementation.
Those companies may have separate contracts, separate responsibilities, separate insurance coverage, and separate defenses if the ERP implementation fails.
Before signing, determine:

Who actually employs the consultants performing the work
Which company is responsible for implementation defects
Who bears responsibility for project delays and cost overruns
Whether the software vendor contractually stands behind the implementation partner
Whether the partner is merely “certified” or whether the vendor accepts responsibility for its work
How much experience the implementation partner has in your industry
How many comparable ERP implementations the vendor and integrator have successfully completed together
Whether you can speak directly with customers who completed similar implementations

Do not rely exclusively on references selected by the vendor or systems integrator. When possible, independently verify the implementation partner's experience with companies of similar size, complexity, and industry.
Claims of “industry experience” should also be examined carefully. Ask which consultants have that experience, what projects they completed, and whether those same people will actually work on your implementation.
Avoid the Accountability Gap Between ERP Vendors and Systems IntegratorsOne of the most dangerous structures in an ERP implementation is having multiple vendors, multiple agreements, and unclear responsibility for the final result.
When something goes wrong, the software publisher may blame the systems integrator. The integrator may blame the software. Both may blame the customer.
Companies should address that accountability gap before the project begins.
Where commercially possible, a contractual structure with clear prime-contractor responsibility and accountability for subcontractors may reduce the risk of ending up between two vendors, each claiming the other is responsible for the failed ERP implementation.
Preserve the ERP Sales and Implementation Paper TrailThe contract is critical, but companies should preserve the broader record as well.
Keep sales presentations, demonstrations, proposals, emails, meeting notes, implementation plans, requirements documents, and other communications related to the ERP purchase.
After important meetings, confirm material verbal representations in writing. Maintain a requirements log and trace important requirements through the SOW, implementation, testing, and acceptance process.
This documentation may feel burdensome while the project is going well.
If the ERP implementation fails, it can become some of the most important evidence your company has.
Before You Sign an ERP Contract, Know What You Are Actually BuyingThe best time to address an ERP implementation dispute is before there is one.
Companies investing millions of dollars in enterprise software should approach the contracting process with the same discipline they expect during implementation. Define the functionality. Identify integrations. Establish acceptance criteria. Document staffing expectations. Clarify responsibility between the software vendor and implementation partner. Preserve important sales representations.
And most importantly, do not assume that a promise made during an ERP sales presentation will protect your company later.
If the promise matters to the deal, document it before you sign.
Tactical Law Group LLP represents companies in failed ERP implementation disputes, enterprise software disputes, software licensing matters, and claims involving ERP vendors and implementation partners. The firm also advises companies on ERP and enterprise software agreements before implementation begins.
Companies facing an ERP implementation problem—or preparing to enter into a significant ERP agreement—can contact Tactical Law Group to discuss contract strategy, risk, and potential disputes.

0 Comments

August 24th, 2026

8/24/2026

0 Comments

A Tactical Take on the gap between what’s promised and what’s signed

If your company is evaluating a new ERP system, the sales process can feel like the most attentive, professional courtship you’ve ever experienced. That’s by design. Understanding how the cycle actually works — and where the traps are — can save you from signing a contract that bears little resemblance to what you were sold.

The Charm Offensive
It usually starts with an impressive show of force. The vendor trots out a small army from their side to “learn your business.” There are discovery calls, scoping sessions, and workshops — a steady rhythm of Zoom, Teams, and in-person meetings, each one devoted to understanding how your operation runs. It looks like a serious commitment of resources, and it feels flattering.
Woven through all of it is the language of collaboration. The sales team talks about wanting to partner with you, to be a long-term ally rather than just a vendor. It’s warm, it’s reassuring, and it’s meant to lower your guard.

Here’s what to keep in mind: the people in those rooms are often genuinely eager but not always genuinely informed. An enthusiastic salesperson may know very little about the technical realities of the product, yet will confidently represent that the software can do everything your company needs. Enthusiasm is not the same as a commitment, and a friendly assurance is not the same as a specification.

Everything is Oral — and That’s the Point
Notice how much of the scoping conversation happens out loud and how little of it lands in writing. Promises about capabilities, custom workflows, integrations, and outcomes tend to be made verbally, across dozens of meetings, with very little committed to paper. That is not an accident. The fewer written representations there are, the smaller the paper trail — and the less the vendor can be held to later.

The Pricing “Test” and the Expiring Discount
Once you’re hooked, the pricing arrives. Treat the first number as what it is: a test of how much they can get. When you hesitate, the discounts appear — often steep ones — accompanied by urgency. You’ll be told the discount is expiring, that you need to sign now, and maybe that this is the best pricing the rep has ever seen.

It usually isn’t. Manufactured urgency and “best I’ve ever seen” framing are standard closing tools, not reflections of a genuinely rare opportunity. A real deal is still a real deal next week.

The Paperwork Switcheroo
Once you agree to move forward, the paperwork comes over — frequently through DocuSign, ready for a quick signature. This is the moment to slow down, because this is where the gap opens up.
The specifics you spent weeks scoping are often nowhere in the agreement. Instead of the tailored solution you discussed, you get a very general scope of work that promises little more than the vendor’s generic, off-the-shelf product. That’s because once you are in implementation and you ask why the software does not have the required functionality you discussed, the ERP vendor pulls out the contract and says it was never included.

Then there’s the order form — often a mystery. It lists multiple modules that, the publisher assures you, will combine to deliver your solution. What’s frequently missing are the key pieces that actually make it work: connectors, integrations, and other essential components. They’re sometimes left out precisely because the sales team fears that including them — and their cost — will tank the deal. After signing, these reappear as change orders or as required add-on items, at an additional expense.
The clause that erases every promise
Buried in the contract is an integration clause (also called a “merger” or “entire agreement” clause). In plain terms, it states that the signed written contract is the complete and final agreement between the parties, and that it supersedes every prior discussion, representation, and promise made during the sales process.

Read that again in light of everything above. All those oral assurances about what the software could do? Legally, they’re gone. If it isn’t in the written contract, you generally can’t rely on it. The integration clause is the mechanism that turns weeks of verbal promises into thin air the moment you sign.

The Disappearing Act
Then the deal closes, and the dynamic changes overnight. The attentive sales team is gone with the wind. In their place arrives the implementation team — and this is often the moment the customer starts learning that what was promised during the sales cycle cannot actually be done, at least not without more time, more modules and add-ons, and more money.

What to Watch For Get it in writing. If a capability matters to you, insist it appear in the scope of work — specifically, not generically. Scrutinize the order form. Ask directly what is not included, and require connectors and integrations to be named and priced up front. Ignore the countdown. Treat expiring discounts and “best ever” pricing as negotiation tactics, not facts. Understand the integration clause before you sign. Know that it can wipe out every oral promise made to you. Involve the right people early. Bring in procurement and legal counsel before the DocuSign link arrives — not after.
The sales cycle is engineered to feel like a partnership. The contract is what actually governs the relationship. Make sure the two agree before you sign.

0 Comments

Episode 2: What Most People Miss

7/6/2026

0 Comments

Tactical Takes: Three Things to Watch in a Software License
To go along with our latest Tactical Takes video, here are a few quick thoughts on reviewing software licensing agreements.

Software licenses tend to get signed in a hurry. The deal is agreed, the procurement team wants the tool live, and the contract feels like a formality. It isn't. A license is the document that decides what happens when something goes wrong, and a few clauses do most of the heavy lifting.

Don't Be Penny Wise and Pound Foolish

The most common mistake is skipping legal review to save a few hours of fees. Hire a lawyer. The cost of having counsel read the agreement before you sign is small next to the cost of discovering a one-sided term after a dispute has already started. Trying to save money up front by going without review is the textbook example of being penny wise and pound foolish—the savings are tiny and the exposure is not.

Read the Dispute Resolution and Choice of Law Clauses

Two clauses quietly decide how painful any future fight will be.

The dispute resolution clause tells you how and where a disagreement gets resolved—court or arbitration, and in which location. That can mean the difference between a manageable process close to home and traveling across the country (or to another country) to be heard.

The choice of law clause tells you whose law applies to interpret the agreement. The same contract language can produce very different outcomes depending on which jurisdiction's rules govern it.
Neither clause feels important when everything is going well, which is exactly why they get ignored. Read them before you sign, because you don't get to renegotiate them once a problem appears.

Always Check the Limitation of Liability

Finally, look hard at the limitation of liability. This is where the vendor caps what it can be held responsible for—often limiting damages to the fees you paid and excluding the consequential losses (lost revenue, downtime, data issues) that usually hurt the most. If the software fails and the cap is low, that clause defines the most you can recover. Make sure the ceiling matches the real risk to your business.

None of this is complicated, but it's easy to skip. Spend a little time on these three areas—and a little money on good counsel—and you'll avoid the surprises that show up far too late.

This article is general information, not legal advice. For guidance on a specific agreement, talk to a qualified attorney.

0 Comments

Episode 1: Introducing Tactical Talks + Tactical Takes

6/1/2026

0 Comments

At Tactical Law Group, we believe businesses make stronger decisions when they have access to clear and practical information. That’s why we’re excited to launch Tactical Talks: a new video series created to provide quick, approachable insights on contracts, licensing disputes, software audits, business risk, and other legal issues that organizations of all sizes may encounter.

Leading the conversation is Pam Fulmer, Founder and Managing Partner of Tactical Law Group LLP. Pam has been practicing law since 1991 and founded Tactical Law Group with a mission to help support businesses navigating increasingly complex legal and contractual landscapes. Over the years, she has worked with organizations of all sizes and understands how overwhelming contracts, software and other vendor agreements, audits, and legal terminology can feel for business leaders who are simply trying to make informed decisions and protect their organizations.

Through Tactical Talks, Pam is sharing some of that knowledge in a way that is practical, accessible, and easy to understand. Each Tactical Talks episode will be short (around five minutes ) and focused on providing quick takeaways companies can apply immediately. Topics will include things to watch for before signing contracts, common agreement pitfalls, software audit concerns, risk management considerations, areas where we often see disputes arise, and other real world business issues. To complement each episode, we will also release a companion blog series called Tactical Takes.

While Tactical Talks delivers the quick overview, Tactical Takes will go deeper into the details and explore the finer points, additional considerations, examples, and “nitty gritty” behind each topic. Our goal is simple: Help in-house counsel and business leaders to feel more informed, prepared, and confident when navigating important decisions for their companies. Whether you are in-house counsel, a small or medium size business owner or multinational corporation, executive leader, IT professional, procurement specialist, or simply someone trying to better understand the agreements your organization is signing, we hope this series becomes a valuable resource for you and your team. We’re excited to have you along for the conversation.

Disclaimer: Tactical Talks and Tactical Takes are provided for informational purposes only and should not be considered legal advice. Viewing this content does not create an attorney-client relationship. For legal guidance specific to your situation, please contact Tactical Law Group directly.

Hosted by Marketing Director Maddy Szymanski and Tactical Law Group Managing Partner, Pam Fulmer, Tactical Talks delivers quick, practical insights designed to help in-house counsel and business owners navigate legal and business considerations with greater confidence

0 Comments

Tactical Talks

If It Isn't in the ERP Contract, Don't Count on It: Protecting Your Company Before an ERP Implementation

August 24th, 2026

Episode 2: What Most People Miss

Episode 1: Introducing Tactical Talks + Tactical Takes

Author

Archives

Categories

tactical law group llp