By Jett McCandless, Founder & CEO, LSP44

In 1999, I dispatched trucks out of a terminal in Portland, Oregon, for $12 an hour. My career plan was pretty simple: get promoted, make another $2 an hour, and use the windfall to upgrade my Friday nights at the sticky-floored bars downtown.

Dispatch had a way of making those well drinks feel medicinal.

We were tied to two-way radios for entire shifts. Bathroom breaks were enough of a luxury that dispatchers getting kidney stones was an actual occupational hazard. Load updates moved through the building one phone call, radio transmission, and desk at a time. The integration layer was basically a kid carrying information around, and most days, I was the kid.

Everyone on that floor knew where the operation fell apart because we spent all day patching it back together by hand. What we didn’t have was anyone who could build something better.

In fact, whenever I suggested a different way to run the desk, the answer was some version of, “That’s an engineering problem.” And with engineering working at corporate, I might as well have been yelling at the clouds.

Sure, every once in a while, somebody from headquarters would visit, ask 100 people what they needed, and get 100 answers. But of course, nothing ever really changed. 

Twenty-seven years, one 3PL, and a little company called project44 later, I still walk into LSPs that have spent millions on software and discover something strangely familiar.

The integration layer is still a person, and thanks to that, you have an integration tax.

What Is the Integration Tax?

If the integration layer is still a person, the integration tax is everything you pay because that person still has to be there.

It’s the engineering hours spent building and maintaining connections between systems that were all sold as solutions. It’s the analysts mapping EDI, the IT team babysitting APIs, and the operations people filling whatever gaps are left when those connections don’t quite work.

Those last costs are the easiest to miss because they look like normal work.

You won’t find a line item called “integration tax” on your P&L. You’ll find it scattered across payroll, IT, implementation costs, support tickets, and thousands of little manual fixes your team has gotten very good at treating as part of the job.

Who Pays the Integration Tax Today?

The people paying the integration tax are the people doing the work your integrations were supposed to eliminate.

In 1999, that was me with a two-way radio, carrying information from one part of the operation to another. Today, it’s the coordinator copying data from a customer portal into the TMS, the offshore team digging shipment details out of PDFs, or the engineer keeping an API alive because somebody changed a field and neglected to tell anyone.

We’ve spent 27 years putting better software around the problem, but the bill never went away. It just got spread across operations, IT, billing, customer service, and engineering, which makes it remarkably easy to underestimate.

What Does One More System Really Cost an LSP?

Once the integration tax is spread across five departments, adding one more system rarely looks expensive. That’s the trick.

You pay for it twice: once for the license, and again for the people keeping it connected.

The second bill starts at go-live:

• An analyst maps the EDI.
• Engineers lose weeknights when a carrier renames a field.
• Coordinators rekey tenders that arrive as PDFs.
• Billing hunts for PODs that never attached.
• An account manager explains why the portal says “in transit” on a load that already delivered.

Procurement can spend a month grinding a few points off the license. I’ve sat on both sides of that table. The higher cost usually shows up later, buried in payroll, support, and hours your team never expected to spend keeping another piece of software alive.

That’s the number I’d want before I signed anything.

How Do You Calculate the Integration Tax at Your Company?

Grab a napkin. Multiply your operations headcount by the fully loaded cost per person, then by the share of their day spent moving data or chasing status. The result is the integration tax your P&L already pays.

My napkin, in round numbers:

• 50 people in operations, each paid $50,000.
• Benefits and payroll taxes are 30.1% of private-industry compensation costs, per BLS data for March 2026, so each person costs about $71,500.
• 20% of their day goes to rekeying, portal checks, status calls, and cleanup.
• 50 × $71,500 × 20% = $715,000 a year.

Don’t trust my 20%? Good. Spend a day on the floor with a notepad and count it yourself.

Calculate Your Integration Tax

Run your numbers through the Integration Tax Calculator and compare the result to every license price on your short list.  

How Much New Freight Does It Take to Match a Dollar Saved?

About $16 of it, at the 5% to 8% operating margin a typical 3PL runs. Cut a dollar of integration tax and the whole dollar lands in operating profit, while a new dollar of revenue only brings its margin along. 

At 6.25%, you’d need $16 of new business to earn the same dollar ($12.50 at 8%, $20 at 5%).

Those numbers come from our May 2026 strategy work. With real assumptions behind them, it’s game over.

Armstrong & Associates’ 2026 market report puts domestic transportation management gross margin at 15.3% for 2025, barely down, so the fight is over cost per load. I think the next 24 months will sort LSPs into haves and have-nots faster than the last 10 years did. Whoever sits it out has close to zero chance of winning.

What Is $715,000 of Integration Tax Worth in New Revenue?

Roughly $11.4 million of new freight at a 6.25% margin, which is a lot of napkin. Depending on your margin, call it $8.9 million to $14.3 million.

You won’t capture all of it, and that’s fine. Even half is the profit on about $5.7 million of new business, collected by absorbing the next wave of volume without the next 10  hires.

At a 5% to 8% margin, every dollar of integration tax you remove is worth roughly $16 of new revenue. Ask your sales team which one is easier to find.

Do Single-Purpose AI Agents Lower the Integration Tax?

Sometimes. But a single-purpose agent can just as easily create more integration work if it doesn’t understand how your operation runs in real life.

Take POD collection. On paper, it sounds easy: once a load delivers, go get the POD. But freight is rarely that clean.

Some carriers have the signed POD immediately. Others scan paperwork a day or two later. Some terminals still send documents to a larger facility before anyone uploads them. A load may also sit for days waiting on an appointment, which makes a simple “four days after pickup” rule useless.

Now your engineers have to teach the agent every one of those exceptions.

That’s the problem with narrow AI built without operational context. It may automate one task, but you can end up spending a lot of time and money teaching it how your business works before it saves you anything.

So Then What Happens When You Stack Single-Purpose Agents?

When you start stacking integration work right along with the agents, your AI budget turns into an integration budget before you know it. Each single-purpose agent takes one task off the job board and hands your people one more connection to babysit.

Some vendors call the result “mostly automated.” I call it the most expensive way to run anything, since you pay for the software and the person who finishes its job.

Fair warning, I’ll take some heat for this. A whole crop of startups is raising money to build a worse version of what we already run at global scale. I’d bet a good number of them get acqui-hired or fold within 18 months, leaving their connection in your TMS for your team to inherit.

Why Do AI Agent Pilots Drag On for Months?

Because the pilot keeps discovering the business in real time, and engineering has to teach the agent every new lesson.

The first few weeks feel great. The agent collects some PODs, the dashboard starts moving, and the project sponsor is understandably fired up. Then the exceptions start arriving. One carrier scans paperwork two days late. Another terminal does it differently. A customer has its own rule. Each one turns into another ticket, another fix, and another round of testing.

Six months later, somebody proudly announces that the agent collected 1,000 PODs.

Great. What percentage of total volume is that?

Sometimes it’s 4%.

That’s how these pilots drag on. The team celebrates activity while coverage inches upward, and by month eight you may have six engineers and $250,000 to $500,000 tied up in one very narrow job.

Where Does an AI Agent Get Its Context?

From freight it’s already seen. That’s why the network behind an agent matters more than the agent. Poor data leads to bad decisions, whether a physical worker makes them or a digital one.

At LSP44, collecting a POD is a button, because we’ve spent 11 years learning how carriers and terminals handle paperwork. Your engineers paid for everything the agent didn’t know in that pilot. Context is the product, and it can’t be raised in a funding round.

People’s eyes glaze over when I say our data graph covers 1.5 billion shipments a year, or close to 48 every second. No single LSP will ever see that much freight on its own, and I don’t care how big you are.

What Does Connect Once Actually Change?

Connect once lets the second system start where the first one left off. The systems and channels your first workflow needs get connected one time, and later workflows build on them. Your TMS and existing integrations stay put.

A second agent becomes a configuration job instead of another integration project, and your operators finally stop being the integration layer. I’d have killed for that in 1999.

The agent is the part you see. The other four layers are why it works: network, observability, intelligence, and integrations. Half of our new carrier connections go live within hours through the Connection Center, and the first agent deploys in a week.

What Is LSP44 Built On?

LSP44 is built on the network LSPs helped us create starting in 2014.

Back then, freight still ran on a heroic amount of phone calls and EDI, and Worldwide Express was the first LSP to write us a check. Since then, that network has grown to 280,000+ carriers and 706 million carrier events a day. Nine of the 10 largest logistics providers on the Armstrong & Associates Top 50 already run on it.

LSP44 takes that foundation and turns it into agentic infrastructure built specifically for LSPs. BlueGrace founder and CEO Bobby Harris put it better than I could: It lets his team put engineering into what actually differentiates BlueGrace.

That’s really the point. Your engineers should be building your advantage, not rebuilding freight connectivity.

Finally: Can You Trust One Provider With Every Connection?

You can, but only if that provider has no reason to turn around and compete with you.

That line matters more once you start connecting your TMS, customers, carriers, workflows, and agents through one infrastructure layer. LSP44 is built for LSPs, and we intend to stay on your side of the table. We 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 make it visible inside project44’s shipper products.

We also built LSP44 as a business, not as a venture experiment we hope someone acquires before the runway ends. We’ve been profitable since day one.

After 27 years in this industry, I have very little interest in giving LSPs another connection to babysit. The whole point is the opposite: connect once, put agents to work across the operation, and let your people spend less time holding the stack together.

Agents deployed. Exceptions handled. Book a mission briefing and bring your calculator number.

We named ourselves LSP44 because “logistics service provider” describes exactly who we build for. Then we started talking to more people in American freight and discovered a small caveat: plenty of them don’t call themselves LSPs.

A broker in Chicago says broker. A 3PL says 3PL. A forwarder says forwarder. A warehouse operator definitely isn’t introducing himself at dinner as a logistics service provider. In Europe, though, LSP is normal lingo for the whole group.

Freight already has enough acronyms to qualify as its own dialect, so normally we’d leave this alone. But the terminology hides a useful point: these companies may all move or manage freight, yet they can run very different businesses.

Armstrong & Associates breaks the market into four major segments, each with its own economics, operating model, and technology needs. Since we build for this industry, those differences are a lot more interesting to us than arguing over vocabulary.

So what actually counts as an LSP, how big are the four segments, and why does an American 3PL in Chicago sound like something completely different in Hamburg?

What Does LSP Mean in Logistics?

LSP stands for logistics service provider, a company that moves, stores, arranges, or manages freight owned by someone else. The shipper owns the goods. The LSP sells the work of getting them where they need to go, using its own trucks and buildings or capacity it buys from carriers.

The term is also an umbrella. Brokers, freight forwarders, 3PLs, third-party warehouses, and 4PLs all sit under it, along with plenty of companies that are all of those at once.

If the goods belong to your customer and your company gets paid to handle them, you’re an LSP, whatever your letterhead says.

It’s also important to note that the overlap with 3PL is large but incomplete. 3PL names the provider by its seat on the contract, the third party next to shipper and carrier. LSP names what the provider sells. 

Which is why it stretches to cover 4PLs and, in most European usage, carriers too.

Which Businesses Count as a Logistics Service Provider?

The definition holds five kinds of business, and big providers often run three or four under one logo.

• Third-Party Logistics Providers (3PLs): Run outsourced transportation and warehousing programs across segments. In the U.S., it’s also the umbrella term.
• Freight Brokers: Arrange truck capacity they don’t own and earn the spread between shipper rate and carrier cost, under FMCSA broker authority.
• Freight Forwarders: Arrange international air and ocean moves, including documents and customs. U.S. ocean forwarders and NVOCCs need a Federal Maritime Commission license.
• Third-Party Warehouses: Store and handle inventory for other companies under contract. Cold storage operator Lineage ranks 27th on A&A’s global 3PL list at $5.4 billion.
• Fourth-Party Logistics Providers (4PLs): Orchestrate the other providers for a shipper, usually asset-light. Andersen Consulting coined and trademarked the term in 1996.

Carriers are the edge case. A carrier sells its own capacity, though the line between the two can run through a single company. For example, Carter Logistics tracks loads as an LSP while its own fleet connects to the same network as a carrier.

How Big Are the Four Segments of the LSP Market?

On paper, the U.S. LSP market is enormous. Armstrong & Associates puts 2025 U.S. 3PL revenue at $323.4 billion, up 5% from the year before.

The interesting part is what’s hiding inside that number. A&A divides the market into four very different businesses, plus another $4.5 billion in contract logistics software.

• Domestic Transportation Management (DTM), $128.3 billion: The biggest piece of the market includes freight brokerage, managed transportation, intermodal, and last-mile. It grew 4.5%, and brokerage alone makes up 83% of the segment.
• International Transportation Management (ITM), $85.9 billion: Air and ocean forwarding, customs, and trade compliance. It grew 7.7%, making it the fastest growing of the four.
• Value-Added Warehousing and Distribution (VAWD), $72.7 billion: Contract warehousing and distribution center management, up 4.4%. Short-term public warehousing sits outside this category.
• Dedicated Contract Carriage (DCC), $32 billion: Trucks and drivers dedicated to a single customer under contracts that typically run one to seven years. Revenue grew 1.6%.

Zoom out, and A&A puts the global 3PL market at $1.3 trillion, with Asia Pacific accounting for 37.5% and North America 28.9%.

Useful numbers, sure. However, they can also fool you into seeing one giant logistics market. A brokerage earning a spread on a load has very little in common economically with a warehouse running a multiyear contract. 

The real story starts when you look at how each of these businesses earns its money.

Why Do LSP Segments Make Money So Differently?

Because they’re selling different things.

A freight broker largely resells transportation capacity it buys from carriers. A warehouse sells its own space and labor. A dedicated fleet puts its own trucks and drivers to work for one customer. Those business models can all live under the LSP umbrella, but the money moves through them very differently.

A&A’s net revenue figures make that obvious. DTM is the biggest segment by gross revenue at $128.3 billion, yet only $19.6 billion remains after purchased transportation is removed. Warehousing, meanwhile, leads the market in net revenue at $56.1 billion. DCC reports the same $32 billion in gross and net revenue because the fleet itself is what the customer is buying.

That leaves brokers operating on a much thinner slice. DTM kept about 15 cents of every gross dollar in 2025, compared with 35.4 cents for ITM.

When your economics look like that, manual work gets expensive very quickly. At a typical 3PL operating margin of 5% to 8%, cutting $1 of cost can have roughly the same profit impact as adding $16 of revenue.

So yes, a warehouse and a brokerage can both call themselves LSPs. They just shouldn’t be buying the same software for the same reasons.

Why Is LSP the Standard Term in Europe?

Because Europe never chopped the industry into as many separate boxes as the U.S. did.

In Germany, logistikdienstleister literally means logistics service provider. It’s a broad, everyday term that can cover a forwarder, contract logistics operator, road carrier, ocean line, or parcel network. Fraunhofer SCS uses it exactly that way in its TOP 100 study of the European logistics market.

That broader definition explains why the European market looks so huge on paper. Fraunhofer says businesses spent nearly €1.6 trillion on logistics in 2023, with about 55% going to outside providers.

Compare that with A&A’s much narrower European 3PL estimate of $229.7 billion for 2025. Different year, different currency, no doubt. But the bigger difference is simple: Europe counts more kinds of logistics companies under the same roof.

That’s also why “LSP” lands naturally with many of our EMEA customers. It’s the language the market already speaks, which is one reason we added a Head of Sales for EMEA North in August.

Why Do U.S. Operators Say 3PL Instead of LSP?

U.S. operators say 3PL instead of LSP because 3PL became the American industry’s catch-all term decades ago, while regulators pushed companies to identify themselves by the specific job they perform.

A broker is a broker. A freight forwarder is a freight forwarder. A carrier is a carrier. FMCSA makes companies choose their type of operation when they register, and ocean freight has its own licensing structure. Even the FDA uses “third-party logistics provider” in its drug supply chain rules.

Meanwhile, 3PL became the broader commercial label. A&A has tracked the U.S. 3PL market since 1994 and still publishes its rankings under that name. Thirty years of reports, conferences, sales decks, and company bios will make a term stick.

We kept LSP44 broader because logistics companies have a habit of refusing to stay in one box. Brokers add warehousing, carriers start brokering freight, forwarders add managed transportation, and so on. 

The specific label still tells you what a company does today, but LSP leaves room for what it becomes next.

So Why Did LSP44 Put the Acronym in Its Name?

After all of that, the name LSP44 is pretty literal.

We build for the whole LSP world: brokers, forwarders, carriers, warehouses, and the companies that have become some combination of all four. That goes back to the earliest days of project44, when logistics service providers like Worldwide Express, BlueGrace, and DSV helped build the carrier network underneath what came next.

LSP44 brings that focus back to the operator, this time with AI-native infrastructure. Connect the systems and channels once, then let AI agents work across them with context from 280,000+ carriers and 706 million carrier events every day.

Nine of A&A’s 10 largest global providers already run on that infrastructure. We also hold no broker authority and no NVOCC license because competing with our customers would be a strange way to build for them.

So yes, we know Americans usually say 3PL. We kept LSP because the industry is bigger, messier, and more interesting than one acronym can capture.

If you run one of these businesses, bring us the workflow your team is tired of doing by hand. That’s a much better conversation than arguing over what to call you.

The appointment strengthens the engineering team building LSP44’s AI agents and infrastructure, as the company builds on a quarter of accelerating growth.

CHICAGO, September 14, 2026: LSP44, the AI-native agent and API infrastructure business for logistics service providers, today announced it has named Andy Simmons as Head of Engineering. Simmons joins as LSP44 builds on Q2 FY27 momentum, including 76% quarter-over-quarter New ARR growth, and will lead the engineering organization building the agents, infrastructure, and developer capabilities LSP44 gives to 3PLs, freight forwarders, and brokers.

Andy Simmons, Head of Engineering

Simmons spent four years at project44, where he led the engineering teams behind Orders and Inventory and then Unified Search, two products built to solve a persistent freight problem: shippers having to chase order, SKU, and shipment data across disconnected systems Orders and Inventory gave them a single view of purchase orders, SKUs, and shipments, and Unified Search extended that same principle, letting users pull up any shipment, order, or inventory record from one place. Earlier in his career, he worked in software consulting at Crowe before joining the startup Telution, later acquired by CSG, then founded and grew Content Direct through its own acquisition.

Most recently, Simmons worked at Atlassian, where he built controls for Rovo, the company’s AI platform, and at iManage, partnering with AI vendors to bring intelligent document management to legal teams.

“Andy has spent his career moving companies from bespoke, disconnected systems to unified, optimized platforms: from Orders and Inventory to Unified Search at project44, then again with AI controls at Atlassian and iManage. He ships agents that hold up under real operations, at scale. That’s exactly the discipline LSP44 needs as we scale our agents across the network.”

Jett McCandless, Founder and CEO, LSP44

In his role, Simmons will lead the teams building and scaling LSP44’s agent platform, from the infrastructure that connects carrier and LSP systems to the controls that let operators trust what an agent does with their data. He will also grow the engineering organization to match LSP44’s pace of customer growth, applying the same discipline he brought to shipping Orders and Inventory, Unified Search, and AI controls at scale.

“I’ve spent my career building systems people can actually rely on, from Orders and Inventory platforms to AI tools for legal teams. The common thread: taking work that used to require constant manual oversight and turning it into something a system can just handle correctly. LSP44 applies that same principle to freight. We’re giving logistics providers AI agents they can trust to run the business, not another dashboard they have to babysit, powered by the best logistics data platform in the industry.”

Andy Simmons, Head of Engineering, LSP44

The hire adds to a leadership bench LSP44 has built quickly since launch, one that pairs deep project44 pedigree with outside AI and logistics experience, and it lands as the company scales its agent platform through a quarter of accelerating growth.

About LSP44

LSP44 is the AI-native agent and API infrastructure business for logistics service providers. Built on the world’s largest logistics data graph and carrier network, LSP44 gives 3PLs, freight forwarders, and brokers the AI agents, carrier infrastructure, and developer capabilities to embed intelligence directly into their own products and workflows. LSP44 is profitable and headquartered in Chicago. Learn more at LSP44.ai.

Media Contact: press@lsp44.ai

By Nick Ruggiero, Head of Product, LSP44

In August, I got on a call with a VP of operations at a brokerage doing about $300M a year. He shared his screen, and there it was: the spreadsheet. Five rows down the side, one per job he wanted off his desk. Seven vendors across the top. Every cell a green checkmark, which is the freight tech equivalent of a dating profile where everyone likes hiking.

He’d started out comparing freight analytics platforms, the way everybody does, and three months later he was looking at agents and asking me which column to pick.

I told him I couldn’t, because his spreadsheet contained no information. He’d asked seven sales teams if they could do a job, and seven sales teams said yes. I spent most of my career building platforms for shippers, so I’ve drawn that checkmark plenty. It’s an honest answer and a useless one.

So I asked if I could redo the spreadsheet with him on the call, and he said sure, in the voice of a man who’s been on many vendor calls. What follows is that hour: two definitions, his five rows, the five questions that weren’t on the grid, and the two rows where I told him to spend his money somewhere else.

First and Foremost: Two Starter Questions

ARC Advisory said something this spring I keep repeating: supply chain leaders have plenty of AI claims and hardly any proof. So before we touched a row, I answered two fundamental questions for him.

What Is a Freight Analytics Platform in 2026?

A freight analytics platform takes your shipment, rate, carrier, and event data and turns it into decisions about cost, capacity, and service. That definition hasn’t moved in a decade. 

What moved, however, is what sits on top. Through 2024, the output was a dashboard somebody squinted at before going and doing something. Now the output feeds an agent that does the something.

He had DAT iQ and rate intelligence bolted onto his TMS, both fine. They tell you what a load should cost, and they’ve never moved one, and most buyers discover those are two different products after the contract is signed. A directory lists options. An operating system decides, executes, and learns from every load.

Why Has the Freight Analytics Platform Question Turned Into an Agent Question?

Because an agent is exactly as smart as the data underneath it, and no prompt is clever enough to fix that. Hand two agents the same instruction with different context and you get two different answers, and I’d bet one of them just re-tendered a load to a carrier with a conditional safety rating and felt great about it.

Gartner’s 2026 Hype Cycle for Agentic AI parks the category at the Peak of Inflated Expectations. Only 17% of organizations have deployed agents, more than 60% say they will within two years, and Gartner’s read is that the foundation matters as much as the agent. 

Three months in, he hadn’t asked one vendor what their agent would know about his carriers before it touched a load.

What Are the Five Jobs Freight Teams Hire AI Agents to Do?

The five jobs are check calls, POD and document retrieval, appointment scheduling, exception management, and inbox triage. It’s the same list at every brokerage and 3PL I’ve walked through this year, because those are the five places a desk burns hours on work that doesn’t need a person.

They were his five rows too. We published a polite version of this list in July. This is the other one.

Job One: Check Calls and Status Cadence

A check call is a rep phoning a carrier to ask where the truck is, and it eats two hours of a rep’s day. His row was seven for seven, and he’d piloted a voice specialist he liked.

On the call itself, a voice agent beats any platform’s voice module, ours included, and HappyRobot’s $150M raise on August 4 at $1.2B says the market agrees.

Then we checked how many of his loads ran on carriers we had API connections to. Most of them. On an API network, a position lands every seven minutes, and a ping is a fact. A call gets a dispatcher once an hour, and a guess. His agent was dialing because dialing was all it had.

Ask what yours knows before it picks up the phone.

Job Two: POD and Document Retrieval

A POD is the signed proof the freight arrived, and you can’t invoice without it, so billing spends its day chasing carriers for paperwork by email and portal. This was the first row I told him a specialist might beat us on. Shortlist two.

The payback is cash; it hits DSO inside a billing cycle, and the good ones read a 2 a.m. truck stop BOL photo better than most humans. The catch is that retrieval is half the job, since the document still has to match a shipment and write back.

His team had hundreds of classified PDFs for loads no one could match. That’s why we built LTL PRO Resolution. A shipment with no valid PRO is a ghost, so the agent gets the number from the carrier and writes it back. Ask what theirs does when the PRO is wrong.

Job Three: Appointment Scheduling and Rescheduling

Scheduling is booking the dock window, and rescheduling is moving it when the truck’s going to miss, and a desk does both by phone. I told him to buy dock scheduling software, and he already had it, which made me like him more. Second row I’d hand to somebody else.

So why was the row still there? Detention. ATRI’s survey of 587 drivers and 245 carriers found drivers held at 39.3% of stops in 2023, up to 209 hours a year each, $11.5B in lost productivity and $3.6B in direct cost.

Rescheduling is an ETA problem before it’s a calendar problem. His dock software owned the slot, with no idea the truck was 90 minutes down outside Effingham. Something has to see the slip and move the slot first. That’s Dispatch & Appointment. Ask what triggers a reschedule, and how early.

Job Four: Exception Management and ETA Validation

An exception is any load that’s off plan, late, stuck, missing a status, and someone has to notice, figure out what’s true, and fix it. He got annoyed here because he’d watched four exception demos that all looked great.

Every exception demo is the same: 90 seconds, red row, click, green row, rehearsed so you don’t ask where the red row came from. Ask anyway. Detection quality is the data underneath, and a tool on your TMS’s feed inherits every gap your TMS has, so it finds what you knew and misses what costs money.

Then there’s the fix, which is a network action. Re-tendering means knowing who’s next best on that lane this week and how to reach them, which ARC Advisory calls tracking to intervention and we call the Intelligence layer. Make every vendor show you an exception your TMS never flagged and what they did. Two of his four couldn’t.

Job Five: Inbox Triage and Inbound Routing

Inbox triage is working the shared ops mailbox, where carrier updates and customer “where’s my freight” emails pile up, and somebody reads each one to figure out which load it’s about. I told him this was the easiest row and to take the win, because sorting email is close to what these models do naturally. What worried me was the write-back.

I made him read CargoNet’s Q2 report from August 6. Theft incidents were down 26% year over year. Yet, losses more than doubled to $304.6M, and the schemes that held steady were business email compromise and shipment misdirection. The physical stuff got harder, and the email stuff kept working.

He was about to let software answer carrier emails without asking what it checks before it hits send. Ask what the agent verifies about a sender before it acts, and at what dollar amount a person has to look first.

Five More Questions Before Putting Pen to Paper 

By then his five rows had answers, and the spreadsheet had run out of columns, which was the point. The questions that decide whether any of this works don’t fit in a grid, and none of his seven vendors had volunteered them.  

Should You Buy a Point Tool and Go Home?

Halfway through, he asked when he should just buy a point tool and be done. Fair question, and there are three cases where the answer is yes.

1. You’re a Shipper: LSP44 is built for brokers, 3PLs, and forwarders moving someone else’s freight. If you’re buying for your own, you want project44, and I’ll walk you over myself.
2. One Desk Is Underwater, and the Rest of the Operation Is Fine: Buy the specialist for that desk. Infrastructure bought in a panic gets ripped out 18 months later by whoever inherited it.
3. Your Dock Calendar Is the Constraint: Covered above, and repeated because it’s the miss I see most.

He didn’t fit any of the three. He had three of five rows on fire at once, and that’s where I stopped being polite.

What Did the Supreme Court Do to Your Audit Log?

On May 14, the Supreme Court ruled 9-0 in Montgomery v. Caribe Transport II that negligent-hiring claims against brokers survive FAAAA preemption, and a decade-old shield was gone. Four days later, the 4th Circuit vacated Echo Global’s summary judgment.

He hadn’t connected that to the spreadsheet. Any agent that picks a carrier or re-tenders a load leaves a discoverable record of a safety decision, and every late-night re-tender is a document a plaintiff’s attorney will eventually read to a jury. If your vendor’s audit log is a CSV export, congratulations, you’ve prebuilt the exhibit. Ask if you’ll still have that log in two years.

Which Autonomy Tier Are You Actually Buying?

He asked this one himself, so the ruling had landed. You set the autonomy by customer, by lane, and by dollar threshold, and a vendor who hands you an on/off switch has never sold to a burned broker. 

Four tiers, and make every vendor name which one you’re buying:

1. Observe: Watches and reports; touches nothing.
2. Recommend: Proposes and waits for you.
3. Act With Approval: Executes after a human signs off, inside your thresholds.
4. Act Autonomously: Executes inside your guardrails, with every action logged.

This matters more than any feature list. Gartner expects over 40% of agentic AI projects will be canceled by late 2027 over cost, value, or controls, and MIT’s NANDA group found 95% of 300 enterprise AI projects had no measurable P&L impact. These projects die in procurement, and they die over control.

What Does Buying Five Tools Really Cost?

We crunched numbers on the call. Five jobs bought separately are five contracts, five integrations, five write-back paths, five audit trails, and five vendors who all have to survive until 2029. Not to mention, the license fees were the smallest number on that list and the only one in his business case. The real cost is the evidence.

ATRI found 94.5% of fleets charge detention and collect on fewer than half the invoices: the work got done and the paperwork couldn’t prove it. Every vendor on his grid priced the task and left the evidence as somebody else’s problem. Ask each one what happens to the record when their tool is wrong, and count the shrugs.

What Happens When You Add the Second Agent?

None of his seven vendors wanted this question, because it separates a pilot from a purchase. Anyone can get one agent live on one workflow. With five-point tools, the second agent is a second integration project and a second vendor to keep alive. With one data graph, it’s a configuration, and the difference compounds with every agent you add.

As of our quarter ending July 31, most customers run three or more agents; the next one adds no integration work, and new ARR grew 76% quarter over quarter with net retention up 393 basis points. 

I’d rather you check it than take my word. Ask every vendor what the second agent costs to stand up, and count the statements of work.

Buy the Layer Underneath the Agent

He went back to his spreadsheet and replaced every green checkmark with the answer to the question for that row. Most turned yellow, a few turned red, and it was the first honest version of the grid he’d seen in three months.

So score the jobs, then buy the data layer. The specialists will keep getting better at single jobs. What compounds is the context underneath, and there’s exactly one place to get 11 years of it.

LSP44 runs on 280,000+ carriers and 706 million carrier events a day, roughly $1B in the making. Nine of the 10 largest logistics providers on the Armstrong & Associates Top 50 run on it; we’ve been profitable since day one, and most of the companies on your grid can’t say either. Your TMS manages the record. LSP44 executes the work.

Sometime in 2028, an attorney is going to ask your software to explain a carrier selection. Buy for that conversation.

If you’ve got a spreadsheet like his, book a 30-minute mission briefing and bring it. We’ll go row by row, and I’ll tell you to your face which rows we lose.

CHICAGO, August 19, 2026 — LSP44, the AI-native agent and API infrastructure business for logistics service providers, today announced it has named Robert Zehentbauer Head of Sales, EMEA North. Zehentbauer joins the sales leadership bench LSP44 named in July, extending dedicated regional coverage across Europe alongside Raphaël Hiff, Head of Sales, EMEA South.

The appointment follows a strong first quarter for LSP44, with New ARR accelerating 76% quarter over quarter in Q2 FY27. Read the full results in LSP44’s Q2 FY27 momentum release.

Zehentbauer brings more than 15 years of sales leadership experience in logistics and supply chain software, including leadership roles at project44, Blue Yonder, Descartes, and i2 Technologies. Earlier in his career, he spent more than a decade at Kuehne+Nagel, one of the world’s top three global logistics service providers, as SVP of Global Key Accounts and Industry Verticals.

Most recently, he served as a senior business advisor to software companies across logistics, supply chain, and AI, including Celonis, the global market leader in process intelligence, and HappyRobot, an AI agent platform, where he supported go-to-market efforts across Europe.

“In my sales leadership and advisor work, I sat in on deal after deal where an LSP got excited about an AI pitch, then killed it three months in because the vendor didn’t understand their business, their data, or their carriers. I heard the same story from 3PLs trying to build it themselves: it worked in the demo, then stalled the moment it hit real operations. LSP44 doesn’t have that problem. It already has the data, the context, and AI agents built specifically for LSPs, with a lot more coming. That’s why I’m joining,” Zehentbauer said.

Jett McCandless, Founder and CEO of LSP44, said, “LSP44’s global momentum is building because logistics service providers need the same infrastructure and AI agents everywhere they operate. EMEA is a huge part of this growth: it’s one of the most complex regions in the world to run freight through, and one of the most important for our LSP customers. Robert has spent his career on both sides of that problem, inside LSPs and advising the AI companies trying to serve them, which is exactly the perspective we need as we bring this API infrastructure and AI agents to more customers in the region.”

About LSP44

LSP44 is the AI-native agent and API infrastructure business for logistics service providers. Built on the world’s largest logistics data graph and carrier network, LSP44 gives 3PLs, freight forwarders, and brokers the AI agents, carrier infrastructure, and developer capabilities to embed intelligence directly into their own products and workflows. LSP44 is profitable and headquartered in Chicago. Learn more at LSP44.ai.

Media Contact: press@lsp44.ai

CHICAGO, August 12, 2026: LSP44, the AI-native agent and API infrastructure business for logistics service providers, today announced Q2 FY27 results for the quarter ended July 31, 2026. New Annual Recurring Revenue (ARR) accelerated 76% quarter over quarter.

Net Retention Rate (NRR) improved 393 basis points quarter over quarter and expansion rate strengthened, up 115 basis points quarter over quarter, as existing customers adopted more agents.

Customers are increasingly leveraging LSP44 Agentic Workflow Manager to configure and deploy their own AI agents, enabling them to automate 80%+ of resolution processes, reduce manual intervention, and lowering procurement costs by 18%, without having to deploy separate AI point solutions.

“We deployed AI agents on the same data graph and carrier network we’ve built and ran for years. This quarter shows how our purpose-built technology for LSPs means has translated into value for our customers: 18% lower procurement costs, 80%+ of exceptions resolved automatically, and New ARR up 76% quarter over quarter as those same customers keep adding more agent. That’s proof LSP44 is winning.”

Jett McCandless, Founder and CEO, LSP44

Product Innovation Leads the Strategy

LSP44 is being built on a five-layer AI framework that manufactures and runs production-grade agents at logistics scale: Network, Observability, Intelligence, Integration, Agents & Workflows. The network layer spans 282,000-plus carriers, 8 billion signals, and 140-plus port terminals, across 1,400-plus IoT devices, 300-plus digitized yards, a million-plus warehouses, 600-plus rail lines, and 100-plus highways, live and learning in real time. Observability delivers Agents and API performance dashboards, health monitoring, SLA tracking, audit logs, and alerting. Intelligence provides the context, semantics, and reasoning to help operators solve increasingly complex problems. Some examples across the LSP organization include security teams assessing route deviation and hot-zone theft risks in real time, capacity teams inferring carrier availability from asset positions, and customer service teams using root cause reason codes and KPI reporting to be proactive in customer communications. Integration connects through API, EDI, AI voice & messaging, video OCR, and document processing, meeting customers’ systems where they are. And the agents themselves: 50+ agents available across 10 categories, running autonomously across the full LSP workflow, from carrier procurement to freight audit and settlement.

Four of the critical agents delivering for 3PLs, freight forwarders, brokers and 3^rd party warehousing or 4PLs, are Carrier Procurement, Exception & Disruption Recovery, Theft Prevention, and LTL PRO Resolution.

Carrier Procurement: 18% Lower Procurement Costs

LSP44’s Carrier Procurement agent automates sourcing, rate comparison, and tender management across the carrier network, scoring carriers on digital performance, on-time performance, lane coverage, and fraud risk, and assembling priced, lane-level bid responses to shipper RFPs in hours instead of weeks. Customers running this agent are seeing an 18% reduction in procurement costs.

Exception & Disruption Recovery: 80%+ Auto-Resolution

The Exception & Disruption Recovery agent detects, classifies, and autonomously resolves shipment exceptions, re-tendering to the next-best carrier or rerouting freight when disruptions occur, without waiting on a person to notice first. More than 80% of exceptions are now resolved automatically.

Theft Prevention: Detection to Resolution in Minutes

Built to address a cargo theft crisis costing the U.S. an estimated $35 billion annually, the Theft Prevention agent continuously monitors truckload shipments using AI models and telematics data from ELD providers, trailer sensors, and door sensors, automatically triggering carrier outreach the instant a high-risk event occurs. Customers running this agent are resolving suspected theft incidents in minutes instead of hours, with unlimited, simultaneous coverage across every shipment in the network.

LTL PRO Resolution: Missing PROs Recovered Without a Human Touch

An LTL shipment without a valid PRO number is invisible. It can’t be connected to the carrier, statuses can’t be returned to the end customer, and invoices can’t be matched at audit. The LTL PRO Resolution agent detects shipments tendered without a PRO or carrying one that fails validation, then sources it: reaching out to the carrier directly by email, message, or voice when the number isn’t published anywhere, writing the confirmed PRO back into the TMS so tracking, customer updates, and invoice audit all proceed on their own.

A majority of customers are running three or more agents concurrently, a trend reinforced by growing adoption of LSP44 Agentic Workflow Manager for self-serve workflow configuration.

What’s Next

Looking ahead, LSP44 is focused on three directions. The first is observability, giving LSPs transparency into what agents and APIs are doing on their behalf so that automated activity is auditable. The second is agent workflows built by Mo and supported by our Forward Deployed Engineers, who scope and tune those workflows alongside operations teams. The third is deeper drayage support, moving past visibility and into the execution to help LSPs reduce lead times and cost in drayage operations.

What Customers Are Saying

“The backbone of Lineage Logistics is our network of sophisticated cold storage facilities, which our customers rely on to get products where they need to be safely, efficiently, and on time.​ Food waste is a growing problem that affects everyone, from shippers to retailers to consumers. LSP44’s unmatched technology and data intelligence made them the obvious choice to be our technology partner.”  

Sudarsan Thattai, Chief Information Officer

 & Chief Transformation Officer, Lineage Logistics

“As a fully-integrated third-party logistics provider, one-dimensional supply chain visibility just doesn’t cut it. LSP44 recognizes the complexity of our multimodal network, which includes truckload, drayage, international and intermodal shipments, and innovates constantly to deliver the most comprehensive solution.” 

Jon Poehnelt, CCO at Steam Logistics

About LSP44

LSP44 is the AI-native agent and API infrastructure business for logistics service providers. Built on the world’s largest logistics data graph and carrier network, LSP44 gives 3PLs, freight forwarders, and brokers the AI agents, carrier infrastructure, and developer capabilities to embed intelligence directly into their own products and workflows. LSP44 is profitable and headquartered in Chicago. Learn more at LSP44.ai.

Media Contact: press@lsp44.ai