By Jett McCandless, Founder and CEO of LSP44 and project44
I’ve had some version of this conversation over and over since July: What’s the difference between project44 and LSP44?
So let me save everyone a few emails.
On July 14, 2026, we split project44 into two businesses because we were serving two buyers who wanted very different things from us. project44 is built for shippers. LSP44 is built for logistics service providers.
I run both, which is probably why some of the confusion has stuck around. They share the carrier network we spent 11 years and roughly $1 billion building, and there’s plenty of technology under the hood that connects them. But a shipper running a global transportation network and an LSP trying to serve 200 shipper customers do not have the same job.
We finally built around that reality.
These are the five questions I keep getting about project44 and LSP44, and the straight answers I’ve been giving.
What is LSP44?
LSP44 is the business we built for 3PLs, 4PLs, freight brokers, and forwarders.
The cleanest way to understand it is this: if you move freight for somebody else, LSP44 is built for you.
Your job is different from a shipper’s. You’re serving multiple customers, working across different systems, and trying to make all of it look seamless from the outside. LSP44 gives you the AI agents, APIs, and carrier connectivity to do that inside your own TMS and customer experience, under your own brand.
We call it Agentic Infrastructure for LSPs because the agents are only part of the story. Connect Once means we connect the systems a workflow needs, then keep building on the same foundation instead of starting over every time.
That foundation has 5 layers:
- Network
- Observability
- Intelligence
- Integrations
- AI Agents
What is project44?
project44 is our business for shippers. If your company owns the freight and you’re responsible for getting it where it needs to go, this is your side of the house.
More than 1,000 brands use Movement to manage transportation, track freight across modes, run yards, and handle the last mile. Since we spun off LSP44 in July, there’s no ambiguity inside the company about who we’re building project44 for: the shipper.
That’s a meaningful change from where we started. project44 was founded in Chicago in 2014, and some of our earliest customers were LSPs. Over time, the shipper business became a very different animal. Our Intelligent TMS launched in August 2025, and shipper revenue grew 57% year over year in fiscal Q2 2027, faster than any other project44 product line.
The outside validation followed. IDC named project44 a Major Player in worldwide TMS applications, and G2 gave us our 22nd straight season of recognition.
If you already use project44, nothing got tossed in the air when we split the businesses. Your contract, pricing, and account team stay the same. We just made it much clearer who gets our full attention.
Are project44 and LSP44 the Same Company?
No. project44 and LSP44 are separate businesses.
They have their own leadership teams, engineers, sales organizations, and product roadmaps. I’m Founder and CEO of both, and Vinay Mathur is CTO of both, but the teams under us run independently because they’re building for different customers.
What they share is the infrastructure underneath them: the carrier network, carrier APIs, logistics data graph, and agent stack. That foundation reaches more than 280,000 carriers and processes 706 million carrier events a day.
There was no reason to rebuild all of that twice. The important distinction is what sits on top of it. project44 builds for shippers. LSP44 builds for logistics service providers.
Does Customer Data Move Between project44 and LSP44?
No. Shared infrastructure does not mean shared customer data.
I know that’s the first place a broker or forwarder’s mind goes. If project44 serves shippers and LSP44 serves LSPs, you want to know whether your rates, lanes, customers, or margins can somehow cross that line.
They can’t. LSP44 put the commitment in writing. It will never:
- Operate as an NVOCC
- Operate as an indirect air carrier
- Seek freight brokerage or motor carrier authority
- Train models that serve other logistics providers on one customer’s data
- Resell customer data to shippers, or put it into project44’s shipper products
LSP44 won’t compete with its customers. project44 makes the same commitment in the other direction: shipper data doesn’t flow to LSP44 or to the providers running on it.
Why Did project44 Split LSP44 Into a Separate Business?
Because trying to serve shippers and LSPs from the same product organization eventually started making both sides worse.
Shippers want applications they can log into and run. LSPs need infrastructure they can build into their own operation: APIs, SDKs, data feeds, and agents that work behind their brand.
Those are different products, different buying motions, and increasingly different roadmaps.
COVID pushed project44 hard into shipper digitalization. At the same time, the freight recession crushed LSP technology budgets, and I’ll own this part: we stopped understanding that customer as well as we should have. I tell the longer version on our company page.
Then LSPs started adopting agents faster than anyone expected, which widened the gap even more.
So we stopped pretending one roadmap could serve both equally well.
LSP44 now gets one test for every product decision: Was this built for an LSP from the start, or are we trying to make shipper software behave like it was?
Does My p44 Relationship Change?
Yes, but not in the way that makes anyone nervous.
Your integrations, carrier connections, and underlying infrastructure keep working because LSP44 runs on the same foundation. Your data stays yours. You’re not being asked to rip anything out or start over.
What changes is who wakes up thinking about your problems.
LSP44 now has an R&D team focused only on LSP workflows, plus forward-deployed engineers who can write production code alongside your developers. Andy Simmons, who spent four years building at project44, now leads engineering. Robert Zehentbauer, a longtime Kuehne+Nagel operator, leads sales in EMEA North.
Customers are already leaning further in. Net retention rose 393 basis points last quarter, and most customers now run three or more agents at once, according to Q2 FY27 results.
If your request used to sit in a shared queue, that queue is gone.
The Split Only Matters If It Makes LSPs Better
I think the next 12 to 24 months are going to be pretty unforgiving for LSPs still carrying too much manual work.
Armstrong & Associates sees capacity tightening as the freight recession finally burns off. At the same time, the 30th Annual Third-Party Logistics Study says shippers still expect more from 3PL technology than many providers are giving them.
I’ve spent enough time around this business to know what happens next. When the market gets tighter, nobody suddenly finds extra hours in the day.
At a 5% to 8% operating margin, taking $1 of cost out can be worth roughly $16 of new revenue. That’s why I care less about flashy AI demos and more about whether an agent can take a tender, exception, document, or audit off somebody’s desk for good.
LSP44 runs on infrastructure already used by nine of the world’s 10 largest logistics providers, based on the Armstrong Top 50, and we publish a one-week time to first deployment.
If you want to know where to start, don’t start with AI. Start with the workflow your team complains about every week. Use the Agent Job Board to pressure-test it, then bring it to us.
