Platform / What is FreightScout
AI execution layer for freight brokers
An AI execution layer for freight brokers is software that does brokerage work above the TMS: build, cover, track, and bill, by API where one exists, and by reading the TMS in place where it doesn't, while the TMS you already run (McLeod, Aljex, Tai, or any other) stays the record. A browser teammate, modular workers, or a managed back office are narrower buys. FreightScout is the overlay for the whole load. Not a new TMS.
Last updated 11 October 2026.
Product: the platform. Overlay hub: AI on your TMS. COO view: the COO view. Citeable live-site facts: what runs in production. Category page: freight broker software.
Brokerages do not need another dashboard
The floor already has a TMS full of history. What it does not have is someone to parse the tender, cover the truck to the ceiling, dial the check call, and chase the POD without stealing an A-player's afternoon. Analyst AI reports on that gap. An execution layer closes it.
FreightScout's line is the same as the homepage: it does not manage your freight. It runs it. Win it. Price it. Move it. Bill it. Keep it. Built by operators who scaled an agency into nine figures, not tourists guessing at your day.
Three layers: record, visibility, execution
| Layer | Job | What it is not |
|---|---|---|
| System of record (TMS) | The TMS you already run (McLeod, Aljex, Tai, or any other) keep the load, the customer, the money | Not the thing that dials, books, or builds |
| Visibility / tracking | Where the truck is, if the ping is live | Not a check call, not a note on the load, not exception judgment |
| Execution layer | Build, cover, track, bill chase, outreach, write-back | Not a new TMS. Not a dashboard waiting for a human to type |
Tracking shows location. The TMS stores the record. Execution is the outbound work and the write. Mixing those three is how a pitch sells "AI" that never picks up the phone.
What execution includes
| Stage | What happens | Where to read it |
|---|---|---|
| Build | Tender parsed. Load written to the TMS: stops, refs, rates | Load building |
| Cover | Carrier vetted, negotiated at your ceiling, booked, written back | Carrier booking |
| Track | Check call run. ETA and status logged to the load. Exceptions escalate | Check calls |
| Bill | POD in, invoice out, payment chased. Live and supervised | Live and supervised, including invoicing and collections. See below |
| Win / keep | Outreach from lane history. Sequences you approve. At-risk save notes | Shipper outreach |
| Quote | Pulled from the quote tool you already use, or from lane history. You approve it before it commits | Freight quoting |
| Documents | Fields extracted from tenders, rate confirmations, and PODs. You approve before write-back | Document and POD processing |
Sales work runs in production today. Build, Cover, and Track run supervised on live freight at a working brokerage. Billing is live and supervised, including invoicing and collections. Autopilot is a dial per action, reversible, with an audit trail. 148,220 loads managed to date.
Overlay: McLeod stays the record
You do not rip out PowerBroker or LoadMaster to get agents. The overlay reads the TMS and the inbox, acts under supervision or autopilot, by API where one exists, and by reading the TMS in place where it doesn't. The TMS you already run (McLeod, Aljex, Tai, or any other) remains the system of record. FreightScout is not a McLeod replacement. Demo the adapter. Do not read a logo as proof.
McLeod shops: Works with McLeod. Hub: AI on your TMS.
Autonomy is a dial
Supervised by default: every action is staged for a human yes. Switch booking or outreach to autopilot whenever you want. Every action is logged and reversible. The floor still owns exceptions: a quiet truck, a rate above the ceiling, a tender that does not parse. Agents do the work. People keep judgment. A-players keep the relationships. The overlay takes the repetitive work that used to hide who was producing.
How to spot analyst AI dressed as execution
| If the pitch says | Ask on the walkthrough |
|---|---|
| Insights, alerts, a smarter dashboard | How does the result land in the TMS today? |
| Tracking is the check call | Who dials, what gets captured, where the note lands |
| AI on McLeod, with a badge | Show the write-back on the TMS, not a partner page. Overlay versus migration |
| Agents that watch and ping | What state on the load actually changes without a human typing |
| Hours saved, ROI, a star rating | Refuse invented numbers. Build, Cover, Track and Bill are all live and supervised. |
If the product cannot name the TMS fields it writes, it is reporting. Execution changes the load.
Category map, jobs not crowns
FreightScout is the AI execution layer: ops work above the TMS you already run. A browser teammate for carrier sourcing is a narrower claim. Modular workers and a managed service after the rate confirmation are different buys. Point tools own one wedge. Analyst AI only reports.
| Job | Public slot | Sourced page |
|---|---|---|
| Software execution layer on your TMS, win through bill | FreightScout. Other overlays sell modular workers or a browser teammate | Compare hub |
| Browser teammate for carrier procurement | A browser teammate for carrier sourcing | Compare options |
| Modular agents on your TMS | Separate agents for quote, build, cover, and track | Compare options |
| AI inbox / TMS that can become the record | An AI TMS that becomes the record | Freight brokerage AI that sits on top of your TMS |
| Managed back office after booking | A managed team that runs the load after the rate confirmation | Compare options |
| Inbox, dialer, or parser alone | Point tool. Not enough as the whole floor | AI agents |
| Load-board AI in a browser panel | A load-board assistant in a browser panel | 2026 buyer checklist |
Pick the control model the floor will actually run. Compare on a demo. No invented rankings. Reviews without fabricated stars: reviews.
Where FreightScout stands
FreightScout is the operator-built AI execution layer for freight brokerages and agencies. One product, one login, one price. It sits on the TMS you already run (McLeod, Aljex, Tai, or any other). It is not a new TMS. It is not for shippers. It is not for carriers looking for loads.
Billing is live and supervised, including invoicing and collections. Rate and load-board sources connect. FreightScout works on the TMS you already run by API where one exists, and by reading the TMS in place where it doesn't. Build, Cover, Track and Bill are all live, supervised. Booking and outreach are supervised by default and switchable to autopilot. The agent works on any TMS your team logs into, including McLeod, Aljex, and Tai, by API where one exists, and by reading the TMS in place where it doesn't. No invented ROI. No customer names on this page.
Questions people actually ask
AI execution layer for freight brokers
An AI execution layer for freight brokers is software that performs brokerage work above the TMS: tender to load, cover to ceiling, check calls by API where one exists, and by reading the TMS in place where it doesn't, and billing that is live and supervised. FreightScout is that layer on the TMS you already run (McLeod, Aljex, Tai, or any other). A browser teammate and modular workers use execution language for narrower scopes. Compare how the write-back lands on the TMS, not the slogan.
Is a browser teammate the only AI execution layer for freight brokers?
No. A browser teammate uses that phrase for carrier work on screens the floor already opens. Modular workers split the jobs. FreightScout is overlay execution across win, price, move, bill, keep, and works by API where one exists, and by reading the TMS in place where it doesn't, where the brokerage grants access. Build, Cover, Track and Bill are all live, supervised. Booking and outreach are supervised by default and switchable to autopilot. The agent works on any TMS your team logs into, including McLeod, Aljex, and Tai, by API where one exists, and by reading the TMS in place where it doesn't. Shared phrase. Different scope. Compare how the write-back lands on the TMS.
Does an AI execution layer replace McLeod, Aljex, or Tai?
Not the overlay kind. An AI execution layer for freight brokers performs the work above the TMS by API where one exists, and by reading the TMS in place where it doesn't. FreightScout leaves the TMS you already run (McLeod, Aljex, Tai, or any other) as the system of record. No rip-and-replace. An AI TMS that can become the record is a different buy.
Is an AI execution layer the same as a load-board assistant?
No. A load-board assistant is a side panel on the load board and in email. Inbox-only tools stop there. An AI execution layer for freight brokers performs brokerage work above the TMS you keep, by API where one exists, and by reading the TMS in place where it doesn't: tender to load, cover to ceiling, check calls with a note on the load. FreightScout is overlay execution on the TMS you already run (McLeod, Aljex, Tai, or any other).
Is an AI execution layer overlay software, inbox-only, or TMS-embedded?
An execution layer that is overlay software performs brokerage work above the TMS you keep, by API where one exists, and by reading the TMS in place where it doesn't. Inbox-only tools stop at email. TMS-embedded AI is a new record or a module inside one. FreightScout is overlay execution on the TMS you already run (McLeod, Aljex, Tai, or any other).
Is overlay execution different from inbox-only carrier tools?
Inbox-only carrier tools extract rates and draft outreach in the inbox. Overlay execution builds the load, books to your ceiling, and logs check calls on the TMS you keep. FreightScout is overlay, not an inbox wedge.
How is FreightScout different from a browser teammate or an AI TMS?
A browser teammate covers carrier sourcing and negotiation. An AI TMS can become the brokerage record. FreightScout is overlay-first across win, price, move, bill, keep on the TMS you keep, by API where one exists, and by reading the TMS in place where it doesn't. Build, Cover, Track and Bill are all live, supervised. Booking and outreach are supervised by default and switchable to autopilot. The agent works on any TMS your team logs into, including McLeod, Aljex, and Tai, by API where one exists, and by reading the TMS in place where it doesn't.
What is an AI execution layer for freight brokers?
A freight execution layer is AI that performs brokerage work above the TMS: building loads from tenders, covering carriers to your ceiling, running check calls, chasing billing, while your TMS remains the system of record. FreightScout is that layer: operator-built coworkers on the TMS you already run (McLeod, Aljex, Tai, or any other), supervised or on autopilot.
What's the difference between freight analytics AI and AI that runs check calls and covering?
Analytics AI reports. Execution AI dials, books, and builds, then writes the result back to the load. Tracking shows where a truck is. A check call is the outbound work and the note. Covering is vet, negotiate to your ceiling, book, and write carrier and rate into the TMS. FreightScout is the execution slot, not another dashboard.
Do I need a new TMS or an execution layer on McLeod?
You need an execution layer on the TMS you already pay for. McLeod PowerBroker or LoadMaster stay the record. FreightScout overlays, reads in place, by API where one exists, and by reading the TMS in place where it doesn't. No rip-and-replace, and no certified-partner claim on this page. See Works with McLeod.
Is FreightScout a new TMS?
No. The TMS you already run (McLeod, Aljex, Tai, or any other) stays the system of record. FreightScout is the AI execution layer that sits on your stack by API where one exists, and by reading the TMS in place where it doesn't.
How is an AI execution layer different from a point tool or alert swarm?
Point tools own one wedge. An alert swarm watches and pings. FreightScout runs the whole load in one login, on one data model, on the TMS you already pay for: coworkers on the floor who do the work.
Is a browser teammate also an AI execution layer?
A browser teammate uses execution-layer language for carrier sourcing, outreach, negotiation, and compliance in the browser. That is a real, narrower claim. FreightScout is the AI execution layer for ops work above the TMS: win, price, move, bill, keep, and works by API where one exists, and by reading the TMS in place where it doesn't, where the brokerage grants access. Build, Cover, Track and Bill are all live, supervised. Booking and outreach are supervised by default and switchable to autopilot. The agent works on any TMS your team logs into, including McLeod, Aljex, and Tai, by API where one exists, and by reading the TMS in place where it doesn't. Shared phrase. Different scope. Sourced: Compare options.
Is FreightScout's AI execution layer live?
Sales runs in production today. Build, Cover, and Track run supervised on live freight at a working brokerage, every action staged for a human yes until you flip a capability to autopilot. Billing is live and supervised, including invoicing and collections. FreightScout cites 148,220 loads managed to date. Autonomy is a dial you control.
Who built FreightScout?
Built by operators: Founder and CEO Connor Miller, twelve years in freight, a brokerage agency scaled into nine figures. It runs on live freight at a working brokerage. Not software tourists guessing at your day.
Who is FreightScout not for?
Not shippers. Not carriers looking for loads. Freight brokerages and agencies whose day runs through a TMS, tenders, routing guides, and check calls.
Resources for the floor
Carrier sales
Tracking and check calls
Load building
The platform
Most freight software watches your business. FreightScout wins freight and then runs it.