Waitlist opening soon
Nobody should hand over their whole company on a promise
This is the most invasive thing a supplier can propose: replacing the systems a business runs on. So it runs our own operations first, and the first engagements will be one domain alongside what a company already has. When the form opens it will ask for an email address and which system hurts most.
Our own operations first
Real orders, real stock, real money, where being wrong costs us rather than somebody else.
One domain, not everything
Alongside what you run today, chosen so there is a way back at every step.
Come back
The blog carries the argument, including where the automation deliberately stops.
Why there is nothing to fill in
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 regardless of whether the software turns out to be good.
What the waitlist will be for
One field, an email address, and optionally which of your systems causes the most trouble — because 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 require 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.
In the meantime
The blog carries the argument: why a system of record cannot act, what the seams between systems really cost, where intelligence stops being lawful, why code written by agents still gets reviewed, and why compute is a market rather than a subscription.
No form, no data collected, no sales calls — just work in progress.