The quiet operating system underneath Walmart's grocery vans, Grubhub's couriers, and 7-Eleven's late-night runs. If something arrived at your door this week, there is a fair chance Nash decided how.
It is 7:42 a.m. in a Walmart fulfillment hub somewhere in Texas. A van is loaded with 92 stops. Two drivers called in sick. A storm rolled in over Dallas. Nobody at the store is panicking, because a piece of software named Nash is already rerouting, reassigning, and writing the apology texts before anyone has finished their coffee.
This is the dull part of e-commerce most people never see. It is also the part that breaks the most. Nash exists because last-mile delivery - the final, expensive, human-shaped step between warehouse and welcome mat - is the one section of the supply chain that still runs on duct tape and dispatcher heroics.
Nash's pitch is almost suspiciously simple: one platform, every carrier, every fleet, every exception, all visible at once. The kind of thing that sounds obvious until you ask why nobody had built it.
In 2021, retail's biggest names were sprinting into on-demand delivery and discovering an awkward truth: their stack ended at the curb. They had inventory systems, payment systems, customer apps. They did not have a way to decide whether a particular taco should ride with DoorDash, Uber Direct, a regional 3PL, or the store's own driver - and then prove it actually arrived.
Most teams solved this by hiring more people. Dispatchers. Ops analysts. A spreadsheet with a sticky note that said "do not delete." It worked at small scale, and only at small scale.
Mahmoud Ghulman and Aziz Alghunaim - both MIT, both repeat founders, one ex-Palantir - looked at the mess and saw an infrastructure gap, not a staffing problem. The thing missing was not more dispatchers. It was an orchestration layer.
The shorthand the founders kept using - Stripe of delivery - was less a metaphor and more a job description. Stripe took a fragmented set of payment processors and hid them behind a single, sensible API. Nash would do the same for couriers.
It is the kind of bet that sounds boring at a dinner party and brilliant in a board meeting. Y Combinator agreed. So did Andreessen Horowitz, which led a $20 million Series A in mid-2022. Total raised, including the seed: $27.8M.
There is a small, useful irony here. The two founders were betting that the wildly chaotic, weather-dependent, hourly-shift world of physical delivery could be tamed by clean code. The market mostly said: prove it.
Nash is best understood as four products doing one job. Integrate an order. Pick a carrier. Survive the carrier. Tell the customer what is happening.
Integrates any order source. Manages dispatch across internal fleets, 3PLs, and Nash's provider network. The dashboard your dispatcher does not need anymore.
A small fleet of agentic AI workers - Dispatch, Support, Analyze - tuned on logistics data. They route, reassign, and answer the 2 a.m. emails.
Over 1,000 delivery providers in 15+ countries, reachable through one integration. Pre-vetted, pre-priced, pre-plugged-in.
Branded tracking links, ETA predictions, multi-channel customer updates. Boring in the best way.
The pitch is one thing. The receipts are another. Nash now powers millions of deliveries across 15+ countries, with enterprise customers running enough volume that the company's plumbing is, effectively, public infrastructure for retail.
Nash's internal phrase for the long game is autonomic logistics - delivery operations that run themselves the way your nervous system handles breathing. You stop noticing them. They do not stop working.
It is a confident framing. It is also testable. If the Walmart hub in Texas still needs a dispatcher at 7:42 a.m. ten years from now, Nash will have missed. If it does not, Nash will have won, and most people will not realize a company called Nash existed.
That second outcome is, oddly, the goal. Plumbing companies do not become household names. They become indispensable.
The next decade of commerce assumes same-day, same-hour, or get-it-now delivery is table stakes. That assumption sits on top of a brittle, balkanized stack of carriers, drivers, and regional 3PLs that were never built to talk to each other. Somebody has to be the translator.
Nash is making a bet that the translator should be one platform, with one API, with one set of AI agents fluent in the language of dispatch. It is a less glamorous bet than autonomous trucks or delivery drones. It is also closer to working.
Back to the Walmart hub. It is 8:14 a.m. now. The Texas storm shifted. Two drivers are back. The van left the dock with 91 stops instead of 92 - one customer got a rerouted ETA, a small refund, and a text that said sorry. Nobody at the store wrote that text. Nobody at the store will write the next one either. That is the part that is new. That is the part Nash sells.