Senior Solution Architect / Full Stack Developer

Systems that stay legible

I design and ship the whole thing — the domain model, the platform underneath it, and the screens people actually use. Eight systems in production, five of them inside Malaysian government bodies.

Based: Kuala Lumpur, Malaysia
Local: --:--
Focus: Platform architecture

Meta verified tech provider◇ WhatsApp Business Platform◇ Multi-tenant SaaS◇ LLM orchestration◇ Event-driven design◇ Role-based access control◇ Approval workflows◇ Audit trails◇ Meta verified tech provider◇ WhatsApp Business Platform◇ Multi-tenant SaaS◇ LLM orchestration◇ Event-driven design◇ Role-based access control◇ Approval workflows◇ Audit trails◇

8Systems in production
5Built for government
6+Years in the field

Most systems do not fail because the code is wrong. They fail because nobody can hold the whole thing in their head anymore. I spend my days on the opposite problem — drawing the lines that keep a platform explainable on a whiteboard in under five minutes.

What I actually do

Sit between the business question and the runtime. Turn a requirements document into a domain model, a permission model and a deployment story — then build it, because an architect who does not ship loses the plot.

How I work

Diagram first, prototype second, document as I go. Boring technology chosen on purpose. Every non-obvious decision gets a written record so the next person inherits reasoning instead of archaeology.

Where I am strongest

I came up through digital forensics and penetration testing before I designed systems, so I start from the failure case and the attacker. Government work that has to survive an auditor is the same instinct pointed at paperwork.

From requirement
to commissioning

Every system on this page went through the same six stages. The order is not negotiable, and the fifth one is where most projects find out what they got wrong. Scroll to walk it.

01 Agree what it must do, in writing
02 Decide the shape before the code
03 Build it, and stay in the codebase
04 Meet the systems already in place
05 Let real users try to break it
06 Hand it over and stay on the hook

Products I
built and run

Eight. Five of them for Malaysian government bodies.

Delegate accreditation · ASEAN Malaysia 2025, Ministry of Finance

ASEAN 2025

The accreditation system behind Malaysia's ASEAN 2025 chairmanship — every delegate from every member state registered, vetted, badged, and cleared into the right room.

The problem

A chairmanship year runs dozens of meetings across ten member states and their partners. Each delegation registers its own people, and no country may see another's list. Every delegate needs vetting, a printed pass with a compliant photo, and access to exactly the events they are entitled to attend. Get it wrong and a head of delegation is standing outside a closed door.

What I built

Country-scoped accreditation, so each Delegation Accreditation Officer manages only their own delegation and never sees another. A registered, vetted, carded pipeline behind it. Pass printing gated on photo validation, per-delegate flight and hotel records, and event-level entitlement driving who gets through which door. I ran it as appointed Project Manager and the technical bridge between the Ministry, the accreditation officers and the development team.

Per countrydelegations isolated by design
3 stagesregistered, vetted, carded
Event-levelentitlement to access

Accreditation
Access control
Multi-tenant
Badge printing
Requirements engineering
Public sector

Government engagement — walkthrough on request

The ASEAN 2025 event management and access control system

National estate management · RISDA

RisEstet

The system Malaysia's rubber smallholder authority uses to register participating estates, inspect them, rate them, and pay out quarterly claims — across every state.

The problem

Every participating estate carries a registration number, a planted hectarage, an inspection history, and a claim ledger. Spread across spreadsheets, none of that reconciles — and a federal allocation has to balance against every ringgit paid out.

What I built

One record per estate carrying registration, category, state and planted area. An inspection workflow that feeds an estate rating. A quarterly claim cycle running submission through review, approval and payment. A per-estate ledger, and a national dashboard with geographic distribution.

149estates under management
Quarterlyclaim and payment cycle
Nationalevery state, one dashboard

Laravel
PHP
PostgreSQL
Claims & ledger
Geospatial
Bahasa Melayu

risestet.risda.gov.my

The RisEstet national dashboard showing estate distribution across Malaysia

Cashless payments · RISDA Smallholder Rubber Market

e-SRM

The cashless payment and incentive module for RISDA's Smallholder Rubber Market — the part that actually pays rubber smallholders for what they sell.

The problem

Paying smallholders for rubber sold means eligibility checks, sale records, incentive rules and a payment run that reconciles exactly. Cash and paper vouchers do not scale, and every ringgit has to trace back to a specific sale and a specific person.

What I built

The backend behind sales, eligibility, incentive calculation and the payment run, plus the integrations moving data between e-SRM and the platforms around it. I ran this one as Project Manager and DevOps while writing the backend, which keeps the schedule honest.

Cashlesspayment and incentive runs
Traceableevery payment to a sale
Integrateddata exchange across platforms

Laravel
PHP
PostgreSQL
REST APIs
Payments
Public sector

Government engagement — walkthrough on request

The e-SRM cashless payment and incentive module

WhatsApp business platform · Meta verified tech provider

HyperChat

A multi-tenant platform that lets a business run its entire WhatsApp presence — AI assistants, broadcast campaigns, and human agents — out of one inbox.

The problem

The WhatsApp Business API gives you a webhook and a send endpoint. Everything a real business needs — template approval, campaign throttling, conversation ownership, an audit trail — you build yourself, correctly, or Meta suspends the number.

What I built

