Investor / Partner View¶
MYConnect begins with a focused operating-system wedge for Malaysian SME hauliers. The expansion path is broader, but the first job is to earn trustworthy operational data from real transport workflows.
Market Wedge¶
The primary customer is the SME haulier operating roughly 10 to 200 vehicles. These operators often have enough operational complexity to need software, but not enough internal engineering or IT capacity to assemble a modern platform themselves.
Common pain points include:
- WhatsApp-based dispatch.
- Excel-based job tracking.
- Paper or delayed POD.
- Separate commodity GPS portals.
- Limited customer visibility.
- Slow billing preparation.
- Weak trip-level cost and profit insight.
Business Model Direction¶
| Stage | Revenue direction |
|---|---|
| V1 | Installation and onboarding fees, telematics device sale or lease, company SaaS subscription, active vehicle/device fees, and premium support. |
| V2 | Safety module, cold-chain module, customer portal/collaboration module, and integration onboarding. |
| V3 | Fuel, energy, insurance, equipment, financing, settlement, and controlled marketplace services after operating density exists. |
Why The Operating Platform Comes First¶
MYConnect should build a data platform before building a marketplace. The defensible asset is trusted operational data across jobs, vehicles, drivers, customers, costs, and sensor events.
Once enough hauliers run real operations through the platform, MYConnect can expand into:
- Shipper visibility and collaboration.
- Cold-chain compliance reporting.
- Safety and driver coaching.
- Finance analytics.
- Insurance and equipment partner workflows.
- Controlled freight matching.
Partner Opportunities¶
| Partner type | Potential role |
|---|---|
| Hardware vendors | Device supply, installation kits, replacement workflow, warranty coordination. |
| Telcos and connectivity providers | SIM bundles, device data plans, managed connectivity. |
| Insurers | Safety data, fleet risk programs, claims support, referral programs. |
| Energy and fuel partners | Fuel offers, transaction records, settlement workflows. |
| Shippers and brokers | Customer visibility, transport status, POD access, future controlled freight workflows. |
Current Build Signal¶
The current local product proof shows the platform direction is not only slideware: admin, device, fleet, transport operations, driver POD, and customer portal slices already have local route/API evidence. The next investor-grade proof layer is production/staging deployment evidence, pilot usage, operational support readiness, and commercial adoption metrics.