Home / Execution layer / For brokers

AI execution layer for freight brokers

AI execution layer for freight brokers is the work above the TMS you already run. FreightScout builds, covers, tracks, and bills on top of McLeod, Aljex, or Tai, and writes back. The TMS stays the system of record. It is not a TMS and it is not a load board. A dashboard that waits for a human to type is not an execution layer. This one does the work.

See the hub for the work above your TMS. Meet the coworkers that run the jobs. Read how this sits on the TMS you keep. Plans are on the pricing page.

What it does

1. Win and price. Spot and contract quotes are priced off your own lane cost history and current buy rates. The reply is drafted and the quote is logged. An RFP comes back in the customer's template, matched to your own cost and service history. Won lanes flow into execution.
2. Move. The tender becomes a load. The carrier is vetted, contacted, and booked to your max pay. Check calls run at pickup, transit, and delivery. A fall-off is re-covered. The dispatch gate call happens before the pickup address goes out.
3. Bill. POD in, invoice out, carrier payable created, exceptions caught before they age, payment chased. A detention claim is drafted from the POD and the in and out times, with no invented amount.
4. Keep. An at-risk score comes from tender volume against baseline, comms cadence, margin erosion, and slow-pay. The save note is drafted to the right contact before the RFP goes out.

Each step writes back to McLeod, Aljex, or Tai. The layer does not keep a private copy of the load and hope somebody syncs it.

What stays with your people

Build, Cover, Track, and Bill are all live and supervised by default, including invoicing and collections. Your people still own the account, the exception, and any call you would not hand off. Booking the carrier and shipper outreach run supervised by default. A broker can switch either one to autopilot whenever they want, per team and per action. Every action is logged and reversible. The execution layer does the repeatable motion. Your people still own the account and the judgment.

What it doesn't do

FreightScout is not a TMS and it is not a load board. It is not a broker and it is not a carrier. FreightScout does not replace DAT, Highway, Truckstop, or your accounting system. It does not invent a rate or a detention amount. A number over your max pay goes to a person. It is not a screen of charts that still needs a person to place the call, key the tender, and chase the POD.

Related

See the execution layer, how check calls come off the floor, AI on your TMS, and pricing.

Questions people actually ask

What is an AI execution layer for freight brokers?

It is the operational work above the TMS you already run. FreightScout builds, covers, tracks, and bills on McLeod, Aljex, or Tai, and writes back. The TMS stays the system of record. It is not a TMS and it is not a load board.

How is this different from a dashboard?

A dashboard waits for a person to type. An execution layer places the call, keys the tender, books to your max pay, and chases the POD, then writes the result to the load.

What stays supervised?

Build, Cover, Track, and Bill are all live and supervised by default, including invoicing and collections. Booking and shipper outreach can be switched to autopilot whenever you want. Every action is logged and reversible.

Where does the load live?

In your TMS. FreightScout does not become a second system of record. McLeod, Aljex, or Tai stays the record, and FreightScout writes back.