First Meter Intelligence

Autonomous delivery is a coordination problem.

The intelligence layer that runs drones, AVs, robots, and couriers as one operation.

The first meter

The first meter is the new last mile.

Autonomous delivery has revealed something nobody planned for: the first meter.

How a package gets from inside the kitchen, the store, or the DC to the drone pad, the AV bay, the robot dock. Who carries it. When. Where it gets staged.

What happens when the merchant is mid-rush and nobody notices the vehicle has arrived. Nash is built for the coordination work this creates.

Learn more about the Nash Platform
Two delivery drones flying over an urban skyline
The first meter is in the air now.
Sidewalk delivery robots crossing an intersection
And rovers are on many city streets.

One engine

Delivery is moving multi-modal.

Drones, drivers, robots, AVs, all operating simultaneously for the same merchants and the same customers. Every new mode multiplies the coordination surface.

Nash treats every mode as part of one capacity pool, evaluated in the same engine against the rules that govern your business.

Drone 0.94
Cost$0.42
ETA3:12
AV 0.97
Cost$0.38
ETA4:01
Robot 0.89
Cost$0.21
ETA6:48
Own fleet 0.91
Cost$0.55
ETA3:48
Gig 0.86
Cost$0.49
ETA4:22
Scored on cost, reliability, eligibility, and your rules

The handoff

Coordinate the handoff, not just the vehicle.

A drone arriving at a rooftop pad. An AV pulling up to the curb bay. A robot waiting at the dock. Each one needs the package staged, the right person at the right time, the handoff verified.

Nash coordinates the merchant-side action against the vehicle's arrival. The handoff lives in the SLA, with timestamps both sides can see.

Stage

Merchant POS · 4:16:08 PM

"Drone is 2 minutes out. Stage order #1247 at pad 2. Confirm when loaded."

Surfaced via POS, operator portal, or MCP call to whatever runs the kitchen

Confirm

Confirmation · 4:18:24 PM

Order #1247 loaded. Pad 2 cleared. SLA met by 1:36.

Confirmation flows back into the dispatch decision in real time

Dispatch

Released · 4:18:32 PM

Liftoff. Window held. ETA to drop point 9:48 PM.

Handoff lives in the SLA with timestamps both sides can see

Failover

When one mode taps out, the next picks up.

A drone that cannot fly today because of weather. An order too heavy for the drone fleet, too small for a van. A robot whose battery dropped below the threshold for its return leg.

Nash treats the modes as a stack. Mode 1 disqualifies, mode 2 picks up the job before a dispatcher has to ask. Internal fleet first, autonomous next, gig as the elastic safety net, or any priority order you configure.

The customer never sees the swap.

01 Drone Standing by
02 AV Disqualified curb bay blocked
03 Own fleet Active · promoted picked up the job
04 Gig Standing by elastic safety net

Energy

Energy is a constraint, not a cost line.

For autonomous modes, energy is a hard physical constraint that bounds every dispatch decision.

Battery state, range envelope, payload weight, weather, charge windows, regulatory operating envelopes: Nash holds each one as a real input.

Every trip needs enough battery for the return leg. Jobs that cannot complete inside the envelope never enter the queue.

Live envelope · 3 of 6 assets eligible for next dispatch window
Drone A1drone
Battery78%
Range4.2km
Payload1.8kg
WeatherOK
Eligible
Drone A2drone
Battery31%
Range1.6km
Payload1.8kg
WeatherOK
Out · insufficient return
AV B1av
Battery92%
Range34km
Payload40kg
WeatherOK
Eligible
Robot C1robot
Battery14%
Range0.8km
Payload10kg
Window16:42
Charging
Drone A3drone
Battery64%
Range3.4km
Payload1.2kg
WeatherOK
Eligible
AV B2av
Battery48%
Range16km
Payload40kg
WeatherWind 22mph
Out · weather window

Drop point

Verified Drop Points.

Today, accepting a drone delivery means physically pre-approving your address, individually, for every operator that wants to serve you. Customers will not pre-approve their backyard twenty times for twenty drone providers.

Nash holds the verified drop point once, in the Context Fabric. Every operator authorized to deliver to that address inherits the location, the access notes, the safety clearance, the homeowner instructions.

Verified drop point · held in Context Fabric 1247 Maple St · back garden pad Homeowner approval Safety clearance Access notes Geofence
Registered once
Inherited by every operator authorized to serve this address
Air AtlasDrone
SkylaneDrone
FlyPathDrone
Cruise FMAV
NuroAV
Curb CoAV
WalkbotRobot
SidewalkRobot

Sequence

There is no parking lot in the sky.

A drone cannot queue. Battery burns whether it's flying or hovering, so any wait time has a real cost.

Nash sequences pickups across the modes a single merchant is serving, so the drone arrives when the order is staged, the AV pulls up when the bay is clear, and the courier slots into the open gap.

Vehicles arrive in sequence and none waits longer than the staging window allows.

4:154:164:174:184:19 4:204:214:224:234:24
Drone
Pad 2 · #1247
AV
Curb bay · #1251
Courier
Side door · #1248
Sequenced across modes for one merchant None waits longer than the staging window allows

Simulate

Simulate the mix before you commit.

Before you sign the drone operator contract, before you fund a robot pilot, before you scale the AV deployment from one zip code to fifty, run the mix in simulation.

Nash evaluates scenarios against the variables that actually decide success: which orders qualify for which mode, what the battery envelope allows, what the weather curve looks like across a year, what the cost-to-serve is per mode at scale, and what the fallback profile holds when conditions turn.

Drone-heavy

Completion94.2%
On-time96.1%
$/drop$3.84
Util71%
Run again

Balanced mix

Completion97.4%
On-time96.8%
$/drop$4.12
Util83%
Chosen · ship Tue

AV-led + gig

Completion96.1%
On-time94.7%
$/drop$4.48
Util78%
Run again

Autonomy runs on Nash.

Talk to Nash