Use case
Agency knowledge walks out of the door with people. Neither side of a client relationship keeps the same team for long, and the understanding that makes strategy and creative good is exactly what disappears when a team changes. Multiply holds client context on the workspace rather than in individuals — so a new person starts from what the agency already knows, and every project adds to it instead of resetting.
Today
The client’s team changes and so does the agency’s, so somebody is always the person who has to explain how this account works — and somebody is always the person who did not get the explanation. The knowledge that matters most, the accumulated sense of how a client thinks, is the least written down. Prompt libraries do not fix it: a consultant’s custom setup is a rental, and when they leave the capability leaves.
How it runs
Brand guidelines, strategy documents, history and instructions live at the client level and steer every project underneath. Set once, applied by default — including agency-wide instructions set at the organisation level, so a house rule is a setting rather than a briefing.
A project starts with what the client workspace knows. When it closes, what was learned enriches the workspace profile — so the fifth project for a client is meaningfully better informed than the first.
Teams build their own agents and they are centralised: an edit propagates to everyone who uses one. That is the difference between institutional capability and someone’s clever setup.
Someone new asks the project what the client cares about and gets an answer with sources they can read, instead of booking an hour with the one person who remembers.
For an established client where the team has been stable, the cold-start gap is already small and this use case will feel less dramatic. It earns its keep at the transitions — a new hire, a departure, an account moving between teams, a client-side reorganisation — and in the aggregate, where a hundred projects’ worth of accumulated context is a genuine asset rather than a hundred fresh starts.
This is the half of the problem agency operations describes, and multi-client operations covers holding many of these apart at once.
Related: the product for how the pieces fit together, multi-client operations for running several of these at once, agency operations for the underlying idea, and the other use cases if knowledge is not the job you want to start with.
Bring a client you have worked with for years. That is where the accumulated context shows.
No, and that distinction matters — a knowledge base someone has to curate is a knowledge base that goes stale. Context accumulates from the work: the files a project already contains, and what it learns as it runs.
Access is managed per workspace, and context does not cross between clients. Private material — meeting recordings, personal mail — stays scoped to private work until a person chooses to share it.
Your material is yours and exports as documents. It is a fair question to ask any platform holding your client knowledge, and a fairer one to ask a consultant who built your setup inside their own account.
We will load what that account already has and show you what comes back out of it.