← Back to homeCustom development

Software for operations that already work

I don't start from a template. I start from the process you already run, understand it, and only then build the tool it's missing.

Let's discuss your projectDirect reply, no forms in between
Who builds it

An engineer who has been on the other side

Software Engineer at Insight Delta, where I build products end to end: frontend architecture, AWS infrastructure and CI/CD automation.

Before that I spent over a decade in corporate B2B finance. I was the link between the finance team and the SAP consultants during the Tango to SAP migration at Lincoln Electric, and did it again at Agrofina. I know what it looks like when a new system collides with a process that already worked.

I trained as an electronics technician. The curiosity about how things work on the inside came before the software.

Current role
Software Engineer, Insight Delta
Years in development
03
Years in B2B operations
10
Base
Buenos Aires, AR
Capabilities

What I build

Scope defined together before the first line of code.

Custom web applications

Internal tools and customer-facing products built on React, Next.js and TypeScript. Designed for the real workflow, not for a demo.

Integrations and migrations

Connecting systems that were never meant to talk to each other. Hands-on experience with ERP migrations and working alongside functional consultants.

Process automation

Finding the repetitive manual work inside a team and replacing it with software. The diagnosis is part of the job, not an add-on.

Infrastructure and deployment

Production setup on AWS with CI/CD pipelines in GitHub Actions. Frequent, reversible releases instead of one risky launch.

Testing and quality

Automated coverage with Vitest, Jest, Testing Library and Cypress. The goal is a system that keeps working when nobody is watching.

Maintenance and continuity

Documentation, readable code and an orderly handover. An external supplier should never be a single point of failure.

How I work

The process

Four stages. Each one gives you something concrete to review.

  1. Discovery

    I learn the current process from the people who run it every day. Output: a document with scope, assumptions and what is explicitly excluded.

  2. Proposal

    Fixed scope, timeline and cost. No open items, no estimates that get revised upward later.

  3. Build

    Reviewable partial deliveries. You see progress on something that runs, not on a status report.

  4. Delivery and support

    Production rollout, documentation and an agreed support window. Ongoing support afterwards if you need it.

Tooling

Technical stack

Frontend & Mobile

  • React
  • Next.js
  • TypeScript
  • Tailwind CSS
  • React Native

Backend & Cloud

  • Ruby on Rails
  • AWS (S3, CloudFront)
  • CI/CD
  • GitHub Actions

Testing & Quality

  • Vitest
  • Jest
  • Testing Library
  • Cypress

Got a process that needs software?

Tell me what's happening today and we'll assess it together. If I'm not the right fit, I'll say so.

Message on WhatsAppSee my full background →