Telematics tells you position, not profitability
Cost per kilometre by vehicle, route and driver requires joining telematics, fuel, maintenance and payroll. Most operations join none of them.
Supply chain & industry
You know where the vehicles are. You do not know what they are costing you.
Telematics answered the location question a decade ago. The economics question is still open.
Book a 20-minute call Free. No demo, no slides.
1 in 3+
of inspected trucks carried maintenance defects that would have put them out of service before the crash.
What is happening
You know where every vehicle is. You do not know what it is costing you.
Maintenance is scheduled by calendar
While the data to schedule by condition is already streaming off the vehicle and being discarded.
Compliance documents expire without warning
Permits, fitness certificates, insurance and driver licences, tracked in a spreadsheet somebody remembers to open.
Proof of delivery disputes are settled by phone
Because the evidence is a photograph on a driver's personal device.
Intelligence, plumbed in
A driver's defect note is a maintenance signal, not a comment box.
We build the reader, the telematics connector, and a scored test against breakdowns you have already paid for.
How we make AI survive real data-
Connectors -
A semantic layer -
Evals you can check
What changes
Judge us on this, not on what we built.
Per km True cost by vehicle, route and driver
Fuel, maintenance, driver cost and utilisation combined, so route pricing is based on actual economics.
Condition Maintenance driven by how the vehicle is running
Using the telematics data you already pay to collect.
No lapses Every document tracked with notice
Permits, fitness, insurance and licences, surfaced weeks before expiry rather than at a checkpoint.
Research
We wrote a full page on each of these, with the sources.
Each one carries its own figures and the citations behind them. Start with whichever sounds most like your week.
However hard, whatever it is
Cost per vehicle is one example. Bring the harder question.
This page is about what a vehicle actually costs. If yours is compliance, driver retention or a depot nobody can compare, same method.
-
01 We sit with you
Days where the work happens, not a workshop in a meeting room. We watch the job get done and write down the shortcuts nobody wrote down.
-
02 We read everything
Your data, your rules, your vendors and their documentation, and the published research on your sector. We report what is actually in there.
-
03 We break it to first principles
Not which tool fixes this. What is actually causing it, taken apart until we reach the piece that cannot be divided further.
-
04 Then we build
Weeks, not quarters. By this point we are not guessing what to build, and guessing is the thing that makes projects long.
Where we sit
Your tracker stays. We build the cost per vehicle nobody can see.
4
What you get
- Per km True cost by vehicle, route and driver
- Condition Maintenance driven by how the vehicle is running
- No lapses Every document tracked with notice
3
Built new for you — none of this exists in your stack today
- A box we build when the telematics unit will not share data
- A driver app that logs a defect in twenty seconds
- A cost sheet per vehicle, not per fleet
2
The vehicle-cost layer Reads your telematics and fuel cards. Sends no instruction to a driver.
Connectors, one agreed meaning per field, and a model reading what no
field holds. Accuracy measured on your own records.
1
- telematics platforms
- GPS tracking
- fuel card systems
- maintenance management
- TMS platforms
What you already run — unchanged, and still yours
If the vehicle knows it, we can read it. If the unit will not share, we build our own. A telematics API, a fuel card file, the CAN bus, a tracker that exports nothing. And a box we make when needed.
-
No API -
No documentation -
A terminal from 1994 -
It arrives as paper -
The vendor said no -
It reports nothing
Not a list of limits. Name yours on the call.
And once we can reach it, a model can read it. Most of the value here is in the sources nobody ever structured — the note, the letter, the screen.
Who this is for
The people who feel this first
-
Fleet Manager -
Operations Director -
Transport Manager -
Finance Head -
Compliance Officer
Straight answers
The questions you would ask on the call
-
We already have GPS tracking. What does this add?
Location is the easy data and it is already solved. What is missing is the join — fuel against distance, maintenance against utilisation, driver cost against route revenue. That join is where the margin question gets answered.
-
Can you work with our existing telematics provider?
Yes. We read from whatever is installed rather than asking you to change hardware. Replacing telematics is expensive and rarely the actual problem.
-
Do you build hardware if we need something not on the market?
Yes, though we would push back first. Most fleet questions are answerable from existing data. Where they genuinely are not, we build the sensor as well as the software.
-
Can AI read driver defect notes?
Yes, and they are the earliest maintenance signal you have. We test the reader against breakdowns you have already paid for.
Also in supply chain & industry
Supply chain & industry
Supply chain & logistics
Stockouts and excess inventory persist in organisations that bought every system designed to prevent them.
Supply chain & industryManufacturing
Production runs on the floor. Reporting runs on a spreadsheet assembled the following morning.
Supply chain & industryConstruction & infrastructure
And the average project still overruns by twenty-eight percent.
Next step
Start with your own numbers.
-
We talk
20 minutes. Free.
You tell us what is not working. We ask how the work really gets done.
-
We look at your data
A few weeks.
We read your systems, including the notes and letters no field holds. You get what is really in there, what it costs, and the accuracy we can hit.
-
We build
A few months.
Only if step 2 says it is worth it. Fixed price, agreed before we start.