Industrial products are designed in three dimensions, but they are often explained to clients through screenshots, PDFs, technical drawings, and calls.
Each format is useful. The problem begins when a client needs to see something that was not prepared in advance: another angle, one part inside an assembly, or the difference between a standard product and a custom configuration.
Dimsight helps industrial sales teams turn STEP files into browser-based 3D visualizations they can share with clients through a simple link, without sending the original CAD file.
The observations on this page come from conversations with industrial companies, reviews of product-sharing workflows, and work with real CAD files. They are working findings, not universal rules, and we will keep testing them as Dimsight develops.
Three findings currently shape our direction:
- Clients need the right product context for a decision, not every detail held by engineering.
- Public product catalogs and private sales sharing solve different problems.
- 3D views, technical drawings, and product information answer different questions and should remain connected.
Our strongest belief is that the hard part is not putting CAD on the web. It is carrying enough of the product’s meaning into a sales conversation for people to understand what they are discussing and decide what to do next.
What we have learned from industrial sales conversations
Industrial sales rarely follows one fixed path.
Sometimes a client chooses a standard product from a catalog. Sometimes that product is adapted to their environment. Sometimes several parts are combined into a new assembly. The more specific the proposal becomes, the less likely it is that every useful view or document already exists.
This is where back-and-forth begins. A client asks for another angle, a closer view, or a detail about one part. Sales returns to engineering. Engineering prepares another export or joins the next call. The answer arrives, but a new question may start the same loop again.
We do not see this as a failure of either team. Engineering and sales already have tools made for their own work. The gap sits between them, at the point where a technical product has to become clear to someone who did not design it.
The questions that appear in this gap are usually practical:
- What am I looking at?
- How do these parts fit together?
- Is this the configuration we discussed?
- What changed from the standard product?
- Can I inspect the detail that matters to my application?
- Can I share this with another person involved in the decision?
These questions led us to an important distinction. A client does not need everything inside the original CAD file. They need enough product context to understand the proposal, ask a useful question, and make the next decision with confidence.
More information does not automatically create more clarity. The value comes from showing the right information at the right moment, in a form that does not require CAD software or specialist training.
Giving clients the right product context
We are working toward an experience where a client can open a link and begin exploring the product immediately.
The first view should make the product easy to grasp. From there, the client should be able to focus on a relevant part, understand its place in the assembly, and move toward more technical detail when the conversation requires it.
Simple does not mean removing everything technical. It means giving each kind of information a clear role.
The complete assembly provides an overview. Individual parts make its structure easier to understand. Dimensions and drawings can support more precise questions. Names, descriptions, and configuration information can help everyone confirm that they are discussing the same product.
The order matters. Showing every available detail at once can make a product harder to understand. Hiding too much leaves the client dependent on another explanation. The experience should move naturally from the whole product to the detail behind a specific question.
Trust matters just as much as ease of use. What the client sees should remain consistent with what sales is proposing and what engineering approved. When something is unknown or needs confirmation, the product should not hide that uncertainty behind a convincing image or a precise-looking number.
This gives us a clear test for every capability we consider: will it help a client understand the product, and will the people responsible for the proposal feel comfortable relying on it?
Why 3D views and technical drawings belong together
There is no single best way to explain an industrial product.
A 3D view is useful for spatial questions. It can help someone understand the product’s shape, overall proportions, assembly, and relationship between parts. It also lets the person choose the angle that makes sense to them instead of relying only on views selected in advance.
A technical drawing is useful when the discussion needs a stable orientation or a precise reference. It gives both sides one view to point at and can remove ambiguity from a detailed question.
Product information gives those views meaning. A name, description, part number, or configuration can confirm what the client is seeing and why it belongs in the proposal.
We believe these elements should form one product context. A person should be able to begin with the complete product, focus on one part, and move toward the relevant technical detail without feeling that they have opened a series of unrelated files.
This is the experience we are working toward. The goal is not to replace CAD software or technical drawings. It is to make their useful product context easier to carry into a client conversation.
Why private CAD sharing is different from a product catalog
Product catalogs are an important part of industrial sales. They help people discover a standard range, compare available products, and find technical information that is meant to be public.
Private sharing serves another moment.
A sales team may need to show one client a specific product, a custom assembly, or a configuration that should not be published for everyone. The client still needs a clear way to understand it, while the company needs to keep control of the original CAD file and the information surrounding the proposal.
This is where a shared product view becomes useful. It can sit alongside the catalog and the existing sales material, giving the people involved in one decision a common reference for the exact product being discussed.
We believe a share link should grant permission to inspect that product, not become a transfer of its source file. The client should receive the context needed for the conversation. The company should decide what belongs in that context.
What Dimsight is working toward
Engineering, sales, and clients look at the same product from different positions.
Engineering needs the product to remain technically trustworthy. Sales needs to connect it to the client’s application. The client needs enough clarity to judge fit, risk, value, and the next step.
Good product communication has to respect all three:
- The product should remain at the center of the conversation.
- Clients should be able to explore it without specialist software.
- Sales should be able to explain a specific configuration without preparing every possible view in advance.
- Engineering should be able to trust the product context being shared.
- The company should be able to keep the original CAD file private and control what it shares.
- Everyone involved should be able to return to the same reference as the conversation develops.
This would not remove the need for sales expertise, engineering judgment, product catalogs, drawings, or direct conversation. It would give them a common place to meet.
We will continue testing this direction against different products and sales situations. A large assembly creates different questions from a single part. A standard product creates different questions from a custom configuration. A technical buyer needs different information from someone making a commercial decision.
Dimsight should handle those differences without making the client experience feel complicated. The technical work should stay behind the product. What the client sees should remain clear, useful, and tied to the decision in front of them.
Our long-term goal is straightforward: give engineering, sales teams, and clients one clear product reference, while keeping the original work behind it private.