Modules enabled
Start with the one chore that costs the most hours — usually import tracing — and add modules when the desk is ready. Each module is self-contained, so enabling one changes nothing about the others.
Pricing
One price per desk. No per-user fees.
Priced per deployment, by the modules you enable and the scheduled volume you run. Quoted after a thirty-minute call on your own lanes.
Per deployment
from$1,500/ month
Plus a one-time onboarding fee scoped in the demo. Quoted for your modules and your volume after a thirty-minute call.
Third-party services — CAPTCHA solving, AI document reading, Motive — run on your own accounts and keys, entered once in the setup workbook. Neo adds no margin on them.
What every deployment includes
- The operations dashboard for your whole dispatch desk — operators and admins, no per-seat charge
- The authenticated API for your TMS, with per-client credentials
- Every carrier handler that is live for the modules you enable, and the ones added later
- Scheduled runs on the Central-Time clock with change-gated email and in-app notifications
- The request → execution → response audit trail with portal captures
- Seventeen in-app operator manuals and the admin configuration pages
- The Motive fleet mirrors (geofences, drivers, vehicles)
- Every release, with migrations applied on start and rollback to the previous tag
How the price scales
Two dials, both in your hands.
Scheduled run volume
Watchlists, timed bookings and digests are the work Neo does while nobody is asking. The number of scheduled runs a month sets the tier, not the number of people who look at the results.
One-time onboarding
Scoped in the demo and quoted with the deployment. It covers the setup workbook (company profile, users, service keys, portal credentials and tariff rules), the Motive scoping for the fleet modules, and a parser format for each delivery-order layout your customers send.
What you host
Neo runs as one Docker image on a VM you own, with its database, Redis, an HTTPS proxy and a backup sidecar from one compose file. Nothing is installed on the host but Docker.
- Minimum
- 2 vCPU · 4 GB RAM · 30 GB SSD
- Recommended
- 4 vCPU · 8 GB RAM · 80 GB SSD
- OS
- Ubuntu 24.04, x86_64
ROI calculator
What would it save your desk?
Your dispatchers, your hours, your incidents. The result is an estimate with your inputs; the only number Neo supplies is its own from price.
Estimate, per month
- Dispatcher hours returned to the desk
- 92 h
- Dispatcher time, in dollars
- $2,625
- Demurrage and per-diem avoided
- $735
- Net of the from price ($1,500 / month)
- +$1,860
of 132 h spent on portals today
$31 per truck per month · break-even at 53 h of dispatcher time
An estimate with your inputs, not a promise. Assumes 22 working days and 8-hour days; the share of work taken over is your assumption and the modules you enable decide it. The only figure Neo supplies is its own from price.
Pricing FAQ
The questions that come before the quote.
Is there a free trial?
No. The demo runs on your own containers, bookings and portals, which is a better test than a sandbox: you see your ETAs, your last free days and your chassis pools before you decide.
Can I start with one module?
Yes. Most desks start with import tracing on a schedule, because that is where the hours go. Every other module can be enabled later without a redeploy of anything but the configuration.
Is there a per-user charge?
No. A deployment serves your whole dispatch desk. Operators see their own requests, admins see everyone's; add as many of either as you like.
What do I pay the railroads, pools and steamship lines?
Nothing new. Neo signs in with the credentials your office already has, under your own authorization, and does the work a dispatcher would do by hand. No portal fees are added.
What happens when a portal changes its pages?
That is covered by the subscription. Carrier handlers are maintained as portals change, and a portal Neo cannot log into shows up in the dashboard's attention feed and in a throttled alert to your ops mailbox until it is fixed.
Who owns the data?
You do. It lives in a database on your VM, backed up daily by a sidecar you can restore from in one line. Nothing is processed outside your deployment except the third-party services you configured.
Get started
Give your dispatchers their day back.
A thirty-minute walkthrough on your own Chicago lanes and carriers. We will show a live trace on one of your ramps, a scheduled watchlist and the dashboard your team would open every morning.