XO3D Studio · Methodology
The product CGI lifecycle.
Most product CGI is commissioned one campaign at a time, and most of it is rebuilt from scratch the next time it is needed. It does not have to work that way. One accurate build, made once to production standard, can serve four distinct commercial stages. This is what each stage asks for, what carries between them, and what the argument deliberately does not claim.

The studio behind this guide
What one build carries
XO3D builds one accurate 3D asset from your CAD, called the Master Asset, and every later deliverable is produced from it rather than rebuilt. That build can serve four commercial stages: showing the product before it is manufactured, carrying the launch across film, stills and social, supplying retail, configurator and AR surfaces during rollout, and supporting later markets, variants and successor products afterwards. Come to us when the product has a life beyond one campaign and you want the visual work to hold together across all of it. If what you need is imagery at catalogue scale, that is a different problem and a volume renderer is the right route.
How XO3D compares to the other five supplier modelsThe constant
One thing
does not
change.
The build. At XO3D it is called the Master Asset: one accurate 3D build, produced once to production standard, from which every deliverable is then made. Film, campaign stills, social formats, press, print, interactive and AR all come from the same source.
That is why a launch looks like one thing across every channel instead of like five suppliers, and it is why the stages below are stages rather than separate projects. Each one asks something different of the same asset.
For AUAR's MicroFactory launch, selected film compositions supplied stills for the website. Additional views showed how the robot would be used inside a factory. The shared scene supported both, but the intended use determined whether an existing shot was suitable or another view was needed.
What makes the asset able to carry is not scale or cleverness. It is accuracy at the point of construction. A model built from your CAD, with materials reconstructed from physical reference and colour held to a specified value, can be taken somewhere nobody planned for. A model approximated by eye cannot, and the failure shows up at the stage you did not anticipate. That standard is set out in product truth, and the governance that holds it is on process.
Four stages
What each one asks for.
The stages are commercial rather than technical. They describe where a product is in its life and what the visual work has to do there, not what software is open.
Stage one
Before the product exists
There is CAD, there are engineering drawings, there is a material and finish intent, and there is nothing to photograph. This is the earliest point at which a product can be shown, and for a launch that depends on pre-orders, investor conviction or a retailer buying decision, it is often the point at which the money moves.
The geometry and the material reconstruction are settled here. Both carry forward unchanged into every later stage, which is why this stage decides how much of the rest is reusable.
Stage two
At launch
The launch suite comes off the same build: the hero film, the campaign stills, the social formats, the press and print assets. Nothing is rebuilt to produce them. The work at this stage is direction and edit rather than construction, which is the whole reason the launch reads as one thing instead of as several suppliers.
The visual language is settled here. Lighting, camera language and grade become the reference that later work is matched against.
Stage three
Through rollout
Retail listings, marketplace imagery, a 360 viewer, a configurator, an AR placement. This is where the same product meets a different set of technical constraints, because a real-time surface has a budget that a rendered frame does not. What changes is the derivative, not the source.
The optimised, real-time derivatives are made here, from the same build. They are a different file, not a different product.
Stage four
After the first campaign
A second market, a seasonal push, a new colourway, a retailer refresh, a successor product that shares components with the one before it. None of these require the build to be made again. You own the delivered work and the commissioned model outright, with no limit on medium, territory or duration, and projects are archived indefinitely.
This is the stage stated as capability rather than as history. What the ownership split and the archive make possible is a returning brief that is a smaller scope of work than the original build.
Boundaries
What this
is not.
- It is not an efficiency argument
- This describes what one build can go on to serve, not what it costs or saves. XO3D does not publish rates, savings or efficiency figures, and any number attached to this elsewhere is not ours. What a commission is judged on is set out on measurement.
- It is not catalogue production
- One product carried across a launch’s channels, markets and variants is a different problem from producing imagery at SKU scale. Range and batch volume is deliberately out of scope here, and the exclusions are stated on investment.
- It is not automatic
- A later stage still needs direction, review and sign-off. The build removes the rebuild. It does not remove the decisions, and a brief that skips them produces the same asset used badly.
- Not every product needs all four
- Plenty of work is a single stage, and starting at stage one is not a prerequisite for anything that follows. The lifecycle describes what is available, not a sequence you are committed to.
The argument is about what becomes possible and what a later brief involves. Where a commission is judged on a commercial outcome, the data sits in your analytics rather than ours, and measurement sets out what a studio can and cannot see.
Related
Where to
go next.
Common questions
Straight
answers.
What is the product CGI lifecycle?
It is the four stages a single accurate 3D build can serve across a product’s commercial life: before manufacture, at launch, through retail and ecommerce rollout, and after the first campaign has finished. At XO3D that build is called the Master Asset. The point of naming the stages is that the geometry and material work done at the earliest one is the same work every later stage draws on, so what happens at the start decides how much of the rest has to be made again.
Does one 3D build really serve all four stages?
The source build does. The derivatives do not. A rendered film frame and a real-time AR model have different technical budgets, so the rollout stage produces optimised versions from the same source rather than using the source directly. That is a file-preparation step, not a rebuild, and the geometry, materials and colour values stay the ones that were approved at the start.
What has to be decided early for the asset to carry?
Three things. The geometry has to come from your CAD rather than an approximation, because a model rebuilt by eye cannot be trusted at a later stage that nobody anticipated. The materials have to be matched to physical reference, not left as library defaults. And brand colour has to be held to a specified value. Those are the checks set out in product truth, and they are what makes a build durable rather than merely finished.
Can XO3D start at a later stage than the first?
Yes, and most commissions do. A product already in market can have a Master Asset built from its CAD at any point, and the same four stages are available from there. Starting later costs you the earlier stages rather than the quality of the build.
What does this not cover?
It does not cover what the work did to your commercial numbers. XO3D can state what a build produced and where it was used, because that is our own production record, but conversion, returns and revenue sit in your analytics rather than ours and we will not claim them. It also does not cover catalogue or SKU-scale imagery, which is a different problem with different economics.
Start with one product
Tell us where
the product is.
Send the product, the source files you have and which stage you are at. We will tell you what one build would carry from here, and say plainly where a later stage is not worth commissioning yet.
Start a conversation