There is one question that almost no one asks during an ERP tender, and yet it is the only one that truly matters: does your future integrator know how to say no to you?
Installing Odoo, configuring the modules, connecting electronic invoicing and the accounting localisation — any certified partner can do all that. The market has dozens ofOdoo integrators in Belgium, France and Portugal, from the freelancer to the structured firm, including the Gold Partners. Technical mastery of Odoo is no longer a differentiator: it's a prerequisite.
What truly makes the difference — what determines whether your project ends as an operational success or as an awkward conversation topic at the next board meeting — is everything that happens before and around the configuration.
The real problem with ERP projects
The studies have been consistent for ten years: between 50% and 75% of ERP projects fail to deliver the expected results. Budget overruns, blown deadlines, disastrous user adoption, management going back to a spreadsheet in parallel a few months after go-live.
Odoo is not the problem. The implementation process is. And in that process, the failure factors are almost always the same: it's not about bugs, but about human decisions — a poorly scoped project from the outset, a client who asked for too much custom development, users who never truly bought into the tool, an accounting setup that ignored local specifics. Situations we regularly see on projects taken over after a first integrator.
What truly makes a good integrator
1. They understand your business before touching the tool
The first mistake in an Odoo project is starting with Odoo. An integrator who turns up with slides about the modules at the first meeting is selling you technology, not transformation. At TSC, we start by understanding how you make money, where you lose time, what your critical flows are, and what your teams on the ground really experience day to day. This business-understanding phase is not a luxury: it's the foundation.
2. They limit customisation — even when you ask for it
The less custom development you build, the better: that's where a large part of the budget and long-term maintainability is decided. Odoo is a complete, evolving ERP whose standard modules cover most of an SME's needs. Every piece of custom development you add is technical debt that will need testing, maintaining and migrating with every new version. A good integrator doesn't say yes to everything: they analyse each request, propose a standard alternative when one exists, and only code what genuinely adds value.
3. It scopes the project with rigour
Scoping is the most underestimated phase of an ERP project: exact scope, priorities, exclusions, success criteria, data migration plan, validation milestones. At TSC, scoping is not an administrative formality: it's a reference document that binds both parties throughout the project.
4. It makes user adoption a priority
The best ERP in the world is worthless if teams don't use it. Adoption is built from day one: design workshops with key users, gradual training, internal champions, training adapted to each team's profile. It's as much change management as it is training.
5. It genuinely masters local accounting specifics
Chart of accounts, VAT obligations, intra-community declarations, electronic invoicing Peppol, balance sheet standards: an integrator who configures an Odoo localisation without mastering these accounting fundamentals will deliver a tool that won't pass your accountant's or auditor's review. At TSC, the team works closely with accounting firms and clients' finance departments, in Belgium, France and Portugal alike: accounting configuration is never a default setting.
6. They govern the project — and own that role
An ERP project without clear governance is a project without a pilot. Who decides when a change request is accepted? Who arbitrates when two departments have conflicting needs? Who approves go-live? Project governance means defining roles on both the client and integrator sides, a regular steering committee, a change-management process and transparent communication about risks.
7. They know how to say no
This is perhaps the rarest skill in the profession, and the most valuable for you. Saying no to a feature that adds complexity without real value. Saying no to an unrealistic deadline imposed by internal pressure. Saying no to a shaky data migration that would compromise system reliability. An integrator who always says yes doesn't respect you: they're setting you up for long-term problems to please you in the short term.
Why TSC Experts
TSC is a consulting and integration firm for Odoo, active in Belgium, France and Portugal, specialising in Odoo projects for SMEs and mid-sized companies. The approach is built around one simple principle: your ERP project must deliver measurable business results, not just a working installation.
The team is involved at every stage: strategic scoping, process analysis, configuration and integrations, training and change support, post-go-live support. It knows the accounting, tax and regulatory specifics of each of these markets — and knows how to say no, because that's how it truly helps its clients.
What you should ask your next Odoo integrator
Before signing, ask the integrator you are evaluating these questions:
- How do you handle custom development requests? (A good integrator will talk to you about value analysis before coding)
- What is your approach to change management? (If the answer is limited to "we run a training session", be wary)
- Do you have experience with local accounting and Odoo? Ask for references where an accounting firm or a finance department was involved.
- What happens if I request a feature you consider counterproductive? (The answer will tell you everything)
- What is your scoping process? (Ask to see an example of a scoping document)
The answers to these five questions often say more about your future partner than any certification.
Frequently asked questions
Is custom development always a risk?
Not systematically, but every piece of custom development adds technical debt to maintain and migrate: it must deliver value that no standard module covers.
How do you assess an integrator's local accounting expertise?
By asking for client references where an accounting firm or a finance department was directly involved in the configuration.
Does scoping make the project longer?
No: rigorous upfront scoping prevents scope creep, which is what actually makes projects longer.
In conclusion
Odoo is a remarkable tool, with native localisation and a skilled partner ecosystem. But the success of an ERP project isn't decided by the software: it's decided by the quality of the partner supporting you — their understanding of your business, their scoping rigour, their ability to challenge your least sensible requests, and their commitment to your teams' adoption.
Considering an Odoo project? Get in touch with the TSC Experts team for an initial, no-obligation conversation: we'll start by listening, and if your project isn't a good fit for us, we'll tell you.
