Project44 splits into two companies, spins off LSP44

On July 14, 2026, in Chicago, project44 announced it is splitting itself into two separate companies. Confirmed by FreightWaves and detailed in the company's own press release, the project44 TMS split creates one business that keeps the project44 name and serves shippers, and a new one called LSP44 that serves 3PLs, freight forwarders and brokers. project44 announced that it is separating into two focused businesses, with project44 serving enterprise shippers as a Decision Intelligence Platform. The split creates project44, the Decision Intelligence Platform for enterprise shippers, and LSP44, the profitable, AI-Native Agent and API infrastructure company that 3PLs, freight forwarders, and brokers embed directly into their own tech stack.

Founder and CEO Jett McCandless runs both entities. "Shippers and LSPs don't buy the same thing, so we stopped pretending one business could serve both," he said in the release sent to FreightWaves. If you're running project44 for TMS, visibility or yard management today, or you've got it on a shortlist against Descartes, FourKites or Blue Yonder, here's what this actually means for your contract, your roadmap, and your next renewal conversation.

Why project44 did this now

The short answer: two very different buyers were competing for the same engineering roadmap. Founded in 2014, project44 entered the market with a focus on replacing manual processes with a real-time API covering rate quotes, dispatch, visibility, and documentation, and early adoption by leading logistics service providers helped build the carrier network, integrations, and data infrastructure that comprise its current platform. That LSP-facing origin never went away, it just got buried under a decade of shipper-facing product built on top of it.

McCandless said that nine of the ten largest logistics service providers in the world now run on what will become LSP44 infrastructure. Meanwhile project44 spent the pandemic years and beyond building the visibility, TMS and yard management tools that enterprise shippers actually buy. Two buyer types, two sales motions, two sets of feature requests fighting for the same sprint capacity. Splitting the company is the fix.

Worth noting: this is the opposite motion from most of what this blog has tracked recently. WiseTech's acquisition of e2open and Descartes' purchase of 3GTMS were consolidation plays, two companies becoming one. project44 is doing a de-merger, one company becoming two. Same underlying pressure (vendors trying to serve fragmented buyer needs efficiently), opposite structural answer.

What changes for European shippers this quarter

If you're a shipper, your day-to-day product doesn't move. project44 will provide shippers with a decision intelligence platform that complements their transportation management system and last mile delivery software with enhanced visibility. Nobody is migrating your account to LSP44. Nobody is asking you to re-onboard. The TMS, visibility, yard management and last-mile modules you're using stay under the project44 name, run by the same leadership.

That said, a corporate split still triggers a few things worth checking with your CSM before your next renewal, especially if you're mid-negotiation on a multi-year deal right now:

• Confirm which legal entity your Master Service Agreement and Data Processing Agreement now sit under, since a "two businesses" announcement can mean new subsidiary structures even when the customer-facing product doesn't change
• Ask whether any carrier connections your account relies on were originally built for LSP use cases and could see reduced maintenance priority once LSP44 has its own separate roadmap
• Get written confirmation that your SLA terms, uptime commitments and support tier didn't shift as part of the reorganization
• If you're mid-evaluation against another vendor, ask project44 directly how the split affects European multimodal and customs-adjacent feature parity over the next 12-18 months

Key dates so far

What doesn't change yet, and what to watch

The two businesses aren't fully independent. They all run on the shared spine of the largest AI-native agent network, carrier API infrastructure and logistics data graph on Earth. In practice, that means the carrier connectivity you rely on today is unlikely to degrade overnight, both businesses need it to work.

The thing to actually watch is what happens in twelve months once the two roadmaps diverge in earnest. Two separate P&Ls, two separate go-to-market teams and two sets of investor expectations historically precede one of three outcomes: a re-merger once the split proves inefficient, a sale of one half to a strategic buyer, or a feature parity gap for whichever side isn't the growth priority that quarter. There's no evidence yet that any of these will happen to project44 or LSP44. But if you're locking in a multi-year contract, it's a reasonable question to put to your account team directly, not a hypothetical to ignore.

Where this leaves the shipper-side vendor map

For shippers, nothing about the competitive landscape shifted overnight. Key players in the visibility platform market remain Project44, FourKites and Shippeo, with Project44 and FourKites US-based and active globally, while Shippeo is based in France. Project44 alone has more than 1,400 telematics integrations and 80 TMS/ERP integrations, a scale advantage that doesn't change because of an internal restructuring.

If your actual pain point is carrier connectivity and day-to-day multi-carrier execution rather than pure predictive visibility, it's worth putting a smaller European specialist like Cargoson on the same shortlist as the bigger suites. Not every European shipper needs a full decision-intelligence platform. Some just need reliable execution across forty carriers without the overhead.

What procurement teams should take from this

Vendor structure changes, mergers, splits, spin-offs, are now a recurring feature of the TMS and visibility market, not a one-off event to react to and forget. Build a vendor-stability clause into every contract renewal from here forward, and treat this project44 split as a live test case: how fast does your account team answer "what does this mean for my contract" when you actually ask them this week?