ERP Demonstrations - Why Functional and Technical Aspects Both Matter

If you focus solely on functional demonstrations without technical discussion, you risk selecting a solution that fits the process but clashes with your enterprise architecture.

Lumenia recommends a structured approach to ERP demonstrations, centred around a set of scripted business process scenarios. Vendors walk through activities such as order to cash, procure to pay, and financial close using a predefined demonstration script to show how the system would support day-to-day business operations.

However, focusing solely on functional scenarios can leave an important part of the evaluation unexplored: the technical architecture that will support the system once it is implemented. To properly assess both perspectives, organisations should define not only a functional script but also a structured technical agenda, with clear topics, time allocation, and consistent questions for all shortlisted vendors.

ERP demonstrations: different audiences, different objectives

ERP projects have a broad range of stakeholders. Functional demonstrations are aimed at business users and process owners, focusing on how well the solution supports business processes, usability and configuration.

Technical stakeholders are usually interested in a different question: how will the ERP platform operate within the organisation’s wider technology landscape? Effectively, ERP demonstrations show how the system works, while technical reviews should establish whether it will work for you.

Topics such as integration architecture, hosting and deployment models, upgrade cadence, data migration approaches, reporting strategy, AI capabilities, integration with collaboration tools such as Microsoft Teams or Office, and security controls do not fit neatly into process-based demonstrations. 

Instead, dedicated time is required to explore these areas and understand technical constraints and integration challenges that might otherwise emerge later in the project. This discussion should be structured around a set of pre-defined technical requirements developed by the selection team and issued to vendors, ensuring responses can be assessed consistently and explored in sufficient depth through targeted questions and examples where needed.

ERP technical architecture: sector-specific considerations

In some industries, technical architecture carries additional implications. Organisations operating in regulated or security-sensitive environments may need to consider issues such as system validation, data classification or specific hosting requirements. 

For example, environments subject to GxP validation, and organisations in aerospace and defence sectors, typically have particular expectations around deployment models, documentation, and control frameworks. Some businesses require single-tenant SaaS or hosted environments to support their validation requirements, data segregation, and tight control over upgrades, ensuring systems can be validated and changes are managed in a controlled manner. Others need to ensure that data residency requirements can be met within specific jurisdictions to comply with regulatory or contractual obligations.

In these situations, the deployment architecture can directly determine the viability of each solution. Clarifying these needs through a scripted technical discussion ensures they are addressed explicitly during vendor evaluation rather than treated as assumptions.

ERP selection approach: matching technical depth to complexity

The level of technical discussion required often depends on the complexity of the organisation’s industry and environment. On simple projects, the ERP platform may sit within a relatively straightforward application landscape with limited integrations and minimal regulatory constraints. In these cases, technical topics can often be addressed through written RFP responses followed by a short discussion at the tail-end of the demo days to clarify the key points.

For many organisations, however, the technology landscape is more complex. Scheduling a dedicated technical session alongside the functional demonstration allows these considerations to be explored in greater depth. In particularly complex environments, organisations may run a structured technical workshop, based on defined technical requirements,  lasting half a day or more. This enables architecture teams and technical specialists to probe platform and implementation considerations in detail and test key assumptions.

Taking a right-sized approach allows organisations to compare vendors effectively and ensures that technical considerations are formally reflected alongside functional fit in the overall evaluation and scoring.

ERP selection: looking beyond the functional demonstration

ERP demonstrations remain a critical part of the selection process. However, ERP systems do not operate in isolation; they sit within a broader technology ecosystem and must integrate with existing applications, data platforms, and security frameworks.

Introducing a formal technical review alongside functional demonstrations helps ensure these broader considerations are explored before a final decision is made. While the core technical themes remain consistent, the emphasis has evolved in many organisations towards areas such as integration, data strategy, and emerging capabilities such as AI.

When planning your ERP selection, define both a functional demonstration script and a structured technical script, and score vendors on both. In more complex environments, this should be treated as a dedicated workstream rather than a supporting discussion. Doing so reduces the risk of architectural surprises later in the project.

This blog was written by Jim Goodison, Principal Consultant at Lumenia. For further information please send an email to Jim Goodison.