What planning teams say after working with us
We've worked with operations teams across Selangor, Penang, and Johor. These are some of the things they told us afterwards — in plain language, without the polish of a marketing brief.
Back to Home38+
Teams advised
4.7
Average satisfaction
3 yrs
Operating from Sepang
100%
Written deliverables issued
From the teams who worked with us
Siti Leila Hamdan
Supply Chain Manager, Shah Alam
We commissioned the Lane Diagnostic to look at our Port Klang–Penang run. What we got back was a written brief we could actually use in a planning meeting — not a dashboard with no context. The integration notes were useful because they were honest about what our TMS could and couldn't support.
April 2025
Rajendran Krishnamurthy
Logistics Director, Klang Valley 3PL
The ETA Co-Pilot rollout was more careful than I expected. Zulaikha's team didn't push us to move faster than our planners were comfortable with. The weekly clinics were where the real value was — my team felt confident asking questions they wouldn't have asked a normal vendor.
March 2025
Ng Chee Weng
Operations Manager, Johor Bahru
I was sceptical about AI coordination services because most of what we'd seen before was offshore teams with generic playbooks. Pelangi Forge knew our customs cycle at Bangunan Kastam JB. That local knowledge saved us a lot of explaining.
April 2025
Faridah Zainudin
Head of Planning, Penang-based Manufacturer
We're on the retainer arrangement now and the monthly brief is something our ops director actually reads. It's written in the kind of plain language that works in a meeting. The RMCD updates section has caught two changes that would have affected our duty classification before we would have spotted them ourselves.
April 2025
Ahmad Taufiq Roslan
TMS Administrator, Selangor Freight Co.
Rajan's read-only integration process was cleaner than anything I'd seen from a third-party before. He documented everything — credentials, access scope, what data was pulled and when. As the TMS admin, I appreciated having that paperwork for our IT security review.
March 2025
Lim Yee Fong
Supply Chain Analyst, Selangor
The diagnostic gave us a clearer picture of where our exception management process was actually losing time. Some of the findings were things we already suspected but hadn't been able to quantify. Having it written down made it easier to bring to the logistics manager.
April 2025
Three engagements, in detail
Case Study · 01 · Lane Diagnostic
February 2025
Challenge
A Klang Valley 3PL was spending roughly fourteen planner-hours per week manually chasing ETA updates on their Port Klang–Singapore corridor. Carrier data was fragmented across email, WhatsApp groups, and a TMS that hadn't been configured for visibility beyond bookings.
Solution
Lane & Node Diagnostic over three weeks. We reviewed 90 days of shipment records, mapped the ETA data sources available, and identified two carrier feeds that could be connected to their existing TMS without custom development. Delivered a written brief with four prioritised actions.
Outcome
The brief identified one carrier integration that reduced manual ETA checks by an estimated 60% on that corridor. The client implemented two of the four recommendations within six weeks of receiving the brief using their existing IT team.
~60% reduction in manual ETA checks
Case Study · 02 · ETA Co-Pilot
December 2024 – February 2025
Challenge
A Penang-based electronics component distributor was managing over 200 active shipments per week across four trade lanes. Their planning team of five was spending most of the morning shift reviewing individual shipment statuses before any customer communication could begin.
Solution
ETA & Exception Co-Pilot with read-only TMS integration. Over six weeks, we supervised the rollout of an exception clustering assist that grouped shipment exceptions into three daily review batches. Weekly clinics helped the team learn when to override the AI groupings.
Outcome
Morning status review time reduced from approximately 2.5 hours to under an hour for the same shipment volume. The planning team described the main benefit as fewer interruptions during the afternoon shift when customer communication volume is highest.
Status review time: 2.5h → <1h
Case Study · 03 · Network Retainer
Ongoing from October 2024
Challenge
A Johor Bahru logistics firm had introduced AI-assisted demand forecasting for their warehouse network in 2023 but had no process for reviewing whether the model was still reading trade patterns accurately as seasonal volumes shifted.
Solution
Network Stewardship Retainer from October 2024. Monthly model behaviour reviews are written as a two-page brief for the operations director. The Q1 2025 brief identified a seasonal drift in the Johor–Singapore truck corridor model that was under-reading peak festive volumes.
Outcome
The festive season model correction was applied before Chinese New Year 2025 volume peaked. The operations director noted that previous years had seen a three-to-four day response lag when the AI model failed to anticipate the volume spike. In 2025 the transition was managed without that lag.
CNY 2025 volume spike managed without lag
Reach our advisory team directly
Phone
+60 13 482 9716Address
Lot 2.04, KLIA Annex, Persiaran KLIA, 64000 Sepang, Selangor
Office Hours
Mon–Fri: 8:30 AM – 5:30 PM | Sat: 9:00 AM – 1:00 PM
Professional affiliations and recognition
MDEC Recognition
Malaysia Digital Economy Corporation — supply chain AI advisory, 2024
Malaysian Institute of Logistics
Associate member contributing to AI in logistics curriculum, 2023
PDPA 2010 Compliant Practice
All data handling documented under Malaysia's Personal Data Protection Act
Ready to discuss your trade lanes?
Send us a note and we will respond within one business day to discuss which engagement might suit your team and where to start.
Request a Quote