Designer first.
Founder by temperament.
I started as a graphic designer in Monterrey and spent a decade running my own studio before the word "product" was on anyone's business card here. Somewhere along the way I noticed the projects I loved weren't the prettiest ones. They were the ones where something measurably changed for the people using them.
The short version
Fifteen years in, my career reads like three careers that turned out to be one. The design years taught me craft and how small businesses actually make money. The founder years taught me unit economics the way only your own bank account can, and ended with an acquisition. The product leadership years put me inside a global industrial company, owning the logic of a platform where close to 30 factors decide whether a truck full of concrete shows up on time, and eventually leading the other product managers who worked on it.
Now those threads run together. I build my own AI-native products end to end, and I bring founder-level ownership to product work for teams I believe in. I'm the person who reads the support tickets, sketches the flow, questions the query plan at a product level, and still cares which word goes on the button.
What I believe about products
Most software fails socially, not technically. It asks people to change their habits to serve the system. The products I admire flip that: they earn their data as a byproduct of something the person wanted to do anyway. That belief shows up everywhere in my work, from a pantry that updates itself when you cook to an ordering platform that got to 85% adoption because we stopped arguing with the people who refused to use it and started listening to them.
I also believe honesty is a product feature. Recommendations should explain themselves. Metrics should survive a hostile interview. And a founder who can't tell you what would make them kill their own idea isn't being brave, just loud.
How I work with AI
Since 2026 I've run my solo product work like a small organization where the teammates happen to be AI agents: written specs, locked decision logs, adversarial cross-model reviews before anything merges, and a canonical source of truth that outranks memory. It's not about speed for its own sake. It's that the discipline which makes AI agents reliable, clear specs, explicit constraints, honest audits, is the same discipline that makes human teams reliable. Building this way has made me a sharper product leader for both kinds.
yes, the chess rating is real. no, I will not tell you what it is until move 20Off the clock
I'm an amateur chess player with a rating I'm proud of and a blitz habit I'm not. Chess and product management reward the same muscle: calculating a few moves deeper than feels necessary, and resisting the flashy move that loses quietly eight turns later. I live in Monterrey, Mexico, work happily across time zones, and cook more ambitiously than my pantry app strictly requires.