Considerations for Your Business When Selecting a New ERP System

Enterprise Resource Planning (ERP) software is one of the most important technology decisions a business will make. Most organizations expect an ERP system to support the business for seven to ten years or longer, which makes the selection process a strategic decision rather than a simple software purchase. The right ERP solution can improve visibility, strengthen process control, reduce manual work, and support growth across finance, operations, supply chain, sales, service, and reporting.

At the same time, ERP selection carries meaningful risk. A system that looks strong in a demo may not fully support how the business operates, where the company is headed, or what leadership needs from the investment. Before engaging vendors or comparing software features, companies should take time to define their current challenges, future-state goals, operational requirements, integration needs, and long-term scalability expectations.

A structured, vendor-neutral ERP selection process helps leadership make a more confident decision. Below are key factors every organization should consider when evaluating a new ERP system for the business.

Functionality that Meets Your Company's Requirements

It's critical to evaluate the unique business requirements of your company before starting the ERP implementation process. An ERP system's available modules are essential for meeting a variety of needs. For example, manufacturers need to consider the available modules, including those for Supply Chain Management, Project Management, and Warehouse Management. They may also want robust functionality for Reporting, Data Analysis, and CRM. Make sure the ERP system you select can support the features and workflows necessary for your particular business processes in addition to meeting industry-specific requirements.

An ERP solution should be evaluated for more than baseline functionality. Advanced capabilities such as predictive modeling, AI-driven analytics, workflow automation, and exception-based reporting should be reviewed to determine whether they can improve decision-making, reduce manual effort, and support the company’s future-state operating model.

John Hannan LLC takes an operations-first approach to ERP software selection, which means the evaluation starts with how the business actually runs, not with a vendor demo or generic feature checklist. For many companies, the most important ERP requirements are found in the details of daily work, including how orders are entered, inventory is controlled, jobs are scheduled, quality issues are handled, approvals are managed, and financial information flows through the business. By documenting these needs before engaging vendors, businesses can evaluate ERP software against real operating scenarios instead of polished presentations. This helps leadership separate standard functionality from workarounds, identify where configuration or integrations may be required, and make a more confident, vendor-neutral decision that supports the way the company needs to operate after go-live.

Scalability to Support Business Growth

An ERP software solution is a long-term business platform, not a short-term technology purchase. If the system is expected to support the organization for seven years or more, the selection process should look beyond today’s pain points and evaluate how well the software can scale as the business grows. That includes supporting more users, higher transaction volumes, additional locations, expanded reporting needs, and new business functions or departments.

JHLLC approaches scalability through an operations-first lens. Growth is not just about whether the software can technically add users or process more data. It is about whether the ERP system can support the way the business will need to operate as complexity increases. For example, a company may need stronger inventory controls, more advanced production planning, improved warehouse processes, expanded approval workflows, deeper financial reporting, or tighter integrations with customer, supplier, e-commerce, or industry-specific systems. These needs should be evaluated during selection so the business is not limited to today’s baseline, but can choose an ERP system that supports the future-state processes, growth plans, and operating complexity the organization is working toward.

Scalability should also include geographic and organizational expansion. If the company plans to add locations, expand into new markets, or operate internationally, the ERP system should be evaluated for multi-entity, multi-currency, tax, regulatory, reporting, and localization requirements. A vendor-neutral selection process helps leadership understand which capabilities are standard, which require configuration, and which may depend on third-party solutions or implementation partner expertise. The goal is to select an ERP platform that can grow with the company while protecting operational fit, data integrity, and long-term value.

Configuration vs Customization

When selecting a new ERP system, businesses should understand how much of the solution can be adapted through configuration and where customization may be required. Configuration uses the system’s built-in tools, settings, workflows, security roles, fields, approvals, reporting options, and business rules to support the way the company operates. Customization usually goes further by changing code, building extensions, or creating functionality that is not part of the standard application.

This distinction matters because configuration and customization can have very different long-term impacts. A highly configurable system may give the business flexibility while preserving a cleaner upgrade path and reducing long-term maintenance. Customization can be valuable when it supports a true business differentiator, but it can also introduce added cost, testing, support risk, and dependency on specific developers or implementation partners.

The goal is not to avoid customization in every case, but to understand why it is needed, what business requirement it supports, and whether there is a better way to achieve the same outcome through standard functionality, configuration, process design, or an integrated third-party solution. This helps businesses avoid recreating outdated processes inside a new ERP system while still protecting the operational needs that make the company unique.

During selection, companies should ask how much of their current and future-state operating model can be supported with standard functionality and configuration. They should also understand where customization is required, how it affects upgrades, how it will be tested, who will support it, and whether it creates risk after go-live. A strong ERP selection process makes these tradeoffs visible before the contract is signed, so leadership can choose a system that fits the business without creating unnecessary complexity.

Integration Capabilities for Best-of-Breed Solution

Integration capabilities are an important part of ERP software selection because most organizations do not operate from one system alone. Many businesses rely on mission-critical applications for customer relationship management, e-commerce, payroll, expense management, warehouse automation, quality, reporting, shipping, electronic data interchange, or industry-specific processes. The ERP system may become the central business platform, but it still needs to exchange accurate and timely information with the rest of the technology ecosystem.

With an operations-first lens, John Hannan LLC evaluates integrations by looking at how information needs to move across the business, when it needs to move, and who depends on it to make decisions. The question is not simply whether two systems can connect. The better question is whether the integration supports the actual workflow without creating manual steps, duplicate entry, timing gaps, or reporting issues. During selection, businesses should identify the key data flows that matter most, such as order activity, inventory availability, production status, shipping updates, financial postings, supplier information, and customer commitments. Each integration should be reviewed for data ownership, update frequency, error handling, monitoring, security, and long-term support. This helps clarify whether an integration is truly standard, requires configuration, depends on middleware, or may introduce cost and complexity that should be understood before selecting the ERP system.

