I'm a process engineer and project leader, not a software vendor.

6 years
Process & equipment engineering at Intel
ESCP Paris
MSc International Project Management
PMP
Certified Project Management Professional
Multiple countries
Operational deployments at CityTaps
RM 3M+
Value of operational systems built at CityTaps
1 rule
Diagnose before you build
Before AtriumX, I spent nearly six years at Intel as a process and equipment engineer, diagnosing production constraints, mapping failure modes, and building systems that worked under pressure. Then I made a deliberate bet: I left a stable engineering career to pursue an MSc in International Project Management at ESCP Business School in Paris, one of Europe's top business schools, graduating with distinction. I'm also a certified Project Management Professional (PMP) through PMI. That combination of deep technical rigour, formal project management discipline, and real-world operational leadership is what I bring to every engagement.
From Paris, I joined CityTaps, a venture-backed water technology company, where I led supply chain and operations for field deployments across multiple countries in Africa and Asia.
At CityTaps, I built a full operational platform — meter deployment tracking, contractor performance monitoring, end-user data collection, and real-time quality dashboards — using zero external vendors. When vendors were quoting €50,000+ for similar solutions, we built it ourselves and it actually worked for the people using it daily. That experience shaped everything: find the real constraint, build the simplest system that solves it, and make sure the people using it can actually use it.
I started AtriumX to bring that same thinking home. Malaysian SMEs are running operations that deserve better systems — but most automation services are either too expensive, too generic, or built by people who've never had to make something work in a messy, real-world environment. I have. And I work directly with every client — no sales team, no junior consultants, no handoffs.
How I work — five principles
Diagnose before you build
The audit comes first. I map how your operation actually runs before recommending anything. Most automation fails because it solves the wrong problem.
Systems over features
I build connected operations systems, not isolated automations. A dashboard without workflow automation behind it is just a prettier spreadsheet.
The tool follows the problem
I select tools based on your setup, your team's comfort, and what will actually get used. The technology is never the starting point.
Measure everything
If a system doesn't save time, reduce errors, or improve revenue, I won't build it. Every engagement is tied to outcomes you can track.
Stay in the building
I'm accountable for the system working, not just delivering it. Most clients keep me on retainer because systems need to evolve as the business grows.
Let's build your operating system.
Start with a free Operations Audit and see where the real opportunities are.
Book Your Free Audit