Operating Scope
Across twelve years at the Company, I have operated simultaneously across the following domains. None of these are claimed — each is backed by case studies in the following section.
Trusted Advisory & Stakeholder Trust. The relationship is the architecture. On the flagship OEM account I operate as a peer-level counterpart to the client's IT director, managing directors, marketing, and data-protection functions — the contact the principals reach for when the question is what is the right call here, not can you build this. The advisory extends past contracted scope: redlining the client's own agreements in their interest, proposing improvements to their internal data-handling governance, and being treated as a subject-matter partner rather than a supplier. Mentees and counterparts have stayed in close professional relationship years after the engagement; anchor clients have renewed across half-decades without renegotiating down. Trust is the delivery mechanism, not a by-product of it. Across my tenure I've worked at decision-maker level with more than ten OEM principals and major insurers — the OEM group, the premium brand, a volume brand, a performance brand, the OEM, the conglomerate, the parent group, a global insurer, a global insurer, Liberty, a major insurer, a takaful operator, and others. The advisory extends into authoring policy artefacts on the client's own side — a Data Retention Policy Proposal covering seven live storage locations across application databases, backups, cloud storage, editorial systems, telemetry, and app stores, grounded in PDPA and contractual obligations, with an operational disposal register and quarterly SOP for enforcement. Produced ahead of a client's internal audit at no additional cost.
Commercial Architecture. Pricing policy, discount governance, retainer structures, proposal sign-off, deal reshaping mid-flight, and the bridge between group legal and business reality. I write the first draft of most commercial agreements before legal sees them. When a client's IT function requested a platform-wide move to Windows infrastructure, I reframed the request from a migration into what it actually was — a full rebuild of four live production systems — quantified the continuity and cost risk, and proposed the Azure-on-Linux path that met the real centralisation goal without it. Pushback delivered as client protection, with the stakeholder handed the internal case to make. The commercial-governance layer is not improvised per deal — it is a documented, reusable instrument set I authored and maintain: the standard Master Service Agreement, rate cards and commitment-discount tiers, editorial and value-added-service content policies, a non-negotiables register tied to operational rationale, and counterparty-pushback decision trees. These now template the rest of the publisher business. Among these, the Premium & VAS Content Policies — the boundary between paid content and complimentary editorial that protects the publication's independence — were recently attached as Schedule 3 to the e-wallet operator framework agreement, becoming contractually binding on the counterparty. Operational mastery of Malaysian SST (Group G and Group I distinctions, inter-industry exemptions, foreign-services treatment), GST (pre-2018), and digital and withholding tax for cross-border digital services — self-taught through GST training and twelve years of operational tax handling, carried alongside the commercial work rather than handed off to accountants.
Product Architecture. Six live SaaS instances in production across two countries, on a shared platform I designed, serving over 600,000 registered users — over 100,000 of whom are active across more than 200,000 vehicles under management. The leads-management system, the queue-management system, and the dealer trade-in platform as adjacent products on the same architectural logic. Currently architecting a graph-native data core in parallel with a modular consumer product on top of it. The commercial logic underneath the architecture: a B2B SaaS book of recurring subscription revenue across multiple independent instances, with custom capability built for one client modularised into the shared core and resold as base capability to others. The IP compounds; the codebase doesn't fork.
Governance and Compliance. PDPA, data privacy, retainer scope governance, data integrity through investor diligence cycles, audit-readiness for enterprise procurement. Designed the consent and data-governance model for a live CRM under Singapore PDPA — a three-state consent architecture (consented / not consented / not recorded) feeding a blocked list, chosen over a single compulsory checkbox, with consent-capture language deliberately worded for evidentiary defensibility rather than tick-box compliance. Self-taught through operational necessity; I work alongside qualified counsel, not in place of them.
Analytics & Data Integrity. I run the analytics layer across the Company's publisher business and the SaaS platform — Google Analytics (UA-era certified, GA4 transition managed), event tracking architecture across the vehicle-database platform, the classifieds site and the app ecosystem, and the Looker Studio reporting infrastructure that abstracts platform changes from internal and client stakeholders. Monthly reports — internal to the Company leadership and external to OEM clients — run on dashboards I designed; they survived the UA to GA4 transition without breaking the reader experience because the integration layer absorbs the methodology shift underneath. When measurement discrepancies surface — including a the flagship publication methodology question raised during a group investor diligence cycle — the defence is structured, cross-validated against independent data sources, and auditable.
Operations and SOP. Company-wide SOP architecture covering commercial, product, and operational workflows — the operational source of truth across the business, including internal policies, approvals, risk controls, QC standards, and escalation frameworks. The commercial-document ecosystem underneath the agreements — Quotations, Inventory Orders, Master IOs, Campaign IOs, in variants for direct clients, agency bookings, and advertising-wallet draws — was authored and codified by me across a decade of practice. The sales enablement layer above them — company profile deck, the Company's automotive ad network profile and rate card decks, the base decks the sales team now derives every client proposal from — is also mine. The pattern extends into the operational layer: HR onboarding workflows, office equipment and software request processes, procurement scaffolding. Most of these emerged because they weren't being built by anyone else and the operation needed them. Over time, "the person who codifies the way we do this" became a role I ended up holding by default across the company, whether or not it was named.
Digital Advertising and Ad Operations. I run the digital advertising business that pays for the rest of the Company — pricing architecture, package design, ad operations, traffic and reporting integrity, and the codified policies the team and clients work to. The business serves an automotive publisher network reaching 4–5 million unique users monthly (the flagship publication as the anchor, plus the vehicle-database platform, the classifieds site, and Tintnow.my). When I took over ad sales and operations from a third-party agency in 2014, I had no prior experience with digital advertising; the system that now runs the business — packaging logic, contextual targeting on the flagship publication, frequency capping, package-over-SOV pricing, the editorial and Value-Added-Service content policies, the agreements framework — is what I built from that starting point. Self-taught end to end.
People Architecture. Lead a digital and product team of seven (four developers, two designers, and the QC and project executive working under me) and a business development team of three sales managers and an ad operations executive, alongside the company's senior data analyst. When multi-region expansion threatened to bottleneck around my own capacity, I restructured the digital division into distinct Run and Build tracks — isolating legacy maintenance to junior developers to protect the technical lead's architecture time, pivoting support staff into dedicated client-facing operational roles, and hiring specifically for meticulous quality-control apprentices to offload logic-checking and QA burdens from the lead and from me. Built a succession bench: a senior project executive emerged as de facto deputy across digital and ops, a second executive in deliberate training toward a parallel lead role, and a technical lead operating as a trusted execution partner converting business logic into system architecture. The stated team goal is self-sufficiency: the operation should not depend on any single person being in the room. I build teams that protect the architecture so the architecture can protect the business.