Operator,
not programmer.

I run and grow a small portfolio of companies. Real businesses with customers, payroll, returns, and quarterly taxes. The largest one is a B2B packaging company in southern Spain. The others span different sectors, all small enough that I can keep my hands on the operating decisions.

Owner-operating multiple things at once forces a particular discipline: I can't be the bottleneck of everything. In 2025 I rebuilt my workflow around AI and a small set of internal tools — out of necessity, not theory. The only way to do more without hiring a layer of managers is to delegate to agents that already understand my context.

I work with an AI-assisted setup of my own — built piece by piece because the work required it, not because the tools were fashionable. It's what runs the portfolio in production, not a thesis about it.

How I decide

Patterns distilled from years of operating calls:

1. Speed > perfection. Ship, measure, iterate.
2. Infrastructure first. Foundations before features.
3. Centralization when you're solo. One hub, one system, one control surface.
4. Own tools > SaaS when I can build it with what I already have.
5. Operational simplicity > raw power. Boring infrastructure before clever infrastructure.
6. Asymmetric bets. Low cost of being wrong, high upside if right — I try it.
7. Cut and reallocate > repair by inertia. If it doesn't perform, the budget moves to what does.

Where I work from

Physically based in southern Spain, but the businesses operate across Spain, Portugal, and the wider EU. I work in English, Spanish, and French depending on the counterparty. The market doesn't care where I sit — it cares whether the email gets answered and the pallets ship.

What I'm not

Not a career programmer. Not an agency. Not a productivity coach. I don't sell courses, and I don't take consulting clients in the generic sense. Open to thoughtful conversations with operators and investors who want to swap notes — my email is here.