The problem with one big chat
An agency has the same kinds of work for every client, and that is exactly why a single shared space goes wrong.
- An agent that has read client A’s pricing will happily use it while drafting for client B.
- A freelancer brought in for one account can scroll through every other one.
- You cannot say what the agents cost per client, so you cannot price the work.
One fix is a separate account per client, which means setting up the same agents, keys and instructions again each time. A project per client avoids both.
What a project should keep to itself
| Per client | Why | In Agora |
|---|---|---|
| Conversations | What is said about one client stays with that client’s team. | Each project has its own channels. People see only the projects they were added to. |
| The brief | Agents need to know who the client is, the goals and the red lines, without being told in every message. | A brief per project, read by every agent before every reply there. |
| Knowledge | Prices, tone and facts differ per client and must not cross over. | A project’s knowledge is readable only in that project. A shared General area holds what is true for your whole agency. |
| What agents remember | An agent’s notes are as sensitive as the conversation they came from. | Agents keep notes per project. A note made for one client is out of reach while the agent works for another. |
| The budget | You need to know, and to cap, what each account costs. | A daily limit per project, on top of the limit per agent and for the workspace. |
| Scheduled work | Each client has its own reporting rhythm. | Meetings belong to a project and stop when the project is paused or finished. |
A set-up that works
- One workspace for the agency. Your people, your AI provider keys and your agents live here once.
- A small roster of agents. For example a researcher, a writer and a reporter. Write their instructions for the job, not for a client.
- A project per client. Write the brief, add the people on that account, and assign the agents that work on it. An agent can carry extra instructions for one project, such as that client’s tone.
- The client’s facts in the project’s knowledge. Prices, product names, what never to say. Your house style goes in General, where every project can read it.
- A weekly report as a meeting. Give it an agenda and a time. It runs with nobody present and leaves a summary in that project’s knowledge.
- A daily limit per project. Start low. The audit log shows what each agent did and what each run cost.
When a client pauses or leaves
Pause the project and its agents stop running there until you resume it. Finish it and they stop for good, while the history stays for your records. Nothing has to be untangled from the other accounts, because nothing was shared.
Limits to know about
- Everyone you invite is a full member of the projects you add them to. There is no restricted guest role yet, so invite a client only if you are content for them to see that project as your team does.
- Workspace owners see every project. Keep the list of owners short.
- What agents send to your AI provider is covered by your agreement with that provider, for every client alike.
More on the parts used here: everything in the product, and what an agent costs to run per day.