The visit that changed everything
In early 2025, we visited a customer's factory — a mid-sized OEM in India. We wore visitor lanyards, walked the shop floor, and sat with engineers, sourcing teams, quality managers, and production planners.
We weren't there to sell. We were there to understand. What we learned started with three questions.
Question One: How long from design change to supplier quote?
The answer came immediately: three to six weeks. Every time.
Not because people were slow. Not because the process was broken. It was because answering that question required someone to manually connect information spread across CAD files, PLM systems, ERP records, supplier databases, and spreadsheets.
The information existed. The connections did not.
Question Two: When a new requirement comes in, how do you know if the company has already solved a similar problem before?
The room went quiet. The honest answer was: we don't. Not reliably. Not quickly.
Manufacturers accumulate decades of engineering knowledge — designs, drawings, supplier history, manufacturing experience. Yet finding a similar solution often depends on knowing where to look, and who to ask.
The data exists. The context around that data is much harder to find.
Question Three: What happens when the one person who knows where everything is leaves the company?
That got immediate reactions. Every company has some version of this problem.
The engineer who remembers why a tolerance was changed ten years ago. The sourcing manager who knows which supplier can actually manufacture a part. The planner who understands why a manufacturing note was added to a drawing years earlier.
Critical knowledge exists. But much of it lives in people, not systems.
Why existing systems struggle
CAD stores geometry. PLM manages lifecycle. ERP tracks suppliers, materials, and costs. Each system does its job well.
But none were designed to understand how engineering decisions relate across the enterprise. As products become more complex, those relationships become harder for people to track and impossible for disconnected systems to see.
The hidden problem
What became clear during that visit was that this wasn't fundamentally a workflow problem. It was a relationship problem.
Engineering data, enterprise systems, and product decisions were all connected — but often only inside people's heads. As complexity grows, those connections become harder to find. When key people leave, many of them disappear altogether.
The insight behind ShapeSense
ShapeSense was built around a simple idea: the intelligence already exists — inside drawings, inside CAD models, inside enterprise systems, inside years of engineering decisions. The challenge is connecting it.
Every manufacturer we have spoken to since that visit has shown some version of the same pattern. Different products, different industries, different geographies — the same underlying problem.
The question is no longer whether the intelligence exists. The question is whether you can find it when a decision needs to be made.