Top 10 ERP Selection Mistakes
Definition
ERP selection mistakes are systematic errors made during the vendor evaluation and selection phase of an ERP project that increase the probability of implementation failure, cost overruns, or functional misfit. These mistakes occur before a single line of configuration is written, yet they account for an outsized share of downstream project failures. With 79% of ERP projects experiencing challenges or outright failure — often costing $1.5M+ and dragging on for years — selection-phase errors are the most cost-effective point of intervention. [src4] The 10 mistakes cataloged here are drawn from consulting firm pattern analysis across hundreds of enterprise ERP selections. [src1]
Key Properties
- Failure rate context: Only 23% of ERP implementations are considered successful; many failures trace back to selection-phase decisions [src4]
- Cost amplification: A selection mistake costing $50K to fix during evaluation costs $500K during implementation and $5M+ post-go-live
- Compounding effect: Selection mistakes rarely occur in isolation — skipping requirements leads to demo-driven decisions, which leads to customization spirals [src1]
- Industry invariance: The same 10 mistakes appear across all industries [src4]
- Recoverable window: Most selection mistakes are recoverable if caught before contract signing [src2]
Constraints
- These mistakes apply primarily to mid-market and enterprise ERP selections ($500K+ projects) [src4]
- Mistake severity varies by industry — regulated industries face amplified consequences
- Ordered by frequency, not financial impact, which varies by organization
- Some mistakes compound: skipping requirements leads to demo-driven selection, then customization spiral [src1]
- Full checklist requires 3-6 months of selection effort [src2]
Framework Selection Decision Tree
START — User needs help with ERP selection
├── Where are they in the process?
│ ├── Haven't started → Read all 10 mistakes as prevention checklist
│ ├── Mid-selection → Diagnose which mistakes they're currently making
│ ├── Post-selection, pre-implementation → Audit for reversible errors
│ └── Post-failure → Map failure to selection-phase root causes
├── What's the project scale?
│ ├── Enterprise ($1M+) → All 10 mistakes are high-risk
│ ├── Mid-market ($200K-$1M) → Focus on #1-5 and #7
│ └── SMB (under $200K) → Focus on #1, #3, #7, #9
├── Is there a selection team in place?
│ ├── YES with executive sponsor → Review for mistakes #2, #5, #6
│ ├── YES but IT-led only → High risk for mistake #4
│ └── NO formal team → Start with mistake #1
└── Has the RFP already been sent?
├── YES → Focus on #5, #6, #8 (evaluation-phase errors)
└── NO → Focus on #1-4 (pre-RFP errors)Application Checklist
Step 1: Validate requirements exist before vendor contact
- Inputs needed: Business process documentation, pain points, compliance requirements
- Output: Prioritized requirements with must-have, should-have, nice-to-have tiers
- Constraint: If the organization cannot articulate 20+ specific requirements before contacting vendors, they are not ready [src1]
Step 2: Assemble a cross-functional selection team
- Inputs needed: Stakeholder map spanning finance, operations, IT, and end users
- Output: Named selection team with executive sponsor and allocated time
- Constraint: If the team is entirely IT-driven with no business process owners, Mistake #4 is guaranteed [src4]
Step 3: Evaluate vendors against requirements, not demos
- Inputs needed: Requirements document, vendor responses, scripted demo scenarios
- Output: Weighted scoring matrix evaluated by cross-functional team
- Constraint: If demo scenarios are vendor-designed, the evaluation tests presentation skill, not fit [src1]
Step 4: Model total cost of ownership over 5-7 years
- Inputs needed: Licensing, implementation, customization, integration, training, support, exit costs
- Output: Full lifecycle TCO comparison across shortlisted vendors
- Constraint: If TCO excludes post-go-live costs, it understates true cost by 40-60% [src2]
Anti-Patterns
Wrong: Letting the vendor control the demo script
The vendor showcases pre-built scenarios that highlight strengths and avoid weaknesses. The team is impressed by polished presentations that bear no resemblance to their actual processes. [src1]
Correct: Providing vendors with your business scenarios
Write demo scripts based on your most complex, frequent, and compliance-critical processes. Require all vendors to demonstrate against the same scenarios. [src1]
Wrong: Selecting based on brand reputation alone
An organization selects SAP because "nobody gets fired for buying SAP," without validating fit for their specific size, industry, and process complexity. Extensive customization follows. [src5]
Correct: Selecting based on fit for your specific context
Evaluate vendors against documented requirements, reference customers in your industry and size bracket, and total cost of ownership. Brand is a tiebreaker, not a decision criterion. [src4]
Wrong: Excluding finance from selection and discovering TCO at contract signing
The IT team selects the best technical fit, but the 5-year TCO is 3x budget because implementation and ongoing costs were not modeled. [src2]
Correct: Involving finance in TCO modeling from day one
Include finance on the selection team. Model full lifecycle costs before shortlisting. Eliminate vendors exceeding budget before investing in deep evaluation. [src2]
Common Misconceptions
Misconception: The RFP process ensures a fair and thorough evaluation.
Reality: Most ERP RFPs are checkbox exercises vendors have pre-built responses for. RFPs measure proposal-writing ability, not software fit. Scripted demos and reference calls are far more revealing. [src1]
Misconception: The most expensive ERP is the best ERP.
Reality: Price correlates with vendor size and market positioning, not fit. A $200K NetSuite deployment may outperform a $2M SAP deployment for a 200-person services firm. [src4]
Misconception: ERP selection is primarily a technology decision.
Reality: ERP selection is primarily a business process decision. Organizations that treat it as an IT project make mistakes #4, #5, and #8 simultaneously. [src1]
The 10 Mistakes
| # | Mistake | Consequence | Prevention |
|---|---|---|---|
| 1 | No documented requirements before vendor contact | Vendor-led evaluation; buying what's sold | Complete requirements first |
| 2 | No executive sponsor or passive sponsorship | No authority to resolve conflicts | Name active exec sponsor |
| 3 | Demo-driven selection | Evaluating presentation skill, not fit | Customer-designed demo scenarios |
| 4 | IT-only selection team | Technical fit without business fit | Cross-functional team |
| 5 | Evaluating features instead of process fit | Checkbox exercise misses workflows | Map end-to-end processes |
| 6 | Ignoring change management in selection | Massive behavioral change not budgeted | Assess change impact per vendor |
| 7 | Ignoring total cost of ownership | 40-60% cost underestimation | Full 5-7 year TCO model |
| 8 | Not checking references in your industry/size | Misleading vendor references | Demand matching references |
| 9 | Rushing selection to arbitrary deadline | Insufficient due diligence | Allow 3-6 months |
| 10 | Failing to negotiate exit terms | Vendor lock-in, no exit path | Negotiate data portability |
Comparison with Similar Concepts
| Concept | Key Difference | When to Use |
|---|---|---|
| Top 10 ERP Selection Mistakes | Errors during vendor evaluation and selection phase | Before or during ERP vendor evaluation |
| ERP Implementation Failure Patterns | Root causes of failures during deployment | After vendor is selected, during implementation |
| ERP Vendor Lock-In Assessment | Switching cost and portability of current system | When evaluating exit from existing vendor |
When This Matters
Fetch this when a user is starting or mid-way through an ERP selection process, asks about common ERP mistakes to avoid, is diagnosing why their ERP project went wrong and suspects selection-phase errors, or needs a prevention checklist for enterprise software evaluation.