One process is stuck?
Review one process for RM350. See where work repeats, waits or gets lost before paying for a larger build.
I need a workflow review →I build production software and review the workflows around it.
Choose the path that fits you · Penang + remote
WhatsApp → spreadsheet → retype → chase the latest version
One clear owner → checked hand-off → visible status
Review one process for RM350. See where work repeats, waits or gets lost before paying for a larger build.
I need a workflow review →See production ERP, full-stack, AI-enabled systems and testing proof before downloading the ATS resume.
I’m hiring a senior engineer →
I work with teams whose daily work has outgrown spreadsheets, WhatsApp and disconnected tools. The first question is not which technology to buy. It is where the work gets copied, delayed, checked twice or lost between people.
I start small: map one workflow, make the next decision visible and define a fix that can be tested. If the problem does not justify a larger build, I will say so before you spend on one.
My rule is simple: if it does not work for real people, it does not ship. That standard comes from enterprise operations software, public C#/.NET work and CHRONO, a free mod with 526 automated tests.
Public-safe proof of the way I work: understand the operation, choose the smallest useful slice and leave evidence behind.
Full-scale ERP replacing SAP/Navision. Supply chain, finance, HR, procurement, and refinery operations — database to frontend to deployment. Production software for a confidential refinery client.
Proof: Public-safe architecture outline showing the ERP core and operational modules.
Read the ERP case study →SaaS platform for engineering teams — projects, delivery standards, and people in one system. Built on the same standards I use to ship.
Proof: Architecture and implementation case study; public demo paused until a stable route is available.
Evidence: architecture and implementation case study available. Public demo paused until a stable, owner-verified route is available.
ML forex decision-support system. My own backtest lied to me for two weeks — I audited it, published the leak, and rebuilt. Honest numbers only.
Proof: An auditable ML pipeline with calibrated probabilities, risk gates and no-lookahead discipline.
Commission platform for the licensed money-lending industry: configurable rules, tier ladders, offline sync, and three role portals.
Evidence: multi-tenant architecture, commission rules and role-based workflow case study. Live demo paused until a stable, owner-verified route is available.
A small, public-safe simulation of a common operational bottleneck: moving spreadsheet rows into a web form without losing validation, traceability or safe restart behaviour.
Proof: synthetic rows, field validation, duplicate detection, interruption recovery and a readable progress log.
See the workflow evidence demo →Malay-first community marketplace proof slice: browse listings, register and log in, then post a listing through a Nuxt API backed by local SQLite.
Evidence: Nuxt API, SQLite persistence, authentication and listing workflow demonstrated locally; public route paused until stable hosting is verified.
Stateless Stremio add-on for Malay, Bollywood, and Asian discovery — 22 live catalogs powered by TMDB metadata, with streaming left to the user's configured providers.
Evidence: stateless catalog add-on architecture and TMDB metadata workflow; public manifest paused until stable hosting is verified.
Free open-source GTA V mod where powers leave a paper trail: witnesses, news reports, notoriety, and a police force that remembers your face. 526 automated tests.
🔗 Proof: Open the CHRONO page and download →
A personal AI that remembers: 125,000+ documents, semantic search, knowledge graphs. My memory has limits — my knowledge shouldn't.
Ongoing private/local engineering project with replaceable model routing, document retrieval, typed capability boundaries and redacted review. Built for private use; no public demo.
Digital products from real work: an AI prompt engineering handbook and a habit builder workbook, live on Gumroad.
🛍️ Storefront: Browse Craftlancer products
We walk through one real process and mark the repeated entry, waiting, checking and hand-off points.
You receive a prioritised next slice with clear assumptions, boundaries and acceptance questions.
When the next step is approved, we build only the agreed slice and check that it behaves as expected.
You receive the scope, verification notes and handover context needed to understand what happens next.
When my own ML backtest produced attractive results, I audited it, found the leak and documented the failure. That standard carries into every system I build.
Bring one process that feels slow or hard to trust. I map the hand-offs, show what repeats or gets lost, and give you a written next step.
You receive: workflow map, friction notes, prioritised next slice and follow-up review. Production implementation is quoted separately.
Describe the workflow →After the review: one dashboard, report, hand-off, validation step, API connection or internal tool with a written boundary.
A practical review of an existing system or quote: what is unclear, what could fail and what should be decided before more money is committed.
Frontend
Backend
Database
AI & ML
DevOps
If work is slow, repeated or hard to trust, describe what happens today. Hiring for senior software and business-systems work? The engineering proof and resume are below.
💬 Describe the workflow