There is a difference between an assistant you call up and a system that runs.
The assistant has to be fetched. You remember it exists, open it, explain the situation, get an answer, close it. Next time you start over. After a few weeks you use it for phrasings and nothing else.
A system that runs does not have to be fetched. It is already there when you open your machine in the morning, and it has been working in the meantime.
For a consulting business on Mallorca we set up such a system.
The Server Belongs To The Client#
The unspectacular part first: all of it runs on a dedicated server in a German data centre. Not at our place, not in a shared account, but on a machine that belongs to the client, with their own credentials.
Application, database and backups sit there. What goes to the language model leaves the EU, because that is where the model runs, and we write that distinction down on every project before it starts. There is no reason to obscure it and many reasons to say it plainly.
In practice a dedicated server means we can keep developing without anybody having to upload their data somewhere new. And when the collaboration ends, the server and its contents stay with the client.
Memory Is The Foundation, Not A Feature#
The core of this system is a memory that carries across weeks and months. Conversations, clients, projects, decisions taken and the small agreements you otherwise go hunting for in old mail.
The effect is hard to overstate. Without memory you explain the backstory to the assistant on every task. That costs more time than the task itself, which is why people stop. With memory you explain once, and two months later the assistant brings the connection back on its own.
That makes memory not an add-on but the reason the system gets used at all. Everything else hangs off it.
The Mail Gets Read Before Anybody Looks At It#
The most visible part in daily use is how the mail is handled.
The system fetches the inbox itself, reads every new message, sorts it and puts a draft reply next to the relevant ones. Not a suggestion out of thin air, but one built on what memory holds about the sender and the matter.
And then it stops. It sends nothing. The draft sits there, the human reads, edits, sends or discards.
We draw that line in every system we build, and it is not caution on principle. The draft is the work, sending is a button. Give away the work and keep the button and you gain nearly everything while risking nothing. Give away both and you risk the relationship with the recipient to save one click.
The system takes the preparatory part off the table. The rest, the place where experience and judgement are needed, stays with the owner. That is also the part they get paid for.
One System, Not Three Islands#
The most common mistake in setups like this is that three things end up running side by side: a chatbot, a mail tool and a pile of notes somewhere. Each works on its own, none knows about the others.
Here memory, mail and assistant share the same context. When a client's mail arrives in the morning, the draft already carries what was discussed in the last conversation, without anybody looking it up. That is the actual gain, and it does not come from a special feature but from the parts being connected.
Nothing Experimental#
The substructure is deliberately boring. Ubuntu, Docker, PostgreSQL, Claude as the model, our own memory server, a connection to the existing mailbox.
That is the same setup we run for ourselves and for other clients. We do not build anybody a special construction only they have and only we understand. The reason is self-interested: a system we run many times over, we know by its failure modes. A one-off you get to know at the client's place, and that is the most expensive way to learn.
What Such A System Is Not#
It is not a replacement for an employee. It has no judgement, no responsibility and no idea what is really going on between two people.
What it can do is the part of the work that consists of remembering, preparing and gathering. In a consulting business that part is larger than you think, and it is also the one left lying around in the evening.
That is exactly where such a system belongs. Not where decisions get made.
