NxDlvry

The delivery day, written down.

NxDlvry runs routes, drivers, proof of delivery, tracking and invoicing for small delivery companies and 3PLs. Tell the assistant what you need. It proposes; you approve; the record shows exactly what happened.

Book a call See how it works

Built and run by one person. You talk to him, not a sales team.

How it works

It proposes. You approve.
The record keeps score.

The assistant has no private write path. It goes through the same doors your staff do, and by default it waits for you, so every action it takes becomes an ordinary, attributed line you can go and read.

01 · You said

“Ramirez can’t take the couch today — push it to tomorrow’s Riverside run.”

Proposedschedule_order
Order#4471
Moving toRIV-2 · Tue 08:00
02 · Awaiting you

Nothing has been written. The order is still on today’s run until you say so.

Pending action#318
Requested byAssistant
ApproverOwner or dispatcher
03 · Written

Order #4471 now sits on RIV-2, and this is what your audit log holds.

14:22:07order.updated
ActorAssistant → J. Adeva
Visible onorder, route, activity feed
Example data, not a real customer
The NxDlvry assistant. An operator asks it to mark order SO-4102 delivered and text the customer on SO-4103 a tracking link. The assistant replies that it has proposed both and asks for approval, and two proposed actions appear below with Approve and Reject buttons.
The assistant proposes, and stops — example data, not a real customer
The pending approvals inbox. Two entries, send_customer_sms and mark_delivered, each labelled with the model that proposed it and a timestamp, each with Approve and Reject buttons.
Every proposal waits here, with the model that made it — example data
What it does

One system, order to invoice

Built for operations measured in trucks, not in warehouses.

Live map

Routes & dispatch

Build multi-stop routes, assign drivers and vehicles, and watch the day move.

14 tools

The assistant

Ask for the change in plain words. It proposes, you approve, the record shows who did what.

Not yet in stores

Driver app

Today’s route, stop by stop, on the driver’s phone. Tap to call, tap to navigate, mark it done.

Photo per stop

Proof of delivery

Require a photo before a stop can be completed. Turn it on per company.

No account needed

Customer tracking

A private link per order showing live status. Nothing for your customer to install.

Rate cards

Orders & invoicing

Orders, items and customers through to a PDF invoice you can email from the app.

A route in progress

The day, as the board sees it

Stops in order, the driver’s GPS arrival stamped on each one as they reach it, and the same record behind every change, whether a driver made it, you made it, or the assistant proposed it and you approved.

Route detail for route RIV-1, in progress, with Marcus Bell driving and vehicle Box 12 assigned. A dark map plots five numbered stops across Riverside with the driver's live position. Below it the five stops are listed with addresses, customer names and order references, each showing the driver's GPS arrival time and its status: the first two delivered, the third marked arrived.
One route, mid-run — example data, not a real customer
The live dispatch map, noting that it updates every 15 seconds. A card shows Marcus Bell on route RIV-1 with two of five stops done, last seen seven minutes ago and currently at stop 3. His marker sits on the map over Riverside.
The whole fleet, refreshing every 15 seconds — example data
In numbers

What the software actually is

No customer counts or growth charts — NxDlvry is pre-launch and doesn’t have them. These are facts about how it is built.

0

Private write paths for the assistant. It calls the same services the interface does.

14

Tools it can call, from scheduling an order to filing a damage claim.

15s

Refresh on the live dispatch map while a route is running.

1–3

Texts a customer gets per delivery order, if they opted in.

100m

Geofence radius that marks a driver as arrived at a stop.

Every

Change carries an actor and commits with its audit row in one transaction.

Text notifications

Delivery texts, with consent

Businesses using NxDlvry can offer their customers delivery status updates by SMS. When a customer agrees, they receive a tracking link and delivery status updates for their order — typically 1–3 messages per delivery order.

  • Customers opt in verbally, in person or by phone, when placing a delivery order with a business that uses NxDlvry. Consent is never a condition of purchase.
  • Message and data rates may apply.
  • Reply STOP at any time to opt out, or HELP for help.

The complete opt-in workflow, including a screenshot of the consent screen, is documented at app.nxdlvry.com/sms-opt-in. See our Privacy Policy and SMS Terms. Mobile information is never shared with third parties or affiliates for marketing or promotional purposes.

Get in touch

Let’s talk about
your operation

NxDlvry is new, and it is built by one person who wants a handful of real delivery operations to shape it. That means no sales process, no seat minimum, and direct access to the person writing the software.

Who it suitsSmall fleets

Furniture, appliance, building-material and medical-equipment delivery, and 3PLs running deliveries for clients.

What you getA conversation

A walkthrough of the real software against your actual delivery day, not a slide deck.

PricingNot published

NxDlvry is pre-launch and pricing isn’t set. Rather than invent a number for this page, we’ll talk about it on the call.

This form needs JavaScript. Email contact@adevious.com instead and it reaches the same person.

Goes straight to the person who builds it. Or email contact@adevious.com.