In brief
An ERP is not software like any other : it is a living structure that evolves with your company, and its success rarely depends on technology alone.
An ERP project unfolds in 4 phases : scoping (defining a clear, shared direction), implementation (turning needs into reliable tools), skills development (getting the tool adopted rather than endured) and continuous evolution (keeping the ERP alive alongside the company).
An ERP project never really ends : it should be thought of as a cycle, not as a one-off assignment.
Why think of your ERP as a cycle ?
An ERP is not software like any other. It is a living structure that evolves with your company. And its success rarely depends on technology alone.
This article summarises the 4 main phases of an ERP project, based on our experience and expertise at Niboo. Its goal is to help you better organise, steer and sustain your digitalisation project.
Phase 1 : scoping, defining a clear, achievable and shared direction
Scoping is the foundation of the ERP project. Too often neglected, it is nevertheless the keystone that determines how smoothly everything that follows will go. It is not an administrative step : it is an act of governance.
What we do at this stage ?
This is the moment when we :
Clarify the real objectives : not "installing an ERP", but rather "streamlining order management", "making invoicing reliable"...
Prioritise needs : distinguish what is vital from what is accessory or can be postponed, what is daily from what happens once a year.
Identify field constraints : human resources, data quality, realistic timing.
Align all decision-makers : prevent the IT project from going right while management pushes left.
Good scoping is one where every person involved in the project can sum up the project in one clear, shared sentence.
The typical mistake to avoid :
Agreeing to embark on a digitalisation without having determined the scope beforehand with your service provider. It opens the door to "Okay, but that wasn't planned originally. So it will be an extra."
Phase 2 : implementation, turning needs into functional, reliable and tailored tools
This is the "visible" phase : we install, we configure, and sometimes, we develop. But this is not where success is decided. A good project does not rely on technical complexity, but on the clarity and simplicity of functional choices.
What you need to do during implementation ?
Translate the company's real processes into the tool : if time and budget allow. Otherwise, it can be worthwhile to favour adapting your workflows to the tool. Who knows, it may be the opportunity to rethink your overall way of working?
Favour the "standard+" approach : make the most of existing features before customising.
Accept being told no to certain requests : and having it explained why. The integrator's role is also to guide and challenge you.
Set up a reasonable iteration rhythm : with regular demonstrations to validate choices.
This is not the time to add 10 features "just in case". It is the time to build a solid, tested and understood foundation. A successful ERP is rarely a "hyper-customised" ERP: it is an ERP that is well thought out and well understood by everyone.
The typical mistake to avoid :
Not actively involving the Key Users in the project. Only department heads and end users can tell you what they need and what matters. Not listening to them is a bit like buying them a house without asking their opinion and forcing them to live in it for years. Conversely, taking part in building their new tool boosts adoption of the system.
Phase 3 : skills development, getting the tool adopted rather than endured
A successful implementation without trained and engaged users is a stillborn project. This crucial phase is not a simple transfer of skills : it is a build-up of confidence.
What this phase aims for ?
Train each profile according to their responsibilities : the accountant does not need to know everything about the CRM, and vice versa.
Give meaning to the tool : explain why it is used, and what each person gains from it.
Reduce resistance : reassure, repeat, correct the first uses.
Create a simple documentation base : guides, videos, internal FAQ.
Appoint business referents : internal relays for common questions.
Buy-in cannot be decreed, it is built. And it does not depend only on the quality of the training, but also on the quality of the communication.
The typical mistake to avoid :
Neglecting the investment to be allocated to training and adoption support. Telling yourself that users will learn well on their own is tempting, but the money saved on a training not given will be paid back twice over when future errors have to be corrected.
Phase 4 : continuous evolution, evolving your ERP with your company
Go-live is not an end, it is a starting point. An ERP is a living tool, which must keep up with the evolution of your processes, the arrival of new employees, the opening of new services, channels or markets, and the maturing of your management culture.
What you need to put in place ?
A governance framework : ERP committee, regular follow-up, prioritisation of requests.
A measurement of real usage : are users using the right features? Why not?
Some thinking about what comes next : automations, integrations, KPI optimisation.
Management of the module lifecycle : some tools become useless, others become essential.
The ROI of an ERP does not happen in one month. It plays out over time, provided you do not freeze it. The tool is there to serve your strategy, not to limit it.
The typical mistake to avoid :
Telling yourself that the investment in the ERP ends at Go-Live. Ideally, plan an annual budget dedicated solely to its updates, upgrades and migrations, or even the implementation of new applications or new departments.
Scoping (defining a clear, achievable and shared direction), implementation (turning needs into functional tools), skills development (getting the tool adopted by teams) and continuous evolution (evolving the ERP with the company).
It determines how smoothly everything that follows will go : it clarifies the real objectives, prioritises needs, identifies field constraints and aligns decision-makers. Without a scope determined beforehand with the provider, you risk being billed extras for what "wasn't planned originally".
No. A successful ERP is rarely a "hyper-customised" ERP. It is preferable to favour the "standard+" approach: make the most of existing features before customising.
Because department heads and end users are the only ones who know what they really need. Involving them in building their future tool also strengthens its adoption.
No, go-live is a starting point. Ideally, plan an annual budget dedicated to updates, upgrades and migrations, and to adding new applications or new departments.
Conclusion :
A cycle, not a construction site
An ERP is not a construction site. It is a strategic tool to be evolved over time. An ERP project never really ends, and that is a good thing: it is a lever for structuring, continuous improvement and collective skills development, provided you have thought of it as a cycle, not as a one-off assignment.
Three questions to ask yourself at least once a year :
Does my tool still reflect my needs today?
Do my teams know how to use it?
Is there a pilot on board to make it evolve?
If you answer "no" to any of them, it is not a problem. It is a good opportunity to restart the momentum.
And if you want to talk about it with people who live this every day, the Niboo team is here to support you !
Feel free to check out our latest updates on our social media channels :
Odoo ERP
From invoicing to marketing campaign management and human resources management, discover Odoo, the comprehensive ERP solution for any agencies looking for digitalise.
. 