Priced on what moves
Transactions and a monthly minimum. Not seats, not licenses, not dev hours.
We do not publish rates, because the number depends on which services you take and how much freight you run. What we can tell you before any conversation is the shape of the bill — and the shape is where most of the difference actually is.
Get a number for your volumeWhat is not on the invoice
The rate is rarely what people are unhappy about. It is everything charged alongside it.
Configuration
Adding a carrier for a new customer is setup. Doing it again for the next customer is also setup. It is not a change order either time.
Seats
Put your whole team in. Put your customers in under your own brand. Your cost tracks freight rather than headcount, so growing the team is free and growing the volume is the thing you pay for.
Development hours
We are not a dev shop with a product attached. Anything that goes into the product is product work, not an hourly line, so it has no reason to take longer than it should. Work that only ever serves one customer is the exception — named below.
Implementation, normally
Standing you up is not a revenue line. Where a project genuinely is new work rather than setup, we say so before you sign — see below.
How the bill is put together
A per-transaction rate and a monthly minimum sized to your account. The minimum exists so a small account is worth supporting properly, and it comes down as volume goes up. That structure is not unusual in this category, and we are not going to pretend it is.
How you consume it does not change the price. Work in our interface, call the same services over the API or MCP, or run the whole thing under your own brand — the bill is the same either way. What you are paying for is the freight going through the system, not the window you looked at it through.
And because every service stands on its own, taking one of them is genuinely cheaper than taking five. A narrow use stays narrow on the invoice. See what each piece replaces.
When something does carry a fee
Three cases, and we would rather name them here than surprise you with them later. The line running through all of them is the same one we use internally: if it goes into the product everyone gets, it is our investment. If it only ever serves you, it is yours.
A carrier or connection only you need
If your volume justifies an integration, it is setup and it is included — we want the freight. If you need a connection nobody else on the platform is asking for, that is different work, and it is charged as recovery of the time rather than as a margin opportunity. It also moves you ahead of our own roadmap, which is usually the actual reason people ask.
Something only you will ever use
Sometimes a request is genuinely specific to how one company runs — and putting it in the global product would be carrying weight nobody else asked for. We will tell you when we think that is what we are looking at. We will still build it, and it is charged at cost recovery on the time, not as a margin opportunity. If we are wrong and it turns out everyone wants it, it goes into the product and stops being your line item.
A capability that does not exist yet
A new mode, or a feature family we have not built. That is a project, it gets priced as one, and there are usually options — a prepaid credit against future transactions often works out better for both sides than a fee. We will show you the arithmetic rather than pick for you.
When we are the wrong answer
At low volume, a monthly minimum divided across not many loads is a high cost per load. We will tell you that number before you sign rather than after, and if it does not work, it does not work. We would rather lose the deal than have you discover it in month three — that is a customer who leaves and tells people why.
If the volume is coming but is not here yet, say so. That is a conversation we have regularly and it usually has an answer.
Why the model is shaped this way
What we think about vendor incentives, and why the bill looks like this.
If AI Made Your Vendor 5x Faster, Why Aren't You Paying Less?
If AI made your software vendor 5x faster… why are you paying the same? Incentive drives behavior. Where your TMS vendor's profit comes from tells you whose side the roadmap is on.
Jul 2026AI & OperationsThe Software Makes the Mess. Someone Else Sells the Cleanup.
Whole companies exist just to check whether your TMS quoted the right number. That is what [freight audit](/audit/) is for. The software makes the mess; someone else sells the cleanup — and everybody just accepted that. Here's what changed my mind.
Jul 2026Rating & QuotingCarrier API, Consolidator, or Your Own Rating Logic?
Three ways to price LTL, three different failure modes. The question isn't which one wins — it's what happens when the one you chose is wrong.
Feb 2026Get a number for your volume
Tell us roughly what you run and which services you are interested in, and we will come back with real numbers rather than a range.