Picking an Odoo partner is one of the highest-leverage decisions in the whole project. The pitch decks rarely help, the questions do.
Here are the nine questions, and what strong and weak answers sound like for each.
What is your client retention rate, and what happens at the end of a project?
Retention is the single most honest number a partner can give you, because it is scored by clients voting with their budgets. Ask for the figure, then ask how it is measured: renewals of support contracts, repeat phases, or simply "nobody complained." A partner that tracks retention will answer instantly and tell you what year two of the relationship looks like: who owns your account after go-live, how often the system gets reviewed, and what happens when Odoo releases its next version.
If they do not track retention at all, that tells you the business model ends at go-live. Handovers, documentation and admin training suddenly matter much more, because you will effectively be on your own.
Who actually does the work, senior consultants or juniors learning on your account?
Every firm sells its best people and staffs projects with whoever is free. Ask for the names of the functional lead and the technical lead who will be on YOUR project, their years with the product, and how much of their week you actually get. Then ask to meet them before you sign, not after.
The pattern to catch is bait-and-switch: a principal consultant runs the demo, then a graduate learns Odoo on your invoice. A confident partner will put the delivery team in the room early, because the team is the product.
How do you handle Odoo version upgrades over the next three years?
Odoo ships a major version every year, and staying two or three versions behind is where systems go to die. Ask what the partner's upgrade policy is: do they plan an upgrade path at implementation time, what does an upgrade typically cost on a system like yours, and who tests your customizations against the new version?
The technical answer you want to hear is that customizations are built as proper standalone modules that survive upgrades, never as edits to Odoo's core. If the partner cannot explain how their build style affects upgrade cost, they have not lived through enough upgrades.
Show me a system you took live more than two years ago that is still running.
Anyone can show a fresh go-live. Durability is the real product: a system still trusted after two years of daily use, staff turnover and at least one version upgrade. Ask to see one (anonymized is fine) and ask what changed in those two years: which modules were added, what broke, how it was fixed.
A partner proud of its old systems will talk about them at length. A partner that only shows launch screenshots is telling you where their involvement usually ends.
How do you handle our regional compliance, specifically?
In the GCC and Egypt this question has precise answers, not adjectives. Saudi Arabia: ZATCA Phase 2 e-invoicing integration, 15% VAT and the Saudi chart of accounts. The UAE: FTA-format VAT returns, corporate tax readiness and WPS payroll files. Egypt: ETA e-invoicing and the local chart of accounts. Odoo covers all of these through official localization packages. The partner's job is knowing them deeply, configuring them correctly and keeping them current.
Ask the partner to name the exact localization modules they deploy and who monitors regulatory changes. If the answer to "how do you handle ZATCA?" is "we have done VAT before," keep interviewing.
What does support look like after go-live, and who is my named contact?
Get the support model in writing before you sign: guaranteed response times by severity, what is included in the monthly fee versus billed separately, and the length of the hypercare window immediately after go-live, when issues surface fastest. Most importantly, ask for a named contact: a person, not a ticket queue.
Then test it: ask what happens if a payroll run fails on the 28th of the month. The quality of that answer (specific escalation steps versus vague reassurance) is the quality of the support you will actually receive.
How do you scope, and what happens when scope changes mid-project?
Budget overruns are almost never caused by day one scope; they are caused by how change is handled in month three. Ask how the partner scopes: is there a paid discovery phase, does it produce a written specification you approve, and is delivery phased so value lands early? Then ask for the change process: who prices a change, who approves it, and how it affects the timeline.
A written change-order process is a sign of respect for your budget. "We are agile, we will figure it out" combined with hourly billing is how a fixed-looking price quietly doubles.
Are you a certified Odoo partner, and at what tier?
Odoo tiers its official partners (Ready, Silver and Gold) based on certified consultants on current versions, new customers delivered and client retention. The tier is not everything, but it is independently verifiable in about ten seconds: every official partner has a public profile in the directory at odoo.com/partners showing its grade, certifications and reference counts.
Look the partner up before the meeting, and be precise about geography: certification lists are per entity, so ask about the tier and certified team in YOUR country, not the group's best market. Plementus publishes its own directory profiles for Egypt, Saudi Arabia and the UAE for exactly this reason: every claim on a slide should be checkable off the slide.
Can I speak to a client in my sector?
Sector fit changes everything: construction progress billing, retail inventory sync and clinic scheduling fail in completely different ways. A reference call with a client in your industry, on roughly your scale, is worth more than any proposal document. Ask the reference three things: did the timeline hold, how were problems handled after go-live, and (the only question that really matters) would they hire the same partner again?
If a partner active in your sector cannot produce a single reference willing to talk, that silence is the answer.
What good answers sound like
A strong partner answers with specifics, not adjectives. They talk about named leads, retention numbers, upgrade plans and real systems still in production. A weaker one talks about being "passionate" and "end-to-end" without ever telling you who picks up the phone in eighteen months.
The cheapest implementer is almost never the cheapest outcome. The one whose systems are still trusted years later is.