I’ve spent more than a decade in IT — from L1/L2 support and a NOC, through product technical roles, and now leading corporate IT and AI adoption at a scaleup. Most of that work happens in private: in Slack threads, in runbooks, in tickets that close quietly. This blog is where some of it will happen in public.

What this blog is for

A few specific things:

Notes from running corporate IT in a scaleup. Real evaluations of real tools — MDM, identity, SaaS sprawl, compliance work. The boring infrastructure that makes everything else possible. The kind of post I’d send to a peer at another company who asked me a direct question.

Practical AI from the trenches. I’m formally responsible for AI adoption at Clarity.ai — not as a strategist, but as the person who sits with Finance, Operations, Marketing and HR teammates and helps them learn to use these tools with judgment. That’s a different kind of writing than most AI content online. There’s translation work to do, and not many people are doing it from inside operations.

Building on the side. A US LLC, a homelab on a Mac Mini, a small SaaS, a KDP business. The work I do outside the day job, when there’s time.

Working from a small place. I’m fully remote from Bollullos de la Mitación, a town of about 10,000 people in Sevilla. That detail doesn’t drive the content, but it shapes it.

What this blog isn’t for

Not a lead funnel. No PDFs to download in exchange for your email, no “12-week roadmap” CTAs, no consulting page. If that changes someday, it’ll be because the writing earned the right to it — not the other way around.

Not AI thought leadership. The internet has enough of that. What I want to write about is what actually happened — including when it didn’t work.

Not a content schedule. I’ll publish when I have something specific to say. If that’s three posts a month, fine. If it’s one, also fine.

What to expect

Most posts in English. Some in Spanish at /es/, when the topic genuinely calls for it — Spain-specific stuff, or AI adoption material where the Spanish-language conversation is underserved. Not auto-translated.

A monthly newsletter, eventually. A few longer pieces over the next few months. The occasional opinion, when it’s grounded in something I’ve actually done.

Why now

Two reasons. First, I keep ending up in conversations — with peers, with colleagues, in podcasts — where someone says “you should write that down.” Enough of those add up. Second, the work I do is interesting to me precisely because it’s at an intersection — IT operations, AI mentoring, building things, working bilingually, running an ERG — that I don’t see represented much online. So either I’m wrong about it being interesting, or there’s a gap. Either way, writing it out is the only way to find out.

If any of this resonates, find me on LinkedIn and say hi.