As an independent Odoo expert, I scope your needs, configure the platform as close to your business as possible and get you live fast, without overengineering. Then I hand over, so the tool keeps growing without depending on me
Odoo is a great platform, but an ERP is only as good as the way it's set up. Get the configuration wrong, and you inherit an overengineered system nobody uses. Get it right, and you finally have a tool that keeps pace with your business instead of slowing it down
That tipping point is exactly what I do. I'm an independent Odoo expert and project director, and I lead Odoo projects in France, the USA, Canada, Switzerland and Italy, remotely or in a hybrid setup, with travel possible. Whether you're starting from scratch, from a spreadsheet that's bursting at the seams or from an ERP at the end of its rope, I take ownership, I lead, and you move forward
No oversized team, no project manager relaying what someone else did. The person leading the project is also the one with their hands in the database
Ship a working tool fast, without overdoing it, then grow from there
I push native Odoo and no-code Studio as far as they'll go before considering anything heavier. That's what spares you technical debt and unnecessary costs. On top of that, Studio customizations are carried over automatically with every version upgrade
A v1 that lets you work from A to Z, with no blockers in your daily flow, but without overengineering. We don't get lost in tiny details and we don't hook Odoo up to eight external tools just for the fun of it. Just what you need to get started
Once you're live, your teams surface the real needs. The onboarding phase becomes my adjustment phase. I don't build anything I consider oversized until actual use has proven the need
From the first meeting to the handover, a clear, well-paced process
One or more meetings to help you describe how you operate, simply and chronologically, from the salesperson looking up a prospect in the CRM to the after-sales team closing a request. Together we fill in a who does what, then what, then what table. That's my raw material
I open the database and configure the general settings, then spend 3 to 4 hours with your accountant to get everything right: payment terms, taxes, overheads, banks, product categories. Your foundation is clean from the start
I prepare import templates for your products and contacts, and load them into the database. From there, we have real material to work with, on a foundation that already has its minimum configuration
I go through your process point by point and configure native Odoo, or build the Studio customizations needed, to fit your daily operations 100%. No more, no less. The goal: an early migration date, sometimes just a handful of weeks if the project keeps a good pace
Your teams get up to speed on a tool that works. This onboarding phase is also my phase for adjustments and additional customizations, driven by real user feedback. We move forward step by step, in a practical, hands-on way
The end of the project and who takes over are set at scoping. I train your internal team or your future provider, your processes are documented and kept up to date by your teams, then I pass the baton. The tool keeps growing, without depending on me
The heart of Odoo is sales and accounting management. We start there, and expand block by block
CRM, Sales, Purchase and Accounting form the backbone. I know the accounting side inside out, as well as working with accounting firms: journal entry extraction, reconciliations, exports. That's where everything holds together
The Inventory module goes hand in hand with sales management. The Helpdesk module is a must-have: essentially a CRM clone for after-sales, extremely versatile for handling your customers' requests efficiently
On demand, the whole Project, Planning and Timesheets block, plus the HR side: Employees, Time Off, Expenses and approvals. We switch them on when your business needs them, not before
One of Odoo's big advantages is progressive deployment. Some of my clients start with Helpdesk only, just so their teams get their hands on the platform and build the habit. We widen the scope once the habit has stuck. Less resistance, more buy-in
Best to be clear from the start, it's what makes projects succeed
An aging Everwin-type ERP, with a heavy Citrix connection, no ability to evolve, a very limited scope of action and imprecise search. A tool everyone just put up with
An Odoo with some twenty modules, 100% web, rolled out in a few months. Strong team buy-in, huge gains in search, analysis and financial reporting, for an overall cost of around €50 per person per month over 3 years, customization included
Each situation has its own page. Find yours, and we'll start from there
You're starting from scratch, from a spreadsheet or from making do. We lay clean foundations, without overengineering
Discover the approach → Already on OdooA shaky database, an overengineered mess or a provider who left. I take back control and set it straight
See how → Just exploringBefore diving in, you just want to grasp what we're talking about. The simple, jargon-free overview
What is Odoo →Some needs come up often, they have their own page
Prospect follow-up, natively connected to your sales and invoicing
Learn more → 2026 complianceThe reform is coming. Odoo is a government-certified e-invoicing platform, and I configure your compliance
Learn more → OnboardingYour teams struggling with Odoo? Often, the real issue is the configuration
Learn more →There's no clear-cut answer, and anyone quoting you a firm price before seeing how your business works is either wrong or covering themselves by overestimating. An Odoo project is 100% tailor-made: take three competitors, and they'll end up with three different Odoo setups
I work on a day-rate basis, within a well-defined engagement: a budget of days, an adjustable pace and a duration of 1 to 12 months. I give you an indicative estimate based on past projects of similar scope, and invoicing follows actual time spent
I explain the cost logic here, and the day rate and engagement model there
My philosophy is to push standard Odoo and no-code / low-code Studio as far as they'll go before considering heavier, costlier solutions. What Studio can do is already huge
When a real business gain justifies it, I do build custom, but sparingly and in a controlled way. I show what's possible with Studio here
I work exclusively on Odoo Online and Odoo.sh, always on a recent version. I don't do on-premise, which I consider counterproductive, even risky, for an SME: my approach is 100% cloud, nothing exposed or to maintain on site
The goal is always to set a migration date close to the start of the project. If the project keeps a good pace and you're available for scoping, we're sometimes talking about a handful of weeks for a first go-live, even if it means enriching it afterwards
Yes. I work remotely by default, and on site when it makes sense, in France, the USA, Canada, Switzerland and Italy, with travel possible. For a 100% web ERP, this works very well. Whether you're in Paris, New York, Montreal, Geneva or Milan, I can lead your project without the distance changing anything about the quality of the follow-up
The engagement has an end, set at scoping, and a named successor. Before I leave, I hand over: to an internal team, which I can help recruit and then bring up to speed, or to a third-party provider who will handle operations
Your processes are written down, organized and kept up to date by your teams. I'm not here to create one more dependency, but to build something that runs on its own, once I'm gone
Whether you're starting from scratch or from a tool at the end of its rope, the first conversation is free and with no commitment