An AI ad workflow for agencies — workspaces, seats and exports

An agency has constraints a solo creator does not. Several clients, several people, one invoice, and a review loop that has to stay private until the client says yes. The creative part of AI video is the easy half; the half that decides whether it works in a shop is billing, access and where the drafts live. This is the setup we would run, with the arithmetic at the end. The short version is on the agencies use case.

One workspace, one wallet, real seats

Credits live on the workspace, not on individual accounts, so a team spends from one balance instead of five personal cards. Members hold a role on a five-rung ladder, invitations go out by email, and seats come with the plan — with one rule worth knowing before you pick: individual plans hold two people. Paying more for compute buys you credits and speed, not a team. A real roster starts at Team.

• Hobby $15 for 1,800 credits: 2 seats, 10 API keys
• Creator $49 for 6,000 credits: 2 seats, 20 keys, every video engine, 2× rate limits, priority video queue
• Studio $149 for 20,000 credits: 2 seats, 50 keys, 4× limits, clips up to 30 seconds
• Team $59 a seat, each seat adding 7,000 credits: 2 to 9 seats, 100 keys, 6× limits, shared folder links
• Agency $119 a seat, each seat adding 16,000 credits: 5 to 25 seats, 200 keys, 8× limits, shared folder links

Team and Agency are billed per seat, and every seat's credits land in one shared pool. Add a seat the day someone joins (it is charged at once, prorated); a seat you remove goes at renewal. What those plans sell is the team: seats, shared folders, more keys and higher limits. Credits alone are cheaper on Studio's larger steps, up to 60,000 credits for $399. Annual billing takes 20 percent off, seats included, monthly credits roll over forever, and credits never expire — which matters more than the headline number when half your months are pitch months. Anything larger goes through Enterprise at hello@eroq.ai. The pricing page has the full comparison.

The Ads Studio and one brand per client

The Ads Studio is organized the way an agency already thinks: by brand. Paste a client's website and Clap, eroq's agent, reads it in about a minute and fills a brand kit: logo, palette, fonts, tagline, tone of voice, selling points, audience, and the products it finds on the site. You review every field before saving, or type the kit by hand. An account holds up to 20 brands, and reading a site costs nothing.

The client's products enter as Elements: each one a reusable object with its photo and description, filed in the brand's folder on the Elements page, up to 50 Elements per account. The places and styles of the client's campaigns can be filed under the brand too. The kit then rides with every ad: its aesthetics and palette fold into the prompt, and its tone of voice, selling points and audience shape the copy Clap writes. The client's look is a saved kit rather than a paragraph everyone copies slightly wrong, and a new campaign is a few picks instead of a re-briefing. It is also how a junior's ad inherits the art director's rules without a meeting.

Inside a brand, the work splits three ways:

• Create → Image ads. Tick where the ads will run (Facebook and Instagram feeds, Stories & Reels, TikTok, Snapchat, Pinterest, Google Display, LinkedIn, X), then the products (or the brand itself) and how many ads of each, up to 24 pictures per batch. Clap plans the batch for free, one selling angle per ad with a headline, a primary text and a call to action cut to the strictest place, in the client's language, and each ad renders at the size of every place it runs (static ad generator).
• Create → Video ads. Where it runs, then one of eight formats (UGC testimonial, Product hero, Unboxing, Street interview and four more), a presenter from your Characters, a spoken line Clap writes, and a direction.
• Multiplier. One ad that works becomes 3, 6, 9 or 12 variants, each with a new character, outfit, location or product, while the motion, the cut and the original audio stay (Ad Multiplier).

Here is a video ad for a fictional client, a cold-brew brand: the In real life format, the cold brew bottle as the product, one of your Characters as the presenter, a line picked from the four Clap writes, and this direction:

A bright apartment kitchen at breakfast, the bottle comes out of the fridge with condensation beading on the glass, handheld camera following it up to the counter, hard morning light through a window, headroom at the top for captions.

Every render made in a brand lands in that brand's own Library folder, named after it, so the campaign material is filed by client before anyone thinks about it. The AI ad generator page has the overview. For free-form shots in the Video tool, the palette and lighting in the Settings panel do the same job and fold into the prompt server-side, while the camera move, lens and aperture are written in the prompt itself or dropped in from its Syntax menu. Enhance rewrites a rough draft there into a director-grade prompt for free, which is a useful equalizer when the person writing the brief is not the person who shoots.

