Built to run a fleet before it was sold
Five subscriptions.
One operation.
None of them agree.
One system for the whole operation. Dispatch, safety, maintenance, hiring, settlements and the driver app if you run your own trucks. Carrier settlements and margin per load if you broker it out. And one search across DAT, Truckstop, 123Loadboard and Trucker Path either way — because the load, the driver, the truck and the dollar are the same record.
No card · free permanently up to three trucks · then $19 per truck
Dispatch board
Illustration · sample data
Booked
$8,985
Invoiced
$8,985
Driver pay
$2,246
0
modules, one subscription
0+
automated tests on every change
$0
per truck a month
0
trucks free, permanently
One load, start to finish
Watch a single load move through the whole system.
Three systems compute revenue three ways and somebody reconciles them every month. A load delivers and sits uninvoiced for three weeks. A truck goes out on a medical card that expired last Tuesday. Every one of those is a gap between two systems. So here is one load crossing all of them, in a system that has no gaps to fall through.
Sample data throughout.
01 · Booked
The rate confirmation becomes the load.
Drop the rate con in and the load exists: shipper, lane, rate, stops, dates. Nobody retypes it into a second system, so there is no second version of it to go wrong.
Booked
FF-4012802 · Dispatched
The board refuses the dispatch that would cost you.
Assign a truck and the system checks what a dispatcher cannot hold in their head: registration, inspection, the driver's medical card, the hours already burned this cycle.
Dispatched
FF-4012803 · In transit
The driver app carries the load, not the margin.
The driver sees the stops, the directions and the paperwork they owe. They never see the rate or the margin, because a phone left in a truck stop is not a place for either.
In transit
FF-4012804 · Delivered
The POD lands in the load, not in a camera roll.
The driver photographs the paperwork and it attaches to the load itself. The load is not billable until it is there, so nothing quietly delivers and then sits uninvoiced for three weeks.
Delivered
FF-4012805 · Billed & settled
One engine computes revenue, pay and margin.
The invoice, the driver settlement and the P&L are three views of the same arithmetic. They cannot drift apart between screens, because there is only one calculation.
Billed & settled
FF-40128Booked
FF-40128One record created. Everything after this reads it.
The fix is structural
Stop integrating.
Start with one record.
Dispatch, safety, maintenance and money are not separate products here, so there is nothing between them to integrate, break, or pay a second vendor to reconcile.
Sample data
Four readers, four different questions, no integration between them — because there is nothing to integrate. They are reading the same row.
Dispatch
A board that blocks a duplicate load number and warns before a truck goes out on lapsed registration.
Load board search
DAT, Truckstop, 123Loadboard and Trucker Path in one query. Duplicates merged, ranked by which of your trucks can cover them.
Dispatch planner
Every driver against every day, with the hours clock one click away.
Safety & DQ files
Offboard a driver once and they leave the DQ file, the testing pool and every headcount at the same moment.
Maintenance
PM by date and odometer. A missing reading is reported, never guessed.
Billing & settlements
One engine computes revenue, cost, driver pay and margin, so the load, the statement and the P&L agree.
Recruiting
A pipeline that becomes the DQ file instead of being retyped into it.
Driver app
Android and iOS, every driver, included. Rates and margins never reach the device.
One search, every board
Stop keeping four load boards open.
DAT, Truckstop, 123Loadboard and Trucker Path answer one query. The same load posted to three boards is merged into one row, and what is left is ranked against the trucks you actually have sitting empty — not against everything moving in America.
- Duplicates merged across boards, so you are not quoting the same load twice
- Ranked by which of your trucks can cover it, with the deadhead already counted
- Save a search and get told when something matching shows up
- Book it and it becomes a load — no retyping into a second system
Each board is reached with your own account and credentials.
Detroit, MI → Dallas, TX
62mph
Speed
0/ 1,180
Miles
19h 02m
ETA
What you actually look at
This is the board your dispatcher lives in.
Where every truck is, what is late and why, and what has delivered but has not been invoiced yet.
Illustration with sample data.
Active Loads
5 of 41Detroit, MI → Dallas, TX
4h 12m
1186 mi
Chicago, IL → Atlanta, GA
—
716 mi
Newark, NJ → Columbus, OH
1h 48m
462 mi
Laredo, TX → Memphis, TN
6h 30m
912 mi
Reno, NV → Denver, CO
On time
1010 mi
287
$2.84
99.2%
8.4%
Network · US-48
Why trust the numbers
Anyone can demo a pretty dispatch board.
The difference between software that demos well and software you can run a company on is whether the money is right. Every consequential calculation here lives in an isolated, tested module, so revenue, driver pay and margin come from one place and cannot drift apart between screens.
Two questions for your current vendor
- How many automated tests cover your settlement calculation?
- What happens to my data when your document store is briefly unreachable?
Built in production first
This ran a working fleet before it was ever sold. The dispatch flow matches how the job is actually done, not how a software company imagines it.
Checkable against a published price
Pricing
Free until your fourth truck.
The free tier is the real product, not a stripped-down preview. Run your actual loads through it and decide from there.
Put three trucks on it this week.
Not a trial, not a sandbox. Your real loads, your real drivers, free and permanently at that size. If it does not hold up, you have lost nothing.
Create your accountNo card · no contract · no implementation fee