Cindy Zhu.
Free guides
Marketing & ads Claude

How to bulk-create ad creatives inside Claude

Hey, it's Cindy ๐ŸŒฑ You commented CREATIVES, so here is the connector setup and the variation prompt that writes twenty scripts which are actually different from each other.
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)

The reason most people never test their ads properly is not laziness. It is that a variation used to cost a shoot. When making creative number two means another day of filming or another creator fee, of course you run one ad and hope. The moment a variation costs a sentence and a few minutes of render time, testing stops being a luxury and becomes the normal way to work. That shift is what this setup buys you.

The plan gate, up front. The writing half runs on any Claude plan, Free included. The video half is paid: Arcads' own documentation says you need an Arcads account with an active subscription and remaining credits, because every generation spends credits and requests fail once you run out (Arcads MCP docs). Arcads does not publish a public pricing page, so read the current plans on your own billing screen after you sign up rather than trusting a per-video figure from a blog post.

the idea

You are building a test, not twenty ads

Twenty random ads teach you nothing. Twenty ads where nineteen things are held identical and one thing moves teach you exactly which thing moves the numbers. That is the whole discipline, and it is the part the tools do not do for you. Before you generate anything, decide which single variable you are testing this round.

๐ŸŽฃ The hook The first spoken line. Test this first, always. In short-form video the opening seconds decide whether anything else gets watched, so a hook test is the highest-information test you can run.
๐Ÿฉน The pain point Which problem you lead with. Same product, same offer, different reason to care. This is the test that finds an audience you did not know you had.
๐Ÿง  The proof What you use to make the claim believable: a number, a before and after, a named customer, a guarantee. Swap only this and you learn what your market actually trusts.
๐ŸŒฑ The ask The closing line. "Link in bio", "start free", "see if you qualify". Cheap to test, and it moves click-through more than people expect.
๐Ÿ“Œ One round, one variable. If the hook and the pain point both change between two videos and one wins, you have learned that something worked without learning what. Lock everything else: same offer, same actor, same setting, same length, same ask.

step one

Give Claude the offer brief

Open claude.ai and start a fresh chat. This first prompt is not the creative, it is the ground truth everything else gets generated from. Spend five minutes here and the twenty scripts come back specific instead of generic.

๐Ÿ“‹ lock the offer brief
I am about to generate a batch of short video ad scripts with you, and before we write anything I want you to interview me and then write the brief we will both work from. Ask me these things one message at a time so I can answer properly: what the product is and what it literally does, who buys it and what their day looks like before they find it, the single strongest outcome a customer gets, the price and how it is billed, the two objections that kill most sales, and the platform these ads will run on.

When I have answered, write the brief back to me as a short document with these labelled sections: product, buyer, core outcome, price, objections, platform, and a list of the specific claims I am allowed to make. In the claims section, only include things I actually told you or that appear in material I paste in. Do not add benefits, statistics, guarantees or emotional promises that I did not give you, and if a section is thin, say which question I answered weakly instead of filling the gap yourself.

Keep the brief under 400 words and write it in plain spoken language rather than marketing language, because everything you generate from here has to sound like a person talking, not a landing page.
๐ŸŒฑ Have customer reviews, support tickets or DMs? Paste fifteen of them in with your answers and ask Claude to pull the buyer's exact phrasing into the brief. Ads written in your customers' words beat ads written in your words almost every time.

the main event

The variation prompt

This is the one you came for. It writes twenty scripts from the brief you locked, isolates one variable, and hands you a numbered table so you can tell afterwards which line did the work. Paste it into the same chat.

๐ŸŽฏ twenty variations, one variable
Using the brief above, write me twenty short video ad scripts for the same offer. The variable I am testing this round is the OPENING HOOK. Every other element must be identical across all twenty: same offer, same core outcome, same single claim in the middle, same closing ask, same length.

Each script is spoken by one person to camera and must run under twenty seconds when read aloud, which is roughly forty to fifty words. Structure every one the same way: one hook line, one line naming the problem in the buyer's own words, one line landing the product as the fix, one closing ask. Write the way people actually talk, including contractions and slightly imperfect sentences, and do not use ad language like "unlock", "elevate", "game-changer" or "revolutionary".

Make the twenty hooks genuinely different in KIND, not twenty rewrites of one idea. Cover at least these angles and label which is which: a direct outcome statement, a specific number, a question, a mistake or warning, a contrarian take, a personal confession, a before and after, a callout to a specific type of person, a curiosity gap, and an objection said out loud first. Two per angle.

Output as a numbered list where each entry shows: the angle label, the hook line on its own, then the full script. After the list, add a plain table with three columns, script number, angle, and hook, so I can paste it into a spreadsheet and record results against it. Do not generate any video yet and do not send anything anywhere until I say go.

Read all twenty before you render a single one. Reading takes three minutes. Regenerating twenty videos because the tone was off costs credits you cannot get back. Delete anything that makes a claim your brief did not authorise, then tell Claude which numbers survived.


step two

Connect Arcads to Claude

