Building for the web since 1995, from hand-written HTML to cloud infrastructure. Very few of these problems are new to me.
Integrations and APIs are the day job: taking systems that were never designed to cooperate and making them work as one, reliably enough that you stop thinking about them.
AI where it earns its place: connected to your systems, reading real data and carrying a task through to the end. Not a chat window bolted onto a website.
I built my first website in 1995. The web was new, everything felt possible, and I have not really stopped since.
What hooked me was never the technology on its own — it was making things fit together. That curiosity turned into a career built on automation, integrations and APIs: taking systems that were never designed to cooperate and getting them to work as one.
It is what I do day to day, and increasingly that means AI. Not as a demo, but as something that has to work reliably against systems people depend on.
Most of this work looks the same from the outside. A business running on four or five tools that do not speak to each other, and someone spending Friday afternoon copying between them. That afternoon is usually what I am hired to give back.
Tardix is where I do that work. If something in your business should be automated and isn't, tell me what it is and I will tell you straight whether it is worth doing.
Albert Sola
The interesting part of AI isn't the chat window. It is what happens when you connect it to real systems and let it act — reading the data, making the call, and carrying the task through to the end.
It is the same problem I have been solving for years, now with much better tools. If you are wondering whether it applies to your business, that is a short conversation and a useful one.