Hi, I’m Johann Rodríguez
Odoo Solutions Architect | Creator of Dr. Odoo
I’m a Systems Engineer with 18 years of experience as a software engineer, currently specialized as an Odoo ERP Solutions Architect.
I’ve worked with service and operations companies, as well as industrial organizations, across sectors such as Oil & Gas, Aerospace, Manufacturing, and Industrial Maintenance—helping them solve real problems through practical, well-designed solutions.
Under the Dr. Odoo name, I provide strategic and independent advisory services for Odoo implementations, with no affiliations and no conflicts of interest.
A Unique Perspective: I’ve Been on Both Sides of the Table
For years, I worked as an implementer and solutions architect at top-tier Odoo partners. I participated in complex projects and saw firsthand how the ecosystem operates from the vendor’s side.
Later, I made the move to the other side. Today, I manage Odoo from within a company, facing the real challenges that end customers deal with every day.
That dual experience allowed me to see something that rarely gets said out loud:
Clients are at an information disadvantage compared to implementers.
Dr. Odoo was created to rebalance that relationship. My role is to represent you —not a partner. I’m here to help you make decisions based on real information, with no conflicts of interest.
When clients make well-informed decisions, implementations are cleaner, and the client–implementer relationship becomes stronger.. Everyone wins.
Why I Work This Way: The “Dr. Odoo” Method, Built from Experience
Just like in medicine, every implementation requires an accurate diagnosis, a responsible prescription, and real support throughout the recovery process. I chose this analogy because it’s memorable—and because it reflects a reality I’ve seen repeated many times: many implementations end up wearing everyone down, damaging the client–partner relationship precisely when it’s needed most.
In Odoo Enterprise, the long-term relationship is critical. The system is updated every year, localizations change with each country’s regulations, and new opportunities for improvement constantly arise. A poor initial implementation doesn’t just fail in the present—it compromises all of that future potential.
🔍 Diagnose
I identify the root cause, not just the symptoms.
📋 Prescribe
I design the most effective strategy with you, free from commercial bias.
🩺 Fix
I stay with you until the results are sustainable.
No Anesthesia — With Respect for Everyone in the Ecosystem
Technical honesty is my policy. I don’t sell licenses, I don’t receive commissions, and I have no incentives other than making sure your system works properly.
In the Odoo ecosystem, everyone has interests: partners sell hours, and Odoo SA sells licenses.
I don’t sell either.
I collaborate with both when necessary, always from a position of technical independence and with a single goal: making your project successful.
I don’t implement Odoo, and I represent only your company.
If something doesn’t make sense, I’ll tell you before it turns into a problem.
My role is not to compete with partners, but to help make your relationship with them more effective and transparent.
I don’t sell licenses
I don’t receive commissions
No conflicts of interest
My latest content
Check out what's new in the Dr. Case Files.
Make decisions based on real information—not promises.
A technical second opinion can save you months of work and thousands of dollars.