business-architect + tech-enthusiast + ai-native
building the ai others only announce.
ceo vision. cto depth. radical clarity in between.
most founders and ctos speak two different languages. i merge them — so the product roadmap, the hiring plan, the technical architecture, and the story the market hears all point the same direction. less keynote. more shipped.
Companies don't fail from bad ideas. They fail from frozen execution. I thaw it, fix it, ship it. Fifteen years of transforming ailing business models into digital, compounding growth engines.
While others ran workshops, I built Germany's most efficient fully-automated AI content distribution system. AI-native before the term was marketing. Models in production. Not on slides.
Invented infinite scroll (2015) — 12× PI lift, copied by everyone three years later. Build what doesn't exist yet. The best engineers don't optimize the current state — they retire it.
CEO at mi media intelligence SL in Palma — a dedicated AI, cybersec, and cloud venture. Because secure infrastructure and a clear narrative are the same skill on different axes.
Fifty internal, forty external, €7.5M revenue. Sales, marketing, tech, narrative, people — all under one responsibility. No hand-offs, no excuses, no "that's another team."
I don't write decks. I don't sell opinions wrapped in frameworks. I walk into the rooms where clarity has died and everyone's still talking — and I build the way out. Strategy and execution are the same discipline. Code and management are the same problem. When a crisis hits, most advisors flinch. I don't. I restructure, I architect, I ship — whether it's a codebase or an entire company. No committees, no consensus theatre, no asking for permission. These are the five situations where people stop looking for consultants and start looking for me.
FinOps is architecture, not a dashboard. I audit your workload topology, right-size compute, consolidate the zombie SaaS stack, and reset the deploy patterns that keep burning money. Usually saves 30-50% in the first quarter without touching roadmap velocity.
Breach response isn't forensics — it's narrative engineering under fire. Who knew what when, what's still exposed, what's already contained, and what the post-mortem answers before the board asks. I've sat in those rooms. Technical truth, executive language, zero theatre.
Every failed AI rollout I've seen traced back to data infrastructure, not model choice. I rebuild the pipeline first — ingestion, governance, quality gates, observability — then the model layer. Takes 90 days. Unlocks everything downstream for the next five years.
Quadrupling headcount without quadrupling chaos requires platform teams before feature teams, a documentation culture before bureaucracy, and senior hires that multiply rather than replicate. I've done this twice. The ones who got it right stayed fast. The ones who didn't are still untangling.
Blind microservices migration is the worst outcome. I map business boundaries to architectural ones — strangler-fig, not demolition. We carve out the high-leverage seams first, keep the monolith running where it works, ship the new bet without a two-year rewrite. Revenue doesn't pause for refactors.
/// something on this list looks familiar?
talk to me04 / principles
principle / 01technology is the only thing that scales faith. build more of it.
principle / 02delivery is the argument. everything else is commentary.
principle / 03authority flows from running code. not from slides, process, or permission.
principle / 04the state lags technology by a decade. build for the decade after. not the one behind.
principle / 05sovereignty is downstream of capability. build capability. the rest follows.
