04 · Logistics & transport

The numbers stopped hiding.

Hock Lee Transport · Tuas · 31 staff

The week that kept going wrong

Which routes made money? Which clients paid late? The answers lived in last quarter’s spreadsheet.

By the time a report was built, the decision it was meant to inform was five weeks old.

Everyone had a theory about the loss-making runs. Nobody had the number.

A Friday questionillustration
“which routes lost money in Q2?”
answered from live data — synced 2 min ago
two slow payers surfaced, chasers drafted
drill-down opened on the Tuas–Jurong run

How a build like this runs, hour by hour.

We built their numbers explainer.

Ask it a question in plain words and it answers from live data, showing where each figure came from. Slow payers surface on their own, with polite chasers drafted — and never sent without a person saying so.

What it gave back

12.2 hours back / weekexample · month 4
Invoices read & matched4.8 h
Route costing3.6 h
Late-payer chasing2.3 h
Report writing1.5 h

You know by Friday what used to take five weeks to find out.

The honest bit. The first month it was wrong twice, both times because two systems disagreed about a job number. Tidying that was the real fix.

This build is an illustration — a composite of the kind of work we do, not a named client.

Yours would be its own build.

This one was shaped around one team’s actual week. The free audit maps yours in two minutes, and the findings report is yours to keep.