Operating cluster 01
The Control Tower is the product. Not the software around it.
A central operations team sits between cargo owners and a vetted provider network. It decomposes the request, sources it, normalizes what comes back, and stays the single authority on who may see what — for every party, on every leg, at every stage.
- specialist roles
- 17specialist roles
- transport & service modes
- 8transport & service modes
- pipeline stages, end to end
- 9pipeline stages, end to end
- integrations, each with a manual fallback
- 10integrations, each with a manual fallback
- of actions immutably audited
- 100%of actions immutably audited
The pipeline
Nine stages, each one an audited state change.
The pipeline is first-class in the schema, the API and the interface — not a diagram drawn after the fact. Every transition writes an append-only record carrying the actor and the old and new values.
- 01
Cargo Request
One intake captures route, cargo, services and documents. A compliance hold at this point stops everything downstream.
- 02
Legs
The request is decomposed into mode-specific transport and service legs — road, rail, sea, air, port, customs, warehouse, insurance.
- 03
RFQs
Each leg is dispatched only to providers whose capability profile qualifies them for that lane, mode and licence. Eligibility scoring is deterministic code.
- 04
Quotes
Providers price a masked brief. A provider sees its own quote and nothing else — no competitor pricing, no customer identity, no margin.
- 05
Route Plans
Quotes are converted to one currency, outliers flagged for revision, and assembled into comparable plans — cheapest, fastest, balanced.
- 06
Booking
The customer approves a plan. That choice is theirs alone: no agent selects a plan, and no plan books itself.
- 07
Shipment
Legs are assigned and advanced against milestones, with event freshness and exceptions surfaced to the operations cockpit.
- 08
Documents
Uploaded, generated, requested and approved under a document matrix that decides which party may see which document.
- 09
Finance
Invoices raised and payments recorded manually under legal review, with recording and releasing held by different people.
Cargo Request → Legs → RFQs → Quotes → Route Plans → Booking → Shipment → Documents → Finance
Modes
Eight modes, legged from a single request.
Multimodal is not a list of services sold separately. One request becomes as many legs as the move needs, and the plan you compare is the assembled whole.
- Road
- Rail
- Sea
- Air
- Port
- Customs
- Warehouse
- Insurance
Execution
From approved plan to confirmed delivery.
Booking assigns legs to the providers that quoted them. From there the shipment advances on milestone events, documents move under the document matrix, and delivery is confirmed against physical proof — never on an agent's word.
01
Describe your shipment
What to move, from where, by when — in plain words. Submit it and the request reaches the Control Tower.
02
We dispatch the RFQs
Your request is split into legs and sent only to providers eligible for each lane, mode and licence.
03
Compare normalized plans
Every quote is converted to one currency, outliers are flagged, and the result is built into route plans you compare side by side.
04
Approve, book & track
Pick a plan, approve the money and compliance, and the corridor runs to delivery — every step audited.
One request. Every mode. One team accountable for the whole of it.
Tell us what needs to move and we will come back with plans you can compare on the number you will actually pay.