Question 01
What's the AI carrier-matching ROI for a freight brokerage portco?
AI carrier-load matching compresses broker research time from 8 to 15 minutes per load to under 60 seconds while improving margin per load 1 to 3% on the spot market. A mid-market brokerage handling 200,000 loads per year recovers $2M to $6M in annualized margin plus 30 to 50% productivity per broker. The pattern holds across Loadsmart, Uber Freight enterprise, and in-house builds on rate-API feeds.
Why most vendors get this wrong: they sell the carrier-match decision in isolation and skip the broker workflow integration. The win isn't the algorithm. The win is the broker spending 60 seconds where they used to spend 12 minutes, with the same or better margin per load. That requires the AI to surface in the broker's actual workflow, not a separate app.
Right answer pattern: the vendor produces a before-and-after broker time-and-margin study from a comparable brokerage customer (same volume band, same lane mix) covering broker research time, margin per load, and conversion rate. The vendor who can't produce that study is selling the algorithm, not the workflow.
Question 02
How does AI improve dock appointment scheduling at 3PL warehouses?
AI dock-scheduling platforms (Shipwell, FourKites, Trimble) replace the phone-tree-plus-clipboard pattern with carrier-preference learning, predictive ETA matching, and dynamic re-slotting. Typical results: 20 to 30% throughput lift on dock doors, 15 to 25% reduction in carrier dwell time, and elimination of the dock-manager spreadsheet entirely. For a 3PL portco running 8 to 25 facilities, the dock-throughput lift is worth $1.5M to $5M per year.
Why most vendors get this wrong: they sell the dock-scheduling product as a standalone SaaS without integration to the WMS, the TMS, or the carriers' visibility platforms. The throughput lift requires the schedule to flex when ETAs shift mid-day, which only works if the visibility layer feeds the scheduler in real time.
Right answer pattern: documented integration with the portco's WMS, TMS, and at least one of FourKites/project44/Trimble Visibility. Bonus points if the vendor has dock-scheduling deployments at carrier-cooperative facilities (where the carrier's TMS feeds back into the dock schedule before the truck rolls).
Question 03
What's the customer service deflection opportunity from AI trace/ETA agents?
Customer service in 3PL and trucking eats 25 to 40% of overhead, and 50 to 70% of inbound contact volume is trace, ETA, or status. An AI agent grounded in real-time visibility (FourKites, project44, Trimble Visibility, Shipwell tracking) plus customer order context resolves 60 to 80% of trace and ETA queries without escalation. The redeployed CSR capacity gets reassigned to exception management.
Why most vendors get this wrong: they pitch deflection as the whole win, when the second-order win (CSR capacity redeployed to exception management) is bigger. The on-time performance lift from CSRs actually solving problems instead of describing them is the durable margin recovery, not the headcount savings.
Right answer pattern: the vendor's scope includes deflection metric and exception-management workflow design. Bonus points if the vendor has named portco customers where on-time performance has measurably improved post-deployment, not just contact volume reduced.
Question 04
Why are PE firms like STG and Thoma Bravo buying logistics tech with AI overhauls in mind?
Two reasons. First, lack of physical assets makes 3PLs and logistics-tech businesses attractive to sponsors who don't want a fleet on the balance sheet. STG acquired Carrier Logistics in 2026 explicitly to fund an AI-agentic platform overhaul for LTL carriers. Thoma Bravo merged WWEX Group with Auctane on a similar thesis. Second, the AI opportunity in logistics is structural rather than incremental: the spread between manual dispatch and AI-optimized dispatch is 8 to 15 percentage points of fuel-plus-labor cost, which compounds across thousands of loads per day.
Why most logistics CEOs miss this: they're competing against single-fleet operators who can't fund the AI build. The PE-backed platform that can fund $5M to $15M of AI build over 18 months captures a structural spread that single-fleet competitors will never close. The sponsor's AI thesis is a competitive moat the operator doesn't see until two quarters in.
Right answer pattern: a portfolio-wide AI roadmap with one CTO-equivalent operating partner and a 24-month build plan that surfaces the spread before the next sponsor's exit cycle. The portco that runs this playbook ahead of its sponsor's exit window sells at a premium multiple.
Question 05
How does AI integrate with McLeod LoadMaster, MercuryGate, or Trimble TMS?
Real integration means working calls against the documented APIs for McLeod LoadMaster (broker, asset, or driver edition), MercuryGate TMS, Trimble TMW Suite, or Carrier Logistics CLI, validated against the portco's actual deployment version. Most AI vendor decks show the TMS partner logo without specifying which edition or version. The honest test: ask for two named carrier or broker customers running on the same TMS version with a live integration in production.
Why most vendors get this wrong: they have a working integration with one version (typically the cloud-modern version) and assume parity with the legacy on-prem deployments most mid-market carriers still run. McLeod LoadMaster broker edition behaves differently from McLeod LoadMaster asset edition. MercuryGate TMS on Oracle DB behaves differently from MercuryGate TMS on SQL Server.
Right answer pattern: two named customers on the same TMS edition and version, a specific named integration partner, and a working scope-of-work covering the portco's TMS customizations. If the vendor can't produce all three within the first phone call, the integration story isn't real yet.