20 questions you should ask an Odoo implementer
Before signing an ERP project, there is one critical meeting: the conversation with the implementer.
These questions are not looking for perfect answers. They look for signs of maturity, approach, and honesty.
These are not trick questions. They are questions that a good implementer knows how to answer naturally.
How to use this guide
Business understanding
Which parts of our business do you think are most critical?
Which processes do you believe typically generate the most problems in projects like ours?
What information do you need to properly understand our operations?
What would you take for granted and what wouldn't you assume without analysis?
What mistakes do you see repeated in companies in our sector?
Positive sign
They ask questions before answering
Warning sign
They talk about modules without discussing processes
Scope and standard
Which parts do you think can be covered with standard features and which cannot?
How do you decide when to develop and when to adapt the process?
What risks do you see in our current scope?
Which functionalities do you usually recommend leaving for later?
What happens if during the project we discover that something doesn't fit?
Positive sign
They discuss boundaries and phases
Warning sign
“Everything is standard”
Team and methodology
Who will be part of the team and what role will each person have?
Who makes functional decisions during the project?
How do you manage scope changes?
What methodology do you follow and why?
How do you validate that what has been delivered meets expectations?
Positive sign
Clear roles and defined process
Warning sign
Dependency on a single person
Support and evolution
What happens after go-live?
How are improvements and new needs managed?
What part of support do you cover and what part don't you?
How is a future migration managed?
What level of dependency will we have on your team?
Positive sign
They talk about the medium term
Warning sign
The project “ends” at launch
How to interpret the answers
Beyond the content, pay attention to:
- Whether they acknowledge risks
- Whether they set boundaries
- Whether they know how to say "I don't know"
- Whether they explain consequences
- Whether they adapt their discourse to your context
Judgment, not reassurance
A good implementer doesn't promise reassurance, they promise judgment.
Common mistakes when asking these questions
Avoid:
An ERP project doesn't start with a signature.
It starts with an honest conversation.
These questions don't guarantee success, but they significantly reduce risk.
Once you've chosen the implementer, one key question remains: