Conversations open soon
Nobody should hand over their whole company on a promise
Replacing the systems a business runs on is the most invasive thing a supplier can propose. So Hurukan is designed to be introduced gradually: it is in build, and the first engagements will start with one domain alongside what a company already runs. When the form opens it will ask for an email address and which system hurts most.
In build, said plainly
The five layers and the modules are being built now. Integrations with Microsoft 365 Copilot, Claude and ChatGPT are planned, not live.
One domain, not everything
Alongside what you run today, chosen so that there is a way back at every step.
Read the argument
The system pages and the blog carry the reasoning, including where agents deliberately stop.
Why there is nothing to fill in yet
Because the scope described on this site is large enough that it should be distrusted until it has been demonstrated. A company that replaces its operating systems on the strength of a well-written page has made a mistake, whether or not the software turns out to be good.
What the form will ask
One field, an email address, and optionally which of your systems causes the most trouble. The first engagements will be chosen for fit, and for many companies the honest answer will be that a narrower product solves their problem sooner.
What the first conversation will cover
Where the seams actually are. Not which products you run, but which handovers between them need a person, how often the numbers disagree, and what the weekly meeting exists to reconcile. That last one usually identifies the domain worth starting with — and the module that would cover it.
In the meantime
The system pages describe the five layers and the ten modules: what each one covers and how it connects to the rest. The blog carries the argument: why a system of record cannot act, what the seams between systems really cost, and why code written by agents still gets reviewed.
No form yet, no data collected, no sales calls.