About me

Why GEO

I grew up close to digital marketing: my mother spent years working in marketing, websites and search engine optimization, and much of what I understand about how a brand gets found online I learned by watching it up close.

When I started working on my own projects, at 22, I found the same problem on new ground. More and more people ask an AI assistant instead of searching Google, and those systems decide which sources they read, how they interpret them and whom they mention. The field is still being mapped: there is no definitive playbook yet, and what works is being found by experimenting and measuring.

That is where I want to be. Just as SEO became a discipline in its own right, I believe preparing a brand for AI engines — its website, its identity and its presence across other channels, organized so a machine understands who it is and what it does — will become a craft of its own. That is why I work in the open: the experiments, the measurements and the tools I use are published, so anyone can check the method instead of taking my word for it.

Background

I trained at CEU San Pablo and started out in cybersecurity as an intern at All4Sec — consulting, network infrastructure and hardening. I'm a software and security engineer, and that shapes how I work: every change I make to a site is reversible, documented, and doesn't put at risk what already works.

What sets me apart

You can check everything before you hire me. My work is public: a repository with the method and documentation, updated every week; another with reproducible experiments, each with the command that measures it; and a real case in production, kenetg.com.

The difference is easy to explain. You can choose a proposal full of promises nobody can guarantee, or someone who publishes what they do, how they measure it and what they can't prove, so that trust rests on evidence rather than on words. I think the choice is clear.

How I work

1. A first conversation. It starts with an introduction: you tell me what problem you have and what you need, and I tell you plainly what I can solve and what I can't. It's a conversation, not a sales pitch.

2. A free mini-audit. Before we talk about a budget, I look at your case with data, so the proposal starts from what is actually on your site rather than from assumptions.

3. A concrete plan, in writing. We narrow each point down until there is a clear plan: what gets done, in what order and why. Before any work begins, the budget, payment terms and estimated hours are agreed, so there are no surprises halfway through.

4. Reports throughout the work. While the project is running, you get a weekly report on what has been done and what comes next. If the engagement is ongoing, reports keep coming at whatever frequency we agree. Their content fits what you hired: a site that has just been optimized needs different information from a brand under monthly monitoring.

If along the way it becomes clear we're not on the same page, we say so early and stop. Starting a project with different expectations helps no one, and it's better to find out in the first week than in the fourth.

What I don't do

I don't promise what can't be delivered. No magic formulas, no "best ChatGPT prompts" that will make you a millionaire, and no guaranteed spot in an AI's answers: that decision belongs to the engine, changes from one query to the next, and nobody outside it controls it. Anyone who assures you otherwise is selling you something they don't have.

Nor do I use shortcuts that work for a while and end up penalizing whoever used them. I work with clean, documented techniques that you can maintain and review yourself.

For the same reason, I turn down projects built on that philosophy. If what you're after is a quick trick rather than work done properly, I'm not the right person — and I'd rather say so from the start.

The name

Zentimes comes from a simple idea: good projects are made calmly and with time. The full story is in the note "Con calma y con tiempo" (in Spanish).