Opaque technical risk
Nobody can explain what the system contains or what would break under change, a sale, or an audit.
Technical audit · Legacy migration · Modernization
Hugo Teijiz
I analyze, stabilize, and modernize critical platforms so they can evolve, raise capital, or change teams without stopping operations.
WhatsAppI do not start by rewriting. First I understand what the system contains, what risk it carries, what logic must be preserved, and the safest transition.

The person to call when business-critical software needs to be audited, rescued, modernized, or migrated without freezing growth.
I work with systems that became business-critical — whether they belong to a startup or a large organization.
Audit, stabilization, modernization, and migration of software that sustains operations, revenue, or compliance.
Nobody can explain what the system contains or what would break under change, a sale, or an audit.
The business must evolve, but every release costs more and fear of breaking production freezes progress.
The vendor, CTO, or only developer who understood the code left.
The technology data room is missing — or will surface findings that stall the deal.
The Legacy Risk Scan is a paid engagement with a defined scope. Pricing depends on size, criticality, and how many systems are involved. Investment is confirmed after an initial conversation. Engagements from USD 1,500.
A clear ladder from diagnosis to program — without selling generic hours or factory capacity.
Entry point to size risk and define the next step with evidence.
For investment, acquisition, vendor change, takeover, or modernization planning.
Retain, retire, rehost, replatform, refactor, or rebuild — with sequence, risks, and transition plan.
Bounded intervention on a representative module, flow, or API to estimate the full program.
Waves, strangler, coexistence, and controlled cutover — no blind rewrite.
Fractional CTO to govern architecture, vendors, roadmap, and transition.
How I work
I understand the system, the business, the urgency trigger, and the real cost of failure.
Inventory, dependencies, risks, documentation, and what the code actually does.
Retain, retire, rehost, replatform, refactor, or rebuild — without rewrite dogma.
Waves, coexistence, tests, cutover, and rollback with operational continuity.
When needed, continuous technical leadership until the change stabilizes.
Only experiences with verification and permission are published. Collabai appears as evidence of decision systems and applied AI — not as migration, and not as a lead destination.
Ministerio de Justicia / DNRPA
Experiencia liderando y evolucionando sistemas públicos críticos en el Ministerio de Justicia y la DNRPA, en contextos donde continuidad operacional, trazabilidad, integración y transformación digital eran requisitos centrales.
Role: Responsabilidad técnica (Senior Technical Manager / liderazgo técnico)
VEMO
Productos digitales de escala con ejecución cross-functional.
Role: Engineering Manager
SportManager
Experiencia construyendo, operando y evolucionando durante años una plataforma deportiva utilizada en Latinoamérica, enfrentando decisiones de arquitectura, producto, integración y continuidad.
Role: Cofundador
Neta México
Startup mexicana de alto crecimiento.
Role: Construcción de tecnología 0→1
OrkestCloud
Plataforma SaaS diseñada para integrar y modernizar procesos operacionales de empresas, incluyendo ventas, compras, stock, administración y reporting.
Role: Founder · arquitectura de plataforma y producto
Collabai
Producto propio de decision systems.
Role: Founder
Evaluación de migración legacy sin frenar el producto
Caso metodológico anonimizado: evaluación de migración de una aplicación legacy sin frenar la evolución del producto ni la operación del negocio.
Role: Evaluación técnica / definición de camino
Takeover y estabilización de sistemas existentes (genérico)
Experiencia evaluando arquitecturas, tomando control de sistemas existentes y definiendo planes de estabilización, evolución y modernización.
Role: Evaluación y dirección técnica
In an initial 30-minute conversation we review context, criticality, the urgency trigger, and whether an assessment is a fit. You do not need to share code or confidential information at this stage.
Audit, migration or transformation: the right format depends on stage. We start by understanding the real system.
In an initial 30-minute conversation we review context, criticality, the urgency trigger, and whether an assessment is a fit. You do not need to share code or confidential information at this stage.
WhatsApp