Marketing creative goes stale the moment a price changes

A designer makes forty product creatives for a campaign. Each carries a name, a price and a photo, typed and placed by hand. Two weeks later the price of nine of them changes, and there is now no way to know which nine files are wrong except by checking all forty.

Most teams do not check. The ads run, slightly wrong, and the cost lands on somebody in customer service explaining why the advertised price is not the price.

One template, one render per row

Rutba Studio fills a template from a dataset: a CSV or JSON file in your library, or rows pasted in. Pick a template, choose the dataset, and it renders once per row, with that row’s name, price and picture filled in. When prices change, the creatives are rendered again from a template that was never wrong, rather than corrected, one file at a time, by somebody who noticed.

It is a mail merge, pointed at an image. What it is not is a live link to your catalogue: Studio does not read the catalogue itself, so a dataset is only as fresh as the export it came from, and re-running it after a price change is still somebody’s job.

The render worker, and why a queue

Two applications ship. Studio is the editors: video, image and slides, rendered in the browser you are already in, with brand libraries and a deck designer. Render worker is the queue for the renders a browser tab cannot do.

• Unattended runs, so a render does not die when somebody closes the laptop.
• Batches: one template across every row of a dataset, which is the actual job in an e-commerce team.
• An MP4 rendered on a server at the end, rather than whatever the browser managed.

Anything that renders in a tab is hostage to the tab. That is fine for one image and useless for forty.

Brand kits, for teams without a designer

Fonts, colours and logos applied consistently. This is aimed squarely at small teams with nobody on staff whose job is design, where the alternative is not worse creative, it is no creative, or a stock template with somebody else’s colours in it.

It requires Rutba Social, and that is not upselling

Creatives attach directly to scheduled social posts, and Studio lists Social as a hard requirement. The reason is the workflow rather than the bundle: producing an asset and then downloading it to upload somewhere else is the step this product exists to remove.