Choose an Odoo implementation partner on how they scope, not on their partner tier. Odoo\u2019s Gold, Silver and Ready tiers reflect licence revenue sold, not implementation quality, and US rates of $65 to $250 an hour tell you almost nothing about what a project will cost. What predicts cost is how many hours a partner needs, and that is decided by how well they understand your accounting before they start.
1. What the partner tiers mean
| Tier | What it measures | What it does not |
|---|---|---|
| Gold | Highest volume of Odoo licences sold, sustained | Code quality, accounting fluency, whether they will staff you properly |
| Silver | Meaningful sustained licence volume | The same things |
| Ready | Certified and active | The same things |
This is not a criticism of the programme, which does what it is designed to do. It is a warning against using it as a proxy for something it was never meant to measure. Some of the best Odoo engineering in the US is done by small firms that will never reach Gold because they do not resell at volume.
2. Rate bands, and why they mislead
| Band | Hourly | Typically |
|---|---|---|
| Offshore-led | $65 – $120 | US-facing account management, delivery elsewhere |
| US mid-market | $120 – $180 | Mixed onshore team, functional lead onshore |
| US specialist | $180 – $250 | Senior engineers, accounting fluency, narrow focus |
A four-fold rate spread invites a rate-driven decision, which is the most reliable way to double an Odoo budget. A partner at $200 who scopes correctly in week one routinely costs less in total than one at $80 who discovers your posting groups in month three and bills the rework.
3. Eight questions worth asking before signing
- What do you need to see before you can quote this? (If the chart of accounts and close process are not on the list, the quote is a guess.)
- Who writes the code, and can I meet them?
- What would you refuse to build for us?
- How do you handle opening balances that do not reconcile?
- What is your approach to Odoo version upgrades with custom modules in place?
- Show me an OWL component or a Python model you have written.
- What happens in the two weeks after go-live, and who is on call?
- Which of our requirements do you think we should drop?
The last one is the most revealing. A partner who cannot name a single requirement worth dropping is either not listening or not willing to say something uncomfortable, and both cost you later.
4. What good looks like
A partner who asks for your trial balance before quoting. Who names the person who will write the code. Who tells you which of your requirements is a training problem rather than a module. Who has a documented answer for what happens if opening balances do not tie out at cutover.
The cheapest engineering decision in an ERP project is the one made before the contract. Every partner question above is cheap to ask and expensive to skip.