A white-label customer engagement platform (2016–present)
The problem as it actually was
Automotive principals in Malaysia and Singapore needed owned engagement channels with their existing customers. They were renting attention through third-party publishers and had no relationship infrastructure of their own. The opportunity was real. The commercial model to deliver it didn't exist yet - bespoke development was too expensive for principals to commit to, and off-the-shelf platforms didn't fit the operational reality of regional automotive aftersales.
The architectural read
The conventional approach would have been bespoke development per client, paid upfront, with no shared architecture. I designed the opposite: a white-label modular platform where the core is shared across instances and the brand identity, content, and configuration are owned by the principal. Subscription model, no upfront development fees. The commercial structure wasn't a pricing decision - it was a trust and adoption decision. Principals would only commit to a customer engagement platform that could survive their internal procurement and risk processes, which meant the financial commitment had to be operational rather than capital.
What was built
A coordinated platform set on a shared core, deployed as six live instances:
- An aftersales-engagement instance (Malaysia) for the OEM
- A lifestyle-engagement instance (Singapore) for the OEM's national sales company
- A volume-brand instance (Singapore)
- A performance-brand instance (Singapore)
- A premium-brand instance (Malaysia) for the brand's official dealer group
- The parent group's aftersales-network instance (Malaysia)
Each instance is a full CRM and marketing-automation backend on the shared core: a single audience-targeting engine reused across banners, vouchers, and system messages; a trigger-driven lifecycle automation layer (birthday, registration, service-due, warranty); self-contained event-funnel mechanics; a fifteen-role access-control matrix; nightly back-office data integration; and system-wide audit trails - uniform across instances, with only brand identity, content, and master data varying. Six years of divergence across six instances, two countries, and multiple OEM brands, with zero codebase forks.
The leads-management system - a leads-management and sales-performance CRM built for the same principal, live on web and mobile across three dealerships, processing 4,000+ leads through a nine-view analytics surface with automated round-robin distribution and a three-state, audit-defensible consent model built for the principal's PDPA obligations. The principal's managing directors reviewed it directly and benchmarked it favourably against the OEM's official enterprise system - the inflection point for a multi-year contract.
The queue-management system - a seven-stage service-lane queue-management system on the same architectural logic, deployed across three branches, built as a unified, persona-gated component model (one detail component; editability role-gated across Call Centre, Reception, and Service Advisor), with redemption audit trails wired through to the platform.
The dealer trade-in platform - a used-car bidding and purchase workflow product built on the same shared architecture. Currently suspended pending client operational alignment and a V2.0 re-architecture. Covered in its own case study below.
Scale
Over 600,000 registered users across the platform, of whom over 100,000 are active. Over 200,000 vehicles under management across all instances. The largest instance is the premium-brand instance at over 95,000 registered users.
Outcome
Three-year renewals signed at flat pricing - clients valued the platform enough not to renegotiate down at contract end. The platform is currently scaling through the Singapore NSC as the central engagement infrastructure across multiple brands. The architectural decision to build modularly on a shared core has held up under six years of growth and divergence - none of the six instances has forked into a separate codebase.
Where this is heading
Positioned within the OEM principal's global IT governance such that the group's official infrastructure provider has moved from competitive threat to formally evaluating the platform for approved regional/global partner recognition - an enterprise-procurement audit the architecture was deliberately built to pass. The architecture was designed to survive hostile audits from global OEM IT functions: strict role separation, comprehensive audit logs, and modular data governance built into the foundation. It routinely passes compliance checks from principals' global IT functions who inherently prefer their own legacy stacks - it survives because replacing the localised integrated ecosystem with their fragmented global alternatives would break the client's ground operations. Currently driving toward first-ever external-partner integration access to the group's global customer database. Early-stage pathways into the UK and Ireland are being carried forward by relocating stakeholders from existing the Singapore NSC and the Malaysian NSC accounts - pre-initial contact only at this stage, not active engagements.
What this shows
Commercial architecture designed in service of operational reality. The product is the artifact; the business model is the architecture.