JHC Group team
Customer Case Study

Winning the long sales cycle

JHC Express Sdn Bhd, the automotive-logistics flagship of JHC Group, replaced a CRM that didn't fit — Salesforce — with a Rework tender pipeline built for the way logistics actually sells: 2–8 month, two-gate, committee deals across 8 business units.

JHC Group Logistics & Freight Rework Sales OS Malaysia 2026
7 stagesTender Pipeline
8 BUsUnified
2–8 moSales Cycle
5 seatsPhase-1 Rollout
Salesforce →Replaced
LN
Linh Ngo
CSM · Lead
CN
Calvin Ng
Business Consultant
01 / 13
Contents

What this case covers

01

Company & Industry

Automotive-logistics specialist selling complex, tender-driven services across 8 BUs.

02

The Turning Point

A CRM that didn't fit — why Salesforce was dropped, and what changed.

03

Implementation

Demo to go-live in ~8 weeks, working around the Hari Raya holiday.

04

Needs & Goals

Excel across 8 BUs to one structured tender pipeline.

05

The Solution

Committees, a two-gate tender pipeline, activity tracking & forecast.

06

Adoption & BD Toolkit

An honest early read — plus selling Rework to logistics & tender firms.

02 / 13
Company & Industry

Logistics doesn't sell like a product — and its CRM shouldn't either

JHC Express Sdn Bhd (flagship of JHC Group, founded 1999, Subang Jaya) is a Malaysian freight & logistics firm specializing in automotive (OEM) logistics — air/sea/land freight, customs brokerage, haulage, warehousing & distribution. ISO-certified, ~51–200 staff, ~50–200 corporate clients. B2B service revenue, tender-driven, 2–8 month cycles.

① Service logistics ≠ product CRM

No weekly "units sold" — it's a long, proposal-heavy, multi-stakeholder cycle. A product-CRM (Salesforce) felt wrong here.

② Technical vs commercial = two gates

Malaysian tenders separate technical qualification from commercial approval — the pipeline must show both.

③ Buyer & seller are both committees

Procurement, ops, finance, directors on their side; multiple BUs on JHC's — single-owner CRMs lose the picture.

8Business Units
2–8 moSales Cycle
~50–200Corporate Clients
20–50Active Opportunities

8 Business Units unified

BU1Air Freight
BU2Sea Freight
BU3Warehouse
BU4Haulage
BU5Freighting
BU6Distribution
BU7Oil & Gas
BU8Automotive
Before Rework: Salesforce (dropped) → Excel weekly tracker + email + WhatsApp. Back-office WMS / TMS / fleet / accounting unchanged.
03 / 13
The Turning Point · Why Now

A CRM that didn't fit the business

01

The failed CRM

Salesforce ran a few months, then dropped — "product-based, not service-based… not suitable for our organization."

02

A long, invisible cycle

2–8 month tenders, separate technical + commercial proposals, tracked in Excel across 8 BUs.

03

MD-led, hard deadline

The Managing Director drove it personally; go-live 1st week April, around the Hari Raya / Eid holiday.

"For logistics we cannot secure a customer in one or two weeks… we participate in tender, we prepare a proposal for a couple of weeks. Whatever software we experienced before was product-base, not service-base — not suitable for our organization."
— En Amran Bin Abdullah, Managing Director · Solution Demo, Feb 9 2026

Decision Journey

NOV 2025

First contact

Laurel ↔ En Amran.

FEB 9 2026

Solution demo

Salesforce history + tender cycle surfaced.

FEB 20

Live trial

Hands-on with champion Aizat.

MAR 16

Alignment & kickoff

Pipeline confirmed; scope = 5–7 key clients.

~MAR 20–27

Hari Raya holiday

Build planned around it.

~1ST WK APR

Training & Go-Live 🚀

Live before Apr 10.

04 / 13
Implementation Timeline

Demo to go-live in ~8 weeks — around a holiday

Phases: setup + pilot < Mar 20 · all staff trained & active < Apr 3 · official go-live < Apr 10.

FEB 9

Solution Demo

Salesforce context + tender cycle mapped.

FEB 20

Live Trial

7-day demo account; champion Aizat hands-on.

MAR 9

Internal Handoff

BC Calvin → CSM Linh.

MAR 16

Alignment & Kickoff

Pipeline confirmed; 5 accounts live; email sync.

MAR 19

Set-up Review #1

Linh × Aizat / Saleh.

~MAR 20–27

Holiday

Hari Raya / Eid — build planned around it.

LATE MAR

Workshops

Fine-tune + pilot on 5–7 key clients.

~1ST WK APR

Training & Go-Live 🚀

Live before Apr 10.

05 / 13
Needs & Goals

Before vs after Rework

Before Rework
❌

A CRM that didn't fit

Salesforce — product-centric, dropped after a few months.

🗂️

Excel across 8 BUs

A weekly tracker + inboxes; visibility siloed per business unit.

📑

Tender stages in people's heads

Technical & commercial proposals tracked in files, not a system.

👥

Stakeholders implicit

Multi-party deals lived with one owner; no continuity on hand-off.

📉

No forecast

Manual "% progress" — no pipeline-health or revenue view for leaders.

After Rework
✅

A service/tender-fit CRM

Configured around the long, proposal-heavy logistics cycle.

🛤️

One 7-stage tender pipeline

All BUs in one view; multiple pipelines for long vs short deals.

🚪

Two explicit gates

Technical Proposal → Commercial Proposal → Approved Commercial stages.

🧑‍🤝‍🧑

Buying + selling committees

Account org-chart + full activity history any member can see.

📊

Forecast dashboards

Pipeline health, revenue forecast, RFQ→tender→bid conversion.

06 / 13
The Solution · Part 1

Streamlined sales pipeline for 2 key motions

A service/tender-driven business with long cycles needs pipelines that mirror how deals actually progress — not a generic product CRM.

Before — The Excel

Weekly tab-duplicate system: 8 BU sections, manual % progress, status columns rarely filled, delays invisible, no sales cycle view.

JHC weekly Excel tracker
Pipeline 1 · Tender / Current Projects

Tender/RFQ/Proposal → Technical Commercial → Submission → Follow-ups → Award/Contract → Kickoff/Onboarding → Operational Review

Tender Pipeline in Rework
Pipeline 2 · Business Development

Referrals/Introduction → Presentation → Registration → Study/Proposals → Engagement/Follow-ups → Tenders/RFQ → Negotiation → Award

BD Pipeline in Rework
Two pipelines built to reflect JHC's actual GTM reality — the operational tender cycle vs the longer BD motion. Progress now visible, not buried in a weekly Excel tab.
07 / 13
The Solution · Part 2

Clear buying and selling committees

Over a 6–8 month tender cycle, no single person closes the deal. Every stakeholder on both sides needs to be mapped and visible in one place.

Accounts & contacts configured

  • Accounts — clients vs strategic partners / sub-vendors, with an account org-chart
  • Buying committee — procurement, ops, finance, directors tagged to the deal
  • Selling committee — the JHC BU members collaborating on the same account
  • Custom fields — Product Offer, Source, Expected Close Date, Deal Value, location
  • Cross-BU visibility — key clients like Petronas appear once; all BU activity visible in one account record
Aizat (BD) serves as the internal champion and primary builder — he manages vendor relationships with Logiflow, Siemens, Yojee, FR8Labs and others in parallel, making clear ownership essential.
Perodua Account — buying/selling committee
08 / 13
The Solution · Part 3

Deal activities fully recorded — health & forecast visible

Every touch, every file, every call logged to the deal. Pipeline forecast with deal value and ownership clear at a glance — for the team and for leadership.

✉️ Emails

Gmail/Outlook sync + open/click tracking — know when a client re-opens your proposal.

📅 Meetings & Calls

Calendar-synced meetings; calls via business number logged to the deal record.

📝 Notes & Files

Tender documents, site visit notes, proposal drafts — all attached to the deal, not buried in inboxes.

📊 Pipeline Forecast

Deal value visible per stage; ownership clear per BU; pipeline health and revenue forecast for the MD.

Why this matters for JHC

The weekly Excel had no continuity — a deal that stalled at 30% looked the same as one actively progressing. With full activity logging, stalled deals surface automatically and leadership sees a real forecast, not a snapshot of manual guesses.

Deal activity stream
09 / 13
End-User Adoption · An honest read

A focused, MD-backed launch — measured later

Phase-1 rollout

Phase-1 seats
5 of ~7
Focus: key clients
5–7 first
BUs unified
8
Captured around go-live — no Active Usage export yet. Adoption to be measured at the +1-week / +1-month reviews. VERIFY

What's driving it

🟢 Green flags

MD En Amran personally sponsors it. Aizat (BD) is an engaged champion; Saleh (IT) builds the system hands-on. Strong ICP fit (B2B service selling).

🔴 Watch items

Salesforce-failure memory → must prove value fast. Holiday compresses the runway. Shared accounts to migrate to 1-user-1-email. No dedicated sales team yet.

🟡 Next up

Migrate full deal set · expand to other BUs · WhatsApp Business integration · resolve account ownership · post-go-live optimization reviews.

JHC IT Control Room
WA CRM Update Reminder
10 / 13
Before & After · Summary

The shift, at a glance

CategoryBefore ReworkAfter Rework
Sales systemSalesforce (dropped) → noneRework Sales OS — service/tender-fit
TrackingExcel, 8 BU tabs + inboxesOne 7-stage tender pipeline
Proposal stagesIn heads / filesTechnical + Commercial gates explicit
StakeholdersImplicit, single-ownerBuying + selling committees, org-chart
EmailUntrackedSync + open/click tracking
ForecastManual % progressPipeline-health + revenue dashboards
Cross-BUSiloed per BUShared accounts/pipeline visibility
11 / 13
BD Toolkit

Selling Rework to logistics & tender-driven B2B firms

Key terms

Freight forwarding
Arranging shipment of goods (air/sea/land) + customs. Service revenue, project- and contract-based — no simple unit-sale motion.
RFQ / RFI / Tender
Request for Quotation / Information / formal Tender — the inbound triggers. Tenders demand formal multi-document responses.
Technical vs Commercial proposal
Two separate gates in Malaysian tenders — technical qualification first, commercial/pricing approval second.
BU / KAM
Business Unit / Key Account Manager. A multi-BU logistics firm coordinates the same key client across several BUs.
Buying / Selling committee
Multi-party decision on both sides — map every stakeholder, since no single person closes the deal.

Win more deals like this

Lead with service-cycle fit

Name why product-CRMs (Salesforce) fail for tender logistics — that's the wedge.

Model technical & commercial as two gates

Showing both stages proves you understand how tenders actually run.

Map committees + cross-BU

Buying + selling committees and one account across BUs — that's the visibility win.

Sell continuity + forecast, not deal count

Over 6–8 months the value is full history surviving hand-offs, and a real forecast for the MD.

Ride MD sponsorship + a seasonal deadline

Top-management mandate + a holiday-bounded go-live converts evaluation to action — plan around the holiday.

Price for the whole team

USD 1,499/yr for 5 users vs per-seat incumbents — decisive for a cost-aware SME.

12 / 13
Conclusion

JHC didn't just replace a CRM.
They got one built for how logistics actually sells.

A 2–8 month, two-gate tender cycle across 8 business units — finally visible, forecastable, and shared. After a generic CRM failed them, the fit is the win.

7Pipeline Stages
8BUs Unified
2–8 moCycle Tracked
5Phase-1 Seats
SalesforceReplaced

Captured around go-live · Rework Sales OS · Malaysia · 2026

13 / 13