Review happens on a private link, not in public

Say this part out loud to the team: client work never goes to the community. Publishing there is a public act — title, cover, likes, comments, views — and it is for your own reel, not for a campaign under embargo.

Client review runs on the private library. Every render is saved automatically with its full recipe, visible to the workspace, so the account manager can see the takes without asking the editor for a link. Give each campaign a Library folder and pick it in « Save to » before the first render — Image, Video, Voice and Cinema then file every take in it on their own.

When it is time for notes, share the folder. On Team, Agency and Enterprise a folder gets a public link (eroq.ai/f/…) the client opens without an account: the files and nothing else — no prompt, no engine, no settings — downloadable or view only. The page follows the folder, so a revised take dropped in shows up on the link already sent, and stopping the share kills the link the same second. Approved cuts can still leave as downloads, into the deck, the shared drive, or the edit. If you cut in Premiere Pro or After Effects, the eroq panel generates from inside the app and imports renders straight into the open project, saved under ~/Documents/eroq; it is distributed unsigned today, so it installs in developer mode.

The corollary is a good habit anyway: one review link, one round of notes, then a Remix of the exact recipe rather than a fresh prompt that quietly changes three other things.

The API for the repetitive third

Some of the work is not creative at all — forty variants of the same spot with a different end card, or the same three shots in three formats. That part belongs in a script. The REST API is OpenAI-shaped at https://eroq.ai/v1 with a Bearer key: images/generations, videos/generations as an async job you post and then receive on a signed webhook, audio/speech, and films for whole storyboards, where one render call shoots every scene. Rate limits are per key — 60 chat requests a minute, 20 images, 6 video or speech — multiplied by your plan.

Per-key limits are the reason to issue one key per client or per campaign: a runaway job on one account does not starve the others, and usage per key is the closest thing to a per-client cost line you will get without an accountant. The docs cover the endpoints, and there is a CLI and an MCP server if the automation lives in a coding agent instead of a cron job.

What a campaign costs

A six-short campaign, three 5-second clips per short on Motion One at 145 credits per 5 seconds, plus one cover still at 10 credits:

• Per short — 3 × 145 + 10 = 445 credits
• Six shorts — 6 × 445 = 2,670 credits

That is about $26.70 at the entry pack rate of $10 for 1,000 credits. Shoot the same campaign on Kling 3.0 (270 credits per 5 seconds) and it is 6 × (3 × 270 + 10) = 4,920 credits. At the Agency seat rate ($119 for 16,000 credits) that campaign costs about $36.59; at the Team rate ($59 for 7,000), about $41.47. The smallest Agency workspace (5 seats) pools 80,000 credits a month, so size the seat count to the people and let the pool absorb the busy weeks.

Add takes to taste — a second take on the hook shot of each short is 6 × 270 = 1,620 credits on Kling — and remember that failed renders refund themselves and blocked requests are never charged, so the estimate does not need a padding line for accidents.

FAQ

Can each client have their own budget?

Credits are pooled per workspace, so the cleanest split is one workspace per client when budgets must not mix, and per-key usage inside a shared workspace when they only need to be reported. Individual plans hold 2 people; Team takes 2 to 9 seats and Agency 5 to 25, all spending from the same pool.

Can the client review without an eroq account?

Yes, on Team, Agency and Enterprise: share the campaign folder as a public link. The client sees the files only, and you choose whether they can download them. It is not a community post — nothing is listed or indexed — and it stops working the moment you stop sharing.

Which content rules apply to client work?

The written acceptable use policy — edgy, dark and provocative concepts included; nothing involving minors, nothing illegal. Motion One is the uncensored video engine and is available on every account; the premium engines are moderated upstream by their providers, and a prompt they refuse returns content_blocked and costs nothing. Real identifiable people without consent are banned outright on every engine, which rules out the deepfake requests you will occasionally be asked for.

How do we hand off to the client's editor?

Share the campaign folder as a link with downloads on, download the renders yourself, or import them straight into Premiere Pro or After Effects with the panel. Everything stays in the workspace library with its recipe, so a change request two weeks later is a Remix of the approved take rather than a rebuild.

Setting up a shop? Get an API key, create the workspace first, and make each client's product an Element before anyone writes a prompt.