Use casesUse case
One memory per client for agencies and consultancies
An agency gives each client an engine of its own, connects its team's AI tools to the engines they work on, invites the client's people for free, and hands the engine over when the engagement ends, history and authorship intact.
What it does
Agency knowledge lives in the heads of the people on the account. When someone is on holiday or leaves, the next person, and every AI tool, starts from nothing. With one engine per client, everything that matters is saved as it happens: decisions and why they were made, the people at the client, meetings, tasks with an owner and a due date, and the client’s own files.
Set it up
- Make an engine for each client, with a purpose in a few sentences. Give it the client’s website: it suggests notes, values, voice and colours, and nothing is saved until you keep it.
- Drop the client’s existing documents into Files: files, whole folders or a .zip. Text and PDFs become searchable and a folder name becomes a tag.
- Each person on the account connects the AI tool they already use (Claude, ChatGPT, Claude Code, Cursor) to that client’s engine.
- Invite the client’s team if they should see it, as admin, member or viewer.
- Read Summaries each week for what happened, and Ask for questions answered from the client’s memories, with the memories each answer came from.
Onboarding a new client
The first week of an engagement is where most context is lost. Save the kickoff as a meeting, the agreed scope as decisions with their reasons, and the open questions as tasks. Every AI tool on the account then starts from the same picture, and the client can check it.
When the work ends
Invite someone at the client to the engine first, then hand it over to them: they accept it and take over paying for it. Or export it. Every memory keeps who wrote it and with which tool.
Questions
How do I stop one client's information reaching another client's work?
Use one engine per client. A connection reaches only the engines you tick, and in Claude Code a project-scoped connection per client repository keeps them apart. In Claude Desktop and claude.ai, switch on only that client's connector in each chat.
Can the client take the memory with them at the end?
Yes. Invite them to the engine, then hand it over; they accept it, takes over paying for it, and authorship stays. Or export it as one ZIP of Markdown and JSON that opens without us.
Do we pay for each person on the client's team?
No. People are free on every plan. A plan sets how many agents connect to one engine and how much it holds; see the pricing page.