Somewhere in a manufacturing company right now
An engineer is looking at an old engineering design of a housing nut.
Within seconds, she knows what questions need to be answered. How is this part manufactured? Who can supply it? Why was that tolerance changed three years ago?
Finding those answers may take days of searching across teams and systems that were never designed to work together. Because no one person in the company — and no single enterprise system — can tell her everything she needs to know.
This scene plays out every day in manufacturing organisations around the world. It is not a failure of the engineer. It is a limitation of the systems around her. Systems that can store engineering information, but struggle to connect it. There is a difference. And it costs manufacturers weeks, millions, and irreplaceable knowledge every year.
Reading versus understanding
Consider a circle on an engineering drawing. A model might correctly identify that circle. That does not mean it understands the drawing. Understanding means knowing the circle is a 12mm through-hole. That it carries an H7 tolerance. That the H7 tolerance requires a particular manufacturing process. That only certain suppliers can achieve it consistently. That the surface finish affects inspection requirements. And that someone changed that tolerance three years ago for a reason now buried in a revision note, an email, or a retired engineer's memory.
At that point, you are no longer dealing with image recognition. You are dealing with engineering intent. The meaning of a single geometric feature cascades through manufacturing process selection, supplier qualification, cost estimation, inspection planning, and design reuse decisions. Every link in that chain represents a decision. Every decision delayed by disconnected context carries a cost.
Why Shape is the Foundation
If the problem is connecting engineering information to enterprise context, where do you start?
We believe the answer starts with shape.
Shape — the three-dimensional geometry of a part — is the most fundamental and reliable signal in engineering data. Understanding that geometry correctly is one of the two core technical problems ShapeSense is built to solve.
File formats change. Drawing standards evolve. Documentation practices vary. PLM systems get replaced. People move on.
The geometry remains.
A part's shape does not change when the CAD system is upgraded. It does not vary between a drawing created in Stuttgart and one created in Pune. It is one of the few signals that remains consistent across systems, formats, and conventions.
Shape captures the outcome of countless engineering decisions. The form, features, tolerances, and spatial relationships of a part reflect choices about function, manufacturability, assembly, and performance.
Understanding that geometry correctly provides a stable foundation. Everything else can then be connected to it.
But shape by itself is not enough.
Context — The Other Half
Geometry tells us what a part is. It does not tell us everything we need to know about it.
Engineering knowledge also lives in drawings, specifications, revisions, manufacturing notes, supplier history, quality findings, and the decisions engineers made along the way — often without documenting why.
This is where the second half of our name comes from.
Humans understand the world through multiple senses. Sight alone does not create understanding. We combine what we see with sound, touch, memory, and experience to make sense of reality.
We believe engineering understanding works in much the same way.
Shape provides the geometric truth. Context provides the meaning. Neither is sufficient on its own.
Shape without context describes a part. Context without shape describes decisions disconnected from the thing they relate to.
When geometry and context are brought together, understanding emerges.
That is why we call the company ShapeSense.
What this means for manufacturing teams
The engineer looking at the housing nut is not struggling because she lacks capability.
She is struggling because the systems around her were never designed to connect geometry with enterprise context. When those connections exist, decisions happen faster. Reuse opportunities become visible. Supplier knowledge becomes searchable. Engineering history becomes accessible.
Reading a drawing and understanding it are two very different things.
That gap is what ShapeSense is built to close.