Flowmaker, a visual builder where non-engineers wire up events, branches, LLM calls and API steps on a canvas. Behind it, a versioned flow engine, an AI layer with intent detection and guardrails, and a shared agent inbox with clean human handover.

Flowmakervisual flow builder
Multi-tenantorg-scoped isolation
LLMintent, reply, guardrails

WhatsApp Cloud API
Laravel
React Flow
LLM orchestration
Webhooks
Multi-tenant

ai.hyperchat.bot

The HyperChat conversation inbox and visual flow builder

Internal operations platform · VFive Group Sdn Bhd

VFive Group

The internal platform my own company runs on — eight modules covering everything a staff member needs to book, declare, or report, behind one dashboard.

The problem

Company operations sprawl into whatever tool is nearest — a spreadsheet for vehicles, a chat thread for meeting rooms, an email for a declaration. None of it is auditable, and nobody can tell you which car is free on Thursday or whether it is due for service.

What I built

One dashboard over eight modules: vehicle logistics, meeting rooms, employee management, general meetings, declarations, whistleblowing, and 5S. The fleet booking carries live mileage and next-service dates, so a car that is due for maintenance stops being bookable.

8modules, one dashboard
Fleetmileage and service aware
Approvalsevery booking on record

Laravel
MySQL
Tailwind CSS
Asset booking
Approval workflow
Compliance

Internal — walkthrough on request

The VFive Group module dashboard and vehicle booking screen

Event registration · SELBIZ, PKNS

SELBIZ 2024

The registration platform for Selangor's state entrepreneur expo — three separate audiences through one intake, each walking away with a scannable credential.

The problem

A three-day expo registers visitors, exhibitors and run participants through completely different forms, then has to get all of them through the door without a queue. An exhibitor carries company registration, trade category and membership status. A visitor just needs to get in.

What I built

A single intake that branches by registration type, an exhibitor form that validates company registration and trade category against the categories the organiser actually uses, and a QR credential issued on screen and emailed — so the door team scans instead of searching a list.

3 tracksvisitor, exhibitor, run
QRissued on screen and emailed
Publicopen registration at expo scale

Laravel
MySQL
QR credentials
Email delivery
Registration flows
Bahasa Melayu

selbiz.my

The SELBIZ 2024 registration type selection and exhibitor form

Grant management · Sabah Parks (LPATTS)

Geran LPATTS

A grant management system for a state statutory body, carrying a public grant from the day it is published to the day the money leaves the account.

The problem

Public money answers to an auditor. Every application needs a reviewable history, applicant organisations must be verified against their official registration, and the annual allocation has to reconcile to the ringgit at any moment someone asks.

What I built

A full grant lifecycle — published calls with categories, deadlines and allocations; applicant profiles gated on registration checks; a staged review, approval and payment workflow; and a live allocation ledger showing committed against remaining budget. Entirely in Bahasa Melayu.

5 stagessubmit to disbursement
ROS / SSMorganisation verification
Ledgerallocation reconciled live

Laravel
PostgreSQL
Tailwind CSS
Workflow engine
Audit trail
Bahasa Melayu

systemsandbox.cloud

The Geran LPATTS grant dashboard and grant listing

Fleet & retail operations · TGA Craftworks

TGA Fleet

An operations system for an automotive detailing business serving two very different customers — corporate fleets on credit terms, and walk-in retail — from one booking engine.

The problem

Fleet and retail look like the same booking on the surface and behave nothing alike underneath. Fleet runs on credit balances, approvals and vehicle registers. Retail is pay-and-go. One codebase had to serve both without collapsing into conditionals.

What I built

A shared booking core with two pricing paths, a permission model spanning eight roles from ground staff to superadmin, credit tracking that warns before a fleet client runs dry, and an audit log covering every state change a booking passes through.

8roles, one permission model
2pricing paths, one core
Auditevery booking state change

Laravel
MySQL
RBAC
Billing & credit
Audit logging
Reporting

fleet.tgas.my

The TGA Fleet operations dashboard and bookings table

The path

2024 — Now

Senior Solution Architect / Full Stack Developer

VFive Group Sdn Bhd

Architecture, development and delivery of government and enterprise systems, and appointed project manager on the ministry engagements. Three federal projects run out of this seat: ASEAN 2025 for the Ministry of Finance, RISESTET and e-SRM for RISDA.
2023 — 2024

Senior IT Executive

BJAQ Group Sdn Bhd

Led technology for the MyLAH learning platform. Built its WhatsApp chatbot, integrated AI into the learning experience, and put the payment gateway in. The WhatsApp work here is what HyperChat later grew out of.
2022 — 2023

IT Executive / Assistant Technical Lead

Irich Beta Sdn Bhd

Assistant technical lead on an election sentiment analysis programme. Led a team of system analysts and built the dashboards that turned very large, very messy datasets into something a decision maker could read in a meeting.
2021 — 2022

IT Analyst

Fahbrim Technology Sdn Bhd

Digital forensics and penetration testing. Mobile device examination and data extraction for authorised investigations, vulnerability research, and open-source intelligence. Delivered forensics training to Royal Malaysian Customs personnel.
2019 — 2021

IT Executive

Nbit Technology Sdn Bhd

Administered Zoho human resources, finance and CRM systems. Designed the company network architecture including link bonding, and led an infrastructure build for a client in Terengganu.