A 3PL in Mexico moved from sampling to full coverage and documented $3.6M MXN in unsupported charges in 6 weeks: 2,250 invoices, ~5.7% of audited spend. The case is published.
In other pilots the pattern holds on a single process: tendering, track, or audit in a 6-8 week pilot with your real operation, not a TMS configuration project that drags on for months. Ops stays the decision owner; the agent speeds up work the team already knew how to do.
The pattern shows up in Mexico freight operations with real volume and real leakage:
- Shippers who already matched rates by hand now release AP with a file before paying.
- Operators who quoted carriers one WhatsApp at a time now compare in parallel.
These are not Fortune 50 logos.
- MXN detected in 6 weeks (3PL case)
- $3.6M
- coverage: 2,250 invoices in the flow
- 100%
- useful pilot per process (OCL pattern)
- 6-8 weeks
They bet on your data and give you slow software
Legacy logistics software bets on the vendor as the expert.
You buy the license. They sell configuration, professional services, and the roadmap. Your operation sits behind a ticket backlog.
A traditional TMS can take 8 to 12 weeks or more to be “ready.”
Meanwhile freight still moves, invoices still land, and sampling still lets the typical 5–7% of unsupported spend through.
The system records what someone types. It does not run the 2 a.m. exception.
The black box is the product:
- Hidden rules
- Integrations only the partner understands
- Operational knowledge that leaves with the consultant
Your data feeds their platform. Your judgment is trapped in their configuration.
For the full contrast, see Traditional TMS vs OCL Cargo and the playbook on complementing or replacing your TMS with agents.
We bet on you and give you iteration speed
OCL bets on the operators who already know their freight, carriers, and exceptions. The agent is a glass box: you see what it matched, against which rate, with which evidence. You iterate in days, not implementation sprints.
Tendering, track & trace, and audit do not replace your judgment. They execute it at scale.
- You set the rule
- The agent applies it to 100% of the flow
- Findings reach AP with a file, not a loose complaint in a chat
We do not appropriate the relationship with your carriers or your customers. That relationship, and the operational judgment behind every exception, was always yours. We give you the speed to use it.
FIGURE 1 · TIME TO VALUE
Weeks to a useful pilot.
Typical TMS/enterprise rollout versus an OCL agent pilot on a single process. The 3PL audit case closed findings in 6 weeks.
Source: OCL pilot pattern (6-8 weeks) · 3PL case /blog/case-study-3pl-audit-agent#resultados (6 weeks, 2,250 invoices).
The freight relationship was always yours. We bet you will run it faster, with evidence, without handing control to a vendor that lives on your lock-in.