For agencies and consultancies
A separate world for every client
The thing that breaks when agencies adopt AI is not quality. It is separation: whose context, whose credentials, whose data, and who approved what.
What is actually hard about this
Shared tooling leaks context
One workspace holding six clients means six brand voices in one context and, eventually, one client's positioning showing up in another's deck. It is not a hypothetical risk, it is a matter of time.
Credentials are the real blocker
Every client has their own CRM, their own social accounts and their own rules about who holds the keys. A tool with one integration slot per provider cannot serve an agency at all.
Every client needs a distinct voice
Repeatedly briefing a generic tool takes time. Give agents each client's brand context so their drafts start from the right audience, positioning and voice.
What changes
The agents named below are the ones that actually do this work, from a fleet of 50.
One world per client, isolated
Separate context, separate knowledge, separate brand kit. Nothing crosses between them, so a client's positioning cannot surface in another client's work.
Multi-account integrations
Each client's HubSpot, Attio, Slack and Apollo connect under their own world with their own credentials, encrypted per tenant. No shared keys, no cross-client reach.
Deliverables grounded in each client
Create content, case studies and campaign plans using the selected client's research and brand voice. Your team reviews the draft before sharing it.
Repeatable campaign briefs
Use a shared brief to coordinate specialist agents and produce a final document. Keep reusable knowledge in the client's world for the next assignment.
A sensible first month
Not a rollout plan. Just the order that tends to work.
- 1Week oneBuild worlds for your two most different clients. Two different ones will teach you more than five similar ones.
- 2Week twoRun one real deliverable per client. Check its facts, brand voice and usefulness, then share it through your existing client approval process.
- 3Week threeConnect one client's CRM. Confirm for yourself that the credentials are scoped to that world before you connect a second.
- 4Week fourDecide what you will and will not put through this, and write it down. An agency that has not drawn that line will eventually be asked about it by a client.
Where most agencies start
The Agency plan
Twenty-five worlds and ten seats, which is a client roster rather than a pilot, plus the credit ceiling to run real production across all of them.
80,000 credits a month · 10 seats · 25 worlds. Your first world is free and needs no card.
Questions this raises
How should we review work with clients?
Review and refine the generated output with your team, then export it for your existing client review process. Keep each client's research and source material in its own world.
Do we have to tell clients we use AI?
That is your call and your contract, and we take no position on it. Your team is responsible for checking facts, brand fit and suitability before sharing generated work.
What happens to a client's world if we part ways?
Everything is exportable, and worlds are deletable individually. Client data is never used to train models, and deleting a world removes its context from every agent immediately.
Is there a white-label option?
Generated documents carry the client's brand, captured from their own site, rather than ours. The application itself is not white-labelled today, which is why the client role is scoped as tightly as it is.