CTO @ Helipagos · Tech Advisor · AWS & AI

You sign off on it. I tell you what it costs and what breaks.

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.

See services and pricing
10 Engineers led
4 Concurrent projects
3+ Years running AWS in production
+60 People trained

01 / Career

Five years building, deciding and teaching.

  1. 01 Jan 2025 → present Current

    CTO · Helipagos

    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.

  2. 02 Jul 2026 → Dec 2026 Current

    Web Development Instructor · Silicon Misiones

    Remote web development classes for the Misiones tech ecosystem.

  3. 03 Dec 2024 → Jan 2025

    Technology Innovation Manager · Helipagos

    Defining the technology roadmap before taking over technical direction of the team.

  4. 04 Mar 2023 → Dec 2024

    PMO & Developer · Helipagos

    Project management and development inside the product team. From planning to writing the code.

  5. 05 Apr 2022 → Mar 2023

    Instructor · Digital House

    A year teaching development and technical fundamentals to bootcamp cohorts. The Knowledge Hub comes from there.

  6. 06 2019 → present Current

    Tech Advisor & Freelance · Own projects

    Digital products for clients across LATAM. Technical mentoring and strategy for early-stage founders.

02 / Decisions

Three things I changed as a CTO.

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.

  1. 01 Measured

    The checkout that took two days

    The problem
    Handing a new client a custom checkout was manual work. Two business days from the moment they asked to the moment it was running.
    What I decided
    Rebuild it as Checkout v2 and move the customisation inside onboarding, instead of treating it as a separate request somebody had to pick up.
    What changed
    Five minutes, and the client does it alone. In production since December 2025.
  2. 02

    Every microservice against the same database

    The problem
    Each microservice connected to one shared database. That couples everything to everything: the schema cannot be touched without coordinating with every team, and isolation between domains exists on the diagram but not in practice.
    What I decided
    Segment by product domain rather than by service. Each domain with its own data, and dependencies written down instead of inherited.
    What changed
    Under way. The slowest of the three, because it is done without stopping the business.
  3. 03

    Shipping to production was an unknown act

    The problem
    Deploying was not part of the day, it was an event — and one nobody could fully predict until it was over.
    What I decided
    Build and review pipelines, validation in pair programming, and moving the team to trunk based. Alongside that, raising the quality of how work is written up — without it, a pipeline only tidies up an existing mess.
    What changed
    Going to production became a normal, controlled, everyday process.

03 / Services See packages →

What I’m good at — and why you should ask me before you start.

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.

S/02

Cloud & AWS

Design and implementation on AWS — right-sized, observable and with costs under control from day one.

S/03

IaC & DevOps

Infrastructure as code with Terraform and Ansible, CI/CD pipelines and reproducible environments. So deploying stops being scary.

S/04

Applied AI

Where AI moves the needle in your product — and where it’s just noise. Pragmatic implementation, not a demo.

See packages and pricing

04 / Articles See all →

Opinions I can defend.

05 / Projects

Things I built, or am building.

06 / Teaching & Education

I also teach. For teams that want to raise the collective floor.

A blocked project, a hard technical call, a team without direction.