What a Water-Tanker Business Taught Us About Dispatch

The Terasek water-tanker logistics case is the project that shaped how we build dispatch systems. Jared Loo, who co-founded Result Marketing, ran Terasek before he became a partner here — he was the client before he was on this side of the table. That background matters.

Why Water Tankers Are a Hard Logistics Problem

A water-tanker operation looks simple from the outside: trucks pick up water, deliver it to construction sites or industrial customers, come back for more. The operational complexity is higher than it appears.

• Each truck has a specific capacity. Jobs need to match available capacity, not just available trucks.
• Delivery windows are tight — construction sites have narrow access times.
• Customers are dispersed across a wide geographic area, often with difficult access.
• A tanker that completes a job early can take another job if dispatch knows about it immediately.
• Failed deliveries — access denied, site closed — need to be logged and rescheduled fast, because the truck capacity is wasted if the driver has to return empty.

The dispatch problem is: how do you assign jobs, track real-time progress, handle exceptions, and maintain records — with a team of drivers who may have limited digital literacy and are on the road all day?

What Generic Fleet Software Gets Wrong

When Jared first looked at solving this, the obvious move was to buy a fleet management or dispatch software product. The products on the market were built for different contexts: freight forwarding, courier networks, or enterprise fleet operations. They brought with them:

• Feature sets designed for Western logistics contexts with different road and workforce conditions
• Driver interfaces built for high-literacy, high-connectivity users
• Billing integration assumptions that did not match Malaysian accounting workflows
• Per-seat or per-truck pricing models that made the cost non-trivial for an SME fleet

None of them handled the specific operational logic of a Malaysian water-tanker business: capacity matching, construction site delivery windows, and the practical needs of a frontline driver workforce.

What We Learned About Dispatch Requirements

Building the dispatch system for Terasek produced a set of principles I apply to every logistics system we build now.

The driver interface must require minimal literacy and minimal taps. A driver in the cab, under time pressure, with gloves on, needs to complete a delivery record in under 30 seconds. Every extra field is a risk of incomplete data.

Exceptions are not edge cases. They happen every day. Failed deliveries, partial loads, access problems, vehicle issues — these need a first-class workflow, not a workaround. If the system does not handle exceptions cleanly, drivers stop using it for exceptions and revert to phone calls.

Dispatch visibility is more useful than route optimisation. Knowing where every driver is and what their job status is — in real time — lets a dispatcher make human decisions quickly. Complex route optimisation algorithms are less valuable than a clear map view.

Billing must connect directly to completion records. The moment a delivery is confirmed on the driver's device, the billing team should be able to act on it. Any gap between operational data and accounting data creates reconciliation work.

How This Shapes What We Build

Every logistics system we build now starts with the driver workflow first. I ask: what is the minimum the driver needs to see, and the minimum they need to input, for the back-office to have everything it needs?

From there, the dispatch module, the customer portal, and the AutoCount integration are built around a clean data flow from driver to finance.

The about page has more on how the founders' backgrounds — as operators, not just developers — shape how we approach these problems.

FAQ

Is the Terasek system available as a product for other logistics companies?

No. We build custom systems tailored to each business's specific workflow. The Terasek experience informs how we think about logistics problems, but each new system is scoped and built for the specific business we are working with.

How do you handle logistics operations with very different vehicle types — trucks, motorcycles, and vans in the same fleet?

Each vehicle type can have its own job constraints, capacity rules, and driver workflow. The dispatch system assigns jobs based on the vehicle's attributes, not a one-size-fits-all model.

What is the minimum fleet size where a custom dispatch system makes sense?

It depends more on delivery volume and billing complexity than fleet size. A 5-truck operation delivering 100+ jobs a day and billing 80+ invoices a month is a better candidate than a 20-truck fleet doing simple bulk deliveries with monthly invoicing.

Want to talk through your dispatch problem with someone who has actually run a logistics business? WhatsApp us.