The same five steps on every Odoo project, from the first call to the support window after go-live.
Before any code, I want the process behind the request — who touches the record, what breaks today, and what 'done' looks like to the person doing the job.
Models, fields and access rules on paper first. Deciding inheritance versus a new model early is what keeps the upgrade path open later.
Backend logic first, then the OWL layer over it. Each piece lands working rather than arriving as one large drop at the end.
A module that works on two demo records is not tested. I run it against a copy of the real database, with the real volume and the real edge cases.
Deployment on Odoo.sh or your own instance, plus the documentation another developer needs to pick the module up without asking me.
Installable, versioned, and written against the Odoo API rather than around it.
What it does, which models it touches, and what to check first when it misbehaves.
Groups and record rules listed explicitly, so nobody has to guess who can see what.
Proven on a copy of your data before it goes anywhere near production.
Send me the process as it works today and I will come back with a scope.