XO3D Studio · Delivery and integration
Where the work
goes live.
XO3D delivers three things into your environment: the final files, a production-ready 3D model, and where the brief calls for it, a built interactive or AR experience. How that reaches a live site varies by project. Sometimes our in-house developers build and embed it. Sometimes your team implements from what we deliver. What stays with you, by design, is the commerce platform, CPQ, CRM and analytics, because a studio should not sit in the middle of a system it does not operate.
Four honest routes
Who does what,
and when.
There is no single correct answer here, and a studio claiming otherwise is selling rather than advising. This is how the four routes actually compare.
Our developers build it.
The experience itself is the deliverable, or your front-end team has no capacity for it.
XO3D has in-house web development. We build and run our own estate, including the Labs tool platform, its embeddable widgets and its account layer. Where a brief needs the interactive built rather than just the asset supplied, that work can sit with us.
Your developers implement it.
You own the platform and the design system, and the 3D asset is what you actually need.
We deliver the model and agreed outputs to your specification and your team takes it from there. This is the cleanest boundary and it is the right answer more often than studios like to admit.
Your platform vendor handles it.
A configurator or product module already exists and needs assets to a defined spec.
We produce to the spec their platform requires. The vendor keeps the integration they built and support, and nobody ends up maintaining a system they do not operate.
Your agency runs the build.
The CGI is one part of a wider campaign or site build somebody else is leading.
We work to the creative direction and the delivery schedule already agreed, with the handoff and approval owners defined before production starts.
The boundary
What stays
yours.
We take the 3D, the interactive and getting it live, including web build where that is the right route. Three things stay on your side, and not because we cannot reach them.
- Commerce platform, PIM and DAM
- Your product data and asset management stay yours. We deliver to the specification your systems require, which is a specification met rather than a pipe connected.
- CPQ and CRM
- Quoting and customer records are operational systems tied to your pricing, your rules and your sales process. A visual studio has no business inside them.
- Analytics, testing and attribution
- Measurement belongs where the data lives. We can tell you what to measure and what good looks like, and the reporting stays in your stack.
A stated edge is worth more than an open offer. It means the scope you agree is the scope that gets delivered, and nothing important is left sitting between two suppliers who each thought the other had it.
On the measurement side of that boundary, what to measure and who owns it sets out the primary measure worth agreeing for each kind of commission, and what a studio can and cannot see.
Most projects
The handoff,
in detail.
On the majority of briefs, integration means a delivery your team can use immediately. That is a specification question, and it gets settled at brief stage.
- Formats
- Stills as TIFF or PNG, motion as ProRes or H.264, 3D as GLB, GLTF, USDZ, FBX or OBJ. Confirmed against your requirement before delivery, not after.
- Colour and resolution
- sRGB for digital, Adobe RGB for print, at the resolutions each channel actually needs.
- Naming
- An agreed naming convention across the whole delivery, so the files arrive usable rather than needing renaming.
- Review
- Structured review through Frame.io for video or an equivalent for stills, with links scoped to named people on your side.
Meeting a retailer or marketplace specification is part of the deliverable, not a separate project. See CGI for ecommerce for how hero, silo, lifestyle and detail imagery is built for product detail pages and retailer listings.
Interactive and AR
Where it
actually runs.
A viewer, configurator or AR model has to run somewhere, load fast enough on your worst-case device, and survive your site's content security policy. Those are the questions that decide feasibility, and they are worth asking before anyone builds anything.
XO3D builds and runs embeddable experiences on its own platform, so the delivery route is not theoretical: the Labs tool platform includes a published embed system and widgets designed to sit on third-party sites. On client work the route varies, and hosting on our side can be arranged where it is genuinely the better option.
For what each interactive format supports and when it is worth doing at all, start with when do you need interactive 3D, then Product Interactives and Product AR.
Choose the right route
Where to
go next.
Before you brief
A few technical
answers.
Who builds the interactive or configurator, XO3D or our developers?
It varies by project and it is agreed before production. XO3D has in-house web development and can build and embed the experience. Equally, if your team owns the platform and the design system, we deliver the 3D asset and outputs to your specification and your developers implement. What decides it is usually who owns the surface it runs on and what front-end capacity you have.
Can XO3D deliver assets straight into our PIM, DAM or commerce platform?
Delivery is a file handoff or a built and embedded experience, produced to whatever specification your systems require. XO3D does not write into your product data or asset management systems, and would not recommend a supplier who offered to. Meeting a retailer or marketplace specification, including specific requirements from retailers such as John Lewis, AO.com or Currys, is a standard deliverable requirement rather than a separate integration project.
Does XO3D provide analytics, A/B testing or conversion reporting?
No, and that is deliberate. Measurement belongs where your data already lives, in your analytics, your commerce platform and your CRM. We can advise on what to measure for a launch and what a reasonable result looks like, and the reporting stays yours. A studio that owned your measurement would be reporting on its own work.
Can XO3D host the experience for us?
Where hosting on our side is genuinely the right route it can be arranged and has been done. More often the better answer is that the experience lives on your infrastructure, because that is where your uptime, your security review and your support arrangements already are. Worth deciding at brief stage rather than at delivery.
What do you need from our team to get an interactive live?
A named technical contact, the platform and page it needs to run on, any performance or file-size limits your site enforces, your supported browsers and devices, and who signs off the implementation. Where an embed is the route, we also need to know any content security policy restrictions that would block it. Resolving those before production is faster than discovering them at launch.
Start with the setup
What does it
have to plug into?
Tell us the platform, who owns the front end, and what the experience needs to do.
Talk through your setup