Arcads is the tool that turns each script into a talking-head video with an AI actor. Connecting it to Claude means you never leave the thread: the scripts you approved go straight through to be rendered. There are two routes, and you only need one.

In the Claude app

Add Arcads as a custom connector once and generate from a normal chat. Nothing to install, no terminal. Pick this if you have never opened Claude Code.

In Claude Code

Install the official Arcads plugin, which brings the same connection plus ready-made ad skills for competitor research and hook cloning. Pick this if you want the research half too.

  1. ๐Ÿงฉ Open Claude and go to Customize, then Connectors. This is the same screen where any other tool gets added to Claude.
  2. โž• Choose add a custom connector. Arcads is not in the built-in gallery, so it goes in as a custom one.
  3. โœ๏ธ Name it Arcads and paste the server address. The address is https://mcp.arcads.ai. Save it.
  4. ๐Ÿ”“ Click connect and approve the sign-in. That links your Arcads account and the Arcads tools appear inside your Claude conversations. You do this once, not per batch.
  5. ๐Ÿ‘ฉโ€๐Ÿ’ป Prefer the terminal? In Claude Code, run /plugin marketplace add arcads-ai/skills, then /plugin install arcads@arcads, then /mcp to sign in. The plugin ships its own connection, so installing it wires up Arcads for you. The repo is public at arcads-ai/skills.

step three

Render the batch without burning credits

  1. ๐Ÿง Approve the actor first. Describe the person once: age range, energy, setting, lighting. Generate one sample before you commit twenty scripts to that face. The actor is the constant in this test, so changing it halfway invalidates the round.
  2. ๐Ÿซด Attach a clean product photo. Plain background, sharp focus, label readable. Tell Claude to keep the product exactly true to the image, no redesigning and no generic substitute for the category.
  3. ๐Ÿ”ข Render in two waves, not one. Send five first. Watch them. If the pacing, the delivery or the framing is off, you have spent a quarter of the credits finding out instead of all of them.
  4. ๐Ÿท๏ธ Make Claude label the outputs. Ask for a plain list mapping each finished video back to its script number and angle. Unlabelled files are the single most common reason a test round produces no learning.
  5. ๐Ÿ—‘๏ธ Cut before you upload. Watch each one with the sound on and drop anything where the delivery undercuts the line. A weak read will lose the test for a hook that was actually fine.
๐ŸŽฅ render the approved scripts
Send scripts 1 to 5 from the approved list to Arcads using the actor and product we already approved, and keep everything except the hook line identical between them so the test stays clean.

Before you send anything, show me in one line what you are about to generate and wait for me to confirm, because every generation spends credits I cannot get back. After they render, give me a plain list mapping each finished video to its script number, its angle label, and its hook line, so I know exactly what I am about to test.

Then stop and wait. Do not render the remaining scripts until I have watched these five and told you to continue.

close the loop

Read the results, then build the next round

A test only pays off if you write down what happened. Run the batch, give it enough spend and enough time that the numbers mean something, then bring the results back to the same thread and let Claude do the reading.

๐Ÿ“Š tell me what actually won
Here are the results from the batch you wrote, pasted below as rows of script number, spend, impressions, three-second views, clicks, and conversions.

Read them against the angle labels you assigned earlier and tell me which ANGLE won, not only which individual video won, because I care about the pattern I can repeat rather than one lucky script. Group the results by angle, show the average for each group, and say plainly where the sample is too small to trust. If two angles are within noise of each other, say so instead of picking a winner to be helpful.

Then write the next round: fifteen new scripts that all use the winning angle, varying only the specific wording of the hook, plus five that test the runner-up angle so I keep a small bet on the alternative. Keep the same offer, actor, structure and closing ask as before.
๐Ÿง  Keep one spreadsheet across rounds with columns for round, script number, angle, hook, spend, and result. After three rounds you stop guessing what your market responds to and start knowing, and that knowledge outlives any individual tool.

the honest bit

Four things to know before you spend

๐Ÿ’ธ Credits are the real budget Every generation spends them, including the ones you throw away. Approve scripts on the page and approve the actor before rendering video, and treat the first batch as a learning cost.
๐Ÿ“ข AI actors carry disclosure rules Several platforms require AI-generated content to be labelled, and the rules differ by country and platform. Check the policy where you are posting before the ads go live.
โœ๏ธ The claims are yours Claude writes the hook, you are the final read. Nothing goes behind ad spend until you can back up every sentence in it.
โณ Give the test room Twenty creatives split across a tiny budget produces twenty meaningless numbers. Either fund the round properly or cut it to five variations and test in waves.

Everything in one place

  • ๐Ÿค– Claude: claude.ai. Connectors live under Customize, then Connectors.
  • ๐ŸŽฌ Arcads: arcads.ai, and the connector address is https://mcp.arcads.ai.
  • ๐Ÿ“„ Arcads' own setup documentation, including the credits requirement: Arcads MCP help article.
  • ๐Ÿ‘ฉโ€๐Ÿ’ป The official plugin repo for Claude Code: github.com/arcads-ai/skills.
the waitlist is now open

AI System Club is launching soon

Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.

btw this list gets first dibs
the moment doors open :)