Carrix · in-flight (Shipsy × HCLTech proposal)
Status: Prospect — not yet live. Included here as a worked example of how Shipsy approaches a discovery + proposal for a large complex deal. Treat content as reference, not a customer story.
Engagement summary
| Industry | Container terminal operator (federated, multi-port) |
| Region | Americas — multi-terminal |
| Engagement type | Joint proposal with HCLTech |
| Stage | Discovery sprint + Phase-1 scoping |
Why this is in the hub
The Carrix proposal is the best worked example we have of:
- How to scope a large federated-stack customer. Eight disconnected source systems, five channels, hundreds of use cases — and the discipline of finding the 3 categories that are 75% of volume.
- How to position with a partner. HCLTech is the systems integrator; Shipsy is the agent platform; both fit cleanly into one delivery model.
- How to drop in without replacing anything. The whole proposal pitches Shipsy as an orchestration layer between channels and existing systems — zero rip-and-replace.
The customer in one minute
Carrix is one of the largest container terminal operators in the Americas. Federated stack across terminals (Main Sail, Forecast, Spinnaker, eModal, CiTAS, Traffic Control, PIS for Mexico, Billing). Most inbound volume is email (~80%); phone is ~15-20%. Top 3 categories — appointments, container ops, fees/demurrage — make up ~75% of volume.
The proposed solution
Six agents, one orchestrator, zero new systems.
The partnership model
| Partner | Brings |
|---|---|
| HCLTech | Carrix relationship · integration delivery · program governance · AI Force (enterprise GenAI governance) · VisionX (edge multimodal AI) |
| Shipsy | Port-domain agent fleet · TOS-grade connectors · 6 functional agents · multilingual voice (EN · ES · AR · HI) · live precedents at Adani, MOVIN, Aramex |
Why CS folks should study this proposal
Three transferable patterns:
- The “biggest channel / biggest use case / systems to integrate” framing. Three numbers (80%, 75%, 8 systems) tell the whole story. Steal this structure for any large opportunity.
- The federated → orchestrated narrative. Don’t ask the customer to consolidate their stack. Sit between channels and systems. Land that first, expand later.
- The joint discovery sprint as the next step. Don’t try to scope a multi-year program upfront. Propose a contained sprint that locks Phase-1 scope.
Status
Proposal stage. Phase-1 scope + POC pilot pending joint discovery sprint.
Materials
- “Shipsy x HCL for Carrix – AI Agents for Port Operations – FINAL” deck (Drive)
- Adani Ports deployment (live reference inside the deck): see Adani case study
Changelog
- 26 May 2026: Initial draft from Carrix proposal deck.