I built josebaqueror.com with AI as copilot

I built josebaqueror.com with AI as copilot. And the important part of that sentence is not "AI": it is "copilot". The AI did not decide the site. I did. That distinction is exactly what I sell to my clients, so it seemed fair to apply it to myself and tell how the work actually gets split when you do it seriously.

What I automated

The list of what the AI executes is long and it is the one people expect: the site's code, the rendering of the brand images, the deployments to production, and the system that every week turns my LinkedIn posts into blog articles in Spanish and English, with their metadata, their cross-linked language versions and their updated sitemap. That circuit runs week after week and it is the reason this blog exists: without it, maintaining constant bilingual content would be a second job.

The practical effect is measured in time: the site and the blog are maintained with hours of my week, not days. And in consistency: the article ships every week even when the week was chaos, because the system does not depend on my afternoon being free.

What I decided

The list of what was not delegated is shorter and worth more. The positioning: I solve problems, AI is the means and not the promise. Which projects get shown and which do not. Which data gets published with a name and which stays confidential to my clients, because a good part of my work lives under agreements that are not negotiable for a post. The design, which I rejected and redid until it stopped looking template-made. And every word of the message, because voice is the one thing you cannot outsource without it showing.

The same recipe I apply in engineering

If this sounds similar to how I build agents for Vault or Inventor, that is because it is the same recipe. A well designed agent performs the complete workflow, but it does not authorize the writes: a person does, with a dry-run in front and a gate that can say no. My site works the same way. AI executes the repetitive work at machine speed; judgment, responsibility and the last word do not change hands.

That is, by the way, the answer to the question I get asked the most: "aren't you afraid it publishes something you don't want?". No, because the system has no permission to decide what gets said. It has permission to produce, and it produces on top of rules I wrote: what gets mentioned, what never gets mentioned, and which tone is mine.

If that relationship with AI is the one you want for your operation, one that executes the repetitive work while your team keeps control, that is exactly what I build inside Vault, Inventor, AutoCAD and Forma. The result of applying it to my own digital presence is what you are reading right now.