Onboarding Guide
Odoo ERP implementation
We know what’s needed for a successful Odoo implementation. Part of this is a technical tale but luckily, that’s right up our alley.
How can you help us?
- With a proper preparation, because in this case it really is half the job.
- The right people in the right position, so we can switch fast and work together as colleagues.
- Clear mutual expectations, so we won’t have to face any unpleasant surprises.
You can expect a lot from us but in our turn, we also expect something from you. In this Onboarding Guide you can read exactly what that something is. So we will be on the same page for a smooth implementation. And as you might already know: in our philosophy, that implementation is just the beginning, the fundament. After that, we’ll start decorating the rooms, and that’s when the real fun starts ;-)
360 Way Of Working
Focus
Our strength lies in Odoo implementation and optimisation, not in business consultancy. So in your tasks, stick to the core.
We optimally use the potential of Odoo by staying as close to standard as possible. This creates a stable and reliable system.
We see Odoo as a classic transactional ERP system. To bridge possible functional flaws in Odoo, we apply a best of breed approach.
From the ‘Keep It Simple Stupid’-mentality, best practices take priority over unnecessary complexness.
In a phased go-live, questions regarding an already live phase are handled through support. This approach helps us maintain focus on the progress of the remaining phases and the overall project goal.
With a migration, we focus on the current functionalities. New ones are added after the migration has been completed.
Checklist
Are you ready to collaborate with us? Do the check and find out if you’ve got what it takes for a smooth Odoo implementation.
Company processes are clearly defined and documented in a standard format, like swimlanes or flowcharts, resulting in a solid basis for the project.
A skilled Odoo Product Owner is fully available throughout the entire project.
Key users have been identified and are authorised to take (detailed) process decisions and are formed in a project team.
The project team is able to distinguish between vital features and nice-to-haves.
The project team will be allocated the necessary hours during the development phase (times 4 indication of 360 ERP).
Time is scheduled for the project team to make and test end-to-end test scenarios.
Time is scheduled for the project team to support other users in the onboarding and training.
Way of communication
In our Odoo project portal, all project tasks are conveniently lined up.
All project related communication takes place through a task.
New tasks can be submitted through our project email address. This will automatically create a task in the appropriate project.
Indicate one subject per task, so we stay focussed.
Things we expect from the customer
Put together a project team with a maximum of 8 key users (max. 2 per department), including an Odoo Product Owner. Create subgroups if needed but keep these groups internal.
There’s flexibility to integrate new insights during the implementation, so all processes are functioning effectively in Odoo.
There’s awareness of parallel IT or e-commerce projects and their potential impact on the ERP implementation.
We will organise one or two train-the-trainer sessions with you. In our budget we hold into account that the trainer actively participates, learns fast, makes test scripts and documents instructions.
The project budget serves as a guideline and is based on the architecture. Detailed scope changes are determined by our consultants during project execution and may vary depending on specific project details.
The goal of the project team is to go live sooner rather than later to start benefiting from Odoo as quickly as possible, rather than aiming for a fully automated and flawless system from the outset.
Last but not least: delays in complex software projects are often caused by factors such as lack of engagement, internal capacity issues, unforeseen complications, third-party dependencies, or a focus on non-essential details. Deadlines should therefore be flexible, prioritising a go-live moment that best supports the project’s success.
Read more about our nice and pragmatic approach here.
Customer in Technology Innovation
