CONTENT CREATION

Generate A/B background variants and auto-score them

Triggered manually on a chosen product, renders three competing background styles with Replicate, scores each for product clarity and brand fit using OpenAI vision.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggermanual
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerManual run with packshot and product
  • ActionRender 3 background variants via ReplicateReplicateReplicate
  • ActionScore each variant with OpenAI visionOpenAI
  • LogicRank by score, flag below threshold
  • OutputSave ranked set to Google DriveGoogle DriveGoogle Drive

What it does

Produces three distinct background treatments for one product and uses an AI vision check to rank them on whether the product stays sharp and on-brand. You get a ranked, ready-to-test set instead of eyeballing renders one by one.

When to use it

Use it when you're A/B testing hero imagery and want a fast, consistent first-pass quality screen before a human picks the test variants. Run it ad hoc on any single SKU.

How it works

  1. 1An operator manually triggers the flow with a packshot URL and product name.
  2. 2Replicate renders three background variants from the same packshot using three different scene presets.
  3. 3OpenAI vision evaluates each render for product clarity, scene realism, and brand fit, returning a score per variant.
  4. 4The variants are sorted by score and any failing a minimum threshold are flagged.
  5. 5The ranked images and their scores are saved to a Google Drive campaign folder for the team to review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ReplicateImage, video, and model inference.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.