How to Choose an ERP System: A Strategic Framework for Enterprise Architecture and Cost Valuation
Table of content
How to choose an ERP system comes down to two questions: which platform fits the processes that make your company money, and what it will cost to run for the next five to seven years. Enterprise Resource Planning (ERP) is one of the costliest purchases a company makes. This guide covers selection criteria, a 100-day selection plan, license prices published as of October 2026, implementation costs, and when custom development pays off.
The Architectural Crossroads: Modernizing Enterprise Infrastructure
Past a certain size, disconnected applications start to hold growth back. The warning signs are concrete: the inventory system does not post to the general ledger, an order is re-typed into three systems before it ships, and month-end close takes two weeks because finance reconciles spreadsheets by hand. Sometimes the trigger is the vendor: SAP’s mainstream maintenance for its older ECC system ends in 2027, and optional extended maintenance ends in 2030, so many SAP customers are choosing their next platform now.
Choosing an Enterprise Resource Planning platform changes how the company works, so treat it as a redesign of your workflows rather than a software purchase. An ERP puts finance, supply chain, manufacturing, HR and sales on one shared database, which is why a wrong choice costs more than wasted licenses: it can disrupt shipments, frustrate customers and create audit findings. If you need a refresher on the modules and the architecture, start with what an ERP system is and how it works.
The market splits into clear tiers. Large enterprises mostly shortlist SAP S/4HANA, Oracle Fusion Cloud ERP or Microsoft Dynamics 365 Finance and Supply Chain Management. Mid-sized companies tend to compare Oracle NetSuite, Dynamics 365 Business Central and Acumatica, while Odoo and ERPNext serve smaller firms and teams that want open source. Look for the system that removes your specific bottlenecks, and stop searching for “the best ERP”.
Systemic Methodology: How to Choose an ERP System Without Operational Disruption
A selection succeeds or fails on preparation. Companies that invite vendor demos before writing down their own requirements tend to buy the slickest interface instead of the best fit for their transactions.
A structured evaluation avoids that trap:
- Establish a Cross-Functional Steering Committee: IT and finance are not enough. Bring in procurement, manufacturing, logistics and sales, each with a named owner who can sign off requirements. A finance-only team tends to buy excellent reporting and weak shop-floor or warehouse workflows.
- Map “To-Be” Processes, Not Legacy Limitations: Document how work flows today, then design the future process you want. Mark the workflows that differentiate you, such as a configure-to-order quote or a custom pricing model, because the new ERP has to support those well. Standard processes such as accounts payable approval can adopt the vendor’s best practice.
- Construct an Objective, Weighted Request for Proposal (RFP): Turn the future processes into specific requirements, give each a weight, and score every vendor against the same matrix. The scores give the board a written justification for the decision.
ERP System Selection Criteria
Functional fit matters most, but it is only one line of the matrix. These are the ERP system selection criteria we would weight in almost every evaluation:
- Fit for differentiating processes: how much of your critical workflow runs on standard configuration, and how much needs extensions.
- Integration: documented REST APIs, prebuilt connectors for your e-commerce, CRM, tax and shipping tools, and the API limits that apply at your transaction volume.
- Hosting, security and compliance: where your data is stored, which audit reports the vendor provides (SOC 1 and SOC 2 are typical), and how the system supports your industry rules.
- Upgrade model and vendor health: cloud ERPs ship mandatory updates on the vendor’s schedule (Business Central has two major releases a year), so ask how extensions survive them, and check the depth of the partner network in your regions.
Regulated buyers add their own criteria. For a large government contractor in the US, the accounting core has to be DCAA-compliant: timekeeping, job costing by contract, indirect rate calculation and the incurred cost proposal that FAR 52.216-7 requires within six months of fiscal year-end. Defense contractors that handle controlled unclassified information also need hosting that fits their CMMC scope. Specialist products such as Deltek Costpoint and Unanet are built for this, while general suites usually need add-ons or partner extensions to match them.
A 100-Day ERP Selection Plan
The steps in purchasing an ERP fit into roughly 100 days if the steering committee meets weekly and has the authority to decide:
- Days 1–20: form the committee, write the problem statement, map current and future processes, and agree on the budget range.
- Days 21–45: write the weighted RFP, send it to a long list of six to eight vendors, and narrow it to three or four.
- Days 46–75: run scripted demos on your own data, call reference customers of similar size and industry, and test the APIs your integrations depend on.
- Days 76–100: build the five-to-seven-year cost model, choose the implementation partner, and negotiate the contract, including renewal price caps, data export rights and service levels.
During the demo phase, do not let vendors show a pre-packaged sandbox. Ask them to run a complex, end-to-end flow with your data, such as turning an irregular customer quote into a production work order, tracking raw material consumption and posting the ledger entries. You will see how many workarounds the presenter needs.
Demystifying the Invoice: How Much Does an ERP System Cost in Reality?
Software licenses are only part of the bill, which is why ERP budgets are hard to get right. Panorama Consulting’s 2026 ERP Report found that more than a quarter of organizations exceeded their project budgets, mostly because they needed technology they had not planned for. To avoid that, calculate the Total Cost of Ownership (TCO) over five to seven years. ERP architecture and operating costs are linked: a heavily customized system or a large on-premise footprint keeps costing money long after go-live.
So, how much does an ERP system cost in practice?
Every quote depends on users, modules, data volume and scope. As a planning assumption to test against real quotes, mid-sized companies should expect total first-year project costs from about $150,000 to well over $1,000,000, and global implementations can pass $10,000,000. The cost breaks down into three buckets:
Software Licensing and Hosting Models
Cloud ERP is sold as a subscription, usually per user per month. Microsoft publishes its US list prices: as of October 2026, Business Central costs $80 per user per month for Essentials and $110 for Premium, and Dynamics 365 Finance costs $210, or $300 for Premium, all billed yearly. Oracle NetSuite and SAP quote each deal individually, and platform fees, light-user licenses and add-on modules change the total a lot. A subscription keeps the upfront cost low, but over a long horizon the fees can add up to more than a perpetual license, so model both.
Perpetual licenses mean a large upfront payment plus annual support, which usually runs at 18% to 22% of the net license fee, plus the cost of hosting the system in your own data center.
Implementation and Consulting Services
For services, many budgets use an implementation multiplier. Treat it as an assumption to check against partner estimates rather than an industry statistic: plan $1.50 to $3.00 of implementation services for every dollar of licenses. If the licenses cost $200,000, set aside $300,000 to $600,000 for services. That money pays for data migration, integrations, configuration and testing. Ask each partner to price these items separately, because a single fixed figure hides the assumptions.
Change Management, Training, and Post-Go-Live Support
People are the most common point of failure. Budget for training and change management explicitly, including time for the key users who test the system and train their colleagues, and for backfilling their daily work. If staff do not understand the system, data quality drops and reports lose credibility. Plan a support budget for the first year after go-live as well, when workflows are adjusted to real usage.
Technical Evaluation: Custom Development vs. Out-of-the-Box Configuration
A major decision is how much to customize the ERP to fit your business, and how much to change your processes to fit the software.
Modern ERPs offer extensive configuration. Administrators can change page layouts, add fields, adjust approval workflows and build reports without touching code. Configuration sits on the standard application layer, so vendor updates rarely break it.
Customization means writing code that changes how the system processes data. It pays off when it protects a real competitive advantage, but it costs money to build and test, and modifications to the core can block future upgrades. Vendors now push extensions outside the core: Business Central customizations are built as AL extensions, and SAP calls its approach “clean core”, with custom logic moved to side-by-side apps on SAP BTP. When no package fits a core process, custom software development connected to the ERP through its APIs can be the cleaner option, and our build vs buy decision framework helps with that call.
Our default is “out-of-the-box first”. If a process does not set you apart from competitors, adopt the ERP’s standard workflow, and spend the custom development budget on the proprietary capabilities that do.
Partnering for Long-Term Success: Strategic ERP Engineering with Diatom
Even a strong ERP will not pay back if it is poorly connected to your other systems, loaded with bad data or rejected by its users.
Diatom Enterprises handles the engineering around the ERP in three areas:
- Legacy Data Migration: moving years of operational and financial history into a new data model. We build automated ETL (extract, transform, load) pipelines that clean and validate historical records before import, so the opening balances and reports reconcile.
- Custom API & Middleware Integration: secure data pipelines between a cloud ERP and on-premise manufacturing systems, shipping portals or custom e-commerce platforms, with monitoring and retry logic so failed messages are caught.
- Tailored ERP Modules & Customization: when standard templates fall short, our architects build isolated custom modules on the vendor’s extension and API model, which keeps them compatible with platform updates.
Diatom Enterprises has built custom software since 2004, has been ISO 9001 certified since 2016, and has 80+ senior engineers on staff.
Contact our consulting team to discuss how we can help you evaluate and integrate your enterprise systems.