Choosing the Right ERP Vendor for Your Business
This paper examines the relationship between businesses and enterprise resource planning (ERP) vendors, arguing that companies too often allow vendors to drive ERP selection decisions rather than first defining their own needs. The paper warns that because vendors understand their products but not the inner workings of their clients' businesses, over-reliance on vendor guidance can result in costly, ill-fitted systems. It recommends that companies assess their requirements independently, consult multiple vendors, and select a partner genuinely committed to understanding the business — ultimately leading to more successful ERP implementation and a stronger long-term vendor relationship.
- Introduction: The Problem With Vendor-Driven ERP Selection: Companies often let vendors drive ERP decisions blindly
- Understanding What Your Business Needs Before Choosing a Vendor: Businesses must assess needs before vendor engagement
- The Risks of Vendor Over-Influence: Vendor knowledge gaps can cause costly ERP mismatches
- Working With Multiple Vendors to Make an Informed Decision: Consulting multiple vendors helps avoid poor choices
- Qualities of a Good ERP Vendor Partnership: Best vendors learn the business before recommending systems
- Conclusion: Taking Control of the ERP Decision: Careful planning prevents vendor over-influence in ERP
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- The paper maintains a clear, consistent argument throughout: companies must define their own needs before engaging vendors, rather than delegating that responsibility to the vendor.
- It balances criticism of vendor over-influence with a fair acknowledgment that vendors can offer genuine value, avoiding a one-sided tone.
- Practical recommendations — such as consulting multiple vendors and researching options thoroughly — ground the argument in actionable advice for real business decision-makers.
Key academic technique demonstrated
The paper demonstrates effective use of a consistent thesis supported by recurring evidence from multiple sources. Each paragraph advances the central argument by addressing a different dimension of the problem (vendor knowledge gaps, misaligned incentives, cost consequences), while citations from Burns, Donovan, Krigsman, and Wailgum are woven throughout to reinforce each claim rather than clustered in one place.
Structure breakdown
The paper opens by framing the problem of passive ERP vendor selection, then progressively deepens the argument: first identifying the knowledge gap between vendors and businesses, then examining the incentive misalignment, then offering solutions (multi-vendor consultation, independent needs assessment), and finally characterizing what a good vendor relationship looks like. The conclusion reinforces the central warning and ends with a forward-looking recommendation.
Introduction: The Problem With Vendor-Driven ERP Selection
When it comes to vendors and enterprise resource planning (ERP) systems, many companies simply do whatever the vendor suggests. These companies often choose the first ERP vendor they speak with, or one recommended by another company. That is not always a sound business practice, because there are many ERP vendors available and some will be far better suited to a particular business than others. If a company takes the time to find the right ERP vendor, it can have a much better experience. However, entering the wrong partnership can spell disaster. ERP is such an all-encompassing type of system that it is crucial to a business's success that the right vendor and the right software be selected (Burns, n.d.).
Locating the right company and software for the job is something all businesses must consider, regardless of their size or specific needs (Donovan, 2011). Overall, vendors often exert too much influence over the ERP decisions that organizations make. This occurs because some organizations are uncertain about what kinds of software are available to them and what that software can do. Faced with that uncertainty, they simply rely on the vendor to tell them what they need (Krigsman, 2011). That might seem reasonable, since the vendor knows the product. Unfortunately, the vendor does not truly know the business. While a vendor can learn quite a bit by working closely with company representatives, that still does not provide all of the information the company itself possesses.
References
Burns, M. (n.d.). How to select and implement an ERP. 180 Systems. Retrieved May 10, 2011, from
Donovan, R. M. (2011). Successful ERP implementation the first time. Retrieved May 10, 2011, from
Krigsman, M. (2011). Enterprise software development from an IT failure perspective. Retrieved July 26, 2010, from
Wailgum, T. (2010). 5 easy steps to ERP software success. CIO Magazine. Retrieved July 26, 2010, from
Create your account
Always verify citation format against your institution’s current style guide requirements.