Prepared by the AIOS for Jonas Pauly
An AI operator
for the day-to-day of
ms gartenreich.
You already run Claude, you keep your brain in Notion, and you built your own ERP for the contracts, the tenant data and the payments. The AIOS is that setup taken one step further and turned into a product: hosted for you, with a memory that never resets, and built so the work actually runs on deterministic scripts rather than on assumptions.
You already know Claude. This is the operator version.
The AIOS is a central AI agent that lives on your own private server. A chat space on one side, a file tree on the other, and an operator that can actually act: the same principle as Claude Code, but delivered as a service, with very long term memory and integration that stops only where the APIs stop.
The part that matters for you is the split. We consider the AIOS to be 10% AI and 90% ordinary technology. The AI builds the process; the process itself is a Python script that then runs on its own, deterministic, with no randomness and no token cost. You use a lot of AI in the first weeks, and that usage is meant to drop fast as your processes settle. It is the direct answer to what you said was bothering you: an assistant that improvises less as time goes on, not more.
What we covered together
Your situation, taken as you described it.
01 · The twenty balls in the air
Ten projects at once, and a different day every day
You told me your bottleneck is not one project, it is that you are juggling at least ten of them and every day looks different. One AIOS holds all of those threads: a folder per project, and an operator that keeps the full history of each one. The cost of switching context drops, because it never lost the context in the first place. You stop re-explaining where a project stood.
02 · The time lost in the car
The part you said you would use the most
You cannot really work mobile, and you know that is where the time goes. With eight sites spread between the Bergisches Land, the Ruhr area and northern Germany, that is a lot of driving. The AIOS has a phone app with a voice mode: you talk, it updates the tracker, drafts the email, writes the note, and reports back. Exactly the story Ben told you from the golf course.
03 · Claude that assumes
Determinism where it actually matters
You have skills set up, a master prompt, plenty of context and a brain to pull from, and it is still messy. The reason is structural: a model is non-deterministic, so anything you make it redo from scratch every time will drift. In the AIOS, once a process works it is frozen into a script and stops going through the model at all. The AI designs it once; the machine repeats it identically.
04 · The stack you already built
Above your ERP, your Notion and your Obsidian
You built the ERP yourself for the contracts, the customer data and the tracking of who owes what, when, and whether they have paid. None of that gets thrown away. The AIOS sits above it and drives it: where there is an API or a database, it connects, reads, writes and extends. It can keep building on what you already have.
05 · The two hires
A recruitment that runs in the background
You mentioned you are looking for two new people, and your site is already advertising a role with full responsibility from day one. This is the shape of process the AIOS runs end to end: sourcing, a first screen against your criteria, scheduling, follow-ups, and a short summary for you. A pipeline that moves without you pushing it.
06 · The recurring operational load
Contracts, payments and tenant requests
Ground leases of 200 to 500 euros a month across many parcels, the operating cost statements, and a tenant inbox served on two phone mornings a week. Anything on that list that repeats can become a process: reconciliation, reminders, statement preparation, first-line answers drafted for you. Start with one, then add the next.
What it actually does
One tool to drive. It handles the others.
Run your inbox and your accounts
Triage, prioritisation, drafts written in your own voice, and connection to your tools through their APIs. You choose how much rope it gets, and you can tighten or loosen it at any time.
Build your own tools
A tracker for parcels and payments, a connector between your ERP and your accounting, an internal dashboard. You describe it, it builds it, it runs it.
Create and host your pages
Landing pages, site sheets, forms wired into your tools. Generated, published over HTTPS, hosted on your own server. This page is an example of exactly that.
Automate your processes
Every recurring action becomes a Python script that runs by itself. Deterministic where it needs to be, free to execute, with no model call in the loop.
Prepare your decisions
Site by site reporting, payment status, a weekly digest ready to read. You arrive at each decision with the context already gathered.
Remember everything, permanently
Every exchange, every decision, every detail about a site, a parcel or a tenant. In six years it still knows, and it retrieves the exact fact at the right moment.
You warned me you were a suspicious person
Your questions, answered properly.
Claude, as the background model. The first thing you do at onboarding is connect your own Claude account, and you keep the usual model range. The AIOS is the layer around it, and its job is to build your processes and then step out of the way. Your Claude subscription is the one thing you bring; everything else comes with the product.
On the server, in two spaces. One is your workspace: readable files, markdown, images, documents, the things you and the operator work on together. The other is not surfaced in the interface and holds the Python scripts that do the running. Nothing is hidden from you, though: if you want to read a script, you open it. It is simply not put in your face, because the product is not built for developers.
Not on your PC. We provide a private server and you reach it as a web app on the desktop and as an installed app on the phone, so there is no VPN to set up and nothing running locally. If you would rather host it on a server you manage yourself, that is fine and we will install it there. Our terms say you cannot copy the system onto a second server, not that you have to use ours.
The AIOS is designed as the right hand of one person: your folders, your history, your way of working, much like you would not hand your own PC to the team. So it is one seat by default. For a whole team we build a tailored offer around how many seats you actually need and how much guidance the team needs, and we usually start with one or two and grow from there. Shared folders then let several AIOS instances work on the same projects.
You are never locked in. There is an export in the Security and Data section that hands you the entire contents of the server, at any point, including during the trial. If you build something you like during the trial week but decide the AIOS itself is not for you, you leave with what you built.
This is the piece most agents do not have, and a large part of why a setup with a master prompt and a pile of context still feels messy. Most of them work per session: new conversation, back to zero. We rebuild the context on every message instead. Facts are extracted, stored in a vector database, and the relevant ones are pulled back in on the fly. Unlimited memory that does not clog the conversation.
It is a progressive web app, so it is not in the App Store or the Play Store. We install it with you during the onboarding session and it takes about five minutes. Once installed it behaves like a normal app, notifications included, and the voice mode is the part that changes how a driving day actually works.
How it works day to day
Plain language is enough. The tool does the rest.
You organise it in folders
Like a computer. A folder per site, a folder for the hiring, a folder for the payments. The operator knows which context it is in from the folder it is working in.
You talk to it normally
No prompt engineering. You say "pull this month's lease payments and tell me who is behind". It understands, it acts, and it works around obstacles the way Claude Code does.
It keeps everything
Every exchange, every decision, every detail on a parcel or a tenant. Tomorrow, in three months, in two years, it uses it. You never rebuild your context by hand.
You extend it without coding
A new automation, a new tool, a new page? You describe what you want. It builds it, tests it, deploys it. You use it the same day.
Documentation
To dig further, your documents.
Everything is hosted here rather than attached to an email: the full legal pack (including the Data and Security annex on hosting and GDPR), the service proposal, the list of tools our clients dropped in their first month, the AIOS presentation and the case studies. It all opens in the browser and downloads from your documents page. One honest note: these documents are currently written in French. Ask me for any of them in English and I will get it to you.
Data and Security annex
Complete legal documentation (v1.8)
AIOS service proposal (v1.8)
Tools replaced by the AIOS, client examples
AIOS presentation
Client case studies
Legal documentation, document by document: Terms of Service, Data and Security annex, Privacy policy, Legal notice, Referral programme terms. Everything also opens and downloads from your documents page.
Documents are readable online and kept up to date here.
The offer
Simple, no commitment, no setup fee.
You settle the use case with Christina
You have your weekly sync with her on Tuesday 29 September, and Philémon has a call with her that same afternoon. You come back Tuesday evening or Wednesday, and we book the kickoff from there.
A one-hour kickoff session
We take the use case you chose and build it together during the call, live. Roughly fifteen minutes of it goes to connecting your tools, which is the genuinely fiddly part with the big suites. The phone app gets installed in the same session.
7 free days, and more if you need them
You said you did not want to waste the week, and that is a fair worry. The seven days are a starting point, not a wall: if the operational load swallows your week, say so and we extend to ten or fifteen days so you get a real test. No card details, no commitment.
- Your own AIOS, hosted on your private server
- Unlimited long term memory across all your projects
- Custom tools and automations built on request
- Phone app with voice mode, installed with you
- Unlimited connection to your tools through their APIs
- Full reversibility: export everything at any point
399 EUR excl. VAT per month on your own. Or 799 EUR excl. VAT per month with accompaniment, which buys 2 hours of sessions per month with Philémon or his associate to build your processes directly inside the company. No setup fee, no middleman, no hidden margin. The only thing you bring is your own Claude subscription. And since Christina pointed you our way, it is worth knowing the referral programme pays 30% for life on every subscription referred.
A question before then? Write to me directly:
No rush on your side: come back once you and Christina have settled on the use case.
One personal note.
This whole page was produced by the AIOS on its own, from our call: it took the recording, read your website, pulled out your actual topics, and built the page end to end, automatically. It also re-transcribed the recording in English, because the meeting tool had mangled our conversation into French. That is precisely the kind of work it would be doing for you day to day. Talk to Christina on Tuesday, pick the one use case you want to test, and we will take it from there.
Philémon Gavoty Azuro AI · azuro-ai.com