By Jett McCandless, Founder and CEO, project44 and LSP44
I get asked this constantly: project44 versus LSP44, which company do you actually run?
I probably deserve the question. My email still ends in project44.com. A September byline in Global Trade Magazine called me “Founder + CEO, project44 + LSP44.” I figured that covered it. Freight people, as usual, wanted a little more detail.
The short answer is both. I’ve run project44 and LSP44 side by side since we split the businesses on July 14.
The longer answer is the one I usually use for brokers, 3PLs, and forwarders after we’ve talked for five minutes. They know project44 works with shippers. They know LSP44 is building AI infrastructure for LSPs. What they really want to know is where the wall sits between the two, because nobody in this business wants to hand over rate data and then wonder who else can see it.
Fair question. It’s also the question that explains the whole setup.
I wrote the clean version in Two Businesses, Two Buyers. This is the version I’d give you over a drink, including why we split the companies and what that means when you’re trying to get an AI business case approved inside your own shop.
What Is LSP44, and How Is It Different From project44?
LSP44 is the company we built for brokers, 3PLs, 4PLs, freight forwarders, and carriers. project44 serves enterprise shippers through Movement, so the cleanest way I know to explain project44 versus LSP44 is to start with the freight itself.
If you own the freight, project44 is built around your operation. If your business is moving freight for somebody else, LSP44 is built around yours.
That distinction sounds obvious once you say it out loud, but it changes almost everything about the product. An LSP already has a TMS, carrier relationships, customer workflows, and its own way of running the business. We built LSP44 to fit into that environment, which is why our agents and APIs sit underneath the operation instead of asking the LSP to rebuild around us.
That’s also what we mean by agentic infrastructure for LSPs. The technology works inside your business, while your customer keeps dealing with you.
Are project44 and LSP44 the Same Company?
No. project44 and LSP44 are separate businesses with their own leadership, engineers, sales teams, and roadmaps. What they share is infrastructure: the largest AI-native agent network, carrier API infrastructure, and logistics data graph connecting more than 280,000 carriers and processing 706 million carrier events a day.
I dispatched trucks back in 1999, so I think about it like a set of doubles. There’s a common tractor underneath, while each trailer has its own freight, customer, and seal. Sharing the tractor doesn’t give anybody permission to break the other seal.
The same rule applies here. project44 doesn’t share shipper data with LSP44, and our commitments to LSPs are in writing. LSP44 won’t become a broker, carrier, NVOCC, or indirect air carrier, use one customer’s data to train models for another, or feed LSP data into project44’s shipper products.
If you build your business on LSP44, we’re not coming after your freight.
Why Did project44 Split Into Two Businesses?
project44 split into two businesses because shippers and LSPs needed different things, and over time we built the company around the shipper side.
The irony is that LSPs were there first. They made up 82 of our first 100 customers, and Worldwide Express wrote our first check. Then shippers started pulling us toward visibility software they could log into, and COVID poured gasoline on that demand.
We followed it. By the time the market cooled and LSPs were dealing with a freight recession, we had a very good shipper business and an LSP customer base waiting behind shipper priorities.
I don’t have a clever way to dress that up. We got better at serving one buyer and worse at serving the other. The fix was to stop asking LSPs to share the line and give them a company built around them.
Does My project44 Relationship Change?
For most customers, no. If you’re an LSP already connected to project44, those integrations and carrier connections keep working, and your data stays yours.
What changes is the team on the other side. LSP44 has its own R&D organization and forward-deployed engineers working directly with LSP developers on the problems sitting inside their operation.
You can see that in the work we announced with Carrier Logistics on AI bot fatigue. When a tracking number is missing or wrong, automated calls and emails can hammer a carrier’s service desk. We’re building an API that can find the shipment anyway, which is exactly the kind of difficult, specific LSP problem I wanted this team waking up to every morning.
If you’re a shipper, even less changes. Your contract, account team, and project44 relationship stay where they are. I split my calendar between two companies. The project44 team doesn’t, and the business has kept growing with them focused on that customer.
How Should an LSP Build the Business Case for AI Agents?
Start with revenue and customer service. Put the efficiency deal a few slides later.
When I dispatched trucks, people on my team got kidney stones because nobody wanted to leave the two-way radio long enough to use the bathroom. That sounds insane now, but the basic constraint hasn’t changed much: an LSP can only move as much work as its people can absorb.
I wrote about this in August. AI agents raise that ceiling, which means you can take on more freight without making every growth spurt a recruiting exercise.
Then show the cost case. At a typical 5% to 8% operating margin, $1 of cost removed is worth roughly $16 of new revenue.
Still, the part I’d lead with is service. The 2027 Third-Party Logistics Study says shippers value trust and open communication most in a partner. For an LSP, protecting that relationship is how the revenue stays.
Finally: Which LSPs Come Out Ahead Over the Next 12 Months?
The LSPs that come out ahead over the next 12 months will be the ones that can take on more freight, respond faster, and protect the customer relationship without adding headcount every time volume moves.
Capacity is already getting tighter. SONAR’s rejection index has been running near 14%, roughly triple its 2023 to 2025 range, which means more exceptions, more touches, and more pressure on the same teams. Meanwhile, more than 40% of shippers already consider a provider’s AI capabilities when choosing who gets the freight.
That’s why I’d build the AI case around growth and service first.
It also brings us back to project44 versus LSP44. I run both. If you own the freight, project44 is built for you. If your business is moving it for someone else, LSP44 is the company I built around your side of the table.
Bring us the workflow your customers feel most. That’s where I’d start.
