Building is the easy part.
The hard part is deciding
what to build.

Will I make it to the end of the month?

I kept my finances in a spreadsheet. It worked, but logging every expense was such a chore that I kept putting it off, and the number stopped being true. No app offered what Argentina needs: installments, two currencies living together and a credit card that closes one month and is due the next. The goal was a single one: make logging an expense easy, and let the question answer itself.

1. 01
   Log without frictionAdd an expense by voice or in two taps. If logging is a chore, the app dies.
2. 02
   Built for ArgentinaInstallments, pesos and dollars, and the card with the bank’s real dates, not a calendar month.
3. 03
   One answerThe whole design points to one number on the home screen: how much you have left until the end of the month.
4. 04
   Design by using itI was the first user, every day; every screen was adjusted with real use, mine and my friends’.

In production at michanchito.net, iterating on what people find when they use it.

How do you change the campus without stopping the school?

Escuela Técnica ORT runs a virtual campus with 20,000 active users that cannot be switched off: every school year depends on it. It needed modernizing, a new platform, and a team that worked without a process needed order. I joined as a frontend developer and ended up designing screens, defining product and coordinating the team.

1. 01
   Coexist before replacingThe new grows next to the old campus, module by module, with no big-bang migration.
2. 02
   Design and buildI co-designed the campus design system and built the self-learning platform end to end.
3. 03
   Propose the missing roleI put the Technical Project Manager role in writing and took it on: coordinator, not boss.
4. 04
   Process and specsSprints, a backlog by epics and screen specs with the decisions made before drawing.

Four years on the campus: from code to deciding what gets built and how.

Who remembers what happened on Tuesday?

Ten projects, a job, a studio and an AI that starts every session with no memory. The context lived in my head and in scattered chats, and every agent I asked for help started from scratch. I wanted a system that held the context for me, without turning me into its administrator.

1. 01
   One source of truthA plain-text vault, versioned, read by people and agents alike.
2. 02
   Rituals instead of featuresA morning briefing, an evening close, a weekly review: cadence, not willpower.
3. 03
   An agent that lives on a serverIt runs on its own, with the PC off, and talks to me over Telegram.
4. 04
   One method for every repoEvery work session opens and closes reading and writing the same state.

It changed my role: less code by hand, more defining what to build and directing agents. This portfolio was built that way.

Two businesses under a single brand?

Naty is a visual artist and tattoo artist: she sells original work and books tattoos, and both live mixed together on the same Instagram. She needed a brand that held both, a shop where the work looks the way it is and a way to book without going back and forth over chat. A real client, with opinions, and no experience running a site.

1. 01
   Two universes, one domainShop and studio with a shared botanical identity: fine lines, sage and cream.
2. 02
   System before screensTokens and components in Figma, so everything added later comes out the same.
3. 03
   The work rulesEvery piece is shown in its real proportions; nothing gets cropped.
4. 04
   A panel for herProducts, orders, shipping and galleries, managed on her own, from her phone.

In production and still being built with the client: the final domain and her content are pending.