How a project is built
We first agree one product in the browser: you see the quality of the future site before the rest is built.
- 1
Brief and materials
What you sell, who buys it, where it will be shown. We list what exists — CAD files, photos, samples, print files — and what is missing.
- 2
Art direction
References, light, palette and a storyboard of the key shots. Each chapter of the scene has a job: show a property of the product.
- 3
One product to agree on
We build one product and show it in the browser: wide shot, profile, close-up, rotation and phone. You approve the level, then we continue.
- 4
Scene and site
Scroll chapters, rotation, variants, zoom, mobile compositions and a full no-3D mode with renders of the same model.
- 5
Integration
Catalogue and variant data, links to the shop, enquiry delivery to email, messenger or CRM.
- 6
Checks and handover
We check loading, controls and accessibility on different devices and hand over source files and documentation as agreed in the project terms.
What you receive
- The site or an embeddable 3D viewer
- An agreed set of models and materials, optimised for the web
- The variants and interactions agreed for the project
- Adaptation to phones, tablets and computers
- Agreed integrations and a short guide to adding products
- Source files and documentation as agreed in the project terms
How the scope is agreed
- Number of models and variants
- Depth of interaction: viewer, story, configurator, tour
- Pages and languages
- How the content is updated
- Integrations: shop, catalogue, CRM, booking
- Support after launch
Have a product that should be seen from every side?
Tell us what you sell and where it should be shown. We reply with a proposed scope.
Discuss a project