The nightmare of anyone running several clients with agents: a draft for one client goes out by mistake with the tone (or worse, the pricing) of another. The fix is to build your folders in the right structure, one that simply doesn't let that mix-up happen.
- A folder per client. clients/acme/, clients/rotem/, and everything that belongs to a client lives only there: summaries, drafts, decisions, preferences.
- A client card at the top of each folder. That's one client.md file that holds it all: who they are, what the right tone with them is, what was agreed on money, and what must never come up. It's the first thing the agent reads before starting work on that client.
- The loading rule. When working on one client, load only their folder. No "hang on, open the other one too for comparison". Comparisons happen in a separate session, one that isn't meant for sending anything at all.
And if you have a human team as well, the same structure gets another floor: every freelancer or partner gets access only to their own clients' folders. Set the permissions at the folder level, and discretion stops being a matter of who remembered what.
There's a nice bonus too: this separation saves money. An agent that loads one client instead of ten reads a tenth of the tokens, which means the safe method happens to also be the cheap one (two birds, zero stones).
And the last rule that closes the loop: at the top of every deliverable headed to a client, add an internal check line stating which client it's for and which card it was checked against. One second of cross-checking against the folder name saves a whole morning of apologies.
A prompt, on the house
Fixed structure for client work:
clients/[name]/client.md → card: tone, rate, boundaries, contacts
Rules:
1. When entering a client: read their client.md first.
2. Load only the active client's folder. Comparisons go in a separate session.
3. Before any outgoing deliverable, write me: "Client: [name] | Checked against: [card]".
4. Numbers and money: only from client.md, never from memory.This separation is exactly as boring as good security should be. Boring is the profession.
