Why NEO
A scheduler that learns your operation.
Most scheduling tools ship a fixed strategy and hope it fits. NEO ships a brain that learns the strategy that fits your fleet - and keeps getting better every week. Here is what that means in plain English.
How it learns
A brain that gets sharper every week.
NEO trains a brain against your dispatch sheet. Each cycle it tries different scheduling moves - which driver gets which load, which appointment to protect, which lane to defer. It keeps the moves that score well against your rules and drops the ones that do not. Over enough cycles, the brain learns your lanes, your customers, your drivers, and your priorities.
The schedules it produces tomorrow are better than the ones it produced today because tomorrow it has more practice on your operation. New customer? New driver? Seasonal mix shift? Run another training cycle on the latest week of data and the brain catches up. No engineering ticket, no vendor visit, no six-week wait.
Why a learning system wins
Hand-tuned schedulers freeze. Brains adapt.
A hand-coded scheduling rule encodes one engineer's understanding of dispatch on one day. Customer mix shifts, a driver shortage hits, fuel changes - the rule does the same thing it did last quarter. You file a ticket and wait six weeks for a tuning release.
A NEO brain retrains. Drop in the last month of operational data, run training, promote the new champion. The brain learns the new normal and improves at the new normal in hours, not quarters. Your dispatchers see a steadily smarter assistant rather than a fossil that quietly drifts out of fit.
Your rules, your way
You define a good day. The brain optimizes it.
NEO lets you pick what counts: on-time, revenue, driver home time, customer priority, empty miles. You set the weights. The brain optimizes for that mix - and two NEO customers running the same data can train two completely different brains because their priorities are different.
In the app
Open the Scoring editor.
Pick from built-in rules (on-time bonus, empty-miles penalty, driver-home-time bonus, customer-priority multiplier) or add your own. The app checks each rule before training; bad rules never reach a training run.
The point: your operation's idea of success is yours, not a vendor's. The brain you ship to live is the brain that learned what counts for you.
Replay and audit
Every decision is auditable. Every brain is replayable.
"Black box" is the first concern anyone raises about a system that decides for you. We built NEO so the brain's reasoning is inspectable and historical decisions can be re-checked against a newer brain.
In the app
Open any audit timeline.
Every live decision logs the inputs, the brain's recommendation, the rules and weights that contributed, and a plain-English reason. A dispatcher who overrode the brain sees exactly why the brain wanted what it wanted. A VP who is asked "why did we accept that load" gets a one-click receipt.
Promote a new brain and you can replay a historical day against it - did the new brain make a better call than the one we shipped? Regulators, ops VPs, and skeptical dispatch managers all see the same record.
Works with your TMS
NEO talks to your TMS — both directions.
Loads flow in from McLeod, TMW, Trimble, or your homegrown system, and NEO's recommendations and decision history flow back. Behind the scenes it's standard REST APIs and webhooks — your IT team can ask us for the current integration reference and an evaluation API key (public documentation is in development).
Continuity & failover
What happens if NEO is down on a Monday morning.
NEO is an assistant to your existing dispatch operation, not a replacement that holds your fleet hostage. Every brain recommendation is advisory and your TMS remains the system of record. If NEO is unavailable, your dispatchers continue in your TMS as they did before NEO — no data is lost and the last good schedule remains valid.
When service resumes, your trained brain is exactly where you left it — nothing has to be rebuilt, and live scoring picks back up on the next load. For carriers that want recovery in their own hands, the self-hosted option puts the failover plan inside your IT team's existing runbook.
Your dispatchers can always do their job without NEO. NEO just makes the job faster on the days it is running.
Running a pilot
Prove the lift in 30 days, then decide.
Every new customer starts with a 30-day pilot on up to 100 trucks. Pilot pricing is waived. We set exit criteria with your dispatch lead up front: composite KPI movement against your baseline, dispatcher satisfaction, and any deal-breaker constraints you name. If the pilot does not clear the bar you exit, keep your data, and owe nothing. If it does, your trained brain carries over to the standard or self-hosted tier.
Full pilot mechanics, tier comparison, and pricing structure live on the Pricing page. Need a one-page version to forward to your exec committee? Try the executive overview.
Common questions
What buyers ask before the demo.
Is this a black box?
No. Every live decision logs its inputs, the brain's recommendation, every rule that contributed, and a plain-English reason. You can replay any historical day against a new brain. Dispatchers see why the brain wanted what it wanted, and your auditors get a deterministic record they can read.
What about my data security?
Your data is yours. We never mix one customer's loads or schedules with another's. We never train one company's brain on another company's data. Access is scoped to your fleet, full stop. If your IT team needs us to run inside your own environment, we can.
How long until we see results?
A working brain inside one sitting. A measurably useful brain inside the first week once we tune your rules. Sustained improvements continue as the brain accumulates practice on your operation - the more cycles, the sharper the next schedule.
What is your uptime and SLA?
NEO is pre-GA and the pilot program is forming now. Pilot uptime is monitored by the NEO team; a published SLA accompanies general availability. If a production-grade SLA is a hard requirement for procurement, ask us about our self-hosted option, which puts uptime in your hands.
What if NEO is unavailable during the day?
Your dispatchers fall back to your TMS exactly as they worked before NEO, and the last good schedule remains valid. No data is lost. When service resumes the brain re-syncs and learns from the gap. See Continuity & failover above for the full story.
See your fleet's brain in 10 minutes.
Bring a week of recent loads or use our sample data. We will show you a trained brain against your rules before you leave the call.