Section 01
What we deliver
Our scope ends at the handoff point — a working 3D scene in the CMS and an embed snippet. Everything after that is the customer's integration work.
→ London Dynamics delivers
- ✓ 3D scene with all models, materials, and lighting
- ✓ All option variants configured in the CMS
- ✓ Rules (e.g. "sink only available in position 2")
- ✓ The embed SDK and documentation
- ✓ Custom UI code (swatches, steps, grids) — if in scope
- ✓ AR functionality — included by default
Not our responsibility
- — Cart / add-to-bag integration
- — Pricing display or price list management
- — Product labels and copy on the customer's site
- — Final styling to match the customer's design system
- — Hosting or CMS subscription management
Section 02
What the customer delivers
The customer's developer handles the integration side. Make sure they have capacity before we schedule the handoff — blocked integrations are the most common cause of delayed go-lives.
- → Mapping our variant IDs to their product SKUs, pricing rows, or CMS entries
- → Adding the embed snippet to their page template or CMS
- → Any cart / add-to-bag integration using our selection events
- → Final CSS to match their design system (if we supplied a custom UI)
- → Hosting the custom UI code within their own deployment pipeline
- → QA and sign-off on the live integration
Tip: The ID alignment meeting (agreeing option names and variant IDs before the build) is the single most important dependency. If it slips past week 1, the whole project timeline shifts.
Section 03
Before the CMS build starts
Use this as your kick-off checklist. Every item here, if missed, risks a rework cycle during or after the build.
Agree all option names and their variants with the customer's developer
These become the variant IDs baked into the 3D scene. Renaming them later requires a CMS update across every rule and preset.
Confirm which options have rules
E.g. "sink only available in position 2", "charcoal colour not available with gloss finish". Rules need to be modelled in the scene — they're not free to add later.
Decide: default SDK panel or custom UI?
Custom UI adds dev time (1–5 days). If the customer hasn't decided, default panel first, then upgrade — it's a clean swap.
Confirm the viewer dimensions and responsive breakpoints
What aspect ratio? Does it need to be full-bleed on mobile? This affects how we frame the scene in the CMS.
Customer has a Customer ID UUID from the CMS
Find it in Brand Settings in the CMS. Required for the embed snippet — without it nothing loads.
Confirm whether AR is wanted
AR is on by default. If the customer wants it off (e.g. B2B tool, no AR use case), confirm before build so we don't have to patch it after sign-off.
Customer's dev team has capacity to integrate during handoff week
The most commonly missed item. "We'll do it next sprint" often means 4 weeks of delay. Confirm a named developer and a date before kicking off.
Section 04
Responsibility split
Use this table in kick-off calls to align expectations. The "Shared" column means both parties need to agree or act.
| Area | London Dynamics | Customer |
|---|---|---|
| 3D scene, models, materials, lighting | ✓ | |
| Option rules (hide / disable variants) | ✓ | |
| Option IDs and variant names (agreed together) | → agree | → agree |
| SDK embed snippet | ✓ provide | ✓ add to page |
| Custom UI code (swatches, steps, grids) | ✓ build | ✓ integrate |
| Cart / pricing integration | ✓ | |
| Variant ID → product SKU mapping | ✓ | |
| Design system CSS (if custom UI) | ✓ | |
| AR functionality | ✓ built in | |
| QA and go-live sign-off | → assist | ✓ own |
Section 05
Typical project scope
Rough sizing for the UI dev work only — does not include 3D scene build time, which varies by product complexity.
Simple embed (default panel)
0 extra dev days
- No custom UI required
- Customer pastes one snippet
- Good for quick sign-off rounds
- Can upgrade to custom UI later
Swatch picker
1 day dev
- Most common pattern we deliver
- Colour + finish + handle controls
- Customer provides brand palette
Step flow
2–3 days dev
- Guided wizard, 3–6 steps
- Each step updates the scene live
- Includes summary on final step
Spatial grid
3–5 days dev
- Per-position module selection
- Based on Minerva Modera pattern
- Scales to 6-wide units
Linked selections
+1 day on top of base UI
- Choosing colour auto-sets finish
- Link table agreed with customer
- User can still override linked values
ID alignment meeting
Must happen in week 1
- Named developer from customer side
- Agree all option + variant names
- Confirm rules and edge cases
- Block the CMS build until done
Note: These are UI dev estimates only. 3D scene build time is scoped separately per project — it depends on the number of variants, rule complexity, and how camera presets are set up.