Can CeylanVienna-based, globally curious.
Articles/Tech & AI

AI and the Logistics Layer Nobody Talks About

Every AI demo shows the glamorous output. Nobody shows the warehouse chaos underneath it.

21.4.2026·2 min read

Every AI demo I watch starts the same way: a slick interface, a prompt, a magical result. What nobody shows you is the logistics layer underneath, the movement of physical goods, the last-mile chaos, the warehouse that had to be completely redesigned just to support the algorithm that makes the demo look seamless.

I spent years at Foodora running logistics operations. We had machine learning optimizing delivery routes before it was fashionable to say "AI-powered." And what I can tell you is this: the technology was the easy part.

The unglamorous truth

When you optimize a delivery route, you're not just solving a math problem. You're negotiating with traffic, weather, human behavior, restaurant kitchen speeds, and the rider who decided today was the day to quit. No algorithm accounts for all of that perfectly.

Continue reading?

The next essay lands in your inbox first. The thinking behind the decisions.

What AI does well is reduce the variance. It narrows the band of bad outcomes. It makes the average better. But the tail risks, the really bad days, those still require humans who understand the system deeply.

The most dangerous place to be is confidently wrong. AI systems can be confidently wrong at scale.

Where it's actually going

The logistics companies that will win in the next decade aren't the ones deploying the most AI. They're the ones building the feedback loops that make their AI smarter than anyone else's. Data moats are real, and they're being built right now in fulfillment centers most people have never heard of.

What I watch closely: autonomous middle-mile (trucks between warehouses), dynamic slotting in warehouses (AI deciding where to place goods in real time), and demand forecasting that actually accounts for social signals, not just historical sales.

The last one is underrated. If you know a product is going viral on TikTok 48 hours before it spikes, you can pre-position inventory. That's not science fiction, it's happening now, and it's a genuine competitive advantage.

What this means for founders and investors

If you're building in logistics-adjacent AI, the question to ask is: who owns the feedback loop? If your model improves every time it runs and your competitor's doesn't, time is on your side. If you're just a thin layer on top of an API, you're a feature, not a company.

The physical world is slow to change. That's not a bug, it's a moat for the people who understand it.

Share

If you read this far, the next one is for you.

The thinking behind the decisions, on Tech & AI and everything adjacent to it. No schedule, no filler. You get it before anyone else does.

More on Tech & AI

AI Is the Most Equalising Force Tech Has Ever Seen, Especially for Women

The real story from an AI coding conference is not about robots replacing developers. It is about who finally gets a seat at the table, and why the old gatekeepers are losing their grip.

Claude Is Overhyped. Codex Is Underrated. Here Is What Actually Happened When I Built Real Products With Both.

After shipping multiple products in a dual AI vibe-coding setup, I have a clearer picture of who does what better, and the answer is more interesting than the hype suggests.

Swipe Right on This: Dating Apps and LLMs Are Running the Same Playbook

Dating apps and AI chatbots both cut you off before it gets good, but one is managing infrastructure and the other is managing your dopamine.

Learn the underlying concept

Learn

Send a read-only agent first

One agent spent three hours chasing a build error. A second agent read the migrations against the query code in two minutes and found the real bug. The lesson isn't about which AI is smarter — it's about audit-first workflows.

Learn

Use a working-memory file as the handoff layer between AI coding sessions

AI coding agents forget everything between sessions. A working-memory.md file kept in the repo solves this — it's the shared brain that survives model switches, overnight gaps, and multi-agent collaboration.

If this resonated, I'd be happy to talk about it.

Find me →
← Back to articles