Defaults beat features
The default workflow has to be right. Configurability is for the 5% case — not a way to dodge having an opinion.
ABOUT US
Built by truckers. For carriers.
CarriersTMS started where most TMSes don’t — on the dock, in the dispatcher’s chair, in the bookkeeper’s spreadsheet. We didn’t hire enterprise consultants to design it. We hired carriers.
OUR ORIGIN
A small fleet, four spreadsheets, and one bad week.
Our founding team ran a 12-truck regional carrier in the Pacific Northwest. We had a TMS — the kind that costs five figures up front and looks like it was designed in 1998. We also had four spreadsheets, two whiteboards, and a Slack channel just for "where is truck #209?" questions.
One Friday in 2022, we sent four invoices late, missed a check-call on a high-value load, and lost a customer. The TMS hadn’t saved us — it had just made us pay for the privilege of doing all the work ourselves.
The next Monday we started building CarriersTMS. The rule was simple: if it doesn’t save a dispatcher time or get an invoice out faster, it doesn’t ship.
WHAT WE BELIEVE
Five non-negotiables for any TMS we ship.
Drivers don’t install apps
SMS pipeline. Web links. The driver’s phone is a tool, not a portal.
Same-day invoicing
The hour the load delivers is the hour the invoice goes out. Anything else is the carrier loaning money to the customer.
Plain pricing
One number per truck. No add-ons, no per-user, no integration upcharge.
Your data is yours
Export everything in one click, anytime. No lock-in is the only acceptable position.
THE TEAM
Operators, builders, and one bookkeeper.
Operations Lead
15 years asset-based carrier ops. Knows what makes a dispatcher quit on a Tuesday.
Engineering Lead
Built distributed systems at two logistics platforms. Believes the API matters.
Finance & Bookkeeping
QuickBooks Pro since the late 90s. The reason our QB integration is bulletproof.