Isaac Correa · Madrid
My role is the one I gave myself: I think, and I direct the product. This is the order I trust, and where it came from.

In January 2025 I sat down to explain what I believed about building, and it came out as three words in an order: data, then media, then product. Not because data is fashionable, but because the other two are guesses without it.
Data is what the business already knows and cannot say out loud. Media is how you find out whether anyone outside the building cares. Product is what you are allowed to build once those two have answered. Do it in another order and you will build something beautiful for nobody, which is the most expensive mistake available.
The part nobody photographs: two months designing screen by screen. Not wireframes in a workshop, actual screens, one at a time, each one argued over until it earned its place.
A screen is a decision made visible. If you cannot say what decision a screen helps someone make, the screen is decoration, and decoration in software is not free: someone maintains it forever.
Hellomatik started as something small: a system to answer the phone in a restaurant. A voice, a brain and a pair of hands. The voice takes the call, the brain decides what the call means, and the hands do the thing.
The hands were the problem. To do the thing, a system has to know what things exist, which rules the business follows and who is allowed to approve what. That question turned out to be much bigger than a restaurant, and answering it properly is what became the method we published with a DOI.
People ask what the goal looks like, and the honest answer is that the picture in my head is HAL 9000: a system that understands the whole company and can act inside it.
I say that with some humility, because HAL is a cautionary tale, and the reason it is one is the same reason our work is mostly about limits. A system that understands everything and answers to nobody is the failure mode, not the goal. That is why every action carries whether it can be undone and whose approval it needs, and why the permission table is the part I would show a sceptic first.
The report states the scope rather than implying it: four systems in production, among them a logistics one with 24 rules over live warehouse and ERP data, with over 30 million operations and 460,000 locations, and a B2B sales one that recalculates 29,000 customers nightly over 14 million sales lines. A method with its scope written down is a method.
Isaac Correa, Madrid. ORCID 0009-0003-0657-4419.
How Hellomatik started — what the two months of screens came after, and why.
Press kit — bios you can paste, photographs, and every fact with its source.
The timeline — every date with the place you can check it.
Photographs — the pictures that exist of him, free to reuse with attribution.
What selling taught me — three hundred commissions, and the lesson underneath them.
Your company already has rules — the first week of automating a business.
The machine of the future — on what the next tool is.
How we build a company’s ontology — the method, published with a DOI.
Copy until you find creativity — how I think about innovation.