Fleet software that turns telematics into a decision
Samsara, Geotab or whatever you run already tells you where every truck is; it won't tell you what each one cost you this month. We build the layer around your telematics and your TMS: cost per mile and per load, maintenance that follows the truck, and the driver paperwork that reaches the invoice.
What fleet operators are actually buying
3 things that decide this
- 01Your telematics feed is raw material, not an answer. Samsara and Geotab report GPS pings, fuel level and engine fault codes; turning that into cost per mile and cost per asset is a separate build that most fleets never get around to commissioning.
- 02ELD compliance is a floor rather than a strategy. The mandate forces hours-of-service logging and says nothing about idle burn, detention you never billed, or which truck is quietly losing money on every lane it runs.
- 03The question your fleet manager can't answer is which asset to replace next, because the fuel card, the maintenance invoice, the lease and the mileage log each spell the vehicle differently and nobody ever built the join. That join is the whole product.
On the record
What you can check before you call
5.0
Clutch rating from client reviews
4
countries our client work runs in: US, UK, Switzerland, Australia
2017
building since. TechNova 2026: Best AI-Native Software House of the Year
2 mo
of support and maintenance free after launch. NDA before the first call
Eight places a fleet leaks time and margin, and what we put in each one
Eight areas our audits keep finding across fleets and carriers, in the order an asset meets them. Each links to the page that owns it.
The order typed once, by nobody
Loads and jobs arrive by email, portal and EDI 204, and somebody types each one into your TMS and then into the dispatch board. An intake agent reads the document, validates the stops and the windows, creates the load, and queues what it can't resolve with the original attached.
Logistics automation →
Telematics that survives a provider switch
Samsara and Geotab each model an asset their own way, and a fleet that runs both across depots ends up maintaining two reports. We build to one internal asset schema that both feeds map onto, so changing provider at one depot is a mapping change rather than a rebuild.
Custom software for industrial operators →
Cost per mile, joined across four systems
Your fuel card, your maintenance invoices, the lease payment and the mileage log rarely share a key, so cost per mile stays an estimate somebody defends in a meeting. We build the asset record that ties all four together, which turns total cost of ownership into a query you can run on a Tuesday.
Custom software for industrial operators →
A fault code read against that truck's history
A code fires, a light turns red, and nothing tells you whether it's the third fault on a truck due for retirement or the first on one with years left. We compare each fault against that asset's own repair history rather than a fleet average, and turn the flag into a work order with an owner.
Logistics automation →
ELD data that also earns its keep
Hours-of-service logs exist because the mandate says so, and the same timestamps show which routes run long, which shippers hold your drivers, and where detention went unbilled. One capture, two uses, and the second one pays for the build.
Logistics automation →
Driver capture that survives a dead zone
A delivery gets disputed nine days later and the evidence is a driver's memory. We build capture that holds the whole stop offline: photo, signature, GPS and the time the work happened, bound to the stop and locked, with the event time stored apart from the sync time so a basement start doesn't read as fraud.
Logistics automation →
One integration layer, not five vendor quotes
Every connection between the telematics, the maintenance shop's system, the fuel card portal and accounting has been quoted as its own project. We build one layer that uses the APIs where they exist, scheduled extracts where they don't, and a reviewed queue where there's neither.
Custom software for industrial operators →
Every depot sees its own numbers
Each depot runs the same job a slightly different way and the roll-up hides it. We build a multi-site operating layer with standard work and a dashboard per depot. WAIQ, the operations and execution platform we built for a multi-site business, is that shape.
Custom software for industrial operators →
From the fault code to the replacement decision, and where the machine takes over
Four stations of an asset's month in your fleet. Pick your system to see what each step writes back; Samsara, Geotab, your maintenance shop's system or your own TMS follow the same pattern to the depth your account exposes, and we confirm that during the audit.
Station 01 · The load that gets typed twice
- Today
- A shipper order lands by email and your dispatcher types it into the TMS, then onto the whiteboard the yard actually works from. One of the two carries a wrong appointment window, and the driver finds out at the gate.
- What we automate
- An intake agent reads the email, the PDF or the EDI 204, validates the stops and appointment windows, creates the load, and queues anything ambiguous with the source document and the failing field flagged.
- What stays human
- A new shipper, a rate that doesn't match the contract or an address that won't validate goes to a person. Nothing gets invented to make a record look complete.
Writes to McLeodLoad created with stops, windows and the shipper reference.
Station 02 · In transit, and the proof
- Today
- Your driver delivers in an underground bay with no signal, and the record uploads three hours later on the motorway. Payroll sees hours that never existed, and an honest driver looks like a thief until somebody checks.
- What we automate
- Driver capture holds the whole stop offline: photo, signature, GPS and the time the work happened, bound to that stop and locked. Event time and sync time are stored as separate fields, and check calls run off the ELD feed rather than your dispatcher's phone.
- What stays human
- Clearing an exception, accepting a claim and adjusting a timesheet stay with your people. We put the evidence one click from the load and leave the judgement where it belongs.
Writes to McLeodPOD, exception code and images attached to the load.
Station 03 · The fault code with no history behind it
- Today
- A code fires and somebody gets a notification. Whether this is the third fault on a truck due for retirement or the first on one with years left is a question your dashboard can't answer, because the repair history lives in the shop's system.
- What we automate
- Each fault is matched to that asset's own repair history, its idle and downtime pattern, and the cost of every prior fix. A deviation from that asset's own baseline raises a work order with an owner and a due date rather than a badge on a screen.
- What stays human
- Grounding a truck and approving a repair are your maintenance manager's calls. We flag the deviation and cost it; nobody's vehicle gets taken off the road by software.
Writes to McLeodAsset status and out-of-service flag reflected against dispatch.
Station 04 · Cost per mile, and the truck to replace next
- Today
- Cost per asset is an estimate somebody defends in a meeting, because the fuel card, the maintenance invoice, the lease and the mileage log each spell the vehicle differently. Detention goes unbilled because nobody joins the ELD timestamps to the load.
- What we automate
- Fuel, maintenance, lease and mileage are keyed to one canonical asset record, so cost per mile, cost per load and total cost of ownership are queries. Trucks are ranked by cost against their remaining life, and unbilled detention is flagged off the ELD timestamps.
- What stays human
- Retiring an asset, buying the replacement and billing a shipper for detention are decisions your people make. We produce the number and show the working.
Writes to McLeodDetention and accessorial charges posted against the load.
Each station links to the page that owns it. Grounding a truck, approving a repair and retiring an asset stay with a person at every one.
We don't replace Samsara, Geotab or whatever you run. We build what they won't.
Your telematics provider is good at the job it was sold for, which is sensing: location, fuel level, engine faults, hours of service. Pulling that feed is the easy part of a fleet build, and most projects stop right there because the last stretch is where the actual work lives. Nobody at your telematics vendor is going to join their data to your fuel card and your maintenance invoices for you.
So the access model matters more than the badge on the login screen. Samsara, Geotab, your maintenance shop's system, your fuel card portal and your own TMS each expose assets, trips, faults and costs through APIs or exports to different depths, and some gate that access behind a plan or a partner programme. We've not shipped an integration into your specific instance, and we won't pretend otherwise: we confirm exactly what your account exposes during the audit and design to it, and where the API stops we build a scheduled extract or a reviewed queue your staff clear with one click instead of re-typing.
- 01Asset, trip, fault and cost data keyed to one canonical asset record, not to whichever id each vendor happens to use.
- 02Your telematics provider stays the sensor layer; where it disagrees with us about a reading, it wins.
- 03Idle time and downtime kept apart. They cost differently and they get fixed differently.
No software runs a line, releases a lot or dispatches a truck without a person. We write that down first.
A plant, a warehouse and a fleet sit under rules that don't bend for software: a line stops on a person's call, a food lot is released or held by QA, a load is tendered by a dispatcher, and the record (the traveler, the batch record, the POD) has to survive an auditor or a recall. So every build starts with a one-page map of what the software records, what it only proposes, and where a person signs.
What follows is simple to state, and we put it in writing. Alerts are designed to be trusted, which means few, specific and escalated; an alarm that cries every hour trains people to ignore it. Records are timestamped, immutable and gap-honest. Invoices, releases and tenders are approved by the person who owns them. And every automated touch is logged so an auditor, a customer or a regulator can read what happened, and when.
- 01Releases, tenders and invoices approved by a person; the software assembles, routes and chases.
- 02Alerts few and trusted; records immutable and gap-honest.
- 03A POD, an inspection and a repair record are immutable once captured; a correction is a new entry alongside the original.
“They will treat your vision like their own and build it that way.”
Ron Klabunde · Founder, SmartREI ↗
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
Some of the systems we have shipped
- AuditFree. We read last month's fuel, maintenance and lease spend against your mileage, your unbilled detention, how a fault code reaches a work order today, and what your telematics account will and won't expose.
- DiagnoseWe map the path into your ERP, TMS or WMS and accounting, and walk the floor or sit with dispatch for an afternoon.
- BuildFixed price from the diagnostic. Tested on your real orders, jobs and loads, under NDA.
- RunMonitoring, a named engineer, and the first two months of maintenance free.
Best fit: an operator with an ERP, TMS or WMS you've outgrown in places, more than one site or shift, and a month-end you can feel. Not a fit yet: a ten-person shop that needs its first system, and we'll say so. You can stop after any stage; the audit note is yours either way.
Before you book
01Can you integrate with Samsara or Geotab?+
To the depth your account exposes, and we confirm that during the audit rather than promising it now. Both publish APIs covering location, fuel, engine faults and hours-of-service data. The build maps each provider's asset model onto one internal schema, so a fleet running both across depots isn't maintaining two separate sets of reports.
02How do you turn telematics data into cost per mile?+
By keying the telematics feed, your fuel card, your maintenance invoices and your lease payments to one canonical asset record. Most fleets never build that join, which is exactly why cost per asset stays a spreadsheet estimate. Once it exists, cost per mile and cost per load are queries you can run in front of the person asking.
03Does this replace our ELD or telematics provider?+
No. Samsara, Geotab or whatever you run stays the sensor layer, capturing location and engine data, and we'd tell you to keep it. We build the reporting and decision layer on top: cost, maintenance history, unbilled detention and predictive flags, connected by API.
04Can predictive maintenance actually predict a breakdown?+
It can flag a deviation from an asset's own pattern early enough for you to schedule the repair instead of getting stranded. That's narrower than naming a failure date, and it's the honest version. We've shipped this pattern on remote-site telemetry, comparing each site against its own baseline rather than a fleet-wide average, and the alert design is what makes people keep reading them.
05We also run our own repair shop. Does that change the build?+
It changes where the maintenance data comes from and usually makes the join easier, since you own the system holding it. If the repair-shop side is the bigger problem, the automotive page covers workshop and service work directly. On the fleet side we still key everything to the same asset record.
06What does the free Load-to-Invoice Audit actually involve?+
An engineer reads last month's fuel, maintenance and lease spend against your mileage, the detention you never billed, how a fault code reaches a work order today, and what your telematics account exposes. You get a written note with the gaps and the shortest path through them. It's yours whether or not you hire us, and there's an NDA before the first conversation.
A senior engineer, not a sales rep
Abdul Basit founded Hashlogics in 2017, and the team runs from Lahore with a US LLC. Clients rate the work 5.0 on Clutch, and in 2026 it was named Best AI-Native Software House of the Year at TechNova. Shift Link, the workforce-compliance and scheduling platform for regulated staffing, and WAIQ, the operations and execution platform for a multi-site business, are two of the systems we built and can show you.
Your audit call is with an engineer who has read travelers, load boards and month-end reconciliations like yours. Bring last month's numbers if you have them, and we'll work from those.
- NDA before the first conversation.
- No pitch on the call. A note you could hand to another firm.
- Fixed price after the diagnostic, so the number isn't a guess.
More for fleets
- Industrial: manufacturing, logistics and food →The hub: what we build across plants, warehouses and fleets.
- Logistics operators →The segment above this one: 3PLs, brokers and fleets.
- Logistics automation →Intake, carrier communications, tracking and billing.
- Freight broker software →For the loads you broker rather than haul yourself.
- Custom software for industrial operators →Integration, dashboards and the reporting your telematics won't build.
- Automotive →Repair-shop and workshop software, if you run your own bays.
- The load moved. Proof of it did not. →Why the evidence trail is the product in a claim.
- Custom software development →How we scope and build the reporting layer above your telematics.
