About
Hi, I'm Andrés.
I've spent my working life between two worlds people usually keep apart: the physical one, where problems are messy, expensive and human, and the digital one, where they finally get sorted out properly.
I grew up in Venezuela, where you learn early that the answer is rarely more resources — it's paying attention. You solve what's in front of you with what you actually have. That habit stayed.
In the United States I started on site: walking properties, assessing damage, reading moisture, documenting what I found and defending those files afterwards. Work where being wrong costs someone real money. Later I coordinated the operations around that work, and something became impossible to unsee: almost none of the failures were technical. Nobody was writing down what was actually happening.
So I stopped patching processes and started redesigning them. Then I started building the software they needed. Today that lives in Optimus Reframe, where it turns into products, and in Labs, where the unfinished ideas stay honest.
What each stage taught me
Five stages, and what each one changed in how I work.
It's not a résumé. Each stage removed a specific way projects tend to go wrong.
- 01
On site
Inspection, damage assessment and on-site documentation.
I'd rather go see it than design around something I only heard about.
- 02
Operations
Coordinating teams and files where a bad process shows up the same day.
I know what a team really does under pressure, not what the manual says.
- 03
Process
Redesigning how the work flows instead of stacking another tool on top.
Automating something broken only makes it fail faster.
- 04
Product
Working software in short cycles, used by the people it's for.
Better to see something usable early than a demo at the end.
- 05
Ventures and Labs
Optimus Reframe and a lab of things built and maintained end to end.
Living with your own decisions after launch changes what you decide to build.
Next step
If any of this sounds like where you are, tell me about it.
I've been the person doing the work, the person coordinating it and the person building the tool. Each of those roles sees something the others don't. A short exchange is usually enough to know whether I can help — and I'll tell you honestly if I can't.