← All expertise

05

Process analysis and ERP

Almost no ERP project fails for technical reasons. It fails because someone automated a process nobody had ever written down end to end, and the gaps show up in production.

The map first, the software after

The first step is reconstructing the process as it actually is: who does what, with which document, where data gets keyed in a second time by hand and where people wait for someone else. The bottleneck is almost never where the client thinks it is.

From there you design the to-be and — above all — decide what not to automate. A manual step that exists to make someone stop and check is worth more than a perfect flow nobody looks at.

Standard while it holds, custom where it counts

Odoo covers a great deal, and every custom module is code to maintain at each upgrade. My rule is simple: customise where the process is the client's competitive advantage, stay on the standard everywhere else.

When customisation is needed it lives in separate, versioned modules rather than edits to the core — that is what keeps upgrading possible.

Go-live without stopping the work

Separate environments for testing and production, database templates to start from a known configuration, data migration rehearsed several times before the real day, and a way back if something doesn't add up.

Analytical accounting is the part that pays off most: once costs attach themselves to the right job, margin per site stops being a year-end estimate.

Portfolio

What I did on this, project by project.

CocoonServer

Management platform for multi-customer Odoo instances

  • A console governing the environment lifecycle: create, start, upgrade, clone and destroy with explicit, traced semantics.
  • Per-instance backup and restore with verification and operation history.
  • Custom module and bundle management: upload, package validation and controlled installation on selected instances.
  • Database templates and environment export, so a new customer starts from a proven configuration instead of from scratch.
  • Activity log and audit of who did what, plus per-instance monitoring and logs.
  • Odoo
  • PostgreSQL
  • Kubernetes
  • Helm
  • Next.js
  • Prisma

ASC Buildings

Construction site access management wired into the ERP

  • Site access records flowing into Odoo and attaching to analytical accounting: attendance becomes cost on the right job, with no manual re-entry.
  • Analysis of the site process before development: who records what, when, and what must reach the back office for the data to be worth anything.
  • Odoo
  • analytical accounting
  • Flutter
  • Odoo API

ERP Next-Gen

Selective port of Odoo onto a TypeScript stack

Internal research: architecture completed, not in production.

  • Portability study of Odoo's base module towards NestJS and Prisma: a modular monolith with explicit boundaries and room for future extraction.
  • Multi-tenant foundation with Row-Level Security, cross-module side effects through events, and GDPR requirements taken as a design constraint (soft delete, anonymisation, audit trail, data export).
  • NestJS
  • Prisma
  • PostgreSQL RLS
  • RabbitMQ
  • Redis
  • MinIO

Need this?

Tell me the problem and I'll tell you how I would tackle it — and if it isn't worth doing, I'll tell you that too.

Let's talk