Optimal Dynamics AI review (Oct 2026): agentic automation for truckload carrier planning and dispatch

What this Optimal Dynamics AI page covers

This page is for a planning lead, dispatch manager, or operations leader at an asset-based truckload carrier or private fleet. It answers: what Optimal Dynamics automates, which load and dispatch decisions it can make without a person, how to compare it with your planners before you trust it, and what Optimal Dynamics publishes about price.

Optimal Dynamics’ home page (read 17 October 2026) groups the product into Plan (Network Simulation, Bid Analysis), Scale (Network Management), and Execute (Dispatch Management), all on one decision engine. Its agentic automation page says Atlas can act “automatically accepting freight that meets specific profit thresholds”, and its decision automation page calls the platform Level 4 “conditional automation … with minimal need for human oversight” on its own five-level scale. Scale was announced on 2 March 2026.

Ground rules: a named planning lead sets the profit thresholds, lane limits, and protected customer commitments, and decides when auto-accept goes on; dispatchers review and assign every driver-to-load recommendation; driver hours-of-service and home time stay the dispatcher’s responsibility. Rate confirmations, customer contracts, and driver details stay out of outside chat tools, and Optimal Dynamics’ figures are its claims, not our measurement.

Major features (with how someone uses them)

Examples at a glance: each feature has a concrete example from a real job plus a short Try this you can run this week.

1. Load acceptance suggestions versus your planners (primary)

What it is: Optimal Dynamics plans freight over three horizons: strategic (a month to a year out), tactical (1–15 days, including “advanced load acceptance”), and real time (under 24 hours) (decision automation page). It uses machine-learning forecasts that give a range of likely loads rather than one number, plus reinforcement learning to value where a driver ends up after a load. The agentic layer can accept or reject freight automatically against profit thresholds you set (Atlas page).

Automatic acceptance is the decision with the biggest downside, because a wrong yes strands a truck and a wrong no loses a customer. Run the suggestions next to your planners before any switch goes on.

Concrete example (planning lead at a 250-truck dry-van carrier) For one week a planning lead logs every load the system would have accepted or rejected next to what her planners actually did. They agree on 82 of 96 loads. Of the 14 disagreements, nine favour the system (planners took short hauls into weak markets), three favour the planners (a customer the system does not know is strategic), and two are data errors from an unsynced TMS field. She fixes the field and adds the customer to the commitments list before turning on auto-accept for one region.

Try this

Primary workflow:

Compare Optimal Dynamics' load-acceptance suggestions with your planners' choices for one week. Have the planning lead review every disagreement before turning on automation.

2. Scale: agents that bid for and book freight

What it is: Scale, launched on 2 March 2026, is described as an “always-on, autonomous agentic workforce” that searches, bids, negotiates, and procures freight across load boards, email, EDI, and direct shipper channels. The Network Management page lists “auto accept or reject network-aware freight” and says secured loads flow straight into dispatch decisions in Execute. Customer quotes in the launch release are about what carriers “expect” Scale to do.

Agents that negotiate rates on your behalf need written limits. The planning lead owns the profit threshold, the lanes, and the customers Scale may not touch.

Concrete example (pricing manager at a regional flatbed carrier) Before Scale bids on its own, a pricing manager writes a one-page rule set: minimum rate per loaded mile by region, no bids into two lanes the sales team is renegotiating, and no auto-accept on loads above 600 miles. For two weeks she reviews every load Scale accepted or declined; she tightens one regional floor after three accepted loads came in below what her team would have taken.

Try this

Limits first:

Before Scale's agents bid or negotiate on their own, have the planning lead write the profit threshold and lane limits for auto-accept. Review every load Scale accepted or declined for two weeks.

3. Execute: driver-to-load recommendations

