How to Select an ERP System: A Vendor-Agnostic Guide for 2026
Dylan Coetzee · ERP Solution Architect & Founder · 22 min read · May 2026
Selecting an ERP system is one of the most consequential technology decisions a business will ever make. Done well, it aligns your operations, consolidates your data, and creates a platform for a decade of scalable growth. Done poorly, it consumes two to four times the expected budget, fractures team morale, and leaves you locked into a platform that fights your workflows rather than enabling them.
The uncomfortable truth: most ERP failures are selection failures, not implementation failures. The wrong platform, poorly scoped and chosen for the wrong reasons, cannot be rescued by even the best implementation team. You are setting the trajectory the moment you draw up your shortlist.
This guide documents every meaningful stage of a rigorous ERP selection — from understanding your own business requirements to evaluating vendors, running proof-of-concepts, and negotiating contracts. It also shows, at each stage, where ERPLenz removes the friction that makes this process expensive and slow for most organisations.
TL;DR: A proper ERP selection takes 4–9 months and 200–600 hours of internal effort. ERPLenz compresses the diagnostic, scoring, and vendor-matching phases into under 30 minutes — producing a vendor-agnostic shortlist and scored report you can bring straight to a steering committee or implementation partner.
Why ERP Selection Is Harder Than It Looks
The ERP software market is worth over $65 billion annually and growing. There are more than 200 credible ERP vendors globally, ranging from vertically-specialised platforms serving niche industries to horizontal giants like SAP, Oracle, and Microsoft targeting the full market spectrum. Beneath each vendor brand are multiple product lines, deployment models, pricing structures, and partner ecosystems.
For a finance director or operations leader who doesn't live in this space every day, the market is deliberately opaque. Vendor sales teams are incentivised to create urgency, obscure total cost, and match you to their platform regardless of fit. Analyst reports are useful but expensive and often generalised beyond practical utility. Implementation partners have financial incentives tied to specific vendors.
The result: most ERP selection processes are under-resourced, vendor-led, and anchored to the first platform that looked good in a demo.
The five phases of ERP selection — and why each one consumes more time than most organisations budget for.
Phase 1 — Needs Analysis: Know Yourself Before You Evaluate Anyone Else
The single biggest cause of ERP mismatches is selecting a system before the organisation has clearly articulated what it actually needs. Without a documented requirements baseline, every vendor demo becomes a passive experience where the vendor tells you what you need — using their own platform as the answer.
What a Proper Needs Analysis Covers
01 — Current System Audit
Document every system currently in use: accounting software, CRM, inventory management, payroll, custom spreadsheets, and anything in between. Map the data flows between them. Identify where manual re-entry, reconciliation errors, and reporting delays occur. This is your pain map — the ERP must resolve these, not replicate them.
02 — Process Documentation
Walk through your core business processes end-to-end: quote-to-cash, procure-to-pay, hire-to-retire, record-to-report. For each, document the current flow, the people involved, and where the process breaks down. This becomes your scripted demo scenario and your UAT framework.
03 — Business Requirements Document (BRD)
Translate process pain into requirements. Categorise each as Must-Have (deal-breaker if absent), Should-Have (strong preference), or Nice-to-Have. A common mistake is elevating everything to Must-Have — this inflates scope and eliminates capable platforms unnecessarily. Be ruthless in prioritising.
04 — Scale and Growth Planning
Document your current and projected user count, transaction volumes, geographic footprint, and any anticipated M&A activity. An ERP that fits perfectly today but cannot handle 3× growth without a re-implementation is a liability. Design for where you will be in five years, not where you are today.
05 — Technical and Compliance Constraints
Identify hard constraints: data residency requirements, industry certifications (SOC 2, ISO 27001, HIPAA, ITAR), integration mandates (EDI, specific API partners), and IT capacity. Some constraints eliminate entire deployment models — data sovereignty requirements may rule out multi-tenant SaaS entirely.
Realistic effort: A thorough needs analysis takes 40–80 hours of internal effort and 3–6 weeks elapsed time. It typically requires a cross-functional team: Finance, Operations, IT, and at least one executive sponsor. Skipping this phase is the single most expensive shortcut in ERP selection.
Phase 2 — Market Scan: Building Your Longlist
Armed with a clear BRD, the next step is mapping the vendor landscape against your profile. The goal of a market scan is to move from 200+ potential platforms to a manageable longlist of 10–20 candidates worth deeper evaluation.
How to Structure a Market Scan
Effective market scans evaluate vendors across six dimensions:
| Dimension | What You're Evaluating | Why It Matters |
|---|---|---|
| Industry Fit | Native vertical functionality vs. generic configuring | Industry-specific platforms reduce customisation cost significantly |
| Company Size Range | SMB vs. mid-market vs. enterprise positioning | Platforms built for the wrong tier create support & scalability gaps |
| Deployment Model | Cloud SaaS, on-premises, hybrid availability | Affects compliance, IT overhead, and long-term upgrade cost |
| Functional Coverage | Native modules vs. reliance on ISV add-ons | Fragmented software stacks multiply integration and licensing cost |
| Partner Ecosystem | Local implementation partners, quality & depth | Without a strong local partner, even great software fails in practice |
| Vendor Stability | Ownership, R&D investment trajectory, market position | ERP vendor consolidation is ongoing — don't bet on a platform that may disappear |
This research phase is time-intensive. Each vendor's positioning materials are deliberately aspirational. Cross-referencing against independent analyst research (Gartner, Forrester, G2, Capterra), peer reviews, and community forums gives a more accurate picture — but at a significant time cost.
Phase 3 — Demos and Shortlisting
Once you have a longlist, the next phase is compressing it to a shortlist of 3–5 vendors for detailed evaluation. This is where most ERP processes become inefficient: unscripted demos, misaligned audiences, and no structured scoring framework.
Running a Scripted Demo
Never sit through a vendor's standard product demo. Their demo is designed to show the platform at its best — not to answer your specific questions. Instead, provide vendors with a scripted scenario based on your actual business processes and ask them to demonstrate those workflows specifically. Your scripted demo should cover:
- Core Workflow Scenarios — 3–5 end-to-end scenarios drawn directly from your documented processes. Each vendor demonstrates the same scenarios, enabling direct comparison.
- Configuration Questions — Specific requirements that require configuration or customisation. Ask vendors to demonstrate — not describe — how they'd handle your edge cases.
- Integration Points — Your existing tech stack (payroll, CRM, e-commerce, logistics). Ask vendors to demonstrate their connectors or REST API in a live environment.
- Reporting Scenarios — Your three most important management reports built live during the demo. This quickly reveals reporting depth and the level of configuration expertise required.
Scoring Framework
Assign each vendor a weighted score across your requirements categories. Use your BRD's Must-Have / Should-Have / Nice-to-Have classification to set weights. This converts subjective demo impressions into comparable, defensible data — essential when you're presenting a recommendation to a steering committee.
Common mistake: Scheduling demos before your BRD is finalised. Without a requirements baseline, demos become brand experiences rather than capability assessments. Vendors are extraordinarily good at demos. Your only protection is structured evaluation criteria applied consistently across all candidates.
Phase 4 — Total Cost of Ownership Modelling
License pricing is the tip of the iceberg. For a 50-user mid-market deployment, the first-year license cost is rarely the largest cost item. Yet most ERP evaluation processes anchor on headline per-user pricing and miss the full picture by a factor of 3–5×.
The ERP cost iceberg — licence pricing is visible; the majority of true cost sits below the surface.
Building a Realistic 5-Year TCO Model
For each shortlisted vendor, model these cost buckets across a 5-year horizon:
| Cost Bucket | What to Include | Common Mistake |
|---|---|---|
| Licensing | Base platform fee + per-user fees + module add-ons | Ignoring 8–15% annual renewal uplifts compounded over 5 years |
| Implementation | Partner fees, internal staff time, project management | Using the vendor's "starting from" figure; budget at the P75 estimate |
| Customisation | SuiteScript / AL development, workflow automation, reporting | Assuming out-of-the-box configuration covers all edge cases |
| Integrations | iPaaS middleware, API development, EDI connectivity | Treating each integration as a one-time cost; maintenance is ongoing |
| ISV Add-ons | Tax engines, WMS, EDI, HR, BI tools outside the core platform | Not including these until post-contract when gaps emerge |
| Support & Training | Premium support tiers, ongoing training for new hires and module expansions | One-time training budget; ERP requires continuous learning investment |
| Infrastructure | Sandbox environments, storage overages, networking | Assuming infrastructure is included in the SaaS subscription |
Phase 5 — Reference Checks, POC, and Negotiation
Reference Customer Calls
Every shortlisted vendor will provide reference customers. These references are curated — you will not be connected to a dissatisfied customer. To extract useful signal, ask reference customers specific questions: What took longer than expected? What would you do differently? How has the platform performed at renewal? What's the support responsiveness actually like when something breaks at month-end?
Supplement vendor-provided references with your own research: LinkedIn searches for people who have recently left implementations of that platform, ERP community forums (Reddit's r/ERP, ERPFocus), and Gartner Peer Insights with the vendor filter applied.
Proof of Concept
For deployments above $250K in total expected spend, a POC is worth the investment. Take your single most complex or differentiating business process and ask the top two vendors to configure and demonstrate it in a sandboxed environment using your own sample data. A POC reveals configuration effort, customisation requirements, and implementation partner quality in a way no demo can.
Contract Negotiation
ERP contracts are negotiable — far more than most buyers realise. Leverage points include: multi-year commitments in exchange for fixed pricing, uncapped user growth within tiers, sandbox environments at no additional cost, defined SLAs with penalty clauses, and contractual caps on annual renewal uplifts. Never sign the vendor's standard contract without legal and commercial review.
Where ERPLenz Changes the Equation
Every phase described above represents genuine, necessary work. But for most mid-market businesses, the combination of internal resource constraints, vendor bias, and market opacity makes executing it rigorously nearly impossible. The result is compressed, shortcut-laden selection processes that produce vendor matches based on brand recognition rather than structural fit.
ERPLenz was built to close that gap — not by removing the need for due diligence, but by radically compressing the most time-intensive and expertise-dependent stages.
ERPLenz compresses Phases 1–4 into a single 30-minute diagnostic — saving 80–120+ hours of internal research and scoping effort.
How ERPLenz Works
01 — Answer the Diagnostic Questionnaire
A structured set of questions covers your industry, company size, current systems, functional requirements, deployment preferences, compliance needs, and budget envelope. The questions are designed by ERP consultants with decades of implementation experience — the same questions a good consultant would charge $2,000–$5,000 to extract in a scoping workshop.
02 — AI-Powered Matching Against a Scored Vendor Database
Your diagnostic responses are matched against a database of 40+ ERP vendors, each scored across dozens of dimensions: functional depth by module, industry suitability, deployment model, company size range, implementation ecosystem quality, and pricing transparency. The matching logic is weighted by your requirement prioritisation — Must-Haves carry more weight than Nice-to-Haves.
03 — Receive Your Scored Report
Your ERPLenz report delivers a ranked shortlist of 4–6 vendors with fit scores, functional gap analysis, indicative TCO ranges for your size and scope, implementation partner recommendations, and a set of scripted demo questions tailored to your profile. The report is formatted for internal sharing — suitable for presenting to a CFO, steering committee, or board.
What this replaces: A good ERP consultant charges $200–$350 per hour for the scoping and market research phases covered by ERPLenz. At 80 hours minimum, that's $16,000–$28,000 in consulting fees — before a single vendor conversation begins. ERPLenz delivers an equivalent output for a fraction of that cost, in under 30 minutes.
What ERPLenz Does Not Replace
ERPLenz is not a substitute for human judgement at every stage. It is a compression tool for the research and diagnostic stages — the stages where most organisations either spend too much money or cut too many corners.
You still need to run scripted vendor demos — but ERPLenz gives you the right vendors to demo and the questions to ask. You still need to negotiate contracts — but ERPLenz gives you benchmarked cost data to negotiate from. You still need an implementation partner — but ERPLenz narrows the field to partners aligned with your shortlisted platforms.
The goal is not to automate your ERP decision. The goal is to ensure that when you make it, it is based on data rather than salesmanship.
Common Selection Mistakes — and How to Avoid Them
| Mistake | What It Costs | How to Avoid It |
|---|---|---|
| Starting with demos | Platform bias before requirements are clear | Complete your BRD before the first vendor conversation |
| Single vendor evaluation | No competitive leverage; no alternative reference point | Always run at least 3 vendors to final scoring stage |
| IT-led selection | Technical preferences override business requirements | Finance and Operations must co-own the selection process |
| Underestimating internal effort | Selection drags, momentum dies, poor decisions under deadline pressure | Assign a dedicated internal project owner, not a part-time contributor |
| Ignoring the partner, focusing on the platform | Great software, terrible implementation | Evaluate implementation partners as rigorously as the platform itself |
| Assuming cheapest upfront = lowest TCO | Undisclosed ISV, customisation, and support costs erode initial savings | Model full 5-year TCO for every shortlisted vendor before comparing |
| Not involving end users | Low adoption rates post go-live | Include representative end users in demos and UAT design from the start |
A Decision Framework You Can Use Today
If you're at the beginning of an ERP evaluation and need a rapid orientation, answer these seven questions. They won't replace a full selection process, but they will immediately clarify which segment of the market deserves your attention.
Q1 — How many users will access the system? Less than 25 users points toward SMB-tier platforms (Odoo, Sage, Xero + add-ons). 25–200 users falls into mid-market (NetSuite, Business Central, Acumatica, Odoo Enterprise). 200+ users requires upper mid-market to enterprise platforms (SAP S/4HANA, Oracle Cloud ERP, Dynamics 365 F&O).
Q2 — Is manufacturing a core operational function? If yes, shortlist platforms with native MRP, BOM management, and shop floor control (Business Central, Epicor, IFS, Infor). Generic ERP platforms can handle light manufacturing but often require expensive ISV add-ons for serious production environments.
Q3 — Do you operate across multiple legal entities or currencies? Multi-entity and multi-currency requirements immediately elevate the platform tier. NetSuite OneWorld, SAP, and Oracle handle this natively. Platforms without native multi-entity support require complex workarounds that rarely hold up at scale.
Q4 — Are you a Microsoft-centric organisation? If your team operates daily in Office 365, Teams, and SharePoint, Microsoft Dynamics 365 Business Central's native integration dramatically reduces training cost and adoption friction — a genuine competitive advantage that non-Microsoft platforms cannot replicate.
Q5 — Do you have hard data sovereignty or on-premises requirements? Certain industries and geographies mandate on-premises or sovereign cloud deployment. This immediately eliminates true multi-tenant SaaS platforms (including NetSuite). Business Central, SAP, and Infor offer on-premises or private cloud deployment models.
Q6 — What is your realistic 5-year budget? Total ERP cost — including implementation, licensing, support, and customisation — should inform which platforms are viable before demos begin. Enterprise platforms with $1M+ 5-year TCO are not appropriate for a 30-person business with a $200K budget. Calibrate the market segment to your budget reality.
Q7 — What is your internal IT capacity? Platforms requiring active infrastructure management, customisation in specialised languages, or significant ongoing administration need internal IT expertise to match. If you have no internal IT team, prioritise platforms with strong managed services ecosystems and minimal infrastructure overhead.
Next Steps
If you're still uncertain after working through the framework above, consider these moves before signing anything:
- Run a parallel scoping workshop with two implementation partners representing different platforms. Compare not just the proposals, but how well each understands your industry.
- Request reference customer calls with companies of your exact size and industry. Demo videos lie; reference customers usually don't.
- Build your own 5-year TCO model using the framework above, including ISVs, integrations, and realistic implementation contingency.
- Pilot a proof-of-concept on one process (e.g., quote-to-cash) before committing to the full platform.
The right ERP decision saves your business millions over a decade. The wrong one defines your operational pain for the same length of time. Take the time to choose deliberately.
Have questions about your specific scenario? ERPLenz publishes vendor-agnostic ERP analysis and implementation guides. Start your free assessment →