During selection, businesses should understand which integrations are available out of the box, which require middleware or third-party tools, and which may need custom development. They should also evaluate how data will move between systems, how errors will be monitored, who will support the integration, and whether the solution can scale as transaction volume and business complexity increase. A strong integration strategy helps reduce manual work, duplicate data entry, reporting gaps, and operational delays.

On-premise, Cloud-based & Mobility

ERP systems are designed to provide a centralized platform for business data, processes, reporting, and decision-making. One of the most important decisions during selection is the environment in which the system will operate. Some ERP systems are deployed on-premise using the organization’s own infrastructure, while others are cloud-based and accessed through the internet. Many modern ERP vendors have shifted their product investment toward cloud platforms, which can provide more frequent updates, broader accessibility, and reduced infrastructure responsibility for the client.

The right deployment model depends on the company’s business needs, IT strategy, regulatory requirements, cost structure, security expectations, and internal support model. Cloud ERP may provide advantages in scalability, remote access, disaster recovery, and vendor-managed updates. On-premise ERP may still be relevant for certain organizations with highly specific control, infrastructure, or legacy system requirements. The selection process should evaluate these options based on the business outcome, not just the technology preference.

Mobile access should also be considered as part of the operating model. Employees in warehouses, on production floors, in the field, or working remotely may need access to ERP functionality without sitting at a traditional workstation. This can include approvals, inventory transactions, time entry, service updates, receiving, shipping, or management reporting. Mobility should be evaluated based on real user scenarios so the business understands whether the ERP system can support work where it actually happens.

Calculate the Total Cost of Ownership Beyond the Initial Investment

The cost of an ERP system goes well beyond the initial license or subscription fee. Total Cost of Ownership (TCO) should include software subscriptions, implementation services, integrations, data migration, reporting, training, testing, change management, internal resource commitments, third-party applications, support, and future enhancements. Without this broader view, it is easy to underestimate the true investment required to implement and sustain the system.

Be sure to look beyond the proposal total and understand the assumptions behind the numbers. A lower software cost may not represent a lower total cost if the solution requires more customization, more third-party products, more implementation effort, or more internal work to support the business after go-live.

Return on Investment (ROI) should also be evaluated in practical business terms. ERP value may come from better inventory visibility, fewer manual processes, faster financial close, improved production planning, stronger reporting, reduced duplicate entry, better compliance, or improved customer service. The selection process should connect cost to the business outcomes leadership expects the system to deliver.

A strong ERP selection process makes these financial tradeoffs visible before contracts are signed. The goal is to choose a solution that fits the business, supports future-state needs, and provides long-term value without introducing unnecessary cost or complexity.

Understanding the ERP Ecosystem

A successful ERP solution often involves more than the software vendor. Most ERP ecosystems include a network of software providers, implementation partners, system integrators, independent software vendors, resellers, managed service providers, consultants, and user communities. Understanding these roles is important because each participant may influence cost, scope, support, accountability, and long-term success.

Software vendors. These companies develop and maintain the core ERP platform. They are responsible for product direction, functionality, security, updates, and the long-term roadmap.

Implementation partners. These firms configure, deploy, and support the ERP system during implementation. Their experience, methodology, staffing model, and industry knowledge can have a major impact on project success.

System Integrators (SIs). These providers focus on connecting ERP with other applications, data sources, platforms, and business systems. Their work is especially important when the ERP system needs to operate within a broader technology landscape.

Value-Added Resellers (VARs) and channel partners. Some ERP vendors rely on partner networks to sell, implement, or support their products. These partners may bring industry specialization, regional coverage, or additional services.

Independent software vendors and technology partners. These providers offer complementary applications, extensions, connectors, or industry-specific tools that expand the ERP system’s capabilities.

Managed Service Providers (MSPs). These providers may support infrastructure, application management, security, monitoring, or ongoing system administration after implementation.

Training and support providers. These groups help users build system knowledge, improve adoption, and support the organization after go-live.

The size and maturity of an ERP ecosystem can be an advantage because it gives businesses more options for implementation, integrations, support, and future enhancements. However, a large ecosystem can also create confusion if roles and accountability are not clear. During selection, businesses should understand who is responsible for software, implementation, integrations, support, and long-term optimization.

John Hannan LLC helps clients navigate this ecosystem with objectivity. As a vendor-neutral and client-side advisor, the focus is on helping leadership understand the full solution landscape, compare options clearly, and make decisions that support the business rather than the interests of any single vendor or partner.

Resources, Knowledge, and Experience

By this point in the ERP selection process, many leadership teams begin asking whether they have the internal experience, time, and structure needed to make a confident decision. Selecting an ERP system requires more than reviewing software features. It requires a clear understanding of business processes, future-state goals, operational requirements, integration needs, cost assumptions, implementation risk, and vendor accountability.

John Hannan LLC supports businesses through ERP software selection with an operations-first, vendor-neutral, and client-side approach. We help companies define requirements, engage stakeholders, structure vendor evaluations, compare solutions, develop demo scenarios, assess Total Cost of Ownership, and create a decision process that leadership can stand behind.

The right ERP selection process should help the business make a confident decision before implementation begins. By combining industry experience, software market knowledge, and structured selection methodology, John Hannan LLC helps organizations choose ERP solutions that fit how they operate today and where they need to go next.

If your organization is preparing for an ERP software selection or needs an independent advocate to help evaluate options, John Hannan LLC can help you navigate the process with structure, objectivity, and practical business focus.