As early as possible. Identifying requirements early creates a roadmap for the entire project and helps all stakeholders align on goals from the start. Leonix approaches it layer by layer:

• Start at a high level- grasp the key business functions and the key performance indicators (KPIs) that the new system must meet.
• Prioritize requirements by importance to narrow down the right solution options.
• Consider this as an iterative process, not a one-time task - requirements are refined as the project progresses.

Avoid "analysis paralysis": detailed enough to get it right, but not so much that it delays the project.

All three times are necessary. Leonix's principle is standardize before digitizing - a clean process allows the software to deliver value.

• Before: define high-level processes (L1 - L2) to create a framework for evaluation and solution selection.
• In the design phase: refine to L3 - L5 with the involvement of actual departments.
• After go-live: continue to optimize as operations reveal areas for improvement.

Don't jump straight into detailed design due to schedule pressure - that is the source of the misalignment between needs and software.

As soon as the decision to implement is made, regardless of what stage the project is in. ERP is not just a technology change - it is a change in culture and how people work.

• Assess the organization's readiness to identify strengths and risks related to people.
• Build a communication and training plan for each user group.
• Maintain support and feedback mechanisms extending beyond the go-live date, not stopping at the handover point.

• 75% over budget / overdue
• 66% result in negative ROI

According to McKinsey, the majority of ERP projects fail not because of weak technology but because of implementation methods. Four common causes:

1. Ambiguous requirements - not clearly defined from the start, leading to solutions misaligned with needs.
2. Weak project governance - loss of control over scope, budget, and time.
3. Resistance to change - personnel not prepared, not accepting the new system.
4. Unrealistic timeline - pushing the schedule causes key steps to be overlooked.

How Leonix addresses the issue: gathering detailed requirements, experienced project management, strong change management, and realistic planning from the Initiation phase.

It should not be handed over "completely". Relying entirely on the implementation unit is a risk - no one understands the strategic goals of the business better than the business itself. The effective model is balanced collaboration:

• Leonix brings technical expertise and standardized implementation methods.
• The business owns the project, bringing knowledge of processes and business objectives.
• The internal project team participates throughout all phases - not standing outside.

Digital transformation is changing how the organization operates, not just applying new technology. Four determining factors:

• Commitment from senior leadership - proactively leading, linking the project to a long-term vision.
• Readiness assessment of both technology infrastructure and organizational capacity before starting.
• Continuous improvement - viewing this as a journey, ready to adjust over time.
• Measured by KPI to continuously evaluate effectiveness and make data-driven decisions.

Optimizing costs does not mean cutting quality. Some effective levers:

• Choose the right model: SaaS reduces initial costs and is flexible for scaling; on-premise is suitable when high security is required.
• Leverage the open-source Odoo to significantly reduce licensing costs.
• Limit excessive customization from the start - avoid incurring costs and complexity during maintenance.
• Comprehensive budget including training, change management, and a contingency fund.

Security is built in during the implementation process, not added later:

• Risk analysis to identify weaknesses in the system and processes.
• Data encryption both at rest and in transit.
• Access control strict with permissions and multi-factor authentication (MFA).
• Monitoring & updates regular patches to keep up with new threats.

Training is a key factor for the system to be truly utilized:

• Group users and design content suitable for each role.
• Hands-on training directly on the system rather than theory.
• Repeated training and post-go-live support to reinforce knowledge and address arising issues.

• Official partner of Odoo - a team certified across multiple versions from Odoo 12 to 19.
• Exclusive module for Vietnam - accounting according to Circular 200/2014/TT-BTC and automatically digitizing electronic invoices using AI.
• Focus on business value, not getting caught up in purely "IT projects."
• Long-term partnership - from consulting, implementation to training, support, and upgrades.