AI, automation and custom software for logistics operators, built around your TMS or WMS
You keep McLeod, ShipStation, your own TMS or WMS and whatever spreadsheets hold the rest. We build the layer around it: the order typed once, the check call your dispatcher no longer makes, the billable touch that reaches the invoice, proof the load moved that survives a claim nine days later, and the cost per mile you can actually see.
What changes in your dispatch office and at month-end
3 things that decide this
- 01Orders and loads stop being re-keyed. An intake agent reads the emailed order, the PDF rate con or the EDI 204, creates the load in your TMS or the order in your WMS, and queues the exceptions rather than guessing at an address or an accessorial.
- 02Your dispatcher stops chasing. Check calls, tracking updates and POD chasing run by agent off the carrier and ELD feeds you already pay for, and anything off-plan is escalated to a person with the load and the history attached.
- 03The invoice matches what actually happened. Billable touches are captured as events at the moment of work, storage days come from a daily snapshot rather than a subtraction, and anything that moved without being billed is flagged the same day instead of at month close.
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 logistics operation leaks time and margin, and what we put in each one
Eight areas our audits keep finding across 3PLs, brokerages and fleets, in the order a load meets them. Each links to the page that owns it.
The order typed once, by nobody
Orders arrive by email, PDF, portal and EDI 204, and the same shipment gets typed into your TMS, your WMS and a spreadsheet. We put an intake agent in front of it: it reads the document, validates the addresses and the accessorials, creates the load or the order, and queues what it can't resolve with the original attached.
Logistics automation →
The check call nobody makes
Your dispatcher spends the afternoon phoning drivers for a location and a status that the ELD already knows. We build carrier communications by agent: automated check calls by text and voice, tracking pulled from the carrier or telematics feed, EDI 214 status updates out, and only the exceptions on a person's screen.
Logistics automation →
The load moved, and you can prove it
A customer disputes a delivery from nine days ago and the evidence is a driver's memory and a photo in a shared drive. We build capture that works with no signal: photo, signature, GPS and time bound to the stop, the event time stored apart from the sync time, and corrections added rather than overwritten.
Logistics automation →
Bill by the touch, not the guess
Receipts, picks, storage days and accessorials happen on your floor and reach the invoice through a spreadsheet somebody reconciles by hand. We build the rating layer: a billable event created at the moment of work against that client's contract, storage from a daily snapshot, and rate cards your client-success team edits without a deploy.
3PL software →
The carrier checked before the load, not after the claim
A load board shows you an MC number and an insurance certificate somebody looked at once, at onboarding. We build vetting as a gate on the tender rather than a flag on the record, so authority and insurance are re-checked when a carrier accepts, and a reassignment to a different truck raises a flag before pickup.
Freight broker software →
Cost per mile, cost per load, cost per asset
Your telematics tells you where every truck is, and nothing tells you what each one cost this month. We join the telematics feed, the fuel card, the maintenance invoices and the lease against one asset record, so cost per mile and cost per load are a query instead of an estimate somebody defends in a meeting.
Fleet management software →
One integration layer, not five vendor quotes
EDI exceptions get handled by email and memory, and every connection between the TMS, the WMS and accounting has been quoted as a project. We build one layer that uses the APIs where they exist, EDI exception queues where the transaction fails, extracts where there's no API, and a reviewed queue where there's neither.
Custom software for industrial operators →
Every client and every site sees its own numbers
Clients want a portal your TMS doesn't ship, and each warehouse or depot runs the same job a slightly different way. We build the client portal off the record you already keep and a multi-site operating layer with standard work and a dashboard per site. WAIQ, the operations and execution platform we built for a multi-site business, is that shape.
Custom software for industrial operators →
From the tender to the invoice, and where the machine takes over
Four stations of a load's life through your operation. Pick your system to see what each step writes back; Manhattan, Blue Yonder, project44, FourKites, Descartes or your own TMS follow the same pattern to the depth your account exposes, and we confirm that during the audit.
Station 01 · The order that gets typed three times
- Today
- An order arrives by email at 4:40pm with the addresses in the body and the accessorials in an attachment. Your CSR types it into the TMS, then into the WMS, then into the spreadsheet billing runs off, and one of the three carries a wrong dock time.
- What we automate
- An intake agent reads the email, the PDF or the EDI 204, validates addresses and appointment windows, creates the load or the order, and queues anything ambiguous with the source document attached and the specific field flagged.
- What stays human
- A new customer, 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 complete.
Writes to McLeodOrder and load created with stops, appointment windows and the customer PO.
Station 02 · Tender to carrier, and the check call
- Today
- Your dispatcher works the board, calls three carriers, sends a rate con, then spends the afternoon phoning drivers for locations that the ELD already reported. Tracking updates go out when someone remembers to send them.
- What we automate
- Carriers are matched from your own lane and rate history, authority and insurance are re-checked at tender, and the rate con goes out and comes back signed. Check calls run by text and voice off the carrier or ELD feed, and EDI 214 status updates go to the customer automatically.
- What stays human
- Tendering a load and accepting a rate stay with your dispatcher. A carrier whose authority or insurance failed the check is held, never auto-tendered.
Writes to McLeodCarrier assignment, rate confirmation and check-call history on the load.
Station 03 · The load moved, proof of it did not
- Today
- The delivery happened. Nine days later a customer disputes it, and your team spends a morning in call recordings and text threads reconstructing a Tuesday. The photo exists somewhere in a shared drive next to a job number.
- 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 afterwards. Exceptions get their own codes: short, refused, damaged, nobody home. A correction posts as a new entry.
- What stays human
- Accepting a claim, waiving a charge and clearing an exception are your calls. We assemble the evidence and put it one click from the load; nobody's claim gets settled by software.
Writes to McLeodPOD, exception code and images attached to the load record.
Station 04 · The touches, the invoice and the margin
- Today
- Receipts, picks, storage days and accessorials get assembled from a report at month end, someone applies the rate card by hand, and the storage count is a subtraction between two dates. A few billable touches never make it onto an invoice at all.
- What we automate
- Every receipt, pick, storage day and accessorial becomes a billable event the moment it happens, rated against that client's contract. Storage runs off a daily snapshot per pallet. The invoice is a query against events, and anything that moved without billing is flagged the same day.
- What stays human
- Your controller releases the invoice and approves any adjustment. A billed event is never overwritten; an adjustment posts alongside it and both stay visible to the client.
Writes to McLeodCharges and accessorials posted to the load for invoicing.
Each station links to the page that owns it. Tendering a load, releasing an invoice and accepting a claim stay with a person at every one.
We don't replace McLeod, ShipStation or whatever you run. We build what they won't.
Every TMS and every WMS is good at the job it was sold for, and the gaps operators describe to us barely change from one company to the next: the order typed three times, the check call that eats an afternoon, the touch that never reaches the invoice, the delivery you can't prove. Replacing the system doesn't close those gaps. It moves them, and it costs you a year of everyone's attention while it does.
So the access model matters more than the badge on the login screen. McLeod, ShipStation, Manhattan, Blue Yonder, project44, FourKites, Descartes and your own TMS or WMS each expose loads, orders, stops, events and charges through APIs, EDI or scheduled extracts 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 an EDI exception queue or a reviewed queue your staff clear with one click instead of re-typing.
- 01Load, order, event and charge write-back into your TMS or WMS, with the source document attached.
- 02Your TMS or WMS stays the system of record; where it disagrees with us, it wins.
- 03EDI 204, 210 and 214 handled as transactions with an exception queue, not as email attachments and memory.
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 exception and a billable event 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 loads and how each order arrived, your check-call volume and who made them, the touches that never reached an invoice, and what your TMS or WMS 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.
The same eight areas, in your business's words
3PLs and fulfilment operators
A warehouse or six on your own WMS, ShipStation, a client's NetSuite or whatever you run. Yours is the touch that never reached the invoice, the storage-day count you can't defend, the EDI 945 that made a shipment look unfulfilled on the client's side, and the portal every client now expects.
3PL software →
Freight brokers
Load boards, a TMS built over years, and margin that lives on a spread you defend one lane at a time. Yours is the carrier who cleared onboarding six months ago, the load that got re-brokered to a truck you never vetted, and the rate con and BOL you need tied to one record.
Freight broker software →
Fleets and carriers
Telematics on every truck, an ELD mandate satisfied, and no answer to which asset to replace next. Yours is the fuel card that won't join to the maintenance invoice, the fault code with no history behind it, and cost per mile that's an estimate somebody defends in a meeting.
Fleet management software →
Manufacturers who ship their own freight
If the load starts on your own dock and the argument is really about the job behind it, the manufacturing page covers the floor-to-invoice half of the same operation.
Software for manufacturers →
Before you book
01Do we have to leave McLeod, ShipStation or whatever we run?+
No, and we'd usually tell you not to. Your TMS or WMS holds your customers, your rates and years of load history, and your team knows it. We build the layer around it: the intake that creates loads in it, the check calls that write events to it, the rating and the portal it doesn't ship. We only suggest replacing a system when it genuinely can't do the job, and we'll show you the specific thing it can't do.
02Have you integrated with our TMS before?+
Not with yours, and we won't claim we have. What we've shipped repeatedly is the integration problem itself: deciding which system owns each fact, working to the depth an account actually exposes, and building an exception queue where the transaction or the API stops. During the audit we check what your McLeod, ShipStation or in-house system exposes and design to that, rather than to a brochure.
03Can driver capture work in a loading bay with no signal?+
Yes, and it has to hold the whole stop rather than a read-only copy of it. Your driver completes the delivery, takes the photo and captures the signature with no connection, and the record queues until there's a link. We store the time the work happened separately from the time it synced, so a delivery made underground doesn't read as a late entry to payroll or to a customer.
04Will an agent phone our carriers and drivers?+
For check calls, tracking and POD chasing, yes, by text and by voice, and it identifies itself. It asks for a location and a status, records what it's told, and escalates anything off-plan to your dispatcher with the load history attached. Tendering a load, agreeing a rate and settling a claim stay with a person, every time.
05How big does an operation need to be for this to pay?+
You need a TMS or WMS you've outgrown in places, more than one site or shift, and a month-end you can feel. Below that, a three-truck carrier or a single small warehouse is usually better served by an off-the-shelf package, and we'll say so on the call rather than sell you a build you don't need yet.
06What does the free Load-to-Invoice Audit actually involve?+
An engineer reads last month's loads and how each order arrived, your check-call volume and who made those calls, the billable touches that never reached an invoice, and what your TMS or WMS 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 logistics operators
- Industrial: manufacturing, logistics and food →The hub: what we build across plants, warehouses and fleets.
- Logistics automation →Intake, carrier communications, tracking and billing.
- 3PL software →Bill by the touch, and the client portal your WMS won't ship.
- Freight broker software →Carrier vetting at tender, and a load record nobody can edit.
- Fleet management software →Telematics into cost per mile, per load and per asset.
- Custom software for industrial operators →Integration, portals and the reporting your TMS won't build.
- Best billing software for 3PLs →Real vendors ranked, with us last as the custom option.
- How to automate 3PL billing by the touch →Billable events, daily snapshots and the rate card.
- How to stop re-keying orders into your TMS and ERP →What an intake agent reads, and what it must refuse to guess.
- The load moved. Proof of it did not. →Why the evidence trail is the product in a claim.
