Freight and logistics
The AI Office for freight operators.
94.5% of fleets charge detention. Most collect on fewer than half of those invoices.
The billing right already exists — what is missing is the evidence trail. On a 60-truck fleet that is roughly $190,000 a year written off. Worth checking against your own detention billing before you read further.
If any of this sounds familiar
We would start by looking at McLeod, TMW, or whatever your dispatchers actually live in all day.
- Dispatchers on the phone all day making check calls a system should already answer
- Detention invoiced and then written off because nobody can prove the clock
- Load confirmations chased through email threads and PDF attachments
- "Where is my shipment" calls that a customer could answer themselves
What we have delivered
In this industry, not an adjacent one
- 85%
- reduction in phone-based coordination in dispatch
- 70%
- fewer "where is my shipment" calls
- 3×
- faster load-confirmation cycles
Reconciling load status across four brokers is the same problem as reconciling eligibility files across four carriers — different industry, identical shape. We built the second one first, twenty-one times.
Who would run it
Someone here has done this job
Vasil Hlinka — Lead Advisor
Roughly eight years in family logistics operations before this, and the founder of a 3PL platform of his own. Named a Supply & Demand Chain Executive “Pro to Know” in 2020. The check-call list and the detention argument with a shipper are not abstractions to him.
Where we would start
One workflow. Four to six weeks. Fixed fee.
Detention evidence assembly — build the per-load timeline automatically from the documents and messages you already generate.
Before we start, we agree in writing the number the build has to hit. If it does not hit it, we keep working for four more weeks at no charge — and if it still misses, we refund the fee in full.
$6,000
credited in full against month one of Build or Run, started within 30 days
Or go straight to a retainer from $2,500/month. Month to month, 30 days’ notice.
The build order
Ranked by what a wrong output costs
We start where mistakes are cheap and visible, and earn the right to touch money. If you ask us to begin at the bottom of this ladder — and people often do — we will explain the sequencing rather than agree to it.
A human reads every output before it matters.
Drafted carrier and shipper communications · internal exception digests and loads-at-risk lists · status collection that replaces check calls
Forgiving, because a review queue sits in front of the system of record.
Rate con, BOL and POD extraction into staging · shipper-facing status responses with a hard escalation rule · load confirmation and e-signature cycles
Advisory only. The machine assembles; a person decides.
Carrier vetting pre-screen · detention and accessorial evidence assembly · claims and OS&D packet assembly
Finance-grade. A wrong output pays a carrier money they are not owed.
Invoice audit, settlement and carrier-pay reconciliation
The question you are about to ask
“Our TMS is on-premise and has no usable API.”
Most do not, and it does not matter for a first build. We start on the documents and the mailbox — rate confirmations, BOLs, PODs, check-call emails — which are already in your Microsoft tenant and need nobody else’s permission. System-of-record integration is an engagement-two conversation, once there is a relationship worth the vendor paperwork.
Your data
Your data never leaves your tenant.
We do not hold your data, because we do not build on our infrastructure. We build inside yours.
- Built inside your own Microsoft tenant
- Entra ID role-based access through security groups
- No static or local accounts
- MFA enforced
- SFTP with IP whitelisting for partner feeds
- Sensitive data masked in every non-production environment
Continuity
One client has renewed us twenty-one times since 2021.
A benefits administrator has brought us back for twenty-one sequential engagements since 2021 — eligibility reconciliation, invoice automation three separate times as the requirement changed, pre-certification workflows, a data-quality programme — and we still operate their platform today, with alerting, weekly. Every one of those twenty-one ended with them asking for the next thing. That is the part worth weighing: twenty-one engagements is not one relationship, it is twenty separate decisions to keep us, each made by someone who could have stopped. Nearly five years is the honest answer to the question behind every retainer decision — will you still be here in year three.
Twenty minutes, and you will know.
We ask what your team spends its week on. If there is nothing here worth doing, we will tell you that.