Making complex products legible: a guide for industrial brands
By Nick Markov · April 2026 · 8 min read
A sales engineer I worked with last year made a comment that stayed with me. He said: "The problem isn't that our customers don't understand our product. The problem is that our catalogue doesn't understand them."
His product was a hydrogen gas compressor. The customer (a plant engineer at a municipal utility, an industrial gas supplier, a fuel-cell manufacturer) knew what a compressor does. What they didn't know was how his compressor did it differently. That difference (a patented eccentric-shaft mechanism, a specific internal cooling loop, a particular serviceability pattern) was what he'd spent fifteen years building and was the reason any of them should buy it.
The 180-page PDF catalogue couldn't carry that story. The photographs didn't show it. The slide deck implied it. Only when he had a whiteboard and thirty-five minutes could he make it click.
His problem wasn't that his product was complicated. His problem was that his product was legible only in three dimensions, and everywhere he was selling was two-dimensional.
The problem, said plainly
Industrial products often have this shape. The thing that makes them worth buying is internal. An arrangement of parts, a cycle, a sequencing, a containment pattern. Photography flattens it. Marketing copy narrates it but doesn't show it. Videos show it but force a single pace and a single path through the content.
Three-dimensional interactive does something none of those do: it lets the customer explore the product at their own pace, from the angles they care about, with the specific callouts relevant to their decision. An engineer wants to see the service access points. A regulator wants to see containment failure modes. An investor wants to see throughput scale. A single 3D app can answer all three, because the customer drives the session, not the salesperson.
This is why every one of the sixteen 3D apps we've shipped over the last few years was for a client whose 2D materials were underperforming. Not whose product was failing. Good products explained badly.
When 3D earns its keep
A rough test: if one or more of these is true, 3D is probably the right instrument.
Your product has internal mechanisms that aren't visible from outside. Hydrogen compressors. Sludge removers. Battery recycling systems. Industrial valves. Any product where what it does is more interesting than what it looks like.
Your product has operational sequences. Assembly, installation, disassembly, maintenance, reconfiguration. Any product where how it moves over time is the information the customer needs.
Your product has configuration depth that photos can't convey. Premium footwear with twenty material combinations. Custom furniture with parametric dimensions. Industrial equipment with modular attachments. Any product where the catalogue photo is missing most of the actual inventory.
Your customer has to understand the product to justify the purchase internally. Enterprise sales where the buyer is presenting to a procurement committee. Regulatory sales where the buyer is documenting compliance. Investment-adjacent sales where the buyer is writing a memo for a funding decision.
Your product exists at a scale that can't be shipped to every prospect. Full plants, full installations, full factory lines. The 3D app is the version that fits in a laptop.
When 3D is the wrong answer
3D is not always the answer.
If your product is visually simple, photography is better. A well-shot jar of face cream outperforms a 3D viewer of the same jar, because the product's value is its packaging aesthetic and its texture. Things a human stylist with a good camera does better than any WebGL engine.
If your customer isn't exploring (if they're just confirming) video or animation is better. A 30-second explainer video outperforms a 3D interactive when the customer is already sold and just needs a final nudge.
If your product catalogue is hundreds of similar SKUs, a configurator platform is better. Threekit, 3D Cloud, or Emersya will serve you well. A bespoke custom-built 3D scene per SKU doesn't economize at that scale.
If your sales process has no time for the customer to interact, you need something shorter. A 3D app assumes your customer will spend 3–5 minutes with it. If your sales cycle's attention budget is 30 seconds, invest in better landing-page design instead.
The four patterns that keep coming back
Of the sixteen 3D apps we've built, four patterns account for most of them. If you're considering a 3D project, it helps to know which pattern your problem fits before scoping.
The product-in-context walkthrough
A product presented in its operational environment. A piece of equipment installed in a plant, a vehicle on a site, a machine on an assembly line. Navigation is usually a guided stepper through equipment components, with spec panels surfaced per piece.
Good for: industrial equipment with catalogue depth. Full-plant explainers. Anything where the product only makes sense in context.
Example: Dowon APEX. A full wastewater treatment plant with twenty-plus pieces of selectable equipment, each with operational specs surfaced in a dismissible panel.
The assembly / installation guide
A step-by-step interactive that walks a user through putting the product together, often multilingual, built for field use on tablets. Replaces the PDF manual that nobody reads.
Good for: products that require installation, configuration, or reconfiguration. Products that ship across multiple languages. Products where installation errors are costly.
Example: Moojin earthquake-resistant ceiling systems, EN/KO interactive installer used by field crews on tablets.
The variant configurator
Real-time variant swapping (color, material, size, feature) usually integrated with an order-capture flow. Built for consumer and D2C brands with premium customization depth.
Good for: fashion, footwear, jewelry, furniture, small appliances. Any product with real variant depth where the catalogue can't show all permutations.
Example: Rawfit women's sneakers. Two models, five colors, three materials, integrated with Rawfit's CRM.
The process visualization
Multi-stage process or system shown as a sequence, with annotations surfaced per audience type. Works well when the same system needs to be explained to multiple audiences at different levels of detail.
Good for: industrial processes, medical procedures, financial or logistical workflows. Anything where a system's sequence is what the customer needs to understand.
Example: DY Engineering black-mass battery recycling. Multi-stage process with three audience-specific annotation layers (safety, operational, investment).
What goes wrong
Three failure modes we see often in other agencies' 3D work. Naming them so you can avoid them.
The product is modeled but nothing else is designed. A beautiful 3D hero product with no interaction logic, no navigation affordance, no reason for the user to engage. These projects photograph well and don't convert. The interaction design (what the user does and learns) is the actual work; the 3D asset is the substrate.
The tech stack is overbuilt. Unity WebGL for a product showcase. A custom shader system for a configurator that could have used baked lighting. A 400 MB load weight on a mobile-first product page. The tech should be the cheapest possible thing that delivers the experience. Most 3D work we've seen is over-engineered.
The multilingual treatment is an afterthought. A 3D app built in English with Korean bolted on in week 10 is not multilingual. It's an English app that some Korean users tolerate. Real multilingual (button widths that survive both scripts, typography that respects both traditions, panels that reflow) has to be scoped from day one or it doesn't ship well.
What to do if you're considering one
Three things in order.
Write down the specific problem in one sentence. Not "we want 3D." Something like: "Our sales team spends 40 minutes of every first call explaining how our sludge remover works, and we lose deals when the customer forgets the explanation before the second call." The specificity of the problem determines the specificity of the solution.
Identify the one buyer the app is for. 3D apps that try to serve three audiences at once usually serve none well. Pick the primary audience, build the core experience for them, and then add annotation layers for secondary audiences if scope allows.
Set a launch context. A trade show, a product launch, a funding round, a training rollout. An arbitrary "next quarter" deadline lets scope drift; a real deadline forces clean scope decisions.
Then send us a two-sentence email at hello@cclemang.com. We'll tell you in 15 minutes whether a 3D project is the right move for your problem. Or whether something simpler is.
Nick Markov is the AI Generalist at CCLemang. He builds most of what the studio ships. Design, engineering, 3D, and the AI-assisted production pipeline.