Does anything reach my client without me?

Only what you allow. Every deliverable waits on the card for your approval, and an agent acts in a connected app only with the access you give it there: read, write or delete, app by app. Leave your email at read, and nothing is sent.

We already keep our playbooks in markdown. Do we start over?

No. Put them in the workspace or project Wiki. Pinned pages go into the agents' runs on that project, so they work from your playbooks.

Will it sound like us, or like every other agency?

Like the client's brand: the voice, words to avoid and examples live in that client's Wiki. When you request changes, what the agent learns is proposed to its Brain for you to review before it is kept.

For agencies

Stop pasting the brand voice in again. Each client's Wiki remembers it.

Afarin keeps a Wiki per client: brand voice, offers, past work. Jevie drafts the copy, Safro the design, Afarin the reports, and every deliverable waits for your review before it reaches the client.

Start your 14-day trial

“In Chat/Claude you're constantly reintroducing yourself to the AI. Here's my brand voice again, here's what we do again, here's how we handle this situation again.”
An agency owner on r/agency, March 2026

A few examples of what the team takes on

See everything the team does

Your weekly client update, drafted before Monday.A routine starts a card for each client every week. Afarin reads what shipped on that client's board, drafts the update in your voice and leaves it for you to review and send.afarin · you review A competitor brief on your desk every Monday.No connector needed. A routine starts the card each Monday; Afarin searches the web, reads the pages that changed and writes a short brief for you to check before it reaches the client.afarin · you review A first draft of the client deck, ready to edit.Give Afarin the brief. Afarin writes the story slide by slide, and Safro lays it out as a deck you can edit in the browser and export as .pptx.safro · you review

Built for client work

A project per client: its own board, its own Wiki and its own chats, so one client's context never reaches another's work.
Every card shows what its runs cost, and every run stops at the caps you set.
ComingA reviewer seat for your client, to approve deliverables on their own project.
ComingA monthly cost line per client, ready to rebill.

Everything else, in the same place

What it costs

One predictable line you can price into your retainer: people never pay for a seat, and every agent runs under a cap you set.

Questions

Does anything reach my client without me?: Only what you allow. Every deliverable waits on the card for your approval, and an agent acts in a connected app only with the access you give it there: read, write or delete, app by app. Leave your email at read, and nothing is sent.
We already keep our playbooks in markdown. Do we start over?: No. Put them in the workspace or project Wiki. Pinned pages go into the agents' runs on that project, so they work from your playbooks.
Will it sound like us, or like every other agency?: Like the client's brand: the voice, words to avoid and examples live in that client's Wiki. When you request changes, what the agent learns is proposed to its Brain for you to review before it is kept.