Case Study: A 3D Security Camera Configurator for QVIS

Most of what gets published about 3D configurators is either vendor statistics or product demos. This is neither. It's a 3D configurator case study from our own client work: a security camera configurator we built for QVIS, a security camera manufacturer whose products are sold through dealers and resellers.

The problem

QVIS doesn't sell most of its cameras directly. Dealers and integrators do, and dealers sell branded versions: a camera carrying the integrator's logo, the customer's colors, the right housing for the site. That's a good business model and a hard ordering process, because the thing being ordered doesn't exist yet in the form the dealer wants it.

Before the configurator, that gap was bridged with spec sheets and email. A spec sheet can list every option a camera supports, but it cannot show the finished result, so the dealer was left to do the imagining. Resellers wanted cameras in their own brand colors with custom logos, and ordering from a flat document was a leap of faith.

The email route had its own cost. Spec-ing a branded camera over email means mockups, revision rounds, and waiting, and when a color or a logo placement got interpreted differently on each end, the result was a wrong order. Wrong orders cost everyone time: the dealer, the manufacturer, and the customer waiting on hardware.

What we built

We built a 3D configurator where a dealer uploads their logo, picks body colors and patterns, and sees exactly how their branded camera will look before placing an order. The camera renders in real time in the browser, so the dealer is looking at the actual model with the actual options, not an artist's impression or a color swatch next to a product photo.

The flow is deliberately short: they see it, approve it, order. What used to be a chain of back-and-forth emails about color choices becomes a self-service task the dealer completes on their own.

There's a second job the same tool does for the manufacturer. Because the configuration a dealer builds is the order they place, the configurator doubles as a quoting front end. There's no translation step between "what the dealer designed" and "what production receives," which is where ordering mistakes used to creep in.

Dealers also use this kind of tool live, spec-ing cameras with customers in the room rather than promising to send something over afterward. You can try the QVIS configurator yourself in the live demos on our homepage.

How it was built

The build followed the same process we use for every custom configurator project, and it's worth walking through because the steps matter more than the technology names. Most of our builds go from first conversation to live in four to six weeks, and the structure below is what makes that possible without the client disappearing into a black box.

Scope first. A project like this starts with a scope call: which options the tool needs to expose, which workflows it supports, and what happens after a dealer approves a design. That conversation produces a scope document and a fixed quote before any work starts.

3D assets from product data. The camera models are the foundation. When a client has CAD files or existing 3D models, we convert and optimize them for the browser; when there are only photos and drawings, we model the product from scratch. Either way, the client approves the models before development starts, because everything downstream renders from them.

Build with weekly check-ins. The configurator itself is built in Three.js, with the option logic wired in: the logo upload, the color and pattern choices, the live preview. The client sees progress every week on a live link rather than in a slide deck at the end.

Review rounds, then handover. The client's team tests the tool on their own devices and against real conversations, we adjust, and at launch the client receives the code repository, the 3D assets, and documentation. Ownership is part of the handover, not an upsell: there are no license fees and no required subscription, and the tool can be hosted anywhere and maintained by any developer.

One decision deserves its own paragraph: the tool is browser-based, and for a dealer network that's not a detail, it's the point. Dealers are independent businesses running whatever hardware they run. A browser tool works on desktop, tablet, and phone with no app download and no special hardware. Distributing it to the entire network means sharing a link, and updating it means updating one deployment instead of asking dozens of companies to install something.

What changed

We'll be upfront about the same thing we're upfront about in our article on configurator sales data: we don't publish conversion percentages or revenue numbers from client projects. What we can describe is what changed qualitatively, and for QVIS the change is easy to state.

Dealers see the configured camera instead of interpreting a spec sheet. The design gets approved visually, by looking at it, rather than through a thread of emails describing it. The back-and-forth about color choices disappears, and so do the wrong orders that used to come out of that back-and-forth.

The sales conversation changes shape too. When a dealer can spec a camera system with the customer in the room, the meeting itself improves: fewer follow-up calls to clarify what was discussed, and agreement on the spec before anyone leaves.

It's also worth naming what this project is not. The QVIS configurator isn't a webshop widget bolted onto a product page. It's a configurator working as a sales tool: a piece of the ordering and quoting process for a dealer network, built around how those dealers actually buy and sell.

Where this pattern fits

The QVIS configurator is one instance of a pattern that fits any dealer-driven product line. When a manufacturer sells through resellers, the manufacturer's sales tool becomes the dealer's sales tool, and a configurator that lets the dealer build, see, and approve the exact product closes the gap that spec sheets leave open.

If your product is sold through a network and your ordering process still runs on flat documents and email threads, the shape of this project probably looks familiar. Our 3D sales tools page covers where configurators fit in a sales process, and the development page walks through scoping, timelines, and what a build like this costs.