One of the most important decisions in an ERP transformation happens before any system is selected: deciding how the business should operate in the future.
ERP transformations are often framed around technology.
Which platform should we choose? What functionality do we need? Should we move to the cloud? How much can we use standard functionality? Which implementation partner should we select?
These are important questions. But they are not the first questions an organization should answer.
Before evaluating ERP solutions, there should be sufficient clarity on the business the new system is expected to support.
What processes should be standardized? Where does the business genuinely need differentiation? Which capabilities need to improve? What information should management have available? What should the future operating model look like?
Without this foundation, an organization risks making one of its largest technology investments before it has clearly defined the business change behind it.
A modern ERP system reaches deep into the way an organization operates.
It influences how orders are processed, materials are purchased, products are manufactured, inventory is managed, financial information is produced and decisions are made.
Changing the ERP therefore means changing much more than technology.
It can affect processes, roles and responsibilities, data, integrations, reporting, controls and ways of working across the organization.
This is why we believe an ERP transformation should begin with the business rather than the system.
The objective should not simply be to replace the current ERP.
The objective should be to create a better foundation for how the business operates and develops in the future.
Organizations don't need every detail of their future operating model defined before starting an ERP selection.
But they should understand the direction.
At a minimum, there should be clarity around questions such as:
This creates a much stronger basis for evaluating ERP alternatives.
Instead of asking only “Can the system support our current requirements?”, the organization can ask:
“How well does this solution support the way we want to operate in the future?”
That is a fundamentally different selection criterion.
One of the biggest risks in an ERP transformation is carrying existing complexity into the new environment.
Over time, organizations accumulate exceptions, local processes, custom functionality, integrations and workarounds. Many originally had a good reason to exist. Some may still be necessary.
Others are simply historical baggage.
If the ERP selection starts by collecting requirements from the existing organization without challenging them, today's complexity can easily become tomorrow's specification.
The result may be a modern platform supporting an unnecessarily complicated operating model.
Before asking how the new ERP should accommodate every current requirement, it is worth asking:
Do we still need to work this way?
This is where process work before system selection becomes particularly valuable.
Standardization is usually one of the promises behind an ERP transformation.
And for good reason. Common processes can reduce complexity, simplify maintenance, improve data quality and make the organization easier to manage and scale.
But standardization should not become an objective in itself.
Some processes genuinely differentiate the business. Others do not.
Finance, purchasing or basic master-data processes may offer significant opportunities for harmonization. A process closely connected to a company's customer proposition or competitive advantage may require more flexibility.
The important thing is to make these choices deliberately.
Standardize where it creates scale and efficiency. Preserve differentiation where it creates business value.
That principle should be established before detailed solution design begins.
ERP doesn't operate in isolation.
It sits within an ecosystem of applications, integrations, data platforms, reporting solutions, digital services and increasingly AI-enabled capabilities.
Selecting an ERP without understanding this wider environment can lead to difficult architecture decisions later.
What role should ERP play in the future application landscape? Which capabilities belong inside the ERP and which outside it? What data should be mastered where? How should systems communicate? Which existing applications can be retired?
These decisions affect not only the implementation but also the long-term complexity and cost of the technology landscape.
A good ERP transformation therefore needs an architectural view early enough to influence the selection—not after the platform has already been chosen.
ERP business cases can easily become dominated by implementation costs, licenses and the cost of maintaining the current environment.
Those numbers matter, but they only describe part of the investment.
The more important question is what the organization expects to gain from the transformation.
Benefits might come from faster processes, improved productivity, better inventory management, fewer manual activities, improved data quality, reduced application complexity or the ability to scale operations without equivalent increases in cost.
Making these outcomes explicit before selecting the ERP does two things.
First, it provides better criteria for comparing alternatives.
Second, it establishes the outcomes against which the transformation can later be managed.
The business case then becomes more than justification for an ERP investment. It becomes a reference point for the transformation itself.
Once the business objectives, target processes, key capabilities and architectural principles are sufficiently understood, technology selection becomes much more meaningful.
Requirements can be prioritized based on business value rather than collected as an unlimited wish list.
Vendors can be evaluated against the future operating model rather than today's system.
Trade-offs become easier to make because there is a common basis for decision-making.
And perhaps most importantly, the conversation changes from:
“Which ERP should we buy?” to: “Which solution gives us the best foundation for the business we are building?”
That's the question an ERP selection should ultimately answer.
ERP programs are large investments and often shape an organization's operating environment for many years.
The decisions made before implementation can therefore be just as important as those made during it.
For us, the principle is simple:
Business objectives first. Processes and capabilities second. Architecture and requirements next. Technology selection after that.
This doesn't mean spending years designing the perfect future state before approaching the market.
It means creating enough clarity to make deliberate choices.
Because by the time an organization starts comparing ERP products, the most important question should already have an answer:
What kind of business are we designing the ERP to support?
At Maya, we help organizations define the business, process and architecture foundations for ERP transformations before major technology and implementation decisions are made.
By connecting business objectives, processes, capabilities, architecture and technology choices early, we help create a stronger foundation for both ERP selection and the transformation that follows.
Considering an ERP renewal? Let’s discuss the decisions worth making before selecting the system.