Sector
Fleet, freight and cross-border trade.
Three engagements where the cargo moved reliably and the information about it did not. Dispatch ran through WhatsApp groups, consignees had no dependable ETA, and the billing caught up a fortnight later.
In this sector
- engagements, under NDA
- 3
- measured results
- 7
A result from each
What these engagements had in common.
A fleet is a system that already works. What tends not to work is everything written down about it: which vehicle went where, what it cost, what the consignee was told, and which of forty-odd cost heads that trip belongs to. A carrier running fifty vehicles was dispatching them from WhatsApp groups and spreadsheets, and reconciling the money by hand afterwards.
Cross-border adds a second problem, which is that the paperwork is the permission. Manifests, customs declarations and certificates of origin assembled by hand take days per consignment and carry a clerical error rate that is expensive in a way that ordinary mistakes are not.
Dispatch and consignee visibility off WhatsApp groups and into one record
Trip cost reconciliation across dozens of heads, without a fortnight of catching up
Customs and origin documentation assembled from the data, not retyped from it
Routing that is measured against fuel rather than assumed
Client privacy and intellectual property
Every architecture and figure below is anonymised under a binding mutual NDA. Company names are withheld to protect our clients’ trade secrets, supplier networks and competitive margins — not to obscure the work. Architecture walkthroughs, system schemas and audited figures are available to a qualified executive enquiry under mutual NDA.
Measured in the engagementEstimated or projected
UAE / India
Cross-border multimodal freight carrier & fleet operator, 50+ vehicles
- Invoice turnaround
- 14 days to 5 days
- Administrative effort
- 34% less — 0.7 FTE reallocated
- Billing errors
- 8% to 2.7%
- Fuel consumption
- ≈15% lower on optimised routing
The problem and what was built
The problem
Fifty vehicles were dispatched through WhatsApp groups and spreadsheets. Consignees had no live visibility and no dependable ETA. Reconciling 40+ logistics vendors ran fourteen days behind with an 8% billing error rate.
What was built
- A logistics operating platform with live GPS telemetry and algorithmic route optimisation
- A consignee tracking portal with milestone messaging over WhatsApp and SMS
- Driver scoring, digital trip-sheet verification and automated trip payroll
- A six-stage financial pipeline across SAP Business One (read-only APIs with RPA writeback), Zoho CRM and exception routing
India
International trade compliance & EXIM documentation agency
- Document turnaround
- 5–7 days to under 24 hours
- Compliance discrepancies
- ≈15% to under 2%
The problem and what was built
The problem
Shipping manifests, customs declarations and certificates of origin were assembled by hand, five to seven days per consignment, with roughly a 15% clerical error rate — and every error risked demurrage or a customs rejection at the far end.
What was built
- A documentation engine producing validated shipping packets and origin certificates from templates
- Multimodal freight routing across carrier schedules and customs brokerage networks
- A statutory compliance engine cross-checking cargo data against destination port rules before dispatch
India
High-volume tour operator & dynamic travel platform
- Campaign rollout
- Weeks to days
- Acquisition cost
- Reduced by instant personalised quoting
The problem and what was built
The problem
Every campaign took two to three weeks of assembly by hand — itineraries, route logistics, pricing tiers, visual collateral. Slow launches pushed acquisition cost up.
What was built
- A generative content sprint framework for multi-destination collateral
- A personalisation engine generating day-by-day programmes, transit routes and pricing tiers per customer profile
Other sectors.
Manufacturing, engineering and export.
Four engagements with manufacturers and industrial distributors. What each of them had in common was not the product — it was that the paperwork around the product had outgrown the people doing it.
FMCG, agri-commodity and multi-branch retail.
Four engagements where the business was distributed — across SKUs, across branches, across channels — and the reporting was not. By the time the numbers arrived they described a month that had already gone.
Request an architectural teardown
Schemas, API writeback routes and production telemetry are shared with verified executives under mutual NDA. Tell us which of these systems is closest to your problem and we will walk you through how it was built.
Confidential. Your enquiry is not shared with anyone.