Leonel Guillén

This page exists for a practical reason: when you are evaluating an ERP implementation, what matters most is not the consulting firm's logo but who will be on the other side of the table. Here is what you get.

What I do

I implement Odoo 19 Enterprise at midsize companies and develop the modules the standard product does not cover. In practice that means two different jobs: a consulting one — understanding how a company really operates and translating that into a system — and an engineering one — writing, versioning and deploying the code that supports its specific rules.

I don't separate them, and I believe that is where a good part of the value lies. A consultant who doesn't code doesn't know what is expensive to build. A developer who doesn't map processes builds what he is asked for instead of what is actually needed.

The idea that drives everything else

That is where the methodology comes from: the implementation aligns the processes to the system and, at the same time, builds the information layer management needs. They are not two projects; they are one.

What I've built

Proprietary modules running in production at clients in Costa Rica and Panama, including:

• Discount and pricing policy control with margin-based approval.
• Costa Rican payroll with social security contributions, accruals and compliance reports.
• Order picking boards for warehouses with high line volumes.
• Credit and delinquency control with invoice holds.
• Consistent fiscal document numbering and journals per branch.
• Direct thermal printing for dispatch, counter and point of sale.
• Cross-company validations for multi-company groups.
• Conversational agents on top of ERP data.

Everything is deployed through Git, with test environments separate from production, and with the code in the client's name.

Where I come from

I hold a master's degree in IT Systems Management. Before focusing on Odoo, I worked in banking as a cybersecurity engineer, where I led the implementation of a third-party risk management product, and at DICORA, a multinational operating in five countries. I also have a background in higher education.

That mix explains a bias I own up to: I care about traceability, permissions and auditing more than is usual in ERP projects. In a system that moves money and inventory, knowing who did what and when is not a luxury.

How I work

1. Process first, system second. Process discovery with the people who do the work, not with the manual.
2. Disciplined scope. I say no to a good part of the initial wish list, and I explain why.
3. Configure before coding. What Odoo already handles doesn't get developed, even if it means changing a habit.
4. Build, then validate. I'd rather have something working to review and correct than a perfect specification nobody has seen on screen.
5. Be there for the first month-end close. That is when what no test catches shows up.

Certifications

In the press

Direct contact

Email: leo@erplexia.com
WhatsApp: +1 (305) 404-5230

If you want to come in with an idea of the project size, start with the calculator.