How Huolala Turns AI Agents into Real Business Results: Three Production Deployments and a Four-Layer Model
This is a rare, production-level account of AI agents operating inside core transaction systems, not just demos. It shows where agents actually add value, what constraints must live in code rather than prompts, and how to define success with business metrics while controlling token costs.
Huolala has shipped AI agents into its real-time freight transaction systems, not as chat assistants but as agents that directly change business state. The engineering leader behind this work, Laurence Qi, walks through three live deployments: AI-guided ordering that turns open user intent into confirmed orders, a continuous matching system that keeps pushing toward a deal after an order goes unanswered, and an operations agent that executes strategies across internal systems. In each case, agents work alongside existing ML, operations research, and transaction systems rather than replacing them.
A central piece is the four-layer model for productionizing agents. Model capability is the common starting point; the harness determines the floor, with two distinct kinds of constraints. Help-the-model harnesses compensate for current model weaknesses and should be deletable as models improve. Protect-the-business harnesses, like permission checks, idempotency, and state machine SOPs, must be written in code and never disappear. A dual loop separates agent capability metrics from business outcome metrics, showing that improving dialogue quality alone can miss the real bottleneck, such as targeting the wrong driver pool. The ceiling comes from how well enterprise knowledge is encoded: deterministic rules into code, quality standards into evaluation, and effective scripts into strategy.
Measured results include 99% intent recognition accuracy, 93% vehicle selection accuracy, 25% faster ordering for new customers, a 12% relative match rate improvement with 4x ROI versus manual matching, and an 80% efficiency gain from 33+ operations agents with zero configuration errors.
Model capability is no longer the differentiator; the harness and the way business knowledge is encoded decide whether an agent helps or hurts.
Improving agent dialogue quality while ignoring which drivers are targeted can actually drive conversion down; the outer loop catches what the inner loop cannot see.
The cautious stance on letting agents set strategy reflects a practical trade-off: the deeper agents go into execution, the more guarded they become near decisions.
Deletable help-the-model harnesses indicate that agent production is still evolving rapidly, while protect-the-business harnesses will remain a permanent engineering layer.