The short version

I grew up in Mexico City. Went to boarding school in Chicago at 15, came back, finished the IB program at Tec de Monterrey, and eventually studied Business Intelligence with a minor in AI at the same university. Somewhere in between I spent a semester at a design school, studied philosophy at the Ibero, and did an exchange in Cologne.

None of it followed a straight line. I kept changing directions because I kept finding things that interested me more than the last thing. That used to worry me. Now I think it's just how I work.

During a summer program at Stanford, I found myself surrounded by people who were constantly building. Not polished products — often ugly ones. Half-working demos. Ideas you could actually download, click, and break. Some of them were already raising small rounds. Others were just shipping because they could.

That environment changed how I thought.

Coming from Mexico, I had grown up with a clean separation: university was for learning, and work was for building. At Stanford, those two things were happening at the same time. People weren't waiting until they were "ready." They were learning by making things real. That realization stayed with me.

Around the same period, I read Hackers & Painters by Paul Graham, which put words to something I hadn't been able to articulate. I had a tendency to overthink ideas — redesigning them, polishing them, waiting for validation — until they turned into folders full of "what ifs." Good intentions, no launches.

So I tried doing the opposite.

Instead of asking whether something was good enough, I started asking whether someone could use it. I made a small pact with myself: build fast, ship early, and let users decide.

At first, I built web apps, because that's what I knew. Then I moved into iOS with Swift. Over time, tools like Cursor and Claude Code made the feedback loop even tighter, allowing me to move quickly while still staying deeply involved in product logic, structure, and decisions.

One project that sticks with me is a simple mobile game called Stacker Rush. I almost didn't publish it. It felt unfinished. A little embarrassing. Exactly the kind of thing that's easy to leave in a drawer. I shipped it anyway.

Today, a couple hundred people use it. That number wouldn't impress anyone in Silicon Valley, but it changed something for me. It proved that imperfect things in the world matter more than perfect ideas that never leave your laptop.

Since then I've shipped 12+ apps to the App Store, published two books on Amazon, built web platforms, and worked on everything from an AI-powered finance app to a connection game inspired by mindfulness. Some worked, some didn't. All of them taught me something.

Outside of building, I directed the INCrew at INC Monterrey — a team of 250 student volunteers behind LATAM's largest entrepreneurship congress. I also worked at DIDI doing data analytics across Mexico and Brazil, and spent time consulting for a digital education platform where I got to build the product from scratch.

More recently, I contributed to a digital platform for the Government of Alvaro Obregon in Mexico City, related to the 2026 World Cup — working across product, design, and public-sector stakeholders.

Most of what I've built so far has been done alone, which taught me speed, ownership, and how to live with uncertainty. Now I want to learn the next layer: how great teams actually work. How founders think together, raise capital, make decisions under pressure, and scale ideas beyond a single builder.

I'm looking to work with high-agency people — the kind who move fast, take ownership, and aren't afraid to jump into uncertainty. I work best when I understand the purpose behind what we're building. I'm not a "do this because I said so" person — I'm a "this matters because of X, so I'll volunteer to help make it happen" kind of teammate.

That's the story so far. It's still being written.