About

We build the control tower we wished we had

The team behind Logistics Tower has run freight operations, built TMS integrations, and sat in the dispatcher's chair. We are building the product we wished we had, and we are building it for the mid-sized 3PLs and freight forwarders the enterprise vendors ignore.

Company statistics

12.4M+ Shipments under management Annualized, network-wide
1,800+ Active lanes Ocean, air, road, rail
420+ Port and hub coverage Across 64 countries
99.95% Platform uptime Rolling 90-day average

Story

Built by people who moved freight

Logistics Tower started in 2024, in a dispatch office, on a Tuesday morning. The dispatcher had four exceptions open, three carrier portals running, and one customer on hold. The customer wanted to know when their container would arrive. The dispatcher did not know. The container was on a vessel somewhere in the Atlantic, and the vessel's position had not updated in 14 hours.

The dispatcher's job, that morning, was not to track the container. It was to make a decision: rebook the customer's delivery slot, or wait. The dispatcher did not have the data to make the decision. They had five pieces of data, from five systems, and no way to merge them.

We built Logistics Tower to be the merge. The platform takes the carrier's vessel position, the rail carrier's intermodal ETA, the drayage carrier's GPS, and the warehouse's dock schedule, and produces one timeline, one ETA, and one action. The dispatcher's job is to act on the action. The platform's job is to compute it.

We are a small team. We have run freight operations, built TMS integrations, and sat in the dispatcher's chair. We are building the product we wished we had. We sell it to mid-sized 3PLs and freight forwarders because they are the ones who feel the pain the most and have the least access to the enterprise tools that fix it.

Principles

Four principles we build against

01

The data is the product

Every feature starts with the data model. If the model is wrong, the feature is wrong. We do not ship features that paper over a broken model.

02

Dispatchers first

We design for the dispatcher at 2 a.m. with three exceptions open. If the product does not work for them, it does not work.

03

No portal-hopping

A dispatcher should never have to leave the console to do their job. If a workflow sends them to a carrier portal, we have failed.

04

Honest defaults

The platform's defaults are the right ones for a mid-sized 3PL. We do not ship dark patterns or opt-out complexity.

Team

The team

Headshots and named bios are available on request. The list below is the role structure, not the org chart.

[TEAM MEMBER]

CEO

Strategy, customer relationships

[TEAM MEMBER]

CTO

Platform architecture, security

[TEAM MEMBER]

Head of Product

Roadmap, dispatcher experience

[TEAM MEMBER]

Head of Solutions

Implementation, customer engineering

[TEAM MEMBER]

Head of Operations

Network, carrier relationships

[TEAM MEMBER]

Head of Design

Console, charts, brand

Want to talk?

We answer every email. Reach out, even if you are just curious.

Get in touch