Software for logistics and transportation
Fleet telematics, dispatch, route optimisation and proof of delivery, built for operators running real vehicles on real roads.
Logistics runs on margin measured in single percentage points, which means the software either pays for itself in fuel, utilisation and detention time, or it does not belong in the business.
Our work in this sector concentrates on the operational core: ingesting telematics from mixed hardware without losing pings, planning routes against constraints that actually bind, and giving dispatchers a board that reflects reality rather than yesterday's plan.
The failure modes
we keep meeting.
- 01
Telemetry volume outgrows the database
A thousand vehicles at a ten-second ping rate is roughly nine million events a day. Transactional databases handle this badly, and the live map is usually the first thing to degrade.
- 02
Dead zones and buffered data
Vehicles leave coverage and return with an hour of buffered pings at once. Systems that assume orderly arrival produce corrupted trips and phantom speeding alerts.
- 03
Systems that do not talk
TMS, ERP, fuel cards, maintenance and telematics each hold part of the truth about a trip. Nobody can compute true cost per kilometre because no single system has all of it.
- 04
Drivers will not use bad software
A driver app that needs signal, drains battery or takes eight taps to close a job simply gets ignored, and the data quality collapses at the source.
Products, not
capabilities.
Each of these is a system we can build from scratch and scale to your size. Everything here works without training a model — where AI is involved it is a hosted model reading a document or answering a question, not a black box.
- Fleet & Telematics01
Fleet tracking and dispatch platform
Live vehicle map, trip reconstruction, geofence entry and exit alerts, and a dispatch board that reflects what is actually happening rather than the morning plan. Ingestion built for mixed telematics hardware and vehicles that go through dead zones.
- Mobile Apps02
Driver and rider mobile app
Offline job cards, navigation handoff, proof of delivery with photo and signature, and cash collection recorded at the point it happens. Works with no signal on a cheap Android phone and syncs when it returns.
- Custom Software03
Hub and branch operations console
Vehicle allocation, shift rosters, attendance, handover checklists and cash reconciliation per hub — the system that replaces a WhatsApp group of supervisors.
- Custom Software04
Subscription and security deposit ledger
Weekly or monthly rental billing, deposit collection, deductions, and refunds recorded as a double-entry ledger so the accounts reconcile without a month-end spreadsheet.
- AI Automation05
Freight invoice and e-way bill processing
Inbound invoices, LRs and e-way bills read automatically, matched against trips and rate contracts, with only the exceptions routed to a person. Uses hosted language models for extraction — no model training involved.
- Asset Management06
Maintenance and spares workflow
Preventive schedules on odometer or engine hours, breakdown tickets raised from the driver app, spares consumption, downtime capture and true cost per vehicle.
The work, and where it sits.
- Practice · Fleet & Telematics01
Fleet tracking and telematics platforms
Streaming ingestion, time-series storage, live maps that stay smooth at scale, geofencing and trip reconstruction.
- Practice · Fleet & Telematics02
Route optimisation and dispatch
Multi-stop planning against time windows, capacity and driver hours, with live re-planning and automatic customer ETAs.
- Practice · Mobile Apps03
Offline-first driver apps
Job cards, navigation handoff, proof of delivery with signature and photo, all functioning with no signal and syncing when it returns.
- Practice · Data & Analytics04
Cost and utilisation analytics
One warehouse joining trips, fuel, maintenance and revenue, so cost per kilometre is a number rather than an argument.
Sector specifics.
Can you integrate with the telematics hardware we already have?
Yes. We write protocol adapters per vendor and normalise into one internal event format, so mixed hardware across an ageing fleet is a solved problem rather than a blocker.
Do you replace our TMS?
Rarely, and not by default. Most engagements build the tracking, dispatch and analytics layer around an existing TMS and integrate cleanly with it.
Tell us what you are building.
A short conversation is usually enough to tell whether we are the right firm for the problem. If we are not, we will say so and point you somewhere better.