The problem
Every client is a different world. A different brand voice, a different history, a different set of decisions and deliverables. That context lives across a few people's heads and a scattered pile of docs. So a new freelancer needs a re-brief, and your AI answers in a generic voice that is nobody's client.
One folder per client, readable by your team's AI
Keep each client's brand guide, decisions, and deliverables in its own folder. Connect Claude or ChatGPT through MCP, and your team's assistant answers from the right client's notes: their voice, their history, what you have shipped.
What an agency keeps per client
- Brand guide: voice, do's and don'ts, the words this client will and won't use
- Decisions: what was agreed, what was rejected, and why
- Deliverables: what you have shipped, what is in flight, what is approved
- Folder roles: choose who can edit or manage each folder; team members can read all shared folders
Start with one client brief
The Client Project Context template gives each project a brief with preferences, scope, decisions, status and next action. The freelancer walkthrough shows one brief saved in ChatGPT, updated in Claude and retrieved again in a fresh ChatGPT chat. Working alone with several assistants does not require a team plan; the recorded example uses a personal account.
Ramp a freelancer faster
Bring someone on for a project. They connect their own AI and ask it to read the client's brand voice, past decisions, and deliverables. A team is free for its first 25 shared notes, and seats prorate after that, so you add someone for the project and remove them when it ends. Everyone in a team can read all its shared folders. For confidential client work, use separate teams with only the relevant members; folder roles control editing and management.
Your client context lives in a few people's heads. It doesn't have to.
What agencies keep in Hjarni
- Per-client brand voice: so every draft sounds like the client, not like your last one
- Decision history: what was agreed and rejected, so nobody reopens settled calls
- Deliverables log: what shipped, what is in flight, what is approved
- Client boundaries: separate teams with distinct memberships when client notes must stay private from other people
- Team AI instructions: folder-level guidance for each client's voice
Client knowledge, out of a few people's heads
Keep your project tool for tasks and timelines. Hjarni is the shared context layer your team's AI reads: the client knowledge that usually lives in scattered docs and a couple of people who are always in meetings. Put it in a shared team space and ask your connected assistant to retrieve the relevant client's notes. For compatible clients that accept manual agent tokens, you can narrow AI access to selected folders; that does not change what human team members can read. See Hjarni for Teams, or the set up your team guide.