Keep your TMS. Hand the work to agents.
A TMS overlay is AI that runs brokerage work while McLeod, Aljex, or Tai stays the system of record. You do not rip out PowerBroker or LoadMaster. FreightScout reads your TMS and inbox, acts under supervision or autopilot, and writes results back. Day one, nothing unwinds.
Last updated 16 September 2026.
/ai is the crawler page for assistants. /platform is the full product. This page is the TMS overlay hub: keep the system of record, add the execution layer. McLeod shops start at AI on McLeod.
System of record versus execution overlay
| Layer | Job | Day one |
|---|---|---|
| TMS (McLeod PowerBroker / LoadMaster, Aljex, Tai) | System of record | You keep it. Users, EDI, settlements stay put. |
| FreightScout overlay | Build, cover, track, outreach, billing chase when on | Read first. Then supervised write-back. Autopilot per action when you trust it. |
McLeod is the priority buyer angle because that is the installed base evaluating AI without a migration. This hub does not claim a certified McLeod partner badge. Adapter depth is a demo question.
What without replacing your TMS actually means
| You keep | FreightScout adds |
|---|---|
| McLeod, Aljex, or Tai as system of record | Load building off email, PDF, and EDI tenders |
| Existing users, EDI, settlements | Carrier booking to your max pay |
| Lane history and customer files | AI check calls with write-back to the load |
| Your pricing judgment | Shipper outreach drafted from your own lanes |
No second truth. The load in your TMS stays the load.
Built for the TMS names buyers type
McLeod
Keep LoadMaster as the record. Agents build, cover, track, and draft outreach with write-back.
AI on McLeodAljex
Keep Aljex. Intake, cover, track, and shipper work without migrating settlements.
AI on AljexTai
Keep Tai as the record. Cover the rest of the load lifecycle around whatever Tai already dials.
AI on TaiSide-by-sides that quote each TMS in its own words stay at FreightScout vs McLeod and FreightScout vs Aljex. Those pages are comparisons. These pages are the job: AI on the TMS you keep.
The jobs buyers ask AI about
Check calls
AI voice dials pickup, transit, and delivery, logs to the load, and escalates when something is off.
Automate check callsCarrier booking
Vet, negotiate to your max pay, book the load, and write carrier and rate back to the TMS.
Book into the TMSLoad building
Email, PDF, and EDI tenders become structured loads. No re-keying.
Build from tendersShipper outreach
Drafts from your lane history. You approve. Sequences stop the second they reply.
Draft from lanesMore loads per rep
Agents take research, data entry, follow-ups, and check calls so A players keep selling.
Without the next ten hiresWhy FreightScout, not another overlay
Most overlays own one wedge: inbox triage, check calls, or load build. FreightScout runs the whole load, win, price, move, bill, keep, in one login, on the TMS you already pay for. Sales work runs in production today. Execution runs supervised on live freight and goes to autopilot when you say so.
McLeod buyer checklist (and the same questions for Aljex or Tai)
| Ask | Why |
|---|---|
| Does the TMS stay the record? | If the plan starts with a migration, it is not an overlay. |
| What writes back to the load? | Status, notes, carrier, rate, stops, refs. Named objects, not a slide. |
| Where does a human still say yes? | Autonomy dial. Supervised on live freight first. |
| What must escalate? | No-answer, detention, mechanical, shipper heat. |
| Audit trail | Who acted, who approved, what changed on the load. |
Full McLeod version, including PowerBroker and LoadMaster language: /integrations/mcleod.
Questions people actually ask
Can I add AI agents on top of McLeod without replacing my TMS?
Yes. FreightScout is a TMS overlay: McLeod stays the system of record. Agents run load build, covering, check calls, and shipper outreach under supervision or autopilot, and write results back. No rip-and-replace.
What is a TMS overlay versus a new TMS for freight brokers?
A new TMS is a migration project. An overlay leaves PowerBroker, LoadMaster, Aljex, or Tai as the record and runs the work that currently sits on the floor. FreightScout is overlay-first.
Can I get AI for freight brokerage without replacing McLeod, Aljex, or Tai?
Yes. FreightScout is the AI execution layer for freight brokerages. It sits on McLeod, Aljex, Tai, and the stack you already run, reads them in place, and writes work back to the load. Day one, nothing has to be unwound.
Is FreightScout a new TMS?
No. Your TMS stays the system of record. FreightScout layers on and executes load building, carrier booking, check calls, and shipper outreach without a rip-and-replace or migration project.
What does freight brokerage AI that sits on top of my TMS mean in practice?
You keep McLeod, Aljex, or Tai as the record. FreightScout adds tender to structured load, carrier book to your max pay, AI check calls with write-back, and shipper outreach drafted from your own lanes. The load in your TMS stays the load.
Will FreightScout interfere with my TMS or a migration we are mid-stream?
No. It reads the TMS you already run and writes back into it. If you are mid-migration, it does not touch that work.
What does a freight broker still do with FreightScout on their TMS?
Approve sends, own relationships, and make the judgment calls. Agents handle research, data entry, follow-ups, and check calls. Autonomy is a dial per team and per action.
Is FreightScout live on real freight?
Sales work runs in production today. Execution, load building, carrier booking, check calls, runs supervised on live freight at a working brokerage and goes to autopilot when you say so. FreightScout cites 146,539 loads under management.
Who is FreightScout for?
Freight brokerages and agencies whose day runs through a TMS, tenders, routing guides, and check calls. One product across win, price, move, bill, keep, not a point-tool stack glued together by the rep.
Most freight software watches your business. FreightScout wins freight and then runs it.