I left Aersure. I'm taking the hard lanes with me.

I left Aersure this month. I'm taking the hard lanes with me.

That's the whole announcement. No sunset post. No "grateful for the journey" paragraph. The company I built got acquired by Shipper.id a while back. It's moving toward what you'll know as Shipper Cross Border. I stayed through that. Then I stopped staying.

The tidy version of a departure is that you close a chapter and walk into a new title. I have a new title. Head of Special Projects, Cross-border, at Ninja Van, across six Southeast Asian markets. The title is not the interesting part. The lanes are.

Leaving a company is not the same as leaving the work. The work was never the logo.

What I'm actually taking

People ask what you take when you leave. They mean contacts, or a playbook in a Google Drive, or the right to tell the origin story at dinners. I'm taking the parts that never sat cleanly on a slide.

Customs that behave like a personality, not a form. Last-mile networks that look identical in a pitch and then fall apart on a Tuesday in rainy season. Returns nobody wanted to own. Duties that were "fine" until a SKU got queried. Commercial invoices that worked in Singapore and then sat in Jakarta. Six markets that share a timezone and almost nothing else.

That's the inventory. Not a client list. Not a revenue number. A way of seeing the seams. I learned it building Aersure. I learned it again after the acquisition, when the brand on the door was no longer the whole story. I'm not going to pretend the next job is a blank page. It isn't. Cross-border at this scale is the same animal in a bigger cage.

The wrong question

The question people ask is why you'd leave a thing you founded. As if founding is a marriage and leaving is a failure. The more useful question is whether the container still matches the work.

For a stretch, it did. Then it didn't. Shipper.id owning Aersure was not a tragedy. It was a fact. Facts are allowed to change what you do next. I started a consultancy earlier this year because some of the thinking needed a place that wasn't an org chart. I'm joining Ninja Van because some of the work needs a network that already exists in six markets, and special projects is the honest name for the work the core product isn't built to hold.

Those two things can sit next to each other. I'm not going to tidy them into a personal brand. One is a small consultancy. One is a job. The lanes don't care which calendar they live on.

You'll hear "special projects" and think staff work. Slide work. The innovation lab that never touches a parcel. That's not what I signed up for. Special projects, in an operator shop, is the pile that arrives when the standard product hits a lane it wasn't designed for. Cross-border is full of those lanes. That's why I took it.

Six markets, not a region

Ninja Van runs in six Southeast Asian markets. That's the job. I am not going to call it one network on week one. It isn't one network. It's six operations that happen to share a company name. Indonesia is not Vietnam. Vietnam is not Thailand. Thailand is not the Philippines. The Philippines is not Malaysia, and Malaysia is not Singapore.

I already knew that from the other side of the table. Building a cross-border company teaches you the seams because you live in them. Sitting inside a 3PL will teach them again, louder, because you see every brand that thought they bought a region and actually bought a contract.

I'm going in with that bias on purpose. The bias is: don't average six realities into one on-time number. Don't let a dashboard become the product. Don't outsource the thinking along with the freight, even if the freight is now my job.

The hard lanes travel. Titles don't.

What I won't do

I won't write a list of lessons from Aersure as if the company was a course. I won't invent a number to make the exit look like a win or a loss. I won't pretend I have already "transformed" anything at Ninja Van. I started this month.

What I will do is keep looking at the same ugly objects. The handoff that nobody owns. The SOP that was copied from a market it doesn't fit. The exception that only happens 8 percent of the time until volume shows up and it's the whole afternoon. The customer who is red while the SLA is green.

If you worked with me at Aersure, you already know how I talk about this. Process first. Then the partner, the software, the warehouse. In that order. That doesn't change because my email signature did.

The consultancy stays in the background. This is not a launch post for that either. It's a note that I left, I'm going inside a 3PL to run the work the core team can't hold, and the hard lanes are coming with me because they're the only part of the last few years that was ever portable.

See you in the exception pile.