Implementation and setup
Odoo ERP and CRM set up around your processes, not the other way
round: sales, stock, invoices, the website. I start from what has
to happen every day and stop when it happens.
A first implementation for a team of ten takes weeks, not quarters.
The scope is written down before the work starts, and what is
outside it is named out loud rather than discovered later.
Odoo implementation in detail
Migration between versions
From any version to any newer one, with your data and your own
modules. The whole run happens on a copy first: what breaks is
fixed in code, not worked around by hand on the live system.
The live move is scheduled only once a rehearsal has become
boring - known duration, known steps, a way back at every point.
Odoo migration in detail
Custom development and complex workflows
The part most integrators walk away from: a workflow that does not
exist in the box, an integration with a system nobody has an adapter
for, a module that has to survive the next version upgrade.
I write Odoo modules rather than click them together - code that is
still readable a year later, with migrations and tests where they
earn their place.
Odoo development in detail
Performance: when Odoo gets slow
Slow queries, a catalogue search that takes seconds, a front end
heavy enough to show up in Core Web Vitals. First measured on your
own data, then fixed where the measurement points.
You get the numbers before and after. If the honest answer is that
the hardware is the limit, that is the answer you get.
Odoo performance in detail
Rescue of a stalled project
A migration quoted at six months and stuck at month nine. A system
that slows down as the data grows. A contractor who left and took
the knowledge with them.
I start by measuring - slow queries, heavy front end, the database -
and then say what is worth fixing and what is worth rewriting, with
the numbers before and after.
Project rescue in detail