Eleven questions that keep coming up — about ownership, control, your voice, and what a personal operating system actually is. Answered briefly, without a brochure.
Not a chatbot, and not a website with an AI button. A personal operating system is a layer that knows your everyday: it sifts what comes in, prepares, drafts in your voice and handles the recurring — by your rules. A website is the facade of it; the system behind it keeps working even when nobody is looking. You don't get a tool you have to operate, but an ensemble that works for you and asks exactly when it matters.
Yes — because your voice is the material, not an add-on. I set up your style canon: vocabulary, stance, limits. Every line, every image is checked against it before it goes out. It sounds like you, not like a machine and not like atelier number four. And the longer it works with you, the more precisely it lands.
It belongs to you — entirely. Your system runs on your foundation, your data stays in your hands, and I don't build a second copy that reads along somewhere. What the system knows about you, it knows for you. You can see at any time what is stored, and take it with you. No subscription holds your content hostage.
You remain the conductor. The system acts on its own where you allow it, and stops where judgement is needed — then it rings exactly once: with you. Every action is visible, every one can be undone. Full autonomy is possible; full sight is guaranteed. You don't lose the work — you lose the fiddly parts.
There will be few. Every system is a one-off, built in the atelier — no template, no series. Something like this only holds at the depth it is meant for, and that limits the number by itself. Whoever has one has something no second person owns in quite the same way.
There is no price on this page, and that stays so. A personal operating system is a commission, not a product off the shelf — what carries something like this depends on how much it should be able to do and how deep it reaches into a working day. That is talked about in conversation, not in a brochure. The thought behind it does not change: something like this is built to stay. Not rented, not temporary.
Like a commission: first the conversation, then the design, then the build. It begins with listening — how someone works, how they sound, what eats their time. From that a design emerges, one that is seen and changed before anything is built. During the build there are interim states instead of a black box. And it is also allowed to say: you choose what fits — then I decide, and it is signed.
It takes the recurring off your hands and prepares the judgement. It sifts what comes in and puts the three things on top that really need you. It writes drafts in your voice — replies, texts, announcements — and lays them before you for approval. It produces series in your handwriting. It remembers what you corrected, and doesn't make the same mistake twice. What it doesn't do: decide in your name without asking.
Look behind. This page shows live what your browser gives away — and that I record none of it; that is not a promise, that is proof you can check yourself. The two sheets show the same for the build: the elevation, how it looks in operation, and the section, how it comes about. I would rather show the blueprint than a brochure.
Then you go — with everything. Your data, your rules, your content belong to you and can be taken along, in formats readable elsewhere too. I don't build a system that has to hold you because it would otherwise be worth nothing. And I don't tie you to a single provider behind the scenes: what runs under the hood today can be exchanged without you starting over.
The decisions stay with a human — with me in the build, with you in operation. The system takes the recurring off your hands so there is more time for the real thing: your work. It doesn't replace the voice, it carries it further — even when you are not speaking right now.
Then write it to me. I answer myself — there is no form that passes you on, and no queue.