§01 · Who this is for

Twelve clients. Twelve brand kits. Nobody touches the wrong one.

Caroufy for Agencies runs the same carousel engine as the solo product — the part that turns a blog post, a script, or a source PDF into a slide-by-slide carousel — inside an account structure built for handling more than one brand at a time. Each client gets an isolated workspace: its own brand kit, its own drafts, its own approval history. A designer working inside one workspace can't see, edit, or accidentally export anything that belongs to another.

It exists for the specific moment carousel work stops being a creative problem and becomes a logistics one: brand guidelines pasted into three different Slack channels, a freelancer working from a color palette they remember instead of the one that's current, a client asking why last week's post used the wrong shade of blue. If you're producing carousel content for a single brand — your own, or one client's — the solo version of Caroufy already covers that, and everything below this line is overhead you don't need yet.

§02 · Solo vs Agencies

Same engine, different account shape.

Carousel generation itself — paste in source content, pick a template, get a slide deck back — doesn't change between tiers. What changes is everything built around it.

§03 · Approval workflow

How a draft becomes a delivered post.

Every carousel in an agency workspace moves through the same sequence. Internal review is optional and set per workspace. Client review is on by default — the point of the queue is that nothing reaches a client's feed without the client having seen it first.

§04 · Roles & permissions

Four roles, on purpose.

The role model is deliberately small. Owner and Admin can do almost everything within the workspaces they're assigned to; the practical difference is that only the Owner sees billing and can remove other Admins. Designer can build and edit drafts inside assigned workspaces but cannot touch the brand kit itself — the fonts, color tokens, logo lockups, and locked template regions stay under Admin control. That's the actual mechanism that lets a junior hire produce on-brand work without being able to drift off-brand. Client Reviewer is scoped to exactly one workspace, sees only what's been submitted for review rather than internal drafts, and can approve or request changes but never edit.

Workspace assignment is separate from the role itself. An Admin at a twenty-client shop is rarely assigned to all twenty; account owners scope people to the clients they actually work on.

§05 · Pricing

Priced on two axes, because clients and headcount don't grow together.

An agency might pick up a new client without hiring anyone, or hire a new designer without picking up a new client. Pricing tracks both separately: a seat count for people, a workspace count for clients. Client Reviewer accounts don't count as seats — external reviewers are free and unlimited, since charging a client's marketing coordinator to click "approve" would be a strange way to run an approval queue.

Both plans bill monthly by default. Annual billing is available and works out to roughly two months free. No setup fee, no minimum term.

§06 · What this isn't

The honest limits.

Worth being upfront about, since the feature list above could imply otherwise: