In the early part of my career, I started at Eastern Airlines in passenger sales and reservations, not cargo. That experience taught me how frontline service really works: fast decisions, constant coordination, and no room for confusion when customers need answers.
After that, I spent nearly a decade in banking. On the surface, it looked like a very different world. But the discipline stayed with me: process, accountability, accuracy, and understanding how breakdowns in communication create bigger operational problems downstream.
The real turning point came when I joined a small family-owned freight forwarder as an EDI Manager and 3PL Manager. That is where I actually learned logistics.
My "office" wasn't a glass-walled suite. It was a desk buried under thermal fax paper, three different phone lines ringing simultaneously, and a massive beige computer monitor that hummed like a small refrigerator.
As the 3PL Manager, I was responsible for setting up accounts with the EDI system and managing customers' traffic departments — spanning some of the largest manufacturers, tech companies, oil & gas firms, and more. It became a professional bootcamp in learning all the ropes across the full logistics spectrum, where I gained hands-on mastery of import/export, air, ocean, trucking, warehousing, pick and pack, and EDI/3PL operations by managing real customer accounts under real operational pressure.
My job was ostensibly about data, but in reality, I was a translator. I spent my days bridging the gap between developers who lived in a world of binary logic and the operations crew who lived in a world of "where the hell is my truck?"
The developers saw data points. The operations team saw a late shipment, a frustrated customer, and a driver waiting at a locked gate.
That small forwarder taught me how differently customers and manufacturers think about shipping, and how execution has to adapt to both. I learned very quickly that the most sophisticated software in the world is useless if it doesn't account for the "dirty" reality of how freight actually moves.
The 25-Year Journey of the "Glue"
For the next two and a half decades, as I built ImEx Cargo, that lesson became my North Star. We weren't just a General Sales Agent (GSA) or a logistics provider; we were the people who fixed things when they broke.
The industry changed, of course. Faxes turned into emails. Emails turned into SaaS platforms. But the core problem remained stubbornly the same: fragmentation.
Every stakeholder: the airline, the trucker, the freight forwarder, the government agency: has their own system. They all work perfectly in a vacuum. But as soon as a shipment moves from one stakeholder to the next, the execution breaks down.
The data gets lost. The accountability vanishes. The visibility goes dark.
I spent 25 years trying to recreate that collaborative environment I learned inside that small forwarder bootcamp in the 90s: not through better faxes, but through a shared "execution layer." We built internal tools to help our team coordinate these messy handoffs because we had to. We couldn't do our jobs without them.
The "Aha Moment"
The realization didn't come in a boardroom. It came during a particularly complex infrastructure project where we were coordinating dozens of diverse suppliers (DBEs), workforce pipelines, and multiple transportation modes.
I looked at the system we had built: the one we were using just to keep our own heads above water: and realized: this is the product.
We hadn't built another Transportation Management System (TMS). We hadn't built a marketplace. We had built a digital execution infrastructure. We had built the "glue" that the entire industry was missing.
"I was trying to solve real operational problems. But somewhere along the way, those solutions evolved into something much larger than us."
Introducing Plug-In Freight Ops™
That internal coordination layer is now what we call Plug-In Freight Ops™.
It wasn't designed by software engineers looking for a "market opportunity." It was designed by logistics operators who were tired of the execution gap.
Unlike traditional platforms that ask you to "rip and replace" your existing systems, Plug-In Freight Ops™ sits above them. It standardizes the workflow from the moment a quote is generated to the final tracking and delivery.
Why Infrastructure Matters More Than Features
In the logistics world, we are often distracted by "shiny" features. But features don't move freight: infrastructure does.
That is the category argument behind Plug-In Freight Ops™ and, more broadly, behind digital execution infrastructure itself.
What matters is not a longer feature list. What matters is whether the operating model creates structured accountability at each handoff, shared visibility across the shipment lifecycle, and a practical way to bring DBE partners, workforce pipelines, and other ecosystem participants into the same execution flow without adding more fragmentation.
That is what turns disconnected activity into coordinated execution.
Lessons from the EDI Days
Looking back at my time at that small family-owned freight forwarder, I realize that the challenges haven't actually changed. That was where I learned the full operating reality of logistics: setting up accounts within the EDI system, managing customers' traffic departments, and gaining hands-on mastery of import/export, air, ocean, trucking, warehousing, pick and pack, and EDI/3PL operations under real operational pressure.
We are still trying to get different people, with different priorities, using different systems, to move a box from Point A to Point B without it disappearing into a black hole of emails.
The difference is that now, we have the technology to build a coordination layer that matches the complexity of the real world.
We didn't set out to build a new category of logistics software. We set out to make sure the truck showed up, the airline was ready, and the customer was happy. But in doing so, we found a way to bridge the gap for everyone else.
The Path Forward
The logistics industry is too fragmented for any one "all-in-one" system to win. The future belongs to the connectors: the layers that allow existing systems to talk to each other and people to coordinate with precision.
As outlined in our June 30, 2026 press release, we are formally putting language around something the industry has needed for a long time: a shift in focus from "shipping" to "execution infrastructure."
If there is a broader takeaway in all of this, it is a simple one: every operation has a point where systems stop and execution has to carry the load. The real question is whether you can see, structure, and manage that point before it becomes delay, cost, or risk.
To learn more about the formal launch of our digital execution layer, read the full June 30, 2026 press release here.
