MP-i · Mattieu Pottier
Process engineering, Odoo, geospatial data. And when the tool does not exist, I publish it: an open-source mapping library on npm, and a suite of Odoo modules for tracking geolocated equipment.
For businesses and public bodies: you work with me directly, from scoping to implementation.
Work carried out for
The problem
In most organisations there are two worlds: the office and the field. On one side, purchasing, stock, invoicing, hours: that is the ERP, and it is kept up to date. On the other, maps, plans, surveys, interventions: they live in spreadsheets, notebooks and the memory of two people.
The two worlds do not talk to each other. It is not negligence, it is an absence: the software on the market places these two domains side by side, it does not integrate them. You buy a GIS next to the ERP, and you copy data across.
I ran into this wall while running a mapping company in Réunion. I found it intact when deploying an ERP from scratch at a modular building manufacturer. That is when I stopped working around it.
A tool configured on a vague organisation produces a vague organisation, only more expensive.
Where it starts
They almost always overlap. A badly framed process becomes a badly configured Odoo; a badly segmented asset base produces a tool nobody opens.
What I publish
Two products, two licences, two audiences. The second is built on the first — which is why they hold together.
A whole mapping application is defined by one JSON profile. Edits made offline are recorded, then replayed. What the page loads at startup is measured and capped.
| Licence | MIT, no exceptions |
|---|---|
| Package | @geoleaf/core 3.4.0 |
| Repository | github.com/ |
| Engine | MapLibre GL JS 6 |
| Runtime | 100% frontend, no backend required |
Every geolocated business record becomes viewable and editable on a map, inside Odoo. Maintenance management (CMMS) is the flagship: equipment, interventions, public reporting, inspection rounds.
| Licence | OPL-1, proprietary |
|---|---|
| Scope | 15 modules for Odoo 19 |
| Core | GeoJSON REST API, Publisher pattern |
| Integration | standard add-ons, no fork of the core |
| Database | PostgreSQL, PostGIS optional |
Not yet published on the Odoo Apps Store, and no public pricing. The demo runs on a test instance: I give named access on request.
In the field
Diagnosis of Réunion's street lighting network, a tender won as part of a consortium. My share: the GIS component.
Recovery of the existing inventories, structuring of a light-point register that several contractors could work with, integration of the field surveys, production of the map deliverables.
A diagnosis is there to decide on a works programme: the register has to live on after the report is handed in. The street lighting vertical of GeoLeaf Suite was born from this engagement.
A manufacturer of industrial modular buildings. An Odoo instance to implement, then to keep running over time.
Implementation and administration of the instance for twelve users. A single trigger, the signed quote, for the whole chain: project, purchasing, manufacturing, stock, invoicing, after-sales.
The project is created with its thirty-one tasks, and each job's income and expenses feed a single dashboard. Not one line of custom development.
Method
Not the procedure: the workaround. The double entries, the unofficial file, the export that gets redone every Monday. That is where the real process is.
Who does what, in which order, with which data. The rules get written down, exceptions included — they are what derails tools.
Documentation and handover are part of the engagement, not an option. A process that only the consultant understands does not exist.
Who I am
Mattieu Pottier. From 2018 to 2023 I ran a mapping solutions company in Réunion, working on territory and network projects. There I designed an equipment tracking tool on QGIS, and wrote the first version of GeoLeaf.
I set that observation aside for a few years and went back into employment, notably to deploy an ERP from scratch at a modular building manufacturer. That spell confirmed two things: the problem is still there, and it is sharper still in industrial and construction settings, where most of the value is created away from the desk.
MP-i grew out of that repeated observation, in August 2025. Not one more developer, not a pocket-sized IT services firm: someone who designs, decides, writes the code when it is needed, and hands it over.
Businesses and organisations only.
Questions
A few lines about your context are enough to start. I reply within 48 hours, in English or French, and tell you whether I am the right fit for your project.