VZU Projects
TrackSphere. The dispatch layer that crosses borders.
14 corridors. 200+ daily shipments. 99.9% on-time. The brief was: build a cross-border dispatch and tracking platform that doesn't depend on any single carrier or country-specific logistics vendor.
A case study · Issue 03 · Mumbai, IN
Chapter 01 · The brief
A logistics operator, broken by 14 different vendors.
TrackSphere started with a logistics operator in Mumbai. They handled cross-border shipments — India to UAE, India to Singapore, India to the UK, India to the US. 14 corridors. 200+ daily shipments. Each corridor had a different carrier. Each carrier had a different API. Each API had a different auth scheme. Each auth scheme had a different failure mode.
The dispatcher's daily reality: 14 browser tabs open, copying tracking numbers from one tab to another, manually updating an Excel sheet, then manually emailing the customer. 30 minutes per shipment. 200 shipments a day. 100 hours of manual work, every day. Error rate: 12%.
The brief from the operator was clear: build a single dispatch and tracking layer that abstracts away the 14 carrier APIs. Single source of truth. Real-time tracking. Webhook-driven updates. Carrier-agnostic routing. A 6-month migration. A 4-month payback on the manual work savings.
Chapter 02 · The architecture
14 carrier adapters. One dispatch model. Real-time.
We built 14 carrier adapters — one per corridor. Each adapter is a small piece of code that translates the carrier's API into a single dispatch model. The dispatch model is what the operator's dispatcher sees. The carrier APIs are invisible. The dispatcher doesn't care if a shipment is moving through DHL or FedEx or India Post. The dispatcher cares that the shipment is moving.
Above the adapters, the Hunter agent runs the orchestration. The Hunter agent is the VZU OS agent for data and automation. It handles rate shopping, ETA prediction, exception handling, customer notifications. The Hunter agent is the brain of the platform.
The dispatcher console is a Next.js app built by the Atlas agent in 4 weeks. The console shows the real-time state of every shipment across all 14 corridors. The console has carrier-agnostic actions — 'reroute', 'cancel', 'refund' — that work the same regardless of which carrier is moving the shipment. The console is the operator's window. The console is the work.
“14 corridors. One dispatch model. Real-time. The dispatcher doesn't care which carrier is moving the shipment. The dispatcher cares that the shipment is moving.”
— TrackSphere brief, VZU OS run #178
Chapter 03 · The result
200+ shipments a day. 99.9% on-time. 0 minutes of manual work.
TrackSphere shipped on time. 6-month migration. 200+ daily shipments. 99.9% on-time. Zero minutes of manual work per shipment. The error rate dropped from 12% to 0.3%. The dispatcher team went from 8 people to 3. The operator's cost-per-shipment dropped 40%.
The VZU team stayed on for the Hunter agent. The brief expanded: now the Hunter agent handles the customer notifications, the rate shopping, the exception escalation, the SLA tracking. Each is a 2-week brief. Each ships through the same Hunter agent, with the same audit trail, on the same NetWit runtime.
This is what the VZU model is built for: a fixed-fee brief, a senior engineer, an agent, a runtime. The work ships. The audit trail is on from day one. The operator owns the goal. The work is the work.
0.3%
error rate · 14 corridors · 1 console
Chapter 04 · The trace
What the Hunter agent did.
The audit trail from one of Hunter's runs. Every step is logged. The trace is the record.
- 01hunter › read brief
read brief
- 02hunter › thinking: bayut scraper. 50k+ listings. daily. 2 weeks.
thinking: bayut scraper. 50k+ listings. daily. 2 weeks. : bayut scraper. 50k+ listings. daily. 2 weeks.
- 03hunter › mcp.robots.check
allowed paths: /properties/*, /agents/* : /properties/*, /agents/*
- 04hunter › mcp.proxy.rotate
1,200 residential proxies
- 05hunter › mcp.scrape.run
playwright + stealth, 5s/listing
- 06hunter › mcp.data.deliver
csv to s3 : //vzu-data/bayut/yyyy-mm-dd.csv
- 07hunter › mcp.schedule.cron
daily 03 : 00 utc
- 08hunter › ship. 2 weeks. 50k listings/day. 99.4% success rate. done
ship. 2 weeks. 50k listings/day. 99.4% success rate.
Audit trail · 6 entries
- T+00:00:00 brief.received 01
- T+00:00:30 robots.checked 02
- T+00:01:00 scraper.built 03
- T+00:08:00 data.delivered 04
- T+00:14:00 schedule.setup 05
- T+02:00:00 brief.completed 06
Get in touch
Brief the Hunter agent.
If your operator is locked in to legacy logistics tooling, the runtime can ship a fix. Fixed-fee, fixed-scope, 6-month briefs. Senior engineers. The audit trail is on from the first character.