S/01
Tech Advisory
I sit down with your team and we decide architecture, stack and priorities. The right call before a line of code gets written.
CTO @ Helipagos · Tech Advisor · AWS & AI
For the owner, founder or manager who has to decide with no technical person they trust: in three weeks I tell you what you have, what’s missing and in what order.
01 / Career
I lead a team of 10 —eight in development and two in operations— across POS, Wallet as a Service, Payments Core, Operations and AI & Automation: technical direction for each product, budget, priorities presented to the Board, and AWS infrastructure as the team's FinOps. I also led the organisation's information security framework, aligned with the requirements of Argentina's central bank.
Remote web development classes for the Misiones tech ecosystem.
Defining the technology roadmap before taking over technical direction of the team.
Project management and development inside the product team. From planning to writing the code.
A year teaching development and technical fundamentals to bootcamp cohorts. The Knowledge Hub comes from there.
Digital products for clients across LATAM. Technical mentoring and strategy for early-stage founders.
02 / Decisions
This is not consulting work for a client: it is what I did and am doing as CTO of Helipagos, a payments fintech. It is where you best see how I decide.
03 / Services See packages →
S/01
I sit down with your team and we decide architecture, stack and priorities. The right call before a line of code gets written.
S/02
Design and implementation on AWS — right-sized, observable and with costs under control from day one.
S/03
Infrastructure as code with Terraform and Ansible, CI/CD pipelines and reproducible environments. So deploying stops being scary.
S/04
Where AI moves the needle in your product — and where it’s just noise. Pragmatic implementation, not a demo.
04 / Articles See all →
Un agente es un while alrededor de la API donde el modelo elige la próxima acción. Un workflow tiene las aristas escritas por vos. De esa diferencia mecánica salen los cuatro criterios para decidir, los cuatro tiers de arquitectura, y por qué elegir bash o una herramienta dedicada es una decisión de control.
Promover el mismo artefacto inmutable a través de los ambientes, en vez de reconstruirlo en cada escalón, es la decisión de la que se deducen todas las demás: dónde vive la configuración, qué paridad importa, qué no se puede promover y cuántos ambientes valen lo que cuestan.
AWS construyó la nube como una jerarquía de fronteras físicas de aislamiento y puso un medidor de facturación en cada cruce. Región, cantidad de zonas y camino de salida son tres decisiones de presupuesto disfrazadas de decisiones técnicas, y las tres tienen precio de lista.
05 / Projects
06 / Teaching & Education