Per-trip pricing taxes growth

Software priced per trip charges you the most in exactly the month you did the most work. A 20-car fleet running 1,500 trips a month on the entry plan of the best-known per-trip platform pays about $1,100 a month for dispatch software, and the number goes up every time the fleet gets busier. That is a tax on growth, and the operator is the one paying it.

What per-trip pricing looks like in numbers

Take the public Limo Anywhere pricing as the example, since it is published and it is the system most operators are comparing against. As checked on 29 October 2026 on their pricing page, the three plans start at $99, $249 and $549 a month, and each base steps up with trip volume (the entry plan runs from $99 at 150 trips to $1,210 at 15,000). On top of the base there is a per-trip charge of $0.25 on the entry plan and $0.20 on the others, an overage of $0.40 to $0.50 on every trip above the plan's included cap, and a one-time upfront fee of $299 to $899.

For a 20-car black-car fleet, 1,500 trips a month is ordinary: a little under three runs per car per day. On the entry plan the base at that volume is $225. The per-trip charge is 1,500 × $0.25, or $375. The plan includes 500 trips, so the other 1,000 carry the $0.50 overage, another $500. The monthly bill is about $1,100, or roughly $13,000 a year, before the upfront fee. The middle plan at the same volume is about $1,200 a month.

Now the fleet has a good year. A new corporate account adds 300 trips a month. The software bill rises by about $225 a month for the privilege, $75 in per-trip charges and $150 in overage, and at 2,250 trips the base steps up again. Nothing about the software changed; the operator just did more business.

The case for per-trip, honestly

Per-trip pricing is not a scam. For a two-car operator doing 100 trips a month, the usage charge is $25, and on the cheapest base plan the total is around $124. That is cheap. A small operator pays little because they use little, and the vendor takes the risk that the operator stays small.

If you are that operator, a per-trip plan may be the right choice today, and this post is not asking you to switch. The point is what happens to that bill as you grow, and whether the pricing model makes sense for what the software actually is.

A dispatch system is an ERP

Strip away the industry vocabulary and a dispatch system is an enterprise resource planning system for a transportation business. It holds the orders (bookings), the resources (drivers and vehicles), the suppliers (affiliates), the customers (accounts), and the money (rates, invoices, payments). The run board is a production schedule. The manifest is a work order.

Nobody prices an ERP per invoice processed. Nobody prices a CRM per deal closed. Those categories settled on per-seat pricing decades ago, because the cost of running the software scales with the number of people using it, not with the volume of the business running through it. A dispatcher assigning 50 trips a day uses roughly the same screen, the same database rows and the same support hours as one assigning 80.

Per-trip pricing in ground transportation is a historical accident. It made sense when the vendor was also processing the reservation, taking the call or running a network. For software that the operator's own staff use, it is a usage meter on the operator's success.

What per-seat looks like instead

The alternative is a price per office seat: one seat for each person who logs in to the office system. Owner, dispatcher, bookkeeper. Drivers and affiliate drivers are not seats, because they do not sit in the office and the software should want as many of them on it as possible.

For the same 20-car fleet, that is typically three to five seats. On liverybook pricing, 1,500 trips a month sits in Professional, which covers up to 5,000 trips at $89 a seat, so four seats is $356 a month, with no per-trip fee and no setup fee. Inside the tier the bill is the same in a slow February and a busy December. When the fleet adds that new corporate account and 300 trips, the software bill does not move. When the operator hires a second dispatcher, it goes up by one seat, which is a cost tied to a real decision.

The operator can forecast it. The bookkeeper can budget it. And the question of whether to take on more work is answered by whether the cars and drivers can handle it, not by what it does to the software line.

The objection

The usual defence of per-trip pricing is that it aligns the vendor with the operator: the vendor only does well when the operator does well. That is half true. The vendor does well when the operator processes more trips, which is not the same as the operator doing well. A fleet can run 20 percent more trips at a 10 percent lower average fare and be worse off, while the software bill goes up 20 percent.

A vendor on per-seat pricing does well when the operator keeps paying, which means the software has to keep earning its place every month. That is a better alignment, and it is the one the rest of the business software world already runs on.

Per-trip pricing has a glossary entry at /glossary/per-trip-pricing. The liverybook model is per office seat, and the current prices are at /pricing.