Waitlist opening soon
Taking over a company's IT is not a thing to learn on
The systems a company runs on are a bad place to be somebody's first project. We are running the full estate ourselves and in a small number of reference environments before offering it. When the form opens it will ask for an email address and roughly how many people you are.
Reference environments
The whole stack in real use, so the first client is not the experiment.
Audit first, always
The first engagement is an assessment you keep, whatever you decide afterwards.
Come back
The blog carries what we would look at first, and when the answer is to change nothing.
Why there is nothing to fill in
Because an IT partner with an empty delivery calendar that is already booking discovery calls is a partner who will learn on your environment. Devices, identity and mail are not a good place for that, and the failure is expensive in a way that is difficult to reverse.
What the waitlist will be for
One field, an email address, and optionally how many people work at your company — because the first engagements will be chosen for fit, and for some companies the honest answer will be that what you have is fine.
What the first engagement will be
An audit, priced separately and yours to keep. What you run, what it costs, who can operate it, what leaving each part would take, and what we would change first. If the conclusion is that you should change very little, that is a legitimate outcome and you still have the document.
In the meantime
The blog carries the reasoning: why the continuity plan in most companies is one person, why nobody can price the exit from their own IT, why identity is the real lock-in, what to do about staff already using AI, and when sovereignty is not worth what it costs.
No form, no data collected, no sales calls — just work in progress.