A business application filling the frame: a kanban board of cards beside a bar chart.AI-generated

Odoo

Seven years inside Odoo, building for its customers

Seven years building Odoo for Odoo's own customers: custom development, upgrades, large rollouts, and the teams I led and trained along the way.

Client
Odoo SA, employed and then as a subcontractor
Role
Developer, then team lead and tech lead
When
August 2019 to July 2026

The situation#

Odoo's own services team takes the implementations where the standard product does not fit the customer's business. I worked in it for seven years, employed at first and then, from the founding of avanserv, as a subcontractor. The customers were Odoo's, not mine, which is why none of them is named here.

  • 100+

    Odoo projects delivered, a career total rather than a tally

  • 20+

    upgrades between Odoo versions

  • 10+

    trainings on Odoo development, for customers and partners

What I did#

Most of the work was custom development: the modules that close the gap between what Odoo does and what a given business needs. Then the upgrades, more than twenty of them, carrying a customer's data and customisations from one version of Odoo to the next.

As a team lead I ran a group of up to ten developers, reviewing their code and releasing it to production. As a tech lead I carried the technical decisions for teams of up to eight on a single project. The largest of those projects served hundreds of users and went live in several phases, each one a rollout of its own.

On those projects the work went past the code. I ran performance analyses and load tests before go-live, so a system that worked for ten testers would also hold under hundreds of users, and deployed Odoo both on Odoo.sh and on customers' own servers. Along the way I trained customers and partners on Odoo development, more than ten times.

What the figures rest on#

My own record. None of it can be rebuilt from a system I still have access to, so every figure is a floor with its plus sign, an order of magnitude rather than a count.

Start with the problem, not with the proposal

A written scope comes back within two working days, with its assumptions and its exclusions stated. It costs nothing, and it is yours whether or not you hire me.

Tell me about your project, or the problem you want solved.

Or write to info@avanserv.com, and I will come back to you with a scope.