The Platform
Six capabilities built for mid-market freight brokerages — integrated directly into Aljex, McLeod, MercuryGate, and Trimble TMW.
The Problem
Mid-market freight brokerages running 150-800 loads per day face a structural problem: manual load-matching by brokers consumes 40-60% of productive hours. The TMS holds every historical load and carrier result, but it has no scoring layer — brokers carry performance knowledge in their heads, burn out, and leave, taking institutional knowledge with them.
The result: 8-15% carrier fallout per day when the first tender goes to the wrong carrier, and $80-220 per load in spot re-cover costs when dispatchers scramble to rebook the morning of pickup. Inbound load tenders from shipper TMS or EDI feed, carrier capacity commitments from DAT and Truckstop postings, and 24 months of lane-level performance data all exist inside or alongside the broker's existing workflow — but nothing connects them at the moment of tender.
Brokerages that survive the next five years of margin compression will be the ones that eliminate the re-cover loop and move first-tender acceptance rates above 85%. That requires a scoring layer the TMS was never designed to provide — which is exactly what Loadwyre is built to do.
Platform Capabilities
Loadwyre sits between your shipper tender and your carrier confirmation — scoring, ranking, and optionally booking the right carrier before manual effort touches the load.
01 / 06
Score every carrier by on-time history on this specific lane before tendering
Loadwyre builds a per-lane, per-carrier performance model updated nightly. Each time a load is tendered, the engine pulls the last 90 days of OTD, fallout rate, and average check-call responsiveness for that carrier on that origin-destination pair. Brokers see a confidence score from 0-100 alongside every candidate carrier, so the first tender goes to a carrier statistically likely to accept and run clean.
02 / 06
Let high-confidence matches book automatically while borderline ones queue for review
Operators set a confidence threshold per lane type or customer. Loads matching carriers above the threshold book automatically and push confirmation back to the shipper TMS within 4 minutes of tender receipt. Loads below threshold surface in a review queue sorted by urgency and margin sensitivity. Brokers stop touching routine lanes and focus attention where their judgment adds real value.
03 / 06
Flag carriers likely to drop a load 12-24 hours before fallout occurs
Using check-call patterns, weather events, and carrier-specific behavioral signals, Loadwyre assigns a live fallout-risk score to each booked load. When risk exceeds a broker-defined threshold, the system surfaces a backup carrier shortlist immediately. Brokers get ahead of the fallout rather than scrambling for re-cover at spot rates the morning of pickup.
04 / 06
Pull posted available capacity in real time without manual load-board search
Loadwyre maintains a live feed from DAT Freight and Truckstop, continuously refreshing available trucks near each origin. When a tender arrives, posted capacity is merged with the broker's preferred carrier list and scored in the same matching pipeline. Brokers no longer switch between TMS and load boards; relevant capacity surfaces inside the workflow they already use.
05 / 06
See how matching quality translates to per-load margin outcomes over time
The margin dashboard breaks down each week's load portfolio by first-tender acceptance rate, fallout rate, re-cover cost, and gross margin per lane. Brokers and operations managers can identify which lanes, customers, or carrier segments are dragging margin and take corrective action. Data exports in CSV for integration with existing management-reporting workflows.
06 / 06
Surface Loadwyre recommendations inside Aljex and McLeod without a tab switch
Native integrations with Aljex and McLeod LoadMaster embed the carrier shortlist directly in the load-editing screen. Brokers click to tender the top-ranked carrier without leaving their existing workflow. For brokerages on MercuryGate or Trimble TMW, a lightweight browser extension provides the same side-panel experience. No separate login, no copy-paste, no workflow disruption.
Who It's For
Not for single-broker owner-operators, not for enterprise national 3PLs with in-house TMS development teams.
Mid-market freight brokerages running 150-800 loads per day with $20M-$200M gross revenue and 15-100 broker headcount. Operations with enough carrier history in their TMS for the scoring models to be accurate, but without in-house engineering resources to build custom matching tools.
Single-broker owner-operators where every carrier decision is personal and relationship-based. Enterprise national 3PLs with proprietary TMS development teams who build custom matching systems in-house at scale. Brokerages running fewer than 100 loads per day where manual matching is manageable.
How It Works
Three steps — data in, scoring, ranked output — all happening inside your existing TMS workflow.
01
Inbound load tender arrives from shipper TMS, EDI 204, or manual entry. Loadwyre ingests load details, origin, destination, pickup window, commodity, and weight — then immediately queries your carrier network and active capacity feeds for that lane.
02
Every carrier in your approved network is scored against 90 days of lane-level on-time delivery, fallout rate, and pickup compliance — merged with live posted capacity from DAT and Truckstop — then ranked by a composite confidence score adjusted for the specific lane, day of week, and pickup lead time.
03
Ranked carrier shortlist with confidence scores and fallout-risk flags surfaces inside your TMS workflow — no tab switch required. Loads above your auto-book threshold tender automatically and push confirmation back to the shipper within 4 minutes. Loads below threshold queue for broker review sorted by urgency and margin sensitivity, with full scoring detail visible for every carrier on the list.
Supported Systems
Loadwyre integrates with the TMS platforms mid-market brokerages already run — no migration, no parallel system.