What it is: Optimal Dynamics’ Dispatch Management page lists ranked driver and load recommendations, automated driver-to-load assignment, dynamic tour building, and spot-freight sourcing across load boards, email, and private customer boards, and says “driver preferences and HOS taken into account”. Its own summary is “Simply review and assign, and done.” The home page says recommendations factor in hours of service, home time, and location.

The software can weigh hours and home time, but the dispatcher still answers to the driver. Check the first week of recommendations against what drivers were promised.

Concrete example (dispatch manager at a dedicated-fleet carrier) A dispatch manager runs Execute for one terminal for a week. Most recommendations match what she would have picked. Two would have sent a driver out the day before a promised home weekend, which the system did not know about because the request lived in a text thread. She moves home-time requests into the TMS field the integration reads before widening to a second terminal.

Try this

Check the driver side:

Run Optimal Dynamics' dispatch recommendations for one terminal for a week. Have the dispatcher check every assignment against driver hours, home time, and stated preferences before assigning.

4. Atlas explanations: why a load was rejected

What it is: Optimal Dynamics’ agentic automation page describes four parts of Atlas. The first, Explain, translates the optimization logic into plain-English “decision stories” so users understand “why a load was rejected, a driver was selected, or a plan changed”. The others cover setup and testing of new models for each customer, learning driver preferences, customer priorities, and lane sensitivities, and connecting decisions to execution systems.

An explanation is only useful if your planners can disagree with it. Read the stories for loads the system turned down, because those are the decisions nobody else sees.

Concrete example (planning lead at a 400-truck reefer carrier) A planning lead reads the explanations for ten loads the system rejected last week. Seven make sense (deadhead into a weak market). Two cite a lane preference the team dropped in the spring, and one ignores a customer the sales team has promised to protect. She sends the three to Optimal Dynamics as setting fixes and adds the protected customer to the commitments list.

Try this

Read the reasons:

Pick ten loads the system rejected and read the plain-English explanation for each. Have the planning lead mark any reason that does not match what your team knows about the customer or lane.

5. Plan: Bid Analysis and Network Simulation

What it is: The Bid Analysis page says it identifies the lanes and volumes worth bidding on for your network and simulates each bid’s effect on profit, coverage, and service before you answer an RFP. Network Simulation models scenarios — such as adding trucks or a new customer — in a digital twin “before executing a single change”. Both run on the same engine as dispatch.

A simulated bid is a forecast. The pricing lead compares it with the team’s own picks and signs off before anything goes to a shipper.

Concrete example (pricing lead at a 150-truck carrier) A pricing lead runs one shipper RFP of 60 lanes through Bid Analysis. It recommends 18; her team had picked 22. They agree on 15. She keeps two of the team’s extra lanes because they feed a dedicated account, drops five, and records why before the bid goes out.

Try this

Compare before you bid:

Run one RFP through Bid Analysis. Have the pricing lead compare its recommended lanes with the team's own picks and sign off before any bid is sent.

6. Proof-of-Value, integrations, and what you need to provide

What it is: Optimal Dynamics’ Proof-of-Value process takes three months of your historical TMS and ELD data, calibrates the engine to your runs and driver types, and simulates how the platform would have decided, with results “in just weeks”. Its integrations page calls it a decision layer on top of your existing systems with two-way TMS and ELD integrations and an API; the logos shown include McLeod, Trimble, Samsara, Motive, and Geotab (see our Motive AI and Geotab AI reviews).

A simulation on your own history is the cheapest test you will get. Check a handful of its “would have” decisions against what really happened on those days.

Concrete example (VP of operations at a temperature-controlled carrier) A VP of operations sends three months of TMS and ELD data for the Proof-of-Value. The results show more loaded miles per truck. Before the contract, his planning lead checks five simulated days: on one, the simulation sent a truck to a shipper that was closed for a holiday. Optimal Dynamics adds the closure calendar to the inputs and reruns that week.

Try this

Test on your history:

Before signing, run the Proof-of-Value on three months of your TMS and ELD data. Have the planning lead check five simulated decisions against what actually happened on those days.

Pricing context (October 2026)

Optimal Dynamics does not publish prices; optimaldynamics.com/pricing returns a 404 page, and the site offers demo requests and a Proof-of-Value on your own data. Pricing is quote-only as of 17 Oct 2026.

Ask which of Plan, Scale, and Execute are in the quote, whether Scale’s agents are priced by truck, by load, or as a flat fee, what the Proof-of-Value costs and how long it takes, and which TMS and ELD integrations are included.

Uncertainty: Optimal Dynamics’ 14 April 2026 results release lists Scale among its fiscal 2025 milestones, while the Scale launch release is dated 2 March 2026; we use the March date. The platform calls itself Level 4 automation with “minimal need for human oversight” and lists auto-accept or reject, while the dispatch page says “review and assign” — we treat automatic acceptance as a setting the planning lead switches on. Scale customer quotes describe what carriers expect, not measured results. We could not confirm which Atlas capabilities each customer gets, and the integration list is taken from logos. Figures such as 80% of fleet managers moved off routine planning, 12.5% and “nearly 20%” more weekly revenue per truck, Ploger’s 14.6% revenue per mile, and Leonard’s Express’s 45% fewer brokerage-booked loads are Optimal Dynamics’ and its customers’ claims, not our measurement.

When it’s useful (honest take)

Useful when you run an asset-based truckload fleet with enough volume that planners spend their day on load acceptance and driver assignment, your TMS and ELD data are clean, and a planning lead will own the thresholds and review disagreements.

Less useful when you are a broker covering loads with outside carriers (Parade AI, HappyRobot AI), a shipper choosing a TMS (Shipwell AI), or a last-mile operation planning many small stops (Locus AI).

Related options (educational)

FAQ

What is Optimal Dynamics Atlas?

Atlas is Optimal Dynamics’ agentic automation layer. It explains decisions in plain English, learns driver and customer preferences, and connects the optimization engine to execution — for example accepting freight that meets a profit threshold.

What is Optimal Dynamics Scale?

Scale, announced 2 March 2026, is a set of agents that search, bid, negotiate, and procure freight across load boards, email, EDI, and direct channels, and can auto-accept or reject loads based on what the network needs.

How much does Optimal Dynamics cost in October 2026?

Optimal Dynamics does not publish prices; its pricing URL returns a 404 and the site offers demos and a Proof-of-Value. Treat it as quote-only.

Does Optimal Dynamics account for hours of service?

Optimal Dynamics says dispatch recommendations take driver preferences and hours of service into account. Dispatchers still review and assign, and hours rules remain the carrier’s responsibility.

Who should approve what Optimal Dynamics does?

A planning lead sets profit thresholds, lane limits, and protected customers and decides when auto-accept goes on; dispatchers review every driver assignment; the pricing lead signs off on bids.

Optional next step (if seats overlap)

If you pay for a TMS, a telematics platform, load boards, a decision engine, and chat seats your planners use to think through loads, that overlap is worth mapping. Map the overlap with the $19 AI toolkit audit or the $9 AI toolkit spreadsheet. Email Audit $19 or Toolkit spreadsheet $9.

Checkout is live via Stripe. After you pay, we email delivery (spreadsheet) or intake next steps (audit).

Related: Descartes AI · ShipBob AI · Locus AI · project44 AI · FourKites AI · Flexport AI · Manhattan Active AI · Blue Yonder AI · Kinaxis AI · o9 Solutions AI · project44 vs FourKites · Uber Freight AI · HappyRobot AI · Parade AI · Blue Yonder vs Manhattan · Loadsmart AI · Shipwell AI · Samsara AI · Motive AI · Cin7 AI · AfterShip AI · Stack map for ecommerce ops · Claude · Three checks before another AI seat · How-to: Write one Optimal Dynamics load auto-accept rule, and have dispatchers review every assignment · ops hub