To choose an Odoo partner, don't stop at the hourly rate or the level shown on their profile: ask who is responsible for the project's success, which commitments go in writing, what «done» means, how much of the time goes into training your users and what they do before proposing custom development. A good partner answers clearly from the first meeting, even when the answer is not the one you expected, and also tells you what they expect from your company. These are the 10 questions worth asking before you sign, the answer to look for in each one and the warning signs.
Why the hourly rate is not enough to compare
Odoo is the same software with any partner: the apps, the localization and the updates come from Odoo. What changes is how the project is run. Two proposals with the same bank of hours can end very differently: in one, users master their flows and go live; in the other, the hours are spent on meetings about scattered questions and go-live is pushed back month after month. That is why cheap often ends up expensive: the real cost includes your team's time, the errors that must be fixed later and, sometimes, a second implementation.
The questions below work with any partner and in any country. They are not looking for a memorized «right» answer, but for whether the partner has a method and explains it to you plainly.
The 10 questions to ask before you sign
1. Who is responsible for the project's success?
An Odoo project succeeds when your users master how to record their work in the system before go-live. Only your company can make sure of that: the partner provides the system, the method and its hours, but it cannot learn for your users or decide for you. Be wary of «don't worry, we'll take care of everything»: it sounds comfortable, but it puts the responsibility in the wrong place, and it is exactly what gets disputed later.
2. Which commitments go in writing?
What is said in a sales meeting is not an agreement. If something is non-negotiable for you, such as a scope, a date or a deliverable, it must be in the contract or in a document accepted by both parties. Also ask whether each session ends with a written summary of what was defined and what is pending. If the partner uses phrases like «we guarantee it» and then does not put them in writing, take note.
3. What does «done» mean?
«Ready» without a definition causes many disputes. A good definition can be checked: the process is defined in Odoo, it is written down and your key users run it end to end in a pilot, without help. Ask them to show you how progress will be measured; if the answer is only «hours used» or «modules installed», you are not measuring results.
4. Do you guarantee a deadline?
The honest answer for a whole project is usually an estimated deadline, not a guaranteed one, because it depends on something the partner does not control: your users' time and practice. A simple, standard project can go live in a few weeks; one with several processes and users cannot. If you need certainty on a specific point, the sensible path is to pay first for a gap and return-on-investment analysis that allows deadlines to be committed for that point. Be wary of a fixed deadline for the whole project given in the first meeting.
5. How much of the time goes into training, and who trains the end users?
Training is the core of an implementation, not an appendix at the end. Look for a partner that spends most of the hours on your users learning their complete flows, with pilots and questions in every session, and that explains how your key users will then train the end users. A useful hint: if nobody on your team asks anything during the sessions, something is wrong.
6. What do you do before proposing custom development?
A partner that builds everything you ask for seems helpful, but leaves you with custom code that must be maintained and migrated with every Odoo version. The answer you want is different: first understand the result you need, then see how to achieve it with what Odoo already includes and only at the end, if it is really needed, develop. Also ask who maintains that code when the next version comes out.
7. Does the consultant lead the project or answer questions?
Implementing is not the same as on-demand consulting. In an implementation, the consultant sets the route: if your team wants to review fixed assets when the journals, bank accounts and e-invoicing are not configured yet, a good consultant says so and returns to the agreed order. Two meetings lost on questions that do not lead to the goal are a lost week. Ask how they decide the order of topics and what they do when the team drifts.
8. Does the consultant understand business processes or only Odoo?
Knowing where every Odoo option is located is not enough. A real example: to get more decimals in the unit price, a consultant recommended changing the currency rounding. Technically it changed the decimals, but it affected the whole accounting. What was needed was to adjust the decimal precision of the product price, which is a separate setting. Ask about cases like this and watch how the consultant reasons. Competence matters more than years: a competent person is not afraid to say «I don't know, let me test it in a test database».
9. What happens if the consultant changes, or if your internal lead changes?
Consultants change at any partner. What keeps the project from starting over is that the knowledge stays on your side: written agreements, recorded sessions and an internal lead who knows what was agreed and how far the project has come. Ask how each session is documented. And ask yourself who that lead will be, how much time they will have and what happens if they go on holiday halfway through the project.
10. How is AI used, and who owns the access?
AI can already carry out configuration and data loads in Odoo, but it does not replace the method: it executes what people define and review. Ask whether the agent will belong to your company or to the partner, which user and permissions it connects with, where the keys are stored and how its work is reviewed. Also ask in whose name the Odoo subscription, the administrator user, the hosting and the custom code repository will be: they should be yours. This is how we work in Odoo implementation with AI.
Warning signs in a proposal
- A fixed deadline for the whole project, without reviewing your processes.
- «We'll build anything you need», without first asking what result you are after.
- The hourly rate as the only argument.
- Nobody asks who your internal lead will be or how much time your key users will have.
- There is no written summary of each session and no definition of «done».
- Administrator access or the code stays in the partner's name.
What a good partner will also ask you
Choosing a partner works both ways. A serious partner will ask you who leads the project in your company, whether they have authority to decide, how much time your key users can spend between sessions and whether you are willing to start with the standard. If those questions make you uncomfortable, better to know it before signing: the project is probably not ready to start, with that partner or with any other.
If you already signed and the project is stuck
Switching partners without understanding what went wrong usually repeats the problem. First, review the 7 signs your Odoo implementation is failing and run a diagnosis: which processes were defined, which users master them and what is misconfigured. It is the first thing we do in an Odoo implementation rescue.
If your company is in Peru and you want to compare local options, also see our page on Odoo partners in Peru.
How we work at Ganemo
We use an implementation methodology that already works, now powered by AI. The method comes first: your team learns and leads, training is the core, agreements go in writing and we start with the standard. Then AI comes in as an accelerator: your own company's agent, Claude Code or ChatGPT Codex, connects to Odoo with keys managed in Secrevo and carries out what we define together, in production too, with review.
We don't sell certificates, we deliver results. We serve companies worldwide and have a presence in Peru, Paraguay, Chile, Mexico, the US, Ecuador, Colombia, Argentina, Spain, Nicaragua and the Dominican Republic. Is your country not on the list? Your company can be the first.
Book a diagnosis or message us on WhatsApp at +1 (828) 672 6150.
Frequently asked questions
Is it better to hire Odoo directly or a partner?
Both options can work. What decides the outcome is the same in both cases: that your company leads, that agreements are in writing and that your users are trained. If your team has no experience with this kind of project, a partner that guides more closely usually helps.
Does the partner level shown by Odoo matter?
It mainly reflects licences sold and other Odoo commercial requirements, not how a project is run. Use it as one more data point and decide with the questions in this guide: method, training, written agreements and the consultant's business judgment.
How long should an Odoo implementation take?
It depends on the number of processes and users and, above all, on the time your team spends practicing. A serious partner gives you an estimated timeline and explains what it depends on; a guaranteed deadline only makes sense for specific items after a prior analysis.
Is the cheapest partner a bad idea?
Not necessarily, but the hourly rate does not measure the total cost. Compare how many hours the project will need with each method, how much time your team will invest and what it would cost to fix errors or unnecessary development.
Can I use my own AI agent with the partner?
Ask before you sign. At Ganemo the agent belongs to your company (Claude Code or ChatGPT Codex): we teach you to connect it to Odoo securely and to work with it during the project and afterwards.