Give it your product photos,
get back a full set you can shipConsistent as a batch, named, sized and written back to your catalogue
In
Photography you already have
Out
Scenes · sizes · social · video
Runs on
Your own servers
Live in
2–4 weeks
The pipeline in one line
Photography in, a shippable set out
What goes in
The product photography you already have. No reshoot, and no need to organise it into a particular format first.
What comes out
Scene imagery, sized hero and detail images, social crops and short-form video source material — consistent across the batch, with filenames and alt text generated, ready to write back to your catalogue.
The part in between
Runs on your own servers. Material, configuration and models never leave your boundary, and nobody is billing you per image.
What actually goes wrong
It isn't ugly, it's uncontrollable
Different every time
The same prompt ten times gives you ten different looks. Fine for one image, fatal for a product range.
You can't specify it
“Product on the left, space above” — a text description can't control layout precisely. Every revision is another roll of the dice.
The product comes out wrong
A general model has never seen your product, so the details are invented. On a commerce detail page that's disqualifying.
And one more practical one: outsourced product imagery costs tens of currency units per image, takes days, and still doesn't match across a set. Launch often enough and artwork becomes the bottleneck for everything downstream.
Three tiers
Not one method — a choice between three
Straight generation
A general model generates the image outright. Suited to mood shots, backgrounds and social filler — anything where the product doesn't have to be exactly right. High volume, fast turnaround.
The limit: the product's actual form is guessed. Not acceptable for a hero or detail image.
Constrained generation
Your real photograph is the reference the output is bound to: the product itself isn't repainted, only the background, lighting and setting are rebuilt. Framing and silhouette hold, a batch comes out as a set, and it can go straight onto a product page.
The prerequisite: the product needs one usable photograph to work from.
Brand-specific model
A model trained on your own product photography, so it knows your products specifically. After that you no longer need a reference shot every time to get the form right — including angles and settings photography can't practically reach. Worth it with many SKUs, frequent launches, or heavy demand for scenes you can't shoot.
The model is your asset. It lives on your servers and you can take it with you.
The three mix. Hero images at tier two where accuracy is non-negotiable, scenes and social at tier three for volume, mood material at tier one. We give a recommendation per category during the diagnostic — including “tier two is enough, don't pay for tier three”where that's the honest answer.
How a batch gets through
Four stages, one of them yours
Your own team runs the next launch without us. For scale: selection takes us roughly 20 seconds an image, about eight minutes for a batch of 24 — but that's our own pace on our own catalogue, not a commitment about yours. Your batch sizes, categories and review standards differ, and we estimate against them during the diagnostic.
Video
The same material, extended into short-form video
What's delivered is repeatable production capacity, not a folder of finished clips. Next month's launch runs the same pipeline with your own people. That's the difference from commissioning a batch of videos: that budget is spent and gone, this one leaves something behind.
Not included in this part
- ✕Physical photography
- ✕Voice talent and on-camera models
- ✕Scripting and creative direction
Brand-specific model
What training one asks of you
What you end up with
A pipeline that runs itself, not a folder of images
A repeatable pipeline
The same configuration next month produces a set that matches this month's. Nobody has to remember how it was tuned.
Your brand-specific model
Delivered when you go to tier three: trained on your product photography, stored on your servers, dependent on no platform.
An export standard
Sizes, spacing and naming rules for hero, detail and social, written down and handed over so a new hire can follow it.
A run log
Who approved each batch, when, and how many frames came out — traceable, and resumable from where it stopped.
Not included
- ✕Physical photography: materials, real usage settings, models
- ✕Models, locations and location shoots
- ✕Voice talent, on-camera models, scripting and creative direction
- ✕Holding your ad accounts or making budget decisions
- ✕Content compliance and legal review
When it isn't worth doing
- ✕A few launches a year and a few dozen images total — outsourcing is cheaper
- ✕No brand visual standard yet: a machine executes a standard, it can't decide one for you
- ✕Products that look different every batch — there's no stable feature for a model to learn
- ✕You want a handful of striking campaign images — that's creative work, not pipeline work
What this looks like wired into a storefront: E-commerce automation & support agent →
Questions
What people ask about this one
01Which tier do we need?+
One question decides it: will a customer use this image to judge what the thing actually looks like? If yes — hero images, detail pages — start at tier two, where the product's form has to be correct. If no — mood shots, backgrounds, social filler — tier one is enough and anything more is wasted money. Tier three earns its cost when you have many SKUs, launch often, or need volumes of angles and settings photography can't reach. During the diagnostic we give a per-category recommendation, including “tier two is all you need” where that's the answer.
02Can the output go live as-is?+
Yes, but it passes one of your people first. Selection is the step we deliberately don't automate — a hero image moves your return rate, and nothing in that category should publish without a human having looked at it. The machine prepares the candidates and every size; which version ships is your call.
03Do we need a brand visual standard first?+
Ideally yes. If there isn't one we'll set it once and write it down, and it stays fixed after that so a new hire can follow it. But to be clear about the boundary: a machine can execute a standard, it can't decide what your brand should look like. Without that decision, the output can only be attractive — it can't be recognisably yours.
04Is the custom model a recurring cost?+
No. Training material, configuration and the model file are all on your own servers and belong to you; you can keep training new versions or hand it to someone else. We don't bill per image or per call, so how much you generate doesn't change your cost structure.
05Our products look different from batch to batch. Can this work?+
Not tier three — there's no stable feature for a model to learn, and forcing it produces something unreliable. We'll tell you that directly. Tiers one and two still hold: as long as this batch has been photographed, scenes and backgrounds can still be produced at volume.
06Does adding a category or a video line later cost extra?+
Yes, and it's written into the contract at signing rather than raised mid-project. Day-to-day maintenance — revising the standard, adjusting parameters, adding sizes, routine checks and incident response — your own technical people can handle, or you can buy an annual maintenance subscription. A custom model for a new category, a new video output line, or connecting a new catalogue system is new development, scoped and priced as a new project. Splitting it this way keeps the accounting honest: folding new work into a maintenance fee either inflates the fee or means the new work gets done carelessly.
Next