Today we announce MatchLog and open early-access applications for freight brokers and fleet operators. This brief post explains what we are building, who it serves, and what we are not aiming to do.
The Problem We Address
Freight dispatch runs amid constant disruption. Carriers arrive late. Loads fall through. Drivers call out. Traffic sends a truck off course when it was meant to meet a tight window. Each event alone is manageable. The difficulty is that they occur across the whole board at once, while dispatch teams use tools not designed for real-time response.
A disruption usually starts with a phone call. The dispatcher calls the carrier to learn what happened, calls possible replacements to locate available capacity, then calls the shipper or receiver to handle the impact. For a five-person broker team managing 60 loads per day, three simultaneous disruptions at 9 AM means approximately 15 to 20 phone calls in the next hour, in addition to everything else on the board. That is not sustainable. It is routine.
MatchLog is designed to alter that routine. When a carrier runs late or a load falls through, the system detects the disruption through telemetry data before the carrier calls, finds the best available replacement in the operation's existing carrier network, and shows it to the dispatcher for one confirmation action. Information gathering and option review that once required phone calls become a decision the dispatcher can make in under a minute.
Who MatchLog Serves
At launch, we are concentrating on two customer types: mid-market freight brokers and last-mile fleet operators.
Mid-market freight brokers generally handle 20 to 150 loads per day with a dispatch team of 3 to 10 people. They have an established carrier network, an existing TMS, and disruption rates that produce substantial daily triage work. They are big enough for the problem to be acute, but not big enough to support a dedicated operations control function or custom tooling investment. That is the gap we address.
Last-mile fleet operators deal with a related but structurally different challenge: they own or manage the vehicles, so disruptions generally involve driver callouts or route delays rather than carrier cancellations. If a driver misses a morning run, that route's stops must be redistributed among other fleet drivers while considering time windows, vehicle capacity, and driver hours. Manual re-sequencing takes 30 to 60 minutes. MatchLog performs the re-sequencing and shows the dispatcher a revised route plan to confirm.
We are not creating this for large national carriers with their own operations centers, or for spot-market brokerages where the main value lies in finding new carriers rather than maintaining existing network reliability. Our focus is on operations with established carrier relationships, where the challenge is managing capacity within those relationships as conditions change.
Autonomous Dispatch: What It Means and Does Not
In freight dispatch, the word "autonomous" can refer to several things. We want to clearly define what it means for MatchLog at this stage.
MatchLog autonomously compares carrier position data with expected progress, spots deviations before they become missed pickups, finds replacement capacity within the carrier network, and scores alternatives using lane history, proximity, and recent reliability. These processes continue without dispatcher action.
MatchLog does not, and will not without a dispatcher's deliberate instruction, commit to a carrier for the operation, send outbound messages to carriers or shippers, or take any action that creates a binding obligation. A dispatcher must review and approve every recommended match. The system accelerates decisions rather than replacing them. This limit is deliberate and reflects what operations teams consistently told us before we built it: dispatchers want assistance with searching and evaluating options. They do not want the tool making commitments for them.
How It Works, Simply
MatchLog connects to your existing TMS through API and to carrier telemetry feeds when available. Standard TMS integrations take less than a day to set up, and we handle the integration work directly with your team. There is no carrier network migration: MatchLog uses the carrier relationships and contact data you already have.
After connection, the system operates in the background alongside your usual dispatch process. Dispatchers receive a live alert feed when potential disruptions appear and a recommended match once a disruption is confirmed. They can accept, modify, or dismiss the recommendation. Every decision is recorded for review and audit purposes.
We charge a flat monthly fee based on team size, with no per-load fees. Pricing is available on our site. We believe per-load pricing creates the wrong incentive for a tool meant for every disruption, rather than one that is rationed.
Early Access
Applications for early access are open now. We are onboarding a small number of operations teams before expanding access. This period includes closer collaboration: we will onboard your team directly, check in regularly, and use your feedback in the product. In return, we are offering early-access pricing below our standard rates.
If you operate a freight brokerage or last-mile fleet and the problem above feels familiar, we would like to speak with you. Apply through our contact page. We respond within one business day.
We are three people building something we believe the industry needs. We do not yet have a large customer list to show. We have a clear problem, a working product, and three operations teams that agreed to try it with us. That is our starting point, and we are being direct about it.