Notes
Three Attempts Before Getting It Right
An AI assistant that wanted to manage everything, a ticketing SaaS, and finally a plain dashboard. The journey toward the useful maintenance tool.
1 min read
Nobody defends a maintenance dashboard because they like the code: they defend it when a backup fails and nobody notices. Even so, it took me three attempts to get the right tool.
The first was an autonomous AI assistant for managing WordPress. Fascinating and useless at the same time: every new feature undermined what was already there, and what was supposed to be centralization became another place to look. The second was a complete SaaS, with a portal, ticketing, and plans: the business structure came before the tool. Both versions grew faster than they matured.
The lesson arrived in the most boring way possible: asking what maintenance actually means. Reliable backups, updates that don't break anything, an audit that tells the truth, and a signature that proves no one has accessed the system. Anything that didn't serve that purpose was out.
The result is a plain system, with no AI, featuring an HMAC-signed connector and an audit based on simple rules. It works flawlessly and is easier to secure precisely because it does less. From here on, it will grow only with what is needed.