Case study
The ERP was the easy part
Telecomba supplies specialist telecommunications and networking equipment, with an Odoo deployment at the centre of how it runs. We started on site, gathering requirements, and the hard problems turned out not to be in the system's design but at its edges.
Mexican electronic invoicing is where a business system meets the tax authority, and it does not forgive approximation. Stamping failures, payment complements, credit notes, cancellations, withholding configuration, rounding differences — each one stops a real invoice for a real customer until somebody resolves it.
So that is what a year of the work was: case by case, beside the people raising the invoices. A recurring micro-support arrangement ran for months, which is not a ticket queue — it is sitting with the person who hit the problem that morning.
The point of that is to end it. The later work is training, so the client's own staff stamp credit notes and payment complements themselves, and then analytics: a reporting instance, dashboards, direct access to their own data. Support that never becomes capability is just a subscription.
What this record establishes
A dated record of the work itself, May 2025 to July 2026.
What it does not: No quantified improvement or fully verified implementation history is asserted; deployment and outcome evidence remains incomplete.
If this resembles your situation, the next step is a conversation about your specifics.
Discuss a similar projectEach case study describes a real engagement or venture, and states what its record establishes and what it does not. Clients and partners keep ownership of their own expertise, delivery and results.