Product
Four surfaces, in the order the work runs. Nothing here needs a training day — the whole point is that it works the way the spreadsheet already did.
A spreadsheet that happens to be a database.
Thirteen columns, the ones a broker reads left to right: what the load is, who it is for, who is hauling it, where it goes, the three dates it moves through, and what it made. Type to edit. Enter saves and moves down. Tab moves across. ⌘V pastes a block straight out of Excel.
Everything about one load, on one form.
Click a load number. The load, the route, the money, the container and the paper are all on one screen, editable where they sit. The three stops each sit on a row with the date they happened — which is what other systems are really describing when they say Shipper and Consignee 1 and 2.
Bill the work, including the charges that get forgotten.
Completed loads queue up ready to invoice, with their accessorials already attached. Loads for the same customer merge into one invoice. Send it, then watch the balance rather than re-keying it into an accounting package.
What they owe you, and what you owe the trucker.
Receivables ages the balance and ranks the calls worth making today by size and lateness. Payables groups what is outstanding by trucker and keeps the settlements you have already sent, so paying someone twice takes effort.
If a dispatcher has to be taught how to put a load in, the load will end up in a spreadsheet instead.
Nothing here is a new gesture to learn. The board answers to the keys a dispatcher already has in their fingers, which is the only reason it gets used instead of the sheet.
Bring the loads you are already running and see the margin on all of them.