Analytics for delivery operators
Your operation already produces the data. We make it readable.
Route exports, weekly scorecards, rosters, telematics and maintenance logs live in five systems that do not talk to each other. We map what you have, model it once, and give you a platform that answers questions before dispatch instead of after.
Answers before dispatch, not after
What does one delivery actually cost?
Four weekly numbers get you an estimate straight away. Add detail when you want to see what is driving it.
Your estimate appears here once the four required numbers are in.
Where the money goes
AUD / monthRoute cost split
What this estimate covers
An estimate from your own figures, not a quote.
The usual state of play
Most delivery businesses are not short of data. They are short of one place to look at it. The scorecard arrives as a PDF on Friday, the roster is a spreadsheet, telematics sits in a vendor portal nobody logs into, and maintenance is a folder of invoices. By the time someone has stitched those together by hand, the week they describe is already over.
- Nobody can say which driver caused which defect without opening four files.
- Cost per parcel is known at the depot level and nowhere below it.
- A metric that slipped on Tuesday is discovered on Friday afternoon.
- Every question that starts with “why” takes a day of spreadsheet work.
How we build it
No two operations store their data the same way, so we do not start from a template. We start from an inventory of what you already have.
Data audit
Half a day with your ops lead: which systems hold what, in which format, how far back, who owns the logins, and what is currently typed in by hand. You get the inventory as a document whether or not you go ahead.
Model and definitions
We agree what each metric actually means before we count anything — what counts as an attempt, when a route is finished, how a rescued parcel is attributed. Most disagreements about data are really disagreements about definitions.
Build
Ingestion for each source, a warehouse you own, and a dashboard built around your questions. Existing systems keep running untouched; we read from them, we do not replace them.
Handover
Training for the people who will use it daily, documentation for whoever maintains it, and a month of support while the habits form. The platform and the data stay yours if you leave.
What the platform answers
Driver scorecard
| Driver | Stops | On time | Defects | 12 weeks |
|---|---|---|---|---|
| Driver 01 | 148 | 99.3% | 1 | |
| Driver 02 | 156 | 98.7% | 2 | |
| Driver 03 | 139 | 98.1% | 3 | |
| Driver 04 | 151 | 95.4% | 9 | |
| Driver 05 | 144 | 97.9% | 3 |
Defects by cause, this week
On-time rate, last 12 weeks
Alert 14:12 — Driver 04 below 97% on-time for the third day
Twelve weeks of trend, not last Friday
Every weekly scorecard parsed into a database the day it lands, so you are reading a trend line instead of a snapshot.
Defects traced to a person and an hour
Each missed delivery, failed scan and contact-compliance miss tied back to the driver, the route and the time of day it happened.
A profile for every driver
Completion rate, parcels per hour, safety events, coaching history and how fast a new hire is ramping — on one card per driver.
Route and wave economics
Cost and minutes per parcel broken down by route, suburb and wave, so you can see which routes are worth redrawing before peak.
Alerts on the day, not on Friday
A metric drifting out of threshold pings the people who can fix it that afternoon, while the week can still be saved.
Benchmarks with real context
Your numbers set against the anonymised depots we run ourselves across six cities, so 99.2% stops being a figure with nothing to compare it to.
What you actually receive
- A hosted BI platform on your own data, with logins for as many of your people as you want.
- A Monday morning pack you can take straight into the depot meeting, as PDF or email.
- Threshold alerts to the phones of the people who can act on them.
- A documented data model, so you are not locked into us to understand your own numbers.
- Optional feed into a BI tool you already pay for, if you would rather not add another login.
Typical build is two to four weeks from the end of the audit, and nothing in your existing systems has to change.
Where this is not the right fit
If you run fewer than about fifteen routes a day, a well-kept spreadsheet will tell you most of what this platform would, and we will say so on the first call rather than sell you something you do not need yet. We also do not take on work where the underlying data is missing entirely — if nothing is being recorded, the first job is recording it, and that is an operations problem before it is an analytics one.
Questions we get asked first
Do we have to move off our current systems?
No. We read from what you already run. We have never asked a client to replace a TMS or a telematics provider to make the analytics work.
Who owns the data and the platform?
You do. The warehouse sits in your cloud account where you want that, the data model is documented, and you can take the whole thing in-house whenever you like.
What does it cost?
The audit is free. The build is quoted as a fixed price once we know what we are working with, and the platform runs on a monthly fee that scales with route count. No lock-in beyond thirty days.
Is our data shared with other clients?
Never in identifiable form. Benchmarks use aggregated, anonymised figures from the depots we operate ourselves, and clients can opt out of contributing to the benchmark pool entirely.
Are you not a competitor?
In some cities, yes. That is exactly why the contract says what we can and cannot do with your data, why benchmarks are anonymised, and why you can take the platform in-house on thirty days’ notice. Read those clauses closely — we would.
Two ways to start
Send your volumes and postcodes
Weekly volumes, the cities and postcodes you need covered, and when you want to start. We come back with how much we can run, out of which depots, and the rate.
delivery@wormholeau.comShow us where your data lives today
The first call is an audit, not a pitch: which systems hold your route exports, scorecards, rosters, telematics and maintenance logs, and what state they are in. From that we scope a BI platform built around your data — not a template you have to bend to fit.
analytics@wormholeau.com