The case for one workspace across five roles

The default architecture at a mid-market freight forwarder in 2025 looks something like this: a legacy TMS for ops, a separate rate-management tool, a separate customer portal (or three, one per key account), an accounting system that talks to none of them, and a set of carrier portals the ops team logs into manually. Five vendors, five contracts, five upgrade cycles, five sets of exports and imports that never quite reconcile.

Where the cost actually lives

The subscription cost of that stack is not the expensive part. The expensive part is the labour cost of the human beings whose job is to keep those five systems in sync. In a typical 30-person forwarder we've assessed, the equivalent of 3-4 FTEs are effectively doing integration work — copying data, reconciling reports, chasing down discrepancies — that would not exist if the underlying systems shared a data model.

There's a second, less visible cost: the customer experience is only as consistent as the weakest handoff between systems. A shipper who gets a clean quote from the rate tool, a confusing booking flow from the TMS, a portal that shows a slightly different ETA, and an invoice that doesn't quite match the quote — that shipper will not be a long-term customer. The multi-vendor stack quietly caps retention.

Why one workspace is finally credible

The historical objection to a single workspace was that best-of-breed always beat integrated. That was true when the integrated products were three years behind on features. In 2026, for the freight-forwarder use case specifically, the integrated products are at feature parity with the best-of-breed on the modules that matter — rating, ops, docs, accounting, portal — and materially ahead on the seams between them.

The unlock is not any single feature. It's that the same shipment, quote, invoice and B/L are the same object across every screen every person on the desk looks at. Reconciliation stops being a job. New hires ramp faster. Customers get a consistent experience. The 3-4 FTEs previously doing integration work can be redeployed onto lanes and accounts, which is where a forwarder's margin actually gets made.

The migration decision

The right time to consolidate is when a specific renewal comes up on one of the five vendors and the honest answer to 'is this vendor genuinely differentiated for us?' is no. That's usually the accounting integration or the portal. Start there, prove the single-workspace pattern on that scope, expand at the next renewal. That's how the forwarders on UbuntuLogistics that started with just the customer portal ended up running the whole desk on one system 18 months later.