For agencies

Every client in their own lane

Client work fails at the boundaries: the wrong voice, the wrong account, or an unreviewed post. Separate tenant-isolated workspaces provide the strongest boundary; advisory reviews and explicit publishing make responsibility visible.

Start free See the workflow

How does multi-client work stay separated?

Use a separate workspace per client when a hard boundary matters. Each workspace carries its own Brand Kit context and connected accounts, database tenant policies isolate workspace rows, and roles control who can draft, review, connect accounts, and publish. This is a tenant boundary, not a claim that an in-workspace brand selector makes mistakes impossible.

Separate workspace Brand Kit context per strictly isolated client
Workspace isolation enforced by database tenant policies
Roles and invitations for account teams
Recorded advisory review decisions; publishing stays separate
Provider receipts per delivery — client-showable state

What does the client-approval loop look like?

Draft in the client's workspace context, request an advisory review, and then separately choose whether and when to publish through that workspace's connected accounts. The review record identifies the actor and decision; it does not freeze the content or authorize delivery. Successful delivery stores a provider receipt.

What does honest delivery state buy an agency?

Trust. publishing uses durable idempotency reservations to reduce duplicate risk, and ambiguous provider outcomes stay reconciliation-required instead of being reported as confirmed success. When a client asks whether Tuesday's post went out, the answer is a receipt, not a guess.

Frequently asked questions

How do I keep client brands from cross-contaminating?

Use a separate workspace for each client that needs strict isolation. Database tenant policies isolate workspace data, while the workspace Brand Kit and connected accounts provide that client's working context.

Can clients approve posts before publishing?

Invite them into the workspace with a role, or run advisory reviews internally. The system records the decision, but approval is not a publishing gate; delivery still requires a separate explicit action or configured schedule.

Can I prove a post was delivered?

Successful deliveries store provider receipts. Metrics can be synchronized on demand where supported, and ambiguous outcomes remain reconciliation-required instead of being presented as confirmed success.

How does agency billing work?

Plans are recurring subscriptions with visible renewal dates and cancellation controls, and AI work meters through an append-only credit ledger — predictable costs you can map to client work.

Write once. Post everywhere.

Draft in your brand voice, approve what matters, and publish with confirmed delivery state.

Start free