The three stages every configurator project goes through, from CMS build to live integration on the customer's site.
We create and configure the 3D models, materials, option groups, rules, and camera presets inside the London Dynamics CMS. This is entirely our responsibility — the customer is not involved in the build itself.
Option names and variant IDs are agreed with the customer's developer before build starts, so their team knows exactly what to map against when they integrate.
LD scopeOnce the scene is published, the customer's developer drops a single embed snippet into their page template. No 3D knowledge is required on their side — the viewer, controls, and AR button are all served by our platform.
For projects with a custom UI, we build the interface code and hand it over at this stage. The customer integrates it alongside the embed, in whatever framework they use.
Shared scopeOur feature and variant IDs need to map to the customer's existing SKUs, pricing, and cart logic. This wiring is done by their developer using the event API we provide — we do not touch their backend or ecommerce platform.
The scope for this step is agreed in the project brief before build starts. A short alignment meeting between the LD team and the customer's developer is always required in week one.
Customer scopeWhat we deliver, what the customer delivers, the pre-build checklist, and a full responsibility split table. For project kick-offs and scoping conversations.
What the configurator looks and feels like, which integration mode to recommend, and live interactive demos for all three modes.