Territory · Substrate signal
Your words: "we used to be a barring company, but then we acquired a lot of industrial motion business... 50/50 types." The acquisitions came in with their own systems, sourcing networks, distribution. The cross-product orchestration layer — when one customer buys both — is the day-2 question. We stitch microservices around your specific shape; we don't pretend it's standard.
Where Caddie sits
Acquired entities each came in with their own systems. The customer doesn't want to track two POs, two delivery promises, two settlements. Caddie stitches the cross-product flow without forcing system unification.
What we read
"We used to be a barring company, but then we acquired a lot of industrial motion business over a period of time. So we are heavily into industrial motion to almost like 50/50 types."
Srini Sarangapani · Director Supply Chain (India + ASEAN)
Naveen on the call: "They take these problem areas which are not standard solutions, right? And say, we have the concept defined, we have the basic fundamentals already there. Now, how do we apply these to other problem areas?" The same optimization core powers warehouse-labor at NX, service-engineer scheduling at Siemens Healthcare, BPO resource optimization at DHL.
Stitch-microservices-for-unique-problems pattern
Mahindra: three different flows on one platform — inbound milk-runs from suppliers, spare-parts distribution, and FG outbound with automatic load planning. Same engine; three different operational shapes. Cross-flow orchestration in production.
Mahindra · three-flow deployment · in production
What Enmovil delivers here
When a single customer PO carries both bearings and industrial motion line items, Caddie reads both, normalizes, and presents one unified planning view — even if the underlying ERPs are separate.
One delivery promise, one settlement, one audit trail per customer — even if the inventory ships from two different DCs running on two different systems.
Bring us the specific shape. We map our existing modules (read · plan · execute · audit) to your problem. Three-month free POC, then MSA. We don't pretend the solution is off-the-shelf.
Proof anchor
3 flows
In production at Mahindra · inbound + spare-parts + FG outbound on one platform
90 days
Free POC pattern · stitched microservices for the specific problem
1 customer
Wedge: one shared bearings + IM customer or distribution lane
For the conversation
We would touch
We would not
Stitched POC: one customer or one distribution lane that today moves through two separate workflows · we bring our existing modules, you bring your shape · three-month free POC, then MSA.