Catalogue search, procurement, quality
Manufacturing
Catalogue search, procurement, quality documentation and the order management underneath industrial operations.
Findability is the whole job. An engineer searching a catalogue of hundreds of thousands of parts either locates the right one in seconds or calls someone, and every downstream process inherits that decision. We design the search, the procurement path and the interfaces around them, we make quality documents traceable instead of emailed, and we build the order management that industrial and automotive operations run on. Our depth is the software and data layer: catalogues, procurement, systems of record and the analytics above them.
Clients in this sector
What we have built here
Manufacturing & distributionUX is the cornerstone of successful everything
Design principles and UX research applied to how engineers search, locate, and procure from a vast catalogue of electro-magnetic parts.
Digitizing quality documentation across the supply chain
Certificate and quality-document exchange between manufacturers, distributors, and their customers, replacing email attachments with a traceable system.
Multifamily procurement, rebuilt around a system of record
Procurement and fulfilment workflows rebuilt for a multifamily supplier, replacing manual coordination with a system of record.
The intersection of strategy and solutioning: an automotive logistics OMS
Order management for automotive logistics, designed alongside the operators who run it daily.
The lines that do this work
Product development
Full product delivery: multi-tenant architecture, operator consoles and the data layer under them. Shipped as Databricks Apps when the product belongs next to the lakehouse.
Data engineering
Pipelines that hold, tables people trust, and a bill that stops surprising you.
Forward-deployed teams
Product, design and engineering people who sit inside your business, find the real problem, and ship it.
FAQ
Manufacturing: questions we get asked
How much of this is manufacturing-specific?
Less than you would expect. The NMBT work at /case-studies/nmbt was UX research into how engineers search an enormous electro-magnetic parts catalogue, and findability under that kind of volume behaves the same way in distribution, retail and lending. The domain shapes the vocabulary and the compliance surface; the engineering underneath transfers.
We need traceability for audits. Where does that come from?
From treating lineage as a product feature rather than a logging setting. SmartCert at /case-studies/smart-cert replaced emailed certificate attachments with a traceable exchange between manufacturers, distributors and their customers. On Databricks, Unity Catalog gives you the substrate and someone still has to ship the workflow people will use.
Do you do plant-floor or industrial systems?
No. Our depth is the software and data layer above it: catalogues, procurement, systems of record, analytics and the applications people use every day. Industrial control and telemetry is a separate discipline.
Talk to someone who has built this.
A technical conversation with a senior engineer who has shipped in this sector, about what you are trying